Results for “stream_id”

1 result




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

Overview

The IEX_PRD_OKL_XREF table is a Collections module (IEX) cross-reference table that stores the association between payment promises recorded in Oracle Advanced Collections and the consolidated invoices to which those promises apply. Its role in Oracle EBS 12.1.1 and 12.2.2 is to preserve the many-to-many linkage between a promise (tracked at the detail level in IEX_PROMISE_DETAILS) and a consolidated invoice identified by CNSLD_INVOICE_ID. When a collector records a customer commitment to pay, the promise may cover multiple invoices and a single consolidated invoice may be covered by multiple promises; this table resolves those relationships so that the application can report, age, and reconcile promise-to-pay data correctly against receivables balances.

The metadata classifies this object, under a heuristic Data Vault analysis, as standalone. Since the table is a pure intersection object rather than a transaction or master record, a modelling exercise would more naturally treat it as a link table bridging the promise-detail hub and the consolidated-invoice entity. The heuristic standalone label reflects that the documented FK graph shows only a security group reference plus the promise detail reference, without a formalized hub-and-satellite decomposition. In practice, the table carries descriptive payload columns in addition to its key columns, so it functions as a link with attached satellite attributes.

Key Information Stored

The table is defined in the IEX schema and contains 16 documented columns. The most significant of these are:

Note that only one unique index beyond the primary key is documented, and it repeats the PRD_OKL_XREF_ID column, indicating that no alternate natural business key is enforced by a unique constraint in the shipped 12.2.2 schema.

Common Use Cases and Queries

Typical usage is reporting on promise coverage of consolidated invoices, either for collections dashboards or for reconciliation against AR. A representative query joining the cross reference to its parent promise detail is:

  • List all consolidated invoices covered by a given promise: SELECT x.CNSLD_INVOICE_ID FROM IEX_PRD_OKL_XREF x WHERE x.PROMISE_DETAIL_ID = :promise_detail_id;
  • Trace a consolidated invoice back to its promises: SELECT x.PROMISE_DETAIL_ID, x.CONTRACT_ID, x.STREAM_ID FROM IEX_PRD_OKL_XREF x WHERE x.CNSLD_INVOICE_ID = :cnsld_invoice_id;
  • Audit rows created by a concurrent program: SELECT * FROM IEX_PRD_OKL_XREF WHERE PROGRAM_ID = :program_id AND REQUEST_ID = :request_id;
  • Multi-org filtered extracts should always include SECURITY_GROUP_ID to respect operating unit security.

Because the table is narrow and index-driven, it is well suited to supporting Collections promise-to-pay analytics and to feeding receivables aging reports that need promise context.

Related Objects

  • IEX_PROMISE_DETAILS — joined on PROMISE_DETAIL_ID; the parent promise record.
  • FND_SECURITY_GROUPS — joined on SECURITY_GROUP_ID; provides the security group definition.
  • IEX_PROMISES — the header-level promise table reached through the promise detail.
  • RA_CUSTOMER_TRX_ALL / RA_CUSTOMER_TRX_LINES_ALL — AR transaction tables that own the underlying invoices consolidated into the referenced consolidated invoice.
  • IEX_CNSLD_INVOICES (or the corresponding consolidated-invoice entity) — the object identified by CNSLD_INVOICE_ID.
  • Collections concurrent programs and OAF pages that insert and maintain cross-reference rows, using the OBJECT_VERSION_NUMBER and WHO columns.