Results for “party_code”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

XTR_COMPANY_AUTHORITIES is a Treasury (XTR) module table in Oracle E-Business Suite 12.1.1 and 12.2.2 that stores the user access authorities granted to companies within the Treasury application. The table defines which dealers are authorized to act on behalf of specific parties (companies), thereby controlling input permissions across Treasury transactions. The object resides in the XTR schema and is documented as VALID in the ETRM metadata.

From a data modeling perspective, the heuristic Data Vault classification mined from the foreign key structure identifies this object as a link — a junction that resolves a many-to-many relationship between two hub-like entities: dealers (XTR_DEALER_CODES) and parties (XTR_PARTY_INFO). This classification is a modeling suggestion rather than a documented DBA characteristic, but it accurately reflects the table's role as an associative relationship carrier.

Key Information Stored

The table is deliberately narrow, containing only three documented columns. The most important columns and their roles are as follows:

• DEALER_CODE — Identifies the dealer or user account to which authority is granted. This column forms part of both the primary key and the unique business-key index, and carries a foreign key reference to XTR_DEALER_CODES.
• PARTY_CODE — Identifies the company (party) for which the dealer holds authority. Like DEALER_CODE, it participates in the primary key, the unique index, and a foreign key to XTR_PARTY_INFO.
• COMPANY_AUTHORISED_FOR_INPUT — A flag or attribute indicating whether the dealer is authorized to perform input operations for the specified company. This is the effective payload of the relationship.

The surrogate primary key is defined by the constraint XTR_COMPANY_AUTHORITIES_PK, composed of (DEALER_CODE, PARTY_CODE). A separate unique index, XTR_COMPANY_AUTHORITIES_U1, exists on (PARTY_CODE, DEALER_CODE) — the reverse column ordering of the primary key — serving as a business-key candidate that enforces the same uniqueness constraint while supporting alternate access paths. Because both columns are part of the primary key, there is no non-key surrogate identifier; the key is wholly natural and composite.

Common Use Cases and Queries

Treasury administrators and developers use this table to determine whether a given dealer may enter or modify transactions for a company. Typical scenarios include security audits, authorization reports, and validation logic embedded in Treasury forms and concurrent programs.

A common query retrieves all companies for which a specific dealer is authorized:

SELECT party_code FROM xtr_company_authorities WHERE dealer_code = :dealer_code AND company_authorised_for_input = 'Y';

Conversely, to list all dealers authorized for a company:

SELECT dealer_code FROM xtr_company_authorities WHERE party_code = :party_code;

Reporting use cases include a join to XTR_DEALER_CODES and XTR_PARTY_INFO to resolve codes into descriptive names for an authorization matrix report. Because the unique index XTR_COMPANY_AUTHORITIES_U1 leads with PARTY_CODE, queries filtering on party are efficiently served, while those filtering on dealer benefit from the primary key ordering.

Related Objects

The following objects are the most significant references and dependencies for XTR_COMPANY_AUTHORITIES:

• XTR_DEALER_CODES — Referenced via the foreign key XTR_COMPANY_AUTHORITIES.DEALER_CODE; supplies dealer definitions.
• XTR_PARTY_INFO — Referenced via the foreign key XTR_COMPANY_AUTHORITIES.PARTY_CODE; supplies company/party details.
• XTR_COMPANY_AUTHORITIES_PK — The composite primary key constraint on (DEALER_CODE, PARTY_CODE).
• XTR_COMPANY_AUTHORITIES_U1 — The unique index on (PARTY_CODE, DEALER_CODE), providing an alternate business-key access path.

Together these objects form the authorization backbone that governs dealer-level input rights across Treasury, and any modification to this link table directly affects user access within the module.