Results for “okl_ext_ap_header_sources_b_u2”

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

Overview

The OKL_EXT_AP_HEADER_SOURCES_B table is a Payables transactions header extension table within the Oracle Lease and Finance Management (OKL) module. It resides in the OKL schema and serves as a persistence structure for header-level source information that originates from external Payables (AP) transactions and is subsequently integrated into the leasing and finance workflow for contract, agreement, and accounting processing.

The table carries a substantial footprint of 79 documented columns in the ETRM 12.2.2 physical schema, reflecting its role as a denormalized staging and enrichment area for data flowing between Oracle Payables and the OKL contract and accounting engines. It captures contract identifiers, customer and party references, agreement details, product and accounting attributes, and a rich set of descriptive flexfield (DFF) attribute columns.

From a Data Vault modeling perspective, the FK structure suggests a satellite-leaning classification. The presence of a surrogate primary key, foreign keys to descriptive and reference tables such as OKL_TRX_TYPES_B, HZ_PARTIES, and HZ_CUST_ACCOUNTS, and dependent children in OKL_EXT_AP_LINE_SOURCES_B indicates a structure that stores contextual and descriptive attributes rather than acting as a pure hub or transactional link.

Key Information Stored

The table is anchored by the surrogate primary key HEADER_EXTENSION_ID (defined by OKL_EXT_AP_HEADER_SOURCES_B_PK). A second unique index, OKL_EXT_AP_HEADER_SOURCES_B_U2 on the combination of SOURCE_ID and SOURCE_TABLE, provides a documented business-key candidate that identifies the origin record from which the extension header was derived.

The most significant columns include:

• SOURCE_ID and SOURCE_TABLE — collectively identifying the source record and the source table of origin, establishing traceability back to the Payables transaction.
• KHR_ID — the lease or finance contract header reference.
• TRY_ID — the transaction type reference, linking header records to OKL_TRX_TYPES_B.
• TRANS_NUMBER, CONTRACT_NUMBER, and CUSTOMER_NAME — core business identifiers used in operational reporting.
• PARTY_ID and CUST_ACCOUNT_ID — references to TCA party and customer account records.
• CONTRACT_CURRENCY_CODE, CONTRACT_EFFECTIVE_FROM, and CONTRACT_STATUS_CODE — contract-level financial and lifecycle attributes.
• BOOK_CLASSIFICATION_CODE, TAX_OWNER_CODE, INT_CALC_METHOD_CODE, and REV_REC_METHOD_CODE — accounting and classification drivers.
• DFF sets (KHR_ATTRIBUTE1–15 with KHR_ATTRIBUTE_CATEGORY, and CUST_ATTRIBUTE1–15 with CUST_ATTRIBUTE_CATEGORY) — flexible descriptive attributes.
• Investor agreement fields such as INV_AGRMNT_NUMBER, INV_AGRMNT_PRODUCT_NAME, and INV_AGRMNT_STATUS_CODE.

Common Use Cases and Queries

Typical usage centers on reconciliation between Payables source transactions and lease contract headers, review of accounting classification for imported transactions, and reporting on investor agreement participation. A common query pattern retrieves header extension records joined to their party and transaction type descriptions:

• Locating extension headers by source: SELECT HEADER_EXTENSION_ID, CONTRACT_NUMBER, CUSTOMER_NAME FROM OKL_EXT_AP_HEADER_SOURCES_B WHERE SOURCE_ID = :source_id AND SOURCE_TABLE = :source_table;
• Contract traceability: joining on KHR_ID to the lease contract tables to compare source metadata with the live contract.
• Accounting classification review: filtering by BOOK_CLASSIFICATION_CODE, TAX_OWNER_CODE, or REV_REC_METHOD_CODE to validate imported Payables transactions.
• DFF-based reporting: querying KHR_ATTRIBUTE_CATEGORY and the KHR_ATTRIBUTE columns to satisfy client-specific descriptive reporting.
• Child line detail: joining to OKL_EXT_AP_LINE_SOURCES_B on HEADER_EXTENSION_ID to obtain line-level extension detail.

Related Objects

The following tables and objects are most significant to the function of this table, based on documented FK relationships:

• OKL_EXT_AP_LINE_SOURCES_B — child table joined via HEADER_EXTENSION_ID, holding line-level extension attributes.
• OKL_TRX_TYPES_B — referenced through TRY_ID, providing transaction type descriptions and behavior.
• HZ_PARTIES — referenced through PARTY_ID, providing party master details.
• HZ_CUST_ACCOUNTS — referenced through CUST_ACCOUNT_ID, supplying customer account information.
• OKL_EXT_AP_HEADER_SOURCES_B self-reference via KHR_ID, used internally within the header structure.