Results for “okl_ext_ar_header_sources_b”

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

Overview

The OKL_EXT_AR_HEADER_SOURCES_B table is a Receivables transactions header extension table that resides in the OKL schema, owned by the Oracle Leasing and Finance Management (OKL) product module. It serves as a supplemental, denormalized store that captures lease-and-finance-specific attributes for Receivables transaction headers generated in Oracle Receivables. When a lease or finance contract produces a billing transaction in AR, standard AR header columns are insufficient to preserve the leasing context — contract numbers, product classifications, accounting methods, investment agreement details, and descriptive flexfield segments. This table supplies that extended context, linking the AR transaction back to the originating lease contract and transaction type.

From a Data Vault modeling perspective, the heuristic classification for this object is link. This is consistent with its structure: the table carries a surrogate primary key (HEADER_EXTENSION_ID) plus foreign keys that associate the extension record to an originating contract header (KHR_ID) and to a transaction type definition (TRY_ID). The link pattern reflects its role as a connective artifact between the AR transaction domain and the OKL leasing contract domain, rather than a standalone hub or a purely descriptive satellite.

Key Information Stored

The table contains 78 documented columns. The most operationally significant include the following.

• HEADER_EXTENSION_ID — the surrogate primary key, enforced through the OKL_EXT_AR_HEADER_SOURCES_B_PK constraint and the unique index OKL_EXT_AR_HEADER_SOURCES_B_U1.
• SOURCE_TABLE and SOURCE_ID — the business-key candidate pair, enforced by the unique index OKL_EXT_AR_HEADER_SOURCES_B_U2. Together they identify the originating source record that the AR header extension mirrors.
• KHR_ID and TRY_ID — foreign keys. KHR_ID associates the record with the lease contract header, while TRY_ID references OKL_TRX_TYPES_B, tying the transaction to its type definition.
• TRANS_NUMBER, CONTRACT_NUMBER, PRODUCT_NAME — human-readable identifiers carried forward from the contract.
• BOOK_CLASSIFICATION_CODE, TAX_OWNER_CODE, INT_CALC_METHOD_CODE, REV_REC_METHOD_CODE, SCS_CODE — accounting and classification codes governing interest calculation, revenue recognition, and book treatment.
• CONTRACT_EFFECTIVE_FROM, CONTRACT_CURRENCY_CODE — contract timing and currency context.
• KHR_ATTRIBUTE1–15 and CUST_ATTRIBUTE1–15 — descriptive flexfield segments preserving both contract-level and customer-level attributes.
• INV_AGRMNT_NUMBER, INV_AGRMNT_PRODUCT_NAME, INV_AGRMNT_CURRENCY_CODE, INV_AGRMNT_SYND_CODE, INV_AGRMNT_POOL_NUMBER — investment agreement detail carried on the transaction.
• OBJECT_VERSION_NUMBER, CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — standard concurrency control and audit columns.

Common Use Cases and Queries

Typical usage centers on reconciling AR transactions back to lease contracts, reporting on lease-driven receivables, and populating custom extracts that require contract classification data not present on the standard AR header. A representative query joining the extension to its transaction type:

• SELECT h.HEADER_EXTENSION_ID, h.CONTRACT_NUMBER, h.PRODUCT_NAME, h.BOOK_CLASSIFICATION_CODE, t.NAME FROM OKL_EXT_AR_HEADER_SOURCES_B h, OKL_TRX_TYPES_B t WHERE h.TRY_ID = t.TRY_ID;
• Reconciliation by business key: SELECT * FROM OKL_EXT_AR_HEADER_SOURCES_B WHERE SOURCE_TABLE = :p_table AND SOURCE_ID = :p_id;
• Contract traceability: SELECT * FROM OKL_EXT_AR_HEADER_SOURCES_B WHERE KHR_ID = :p_khr_id;

These patterns support subledger analysis, revenue recognition audits, and integrations that must carry leasing attributes into downstream AR reporting.

Related Objects

• OKL_TRX_TYPES_B — referenced by TRY_ID; provides the transaction type definition associated with each AR header extension record.
• OKL_EXT_AR_HEADER_SOURCES_B.KHR_ID — the self-referencing foreign key target, linking the extension record to its originating contract header context.
• OKL_EXT_AR_HEADER_SOURCES_B_U1 / _U2 — the unique indexes that enforce the primary key and the SOURCE_TABLE/SOURCE_ID business key.
• Oracle Receivables AR header tables (for example, RA_CUSTOMER_TRX_ALL) — the downstream transaction headers to which these extensions correlate through the source identifiers.
• OKL contract header objects referenced by KHR_ID — supplying the lease contract context denormalized into this table.