Search Results oks_con_lines_int_all




Overview
Explore in AI Chat

Overview

OKS_CON_LINES_INT_ALL is the open interface table for the Oracle Service Contracts (OKS) module, owned by the OKS schema. Its purpose is to stage contract line information that is imported into Oracle Contracts for Service and materialized as contract lines in the base OKS contract tables. In Oracle EBS 12.1.1 and 12.2.2, it functions as the inbound staging area for bulk contract authoring and migration scenarios, such as conversions from legacy service agreement systems, mass contract line loads, or integration feeds from external order capture applications. Rows inserted into this table are processed by the Service Contracts import program, which validates the data, resolves references, and inserts the resulting records into OKS_CONTRACT_LINES_ALL and its related pricing, coverage, and billing entities.

The documented structure contains 67 columns. Because the table is a standalone staging object and does not participate in normalized parent-child relationships within the OKS model, the metadata’s heuristic Data Vault classification suggests that it is best modeled as a satellite or staging table rather than a hub or link. Its defining role is transactional: rows represent candidate contract lines awaiting validation and transfer, not durable master data.

Key Information Stored

The single documented foreign key in the schema is CUST_ACCOUNT_ID, which references HZ_CUST_ACCOUNTS, anchoring each staged line to the customer account that will own the imported contract. Beyond that, the most operationally significant columns fall into several groups:

The descriptor ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15 provide a flexible descriptive flexfield surface for customer-specific data. INTERFACED_STATUS_FLAG is the primary control column: rows remain unprocessed until the import program sets it, at which point the row is either promoted to a contract line or flagged with an error. No surrogate primary key is documented for this table; CONTRACT_LINE_ID and CONTRACT_LINE_NUMBER serve as the practical business-key candidates, while the underlying unique identifier is assigned by OKS at interface completion.

Common Use Cases and Queries

Typical uses include legacy service-agreement migration, mass creation of coverage lines for a new service offering, and reconciliations between external order systems and OKS. Queries generally filter on INTERFACED_STATUS_FLAG to isolate pending or failed rows, and join to HZ_CUST_ACCOUNTS via CUST_ACCOUNT_ID to validate the customer context.

For example, to identify unprocessed lines for a given customer:

SELECT CONTRACT_LINE_ID, CONTRACT_LINE_NUMBER, LINE_STATUS_CODE, START_DATE, END_DATE
FROM OKS.OKS_CON_LINES_INT_ALL
WHERE INTERFACED_STATUS_FLAG IS NULL
AND CUST_ACCOUNT_ID = :account_id;

A reconciliation query joins the interface to the customer account for reporting: SELECT i.CONTRACT_LINE_REF, i.CURRENCY_CODE, i.PRICE_NEGOTIATED, a.ACCOUNT_NUMBER FROM OKS.OKS_CON_LINES_INT_ALL i, HZ_CUST_ACCOUNTS a WHERE i.CUST_ACCOUNT_ID = a.CUST_ACCOUNT_ID. Standard practice is to run the Service Contracts import concurrent program after populating the table, then query INTERFACED_STATUS_FLAG to confirm success or extract error rows.

Related Objects

The principal related objects are HZ_CUST_ACCOUNTS (referenced through CUST_ACCOUNT_ID, the sole documented FK), the base contract line table OKS_CONTRACT_LINES_ALL, the contract header table OKS_CONTRACTS_ALL, and the coverage entities referenced by COVERAGE_ID and COVERAGE_TEMPLATE_ID. The Service Contracts import concurrent program consumes this table, and pricing and billing validations draw on PRICE_LIST_ID, PAYMENT_TERMS_ID, and ACCOUNTING_RULE_ID. The ORDER_HEADER_ID and ORDER_LINE_ID columns create an operational link to Oracle Order Management. Reporting views over OKS contract data typically depend on the successful transfer of interface rows, making OKS_CON_LINES_INT_ALL the entry point for contract line master data.