Results for “cp_bank_code”
18 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
XTR_IG_JOURNAL_STRUCTURES_V is an APPS-owned database view in the Oracle E-Business Suite Treasury (XTR) module. It is a denormalized, presentation-oriented view defined over the XTR_IG_JOURNAL_STRUCTURES table, which stores the journal structure setups used by Treasury for interest and general ledger accounting of intercompany or counterparty-related transactions. The view consolidates journal structure configuration with descriptive attributes sourced from the bank account and party tables, so that reports, concurrent programs, and integration interfaces can retrieve a complete accounting-relevant record without performing multiple joins themselves.
The view is documented in ETRM metadata as VALID in both Oracle EBS 12.1.1 and 12.2.2, and its use is limited to read access; it does not support DML. Its role is primarily reporting and inquiry: it exposes the counterparty bank code, counterparty name, and the GL account values that drive downstream accounting entries, while preserving the row identity and audit columns of the base journal structure record. This makes it the natural query surface for users investigating how a given counterparty account is mapped into Treasury accounting.
Underlying Base Objects
The view is defined over three base objects, all referenced through APPS synonyms:
- XTR_IG_JOURNAL_STRUCTURES — the driving table, storing journal structure identifiers, company and counterparty codes, principal and interest GL accounts, counterparty currency and account number, and audit columns. It is aliased IG in the view text.
- XTR_BANK_ACCOUNTS — the Treasury bank account definition, aliased BA. It supplies BANK_CODE, BANK_SHORT_CODE, and the AUTHORISED flag, and provides the join keys PARTY_CODE, CURRENCY, and ACCOUNT_NUMBER.
- XTR_PARTY_INFO — the party master, aliased PTY, which supplies the counterparty descriptive name (FULL_NAME) via the shared PARTY_CODE.
Joins are enforced on CPARTY_CODE to PARTY_CODE across both bank accounts and party info, and on CP_CURRENCY to CURRENCY and CP_ACCT_NO to ACCOUNT_NUMBER against the bank account. Because the joins are inner joins, a journal structure row surfaces only when a matching authorized-or-not bank account and party record exist.
Key Columns
- ROW_ID — the ROWID of the underlying journal structure row, used for direct row addressing.
- XTR_IG_JOURNAL_STRUCTURE_ID — the primary key of the journal structure.
- COMPANY_CODE — the Treasury company that owns the journal structure.
- CPARTY_CODE / CPARTY_NAME — the counterparty code and its resolved full name from XTR_PARTY_INFO.
- CP_BANK_CODE — the counterparty bank code, computed as NVL(BA.BANK_CODE, BA.BANK_SHORT_CODE), so a short code is shown when the full bank code is not maintained. This is the column returned when users search for "cp_bank_code".
- CP_CURRENCY / CP_ACCT_NO — the counterparty currency and bank account number used in the bank account join.
- PRINCIPAL_GL / INTEREST_GL — the GL accounts applied to principal and interest postings.
- AUTHORIZED — the authorization flag of the bank account (aliased from BA.AUTHORISED).
- CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard audit columns propagated from the base table.
Common Use Cases and Queries
Typical use is validating journal structure setup ahead of accounting generation, reconciling counterparty bank codes against bank account master data, and driving custom reports. The search term "cp_bank_code" corresponds directly to a view column, so queries filtering on it are straightforward:
- List all journal structures and their resolved bank codes for a company:
SELECT company_code, cparty_code, cparty_name, cp_bank_code, cp_currency, cp_acct_no FROM apps.xtr_ig_journal_structures_v WHERE company_code = :company; - Find structures referencing a specific counterparty bank code:
SELECT xtr_ig_journal_structure_id, cparty_name, cp_bank_code FROM apps.xtr_ig_journal_structures_v WHERE cp_bank_code = :cp_bank_code; - Review GL mappings for a counterparty account:
SELECT cparty_code, principal_gl, interest_gl FROM apps.xtr_ig_journal_structures_v WHERE cp_acct_no = :account AND cp_currency = :currency;
Because CP_BANK_CODE is derived with NVL, filtering on it returns the short code where the primary bank code is null, a behavior worth noting during reconciliation. All queries should be run against the APPS schema with appropriate Treasury responsibility access.
-
View for XTR_IG_JOURNAL_STRUCTURES table.
APPS.XTR_IG_JOURNAL_STRUCTURES_V·↳ XTR_BANK_ACCOUNTS·↳ XTR_IG_JOURNAL_STRUCTURES·↳ XTR_PARTY_INFO·Explore XTR module →
-
View: XTR_SWIFT_EFT_V 12.2.2
A public view for Treasury payments.
APPS.XTR_SWIFT_EFT_V·↳ XTR_BANK_ACCOUNTS·↳ XTR_PARTIES_V·↳ XTR_SETTLEMENT_SUMMARY·Explore XTR module →
-
View for XTR_IG_JOURNAL_STRUCTURES table.
APPS.XTR_IG_JOURNAL_STRUCTURES_V·↳ XTR_BANK_ACCOUNTS·↳ XTR_IG_JOURNAL_STRUCTURES·↳ XTR_PARTY_INFO·Explore XTR module →
-
View: XTR_SWIFT_EFT_V 12.1.1
A public view for Treasury payments.
APPS.XTR_SWIFT_EFT_V·↳ XTR_BANK_ACCOUNTS·↳ XTR_PARTIES_V·↳ XTR_SETTLEMENT_SUMMARY·Explore XTR module →
-
VIEW: APPS.XTR_SWIFT_EFT_V 12.2.2
-
VIEW: APPS.XTR_SWIFT_EFT_V 12.1.1
-
VIEW: APPS.XTR_SWIFT_EFT_V 12.2.2
-
VIEW: APPS.XTR_SWIFT_EFT_V 12.1.1
-
eTRM - XTR Tables and Views 12.2.2
Created on 29-OCT-96
-
eTRM - XTR Tables and Views 12.1.1
Created on 29-OCT-96