Results for “okl_ext_ap_line_sources_b_u2”

10 results




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

Overview

OKL.OKL_EXT_AP_LINE_SOURCES_B is a transactional extension table in the Oracle E-Business Suite Contracts (OKL) schema, present and VALID in both release 12.1.1 and 12.2.2. Its purpose is to store contextual, descriptive information associated with OKL accounting transaction lines. The captured attributes are sourced through to Subledger Accounting (SLA), where they can be consumed by Application Accounting Definitions (AADs) and Accounting Methods Builder (AMB) setups to drive or condition accounting rule derivation.

The table resides in the APPS_TS_TX_DATA tablespace with PCTFREE 10, which is consistent with a high-volume transaction data object. It forms part of the lease and contract accounting extension model, complementing the header-level equivalent OKL_EXT_AP_HEADER_SOURCES_B. From a dimensional modeling perspective, the mined foreign-key structure suggests a Data Vault link classification, since the table connects multiple business keys (contract line, stream type, supplier, header extension) rather than acting as a standalone hub or a purely descriptive satellite.

Key Information Stored

The table contains 43 documented columns. The surrogate primary key, enforced by OKL_EXT_AP_LINE_SOURCES_B_PK, is LINE_EXTENSION_ID. Two unique indexes exist as business-key candidates: OKL_EXT_AP_LINE_SOURCES_B_U1 on LINE_EXTENSION_ID (redundant with the primary key) and OKL_EXT_AP_LINE_SOURCES_B_U2 on the composite of SOURCE_ID and SOURCE_TABLE, which anchors a record to its originating source row.

Common Use Cases and Queries

The table is typically queried to trace which source document or contract line produced a given accounting line, and to inspect the contextual attributes passed to SLA. A frequent pattern joins line extensions to their header parent and to the contract line:

  • Retrieve extension context for a contract line: SELECT s.* FROM okl.okl_ext_ap_line_sources_b s WHERE s.kle_id = :kle_id;
  • Resolve the originating source row via the U2 business key: SELECT * FROM okl.okl_ext_ap_line_sources_b WHERE source_id = :source_id AND source_table = :source_table;
  • Link line to header context: SELECT h.*, l.* FROM okl.okl_ext_ap_line_sources_b l JOIN okl.okl_ext_ap_header_sources_b h ON l.header_extension_id = h.header_extension_id;

Reporting use cases include auditing accounting template usage by fee type, reconciling SLA transfer for lease accounting, and analyzing asset vendor or location distribution across contract lines.

Related Objects

The most significant dependencies, based on documented foreign-key relationships, are:

  • OKL.OKL_EXT_AP_HEADER_SOURCES_B — joined on HEADER_EXTENSION_ID; header-level counterpart.
  • OKC.OKC_K_LINES_B — joined on KLE_ID; the contract line definition.
  • OKL.OKL_STRM_TYPE_B — joined on STY_ID; stream type definition.
  • AP.AP_SUPPLIERS — joined on ASSET_VENDOR_ID; asset vendor supplier master.
  • OKL.OKL_EXT_AP_LINE_SOURCES_B_U1 / _U2 — unique indexes defining access paths and business keys.
  • SLA (XLA) schema objects — consume the sourced attributes through AMB/AAD configuration.