Results for “object_id2_new”

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

Overview

The OKL_LA_ASSET_IB_UV view is an APPS-owned database object within the Oracle E-Business Suite Leasing and Finance Management (OKL) module. It functions as a user interface (UI) view that consolidates asset-level information with corresponding Oracle Install Base (IB) instance data. The suffix "UV" denotes its role as a UI version view, meaning it is designed to be queried directly by Oracle Forms or OAF-based pages that present asset and Install Base details to end users. In Oracle EBS 12.1.1 and 12.2.2, this view serves as a read-only abstraction layer over a complex join between the OKC contract tables and the HZ (Trading Community Architecture) location tables.

The view is particularly relevant when reporting or displaying the physical location associated with a leased asset. The ADDRESS_DESCRIPTION column—the term for which users frequently search—is generated by calling the ARP_ADDR_LABEL_PKG.FORMAT_ADDRESS API, which assembles a formatted address string from the underlying HZ location attributes. This makes the view the primary reference point for any query requiring a human-readable asset address without manually joining to the multi-table HZ address model.

Underlying Base Objects

The view is defined over a combination of contract and customer-master synonyms. Documented referenced base objects include:

• OKC_K_LINES_B, OKC_K_LINES_TL, OKC_LINE_STYLES_B — the core contract line, translated line, and line-style tables that define the contract hierarchy (free-form lines, item lines, instance lines, and install-item lines).
• OKC_K_ITEMS — supplies the inventory item identifier, inventory organization, and unit count.
• OKL_TXL_ITM_INSTS — holds the transaction item instance records linking assets to party site uses.
• HZ_LOCATIONS, HZ_PARTY_SITES, HZ_PARTY_SITE_USES — the Trading Community Architecture tables providing address and site-use information.
• ARP_ADDR_LABEL_PKG — the address formatting package invoked in the SELECT list.

The joins traverse the contract style codes FREE_FORM1, ITEM, FREE_FORM2, and INST_ITEM, ensuring each asset record is resolved to its corresponding Install Base instance and party site usage.

Key Columns

• TOP_LINE — the top-level contract line identifier (from OKC_K_LINES_TL).
• IB_ID — the Install Base instance identifier.
• DNZ_CHR_ID — the contract header/character ID associated with the line.
• ASSET_NUMBER — the asset name/number as stored on the contract line.
• DESCRIPTION — the item description of the asset.
• INVENTORY_ITEM_ID / INVENTORY_ORG_ID — the inventory item and organization identifiers derived from OKC_K_ITEMS object columns.
• UNITS — number of items/units on the line.
• OBJECT_ID1_NEW / OBJECT_ID2_NEW — instance object identifiers used to join to HZ party site uses.
• ADDRESS_DESCRIPTION — an 80-character formatted address string produced by ARP_ADDR_LABEL_PKG.FORMAT_ADDRESS, combining address lines, city, county, state, province, postal code, and country.

Common Use Cases and Queries

Typical scenarios include asset location reporting, Install Base reconciliation, and lease contract dashboards. A representative query retrieving asset number, description, and formatted address is:

• SELECT asset_number, description, units, address_description FROM apps.okl_la_asset_ib_uv WHERE asset_number = :p_asset_number;
• SELECT top_line, ib_id, address_description FROM apps.okl_la_asset_ib_uv WHERE inventory_item_id = :p_item_id AND inventory_org_id = :p_org_id;

Because the view is APPS-owned and joins multiple synonym layers, queries should be executed with the APPS schema context or through a responsibility whose MOAC access permits the OKL and HZ data. Performance is influenced by the underlying contract line style filters, so filtering on ASSET_NUMBER or IB_ID is recommended.