Results for “cust_object1_id2”

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

Overview

OKL_LA_SERV_INTGR_UV is a read-only database view owned by the APPS schema in Oracle E-Business Suite, defined within the OKL — Lease and Finance Management product family. Its documented purpose is to support the Service Integration page, an authoring-time user interface that presents lease contract service lines alongside the associated item, supplier, and relationship data. The view consolidates header, line, item, and party information from multiple OKC (Contracts Core) and OKL (Lease Management) base objects into a flattened, denormalized result set suitable for form-based display and reporting.

Because the view exposes both contract header context and lease-line detail, it functions as a bridge between the contracting model (OKC_K_HEADERS, OKC_K_LINES, OKC_K_ITEMS) and the lease management model (OKL_K_LINES). It is most relevant to implementers and report developers who need a single query surface for service-related lease line integration data without manually joining the constituent Contracts Core tables.

Underlying Base Objects

The view is defined over the following documented base objects and synonyms:

• OKC_K_HEADERS_B and OKC_K_HEADERS_TL — contract header base and translation tables, supplying contract numbers and language-specific descriptions.
• OKC_K_LINES_B — contract line base table, providing the CLE (contract line) identifier and start/end dates.
• OKC_K_ITEMS, OKC_LINE_STYLES_B — item association and line style data; the line style code is filtered to 'SERVICE'.
• OKC_K_REL_OBJS — the relationship object table, joined twice (aliases CHR_CRJB and CLE_CRJB) to resolve header-level and line-level relationships.
• OKC_K_PARTY_ROLES_B — party role data associated with the contract.
• OKL_K_LINES — lease line table, supplying the amount and the DNZ_CHR_ID linkage.
• MTL_SYSTEM_ITEMS_B_KFV and MTL_SYSTEM_ITEMS_TL — inventory item key flexfield view and translation table, providing concatenated item segments and item names.
• PO_VENDORS — supplier master view, providing the vendor name.

Joins are keyed on CHR_ID (contract header), CLE_ID (contract line), and OBJECT1_ID1/OBJECT1_ID2 relationship values, with the contract header translation restricted to the session language via USERENV('LANG').

Key Columns

• CLE_ID, DNZ_CHR_ID, SERVICE_CONTRACT_NUMBER — contract line identifier, lease header linkage, and the human-readable contract number.
• START_DATE, END_DATE — effective date range of the service contract line.
• ITEM_NAME, SUPPLIER_NAME — concatenated inventory item segments and the supplier name for the service line.
• AMOUNT — monetary value drawn from OKL_K_LINES.
• K_REL_OBJS_* and L_REL_OBJS_* — parallel column families exposing header-level and line-level relationship attributes (RTY_CODE, OBJECT1_ID1, OBJECT1_ID2, JTOT_OBJECT1_CODE).
• INV_ORGANIZATION_ID — a literal string column returned by the view; in the SELECT list it is emitted as the constant 'INV_ORGANIZATION_ID', acting as a column placeholder rather than a runtime inventory organization value. This is the token the user searched for and explains why direct queries surface a static literal.
• AUTHORING_ORG_ID, CURRENCY_CODE, CUST_OBJECT1_ID1/ID2, BTO_OBJECT1_ID1/ID2 — additional literal placeholder columns used by the Service Integration page framework.

Common Use Cases and Queries

Typical usage involves retrieving service contract lines for a given lease or contract, verifying item and supplier content, and reviewing relationship objects. A representative query:

• SELECT cle_id, service_contract_number, item_name, supplier_name, amount FROM apps.okl_la_serv_intgr_uv WHERE dnz_chr_id = :chr_id;
• SELECT service_contract_number, item_name, start_date, end_date FROM apps.okl_la_serv_intgr_uv WHERE item_name LIKE :item_pattern;
• SELECT k_rel_objs_id, l_rel_objs_id, amount FROM apps.okl_la_serv_intgr_uv WHERE cle_id = :cle_id;

Because INV_ORGANIZATION_ID is returned as a literal, it should not be used as a filter predicate for actual organization values; a direct query against MTL_SYSTEM_ITEMS_B_KFV or the underlying OKC/OKL tables is required for true inventory organization resolution.