Results for “okl_lines_interface”

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

Overview

The OKL_LINES_INTERFACE table is a staging and open-interface table within the Oracle Leasing and Finance Management (OKL) module of Oracle E-Business Suite. It holds contract line information that is intended to be loaded into, or used to update, contract records in the OKL production schema. Contract lines represent the individual assets, fee items, usage items, and other chargeable components that make up a lease or loan contract, and this interface table provides the vehicle through which external sources, feeder systems, and integration processes supply that line-level data before validation and import.

The table resides in the OKL schema and is documented in ETRM 12.2.2 with 219 columns, indicating a wide denormalized staging structure that mirrors the breadth of the OKL contract line entity. Because it acts as an interface rather than a transactional master, records are transient: they are populated by external processes, validated by the OKL Contract Open Interface concurrent program, and then either promoted into the base OKL line tables or rejected with error messaging. From a heuristic Data Vault modeling perspective, the metadata classifies this object as standalone, which suggests it is best treated as a staging or source object rather than a hub, link, or satellite; the presence of descriptive, amount, and reference attributes on a single row makes it a natural fit for a staging satellite pattern during data-warehouse extraction.

Key Information Stored

The table stores one row per contract line to be interfaced, identified by the combination of CONTRACT_NUMBER_OLD and LINE_NUMBER. These two columns function as the principal business-key candidates, since a line is meaningless outside the context of its parent contract. The table does not expose a single surrogate primary key in the documented metadata; identity is therefore derived from the contract-number and line-number pair.

The most significant columns include:

• CONTRACT_NUMBER_OLD and LINE_NUMBER — the business identifiers that tie each interface row to a contract and its line sequence.
• LINE_TYPE — distinguishes asset lines from fee, usage, or other line categories, driving downstream processing logic.
• ASSET_NUMBER, ASSET_KEY_ID, and LINK_ASSET_NUMBER — identify the specific and linked assets associated with the line.
• ORIGINAL_COST, AMOUNT, and AMOUNT_BALANCE_LEGACY — capture the financial magnitude and any legacy balance carried forward.
• CURRENCY_CODE — defines the currency of the monetary amounts.
• STATUS, DATE_APPROVED, and DATE_SIGNED — record the line's lifecycle state and key milestone dates.
• INVENTORY_ITEM_ID and INVENTORY_ORGANIZATION_ID — link the line to inventory-backed equipment.
• PAYMENT_TERM and PAYMENT_TERM_ID — reference the payment terms governing the line.
• RESIDUAL_AMOUNT and RESIDUAL_PERCENT — define residual value expectations.
• ASSET_LOCATION_ID — references the physical location of the asset.
• COUNTER_GROUP_ID — references the counter group used for usage-based billing.

Common Use Cases and Queries

The primary use case is the bulk import or update of contract lines through the OKL Contract Open Interface. Integration developers populate OKL_LINES_INTERFACE from external systems, run the interface program, and inspect success and failure rows. A typical validation query identifies rows pending import:

• SELECT CONTRACT_NUMBER_OLD, LINE_NUMBER, LINE_TYPE, STATUS FROM OKL_LINES_INTERFACE WHERE STATUS = 'NEW';
• SELECT CONTRACT_NUMBER_OLD, COUNT(*) FROM OKL_LINES_INTERFACE GROUP BY CONTRACT_NUMBER_OLD;
• Joining to PN_PAYMENT_TERMS_ALL on PAYMENT_TERM_ID validates that referenced payment terms exist.

Reporting scenarios include reconciliation of interfaced versus imported line counts, verification of asset and residual amounts before posting, and exception reporting on rows whose referenced locations, counter groups, or payment terms fail foreign-key validation. Because the table is a staging area, queries should be scoped by interface run or load batch to avoid mixing historical and current loads.

Related Objects

Foreign-key relationships documented for this table anchor it to several reference objects:

• CSI_A_LOCATIONS — joined via ASSET_LOCATION_ID to resolve the asset location.
• CS_COUNTER_GROUPS — joined via COUNTER_GROUP_ID for usage-based lines.
• PN_PAYMENT_TERMS_ALL — joined via PAYMENT_TERM_ID to validate payment terms.
• OKL_CONTRACTS_INTERFACE — the contract-header counterpart that supplies the parent contract for each line.
• OKL base line tables — the production contract line entities populated after successful interface processing.

These relationships should be enforced or validated before the interface program is executed, as orphaned references to locations, counter groups, or payment terms are a common cause of interface rejection.