Results for “chr_crjb”

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

Overview

The view APPS.OKL_LA_SERV_INTGR_UV exposes Oracle Lease and Finance Management (OKL) service-line data in a flattened, integration-ready form. It is a reporting and integration construct owned by the APPS schema and is derived from the OKC contract authoring tables in combination with OKL line tables, inventory item definitions, and supplier (vendor) records. Its name indicates its purpose: it is a user view (_UV) that surfaces Lease Authoring (LA) service integration records, supplying denormalized contract, line, item, and party information to downstream processes such as service billing, asset integration, and external interfaces.

The view places service lines on a contract in context with both their header-level relationship and their line-level relationship, joining the two relationship records (OKC_K_REL_OBJS) through the shared contract identifier. This makes it particularly useful for identifying the service item, its supplying vendor, the governing service contract, and the amounts associated with each service line.

Underlying Base Objects

The view is defined over the following documented objects:

• OKC_K_REL_OBJS (aliased twice as CHR_CRJB and CLE_CRJB) — the contract relationship objects at header and line level. These provide the k_rel_objs and l_rel_objs surrogate and descriptive identifiers.
• OKC_K_HEADERS_B and OKC_K_HEADERS_TL — the contract header base and translation tables, supplying the contract number (service_contract_number).
• OKC_K_LINES_B — the contract line base table, providing line identifiers, start/end dates, and the line style reference.
• OKC_LINE_STYLES_B — line style definitions, filtered to LTY_CODE = 'SERVICE' to restrict the view to service lines.
• OKC_K_ITEMS — the contract line item table linking lines to inventory items.
• OKC_K_PARTY_ROLES_B — party role definitions on the contract.
• OKL_K_LINES — the OKL-specific line extension, supplying the amount.
• MTL_SYSTEM_ITEMS_B_KFV and MTL_SYSTEM_ITEMS_TL — inventory item key flexfield view and translation, providing item_name.
• PO_VENDORS — the supplier view supplying supplier_name, SUPPLIER_NUMBER, and SUPPLIER_ID.

Key Columns

• CLE_ID, START_DATE, END_DATE, DNZ_CHR_ID — line identity, effective dates, and the denormalized contract header identifier.
• ITEM_NAME — the concatenated inventory item segments for the serviced item.
• SUPPLIER_NAME, SUPPLIER_NUMBER, SUPPLIER_ID — vendor attributes for the service supplier.
• SERVICE_CONTRACT_NUMBER — the contract number derived from the header base/translation join.
• K_REL_OBJS_* and L_REL_OBJS_* — the header-level and line-level relationship object attributes, including RTY_CODE, OBJECT1_ID1, OBJECT1_ID2, and JTOT_OBJECT1_CODE.
• AMOUNT — the OKL line amount for the service line.
• Placeholder columns AUTHORING_ORG_ID, INV_ORGANIZATION_ID, CURRENCY_CODE, CUST_OBJECT1_ID1, CUST_OBJECT1_ID2, BTO_OBJECT1_ID1, and BTO_OBJECT1_ID2 — literal placeholders reserved for integration consumers.

Common Use Cases and Queries

Typical uses include extracting service lines with their suppliers for a given service contract, reconciling service item details against inventory, and feeding integration staging tables. A representative query follows:

• SELECT cle_id, service_contract_number, item_name, supplier_name, amount FROM apps.okl_la_serv_intgr_uv WHERE service_contract_number = :contract_number;
• SELECT supplier_id, supplier_number, supplier_name, COUNT(*) FROM apps.okl_la_serv_intgr_uv GROUP BY supplier_id, supplier_number, supplier_name;
• SELECT item_name, SUM(amount) FROM apps.okl_la_serv_intgr_uv WHERE start_date >= :from_date GROUP BY item_name;

Joins to OKC_K_HEADERS_B, OKL_K_LINES, and PO_VENDORS on the exposed identifiers can enrich the extract further, and the placeholder columns are intended to be populated by consumers when the view is used to build an integration payload.