Results for “confo_group_code”

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

Overview

XTR_A_PARTY_INFO_V is an Oracle E-Business Suite views residing in the APPS schema under the XTR (Treasury) product. It exposes a flat, denormalized projection of counterparty and party master data used throughout Oracle Treasury for deal capture, settlement, risk aggregation, and reporting. The view is documented as VALID in ETRM 12.1.1 and 12.2.2, and it is intended for read-only access by Treasury forms, concurrent programs, and external integrations that require party attributes without navigating the full normalized party model.

For users searching on the column suspense_ccid, this view is significant because it surfaces the suspense account Code Combination Identifier directly at the party level. That column allows Treasury settlements and accounting events to resolve a default suspense account when a party's primary settlement instructions cannot be determined, making the view a convenient single source for party-to-account mapping queries.

Underlying Base Objects

The documented dependency of XTR_A_PARTY_INFO_V is a single referenced base object: the synonym XTR_A_PARTY_INFO, which resolves to the underlying Treasury party information table in the APPS schema. The view is a straightforward SELECT list over that object with no documented joins, aggregations, or filters — every row in the base table is exposed, and every column listed in the view text maps one-to-one to a column in XTR_A_PARTY_INFO.

Because the view is defined over a synonym rather than a physical table directly, the object resolution depends on standard APPS synonym configuration. This is consistent with Oracle's practice of insulating custom and reporting SQL from physical table reorganizations across 12.1.1 and 12.2.2 upgrades. No editioning or materialized-view behavior is documented; the view is an ordinary relational view.

Key Columns

The view exposes approximately seventy columns. The most operationally relevant include:

• PARTY_CODE, PARTY_TYPE, SHORT_NAME, FULL_NAME — core party identification and classification attributes.
• SUSPENSE_CCID — the suspense account code combination identifier associated with the party; used in settlement and accounting defaulting logic.
• SET_OF_BOOKS_ID, CHART_OF_ACCOUNTS_ID — the ledger and chart of accounts context in which the party's account references, including SUSPENSE_CCID, are valid.
• LEGAL_ENTITY_ID — links the party to a legal entity for regulatory and consolidation reporting.
• RISK_PARTY, FX_CPARTY, MM_CPARTY, BROKER — role flags identifying the party's function in FX, money market, and brokerage transactions.
• CONVERSION_TYPE — default conversion type applied to the party.
• AUTHORISED, ACCOUNT_STATUS, AUDIT_INDICATOR, AUDIT_DATE_STORED — status and audit controls governing whether the party may transact.
• SWIFT_ID, FX_MATCH_ID, CONFO_GROUP_CODE, CONFO_ACTION_CODE — messaging and confirmation routing attributes.
• DEFAULT_COMPANY, DEFAULT_ADDRESS_DETAILS, ADDRESS_1..ADDRESS_6, EMAIL_ADDRESS — default remittance and contact information.

Common Use Cases and Queries

Typical uses include validating that a counterparty has a suspense account before settlement processing, reconciling party-level account defaults across ledgers, and feeding counterparty extracts into risk or credit systems. A representative query retrieving suspense account assignments is:

• SELECT party_code, full_name, set_of_books_id, chart_of_accounts_id, suspense_ccid FROM apps.xtr_a_party_info_v WHERE suspense_ccid IS NOT NULL;
• SELECT party_code, party_type, risk_party, fx_cparty, mm_cparty FROM apps.xtr_a_party_info_v WHERE authorised = 'Y' AND account_status = 'ACTIVE';
• SELECT p.party_code, p.full_name, g.name FROM apps.xtr_a_party_info_v p, apps.gl_code_combinations g WHERE p.suspense_ccid = g.code_combination_id;

Because the view performs no filtering, consumers should always apply their own WHERE predicates and, where possible, join SUSPENSE_CCID to GL_CODE_COMBINATIONS to resolve the account string for reporting.