Results for “inventory_org_code”

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

Overview

The OKL_EXT_AP_LINE_SOURCES_V view is a reporting and integration object within the Oracle E-Business Suite (EBS) Leasing and Finance Management (OKL) module. It resides in the APPS schema and is defined as a valid, non-base view that exposes lease-related line source data, including extension information used by external and internal accounting processes. This view plays a central role in bridging Oracle Lease Management contract data with Payables-facing integration flows, allowing developers and integrators to retrieve extended line source attributes in a denormalized, query-friendly format.

The view is particularly relevant when the header_extension_id column is referenced. That column links a transaction line back to its parent header extension record, which is fundamental in ETRM's extension framework. The extension framework enables organizations to attach custom, implementation-specific attributes to lease contracts and contract lines without modifying the underlying base tables. Because OKL_EXT_AP_LINE_SOURCES_V surfaces both HEADER_EXTENSION_ID and LINE_EXTENSION_ID, it acts as a key reference point for any query or integration that must reconcile line-level source data with its corresponding header extension context.

Underlying Base Objects

According to the documented ETRM 12.2.2 metadata, OKL_EXT_AP_LINE_SOURCES_V is defined over two base objects:

• OKL_EXT_AP_LINE_SOURCES_B (synonym) — the primary base table holding the transactional line source columns, aliased as PXL in the view definition.
• OKL_EXT_AP_LINE_SOURCES_TL (synonym) — the translation table providing language-dependent descriptive columns such as INVENTORY_ORG_NAME, STREAM_TYPE_NAME, and TRANS_LINE_DESCRIPTION, aliased as PXLL in the view definition.

The view text joins these objects, with the _B table supplying identifiers and attributes (LINE_EXTENSION_ID, HEADER_EXTENSION_ID, SOURCE_ID, SOURCE_TABLE, KLE_ID, STY_ID, and numerous LINE_ATTRIBUTE1..15 columns) and the _TL table supplying localized descriptive text filtered by LANGUAGE. This pattern is a standard EBS technical construct: a _B table for operational data, a _TL table for multilingual descriptions, and a _V view that reconstructs them for reporting consumers.

Key Columns

The most significant columns exposed by the view include:

• LINE_EXTENSION_ID / HEADER_EXTENSION_ID — Identifiers that tie the line source record to its extension line and extension header, respectively. HEADER_EXTENSION_ID is the pivotal join key for associating lines with a specific header-level extension instance.
• SOURCE_ID / SOURCE_TABLE — Identify the originating transactional record and its source table, enabling traceability back to the functional document.
• KLE_ID / STY_ID — Lease and stream type identifiers used to classify the financial stream associated with the line.
• ASSET_NUMBER / CONTRACT_LINE_NUMBER — Human-readable references to the leased asset and contract line.
• LINE_ATTRIBUTE_CATEGORY and LINE_ATTRIBUTE1..15 — Flexible descriptive flexfield (DFF) columns that carry configuration-specific data.
• STREAM_TYPE_CODE / STREAM_TYPE_PURPOSE_CODE, INVENTORY_ORG_CODE, FEE_TYPE_CODE, MEMO_FLAG, CONTRACT_LINE_TYPE — Codes that drive accounting and stream generation logic.
• Translated columns (INVENTORY_ORG_NAME, STREAM_TYPE_NAME, TRANS_LINE_DESCRIPTION) and audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE).

Common Use Cases and Queries

This view is commonly queried during extension-driven reporting, debugging of Payables line generation, and reconciliation between lease contract lines and their header extension records. A typical query locating all lines for a given header extension is:

• SELECT line_extension_id, header_extension_id, source_id, source_table, kle_id, sty_id, contract_line_number FROM okl_ext_ap_line_sources_v WHERE header_extension_id = :p_header_extension_id;

Another frequent pattern retrieves attribute and descriptive data for detailed analysis:

• SELECT header_extension_id, line_extension_id, stream_type_name, trans_line_description, line_attribute1, line_attribute2 FROM okl_ext_ap_line_sources_v WHERE source_table = 'OKL_EXT_AP_LINE_SOURCES_B' ORDER BY line_extension_id;

Because the view is owned by APPS and defined over _B and _TL synonyms, it is safe to reference directly from custom reports, concurrent programs, and integration extracts in both EBS 12.1.1 and 12.2.2, provided the caller has appropriate APPS-level grants. Developers should treat it strictly as a read-only object, since the underlying extension data is maintained through the standard ETRM extension framework rather than direct DML.