Search Results xtr_ig_journal_structures_u1




Overview

XTR_IG_JOURNAL_STRUCTURES is a Treasury (ETRM) configuration table owned by the XTR schema. It stores the intercompany (IG) journal structures that govern how cash flows between a company and its subsidiaries and other Intercompany counterparties are posted to the General Ledger. Specifically, the table defines, for a given company/counterparty pair within a currency and counterparty account context, which GL account code combinations should be used for principal cash flows and for interest cash flows. This makes the table a central reference for automated intercompany journal creation, cash pooling, and in-house bank settlements, where consistent account derivation is required across transactions.

In Oracle EBS 12.1.1 and 12.2.2, the object retains the same structure; the only difference of note is that 12.2.2 online patching requires the editioning view (XTR_IG_JOURNAL_STRUCTURES#) and the corresponding synonym to be used in custom code rather than referencing the base table directly. The table resides in the APPS_TS_TX_DATA tablespace, with its unique index in APPS_TS_TX_IDX. From a Data Vault modeling perspective, the mined relationship data suggests this object is satellite-leaning: the natural business key (company, counterparty, currency, counterparty account) identifies a reference context, while attributes such as the principal and interest GL account identifiers describe that context and may change over time.

Key Information Stored

The table is defined by a surrogate primary key and a four-column business key, with several descriptive attributes that drive GL account derivation.

Common Use Cases and Queries

Typical use cases include validating that an IG journal structure exists before an intercompany settlement is processed, reporting on the GL accounts configured for principal and interest flows, and auditing configuration changes through the WHO columns. A common query joins the table to the bank account uses entity to resolve the counterparty account context:

  • SELECT j.COMPANY_CODE, j.CPARTY_CODE, j.CP_CURRENCY, j.PRINCIPAL_GL, j.INTEREST_GL FROM XTR_IG_JOURNAL_STRUCTURES j WHERE j.COMPANY_CODE = :company AND j.CPARTY_CODE = :cparty;
  • SELECT j.*, u.BANK_ACCOUNT_ID FROM XTR_IG_JOURNAL_STRUCTURES j, CE_BANK_ACCT_USES_ALL u WHERE j.CPARTY_ACCT_USE_ID = u.ACCT_USE_ID;

For existence checks prior to journal generation, the U1 index columns should be used in the WHERE clause to ensure index-driven access. Reporting solutions frequently extract the full column list for reconciliation against GL code combinations.

Related Objects

The table has one documented foreign key dependency and is referenced by an editioning view in 12.2.2.

  • CE_BANK_ACCT_USES_ALL – referenced via XTR_IG_JOURNAL_STRUCTURES.CPARTY_ACCT_USE_ID → CE_BANK_ACCT_USES_ALL.ACCT_USE_ID; provides the counterparty bank account usage context.
  • XTR_IG_JOURNAL_STRUCTURES# – the editioning view over the base table in 12.2.2; custom code should query this view.
  • GL_CODE_COMBINATIONS – resolves the PRINCIPAL_GL and INTEREST_GL numeric identifiers to account segments.
  • XTR_COMPANIES / company entities – provide descriptions for COMPANY_CODE and CPARTY_CODE.
  • FND_CURRENCIES – resolves CP_CURRENCY to a currency description.