Results for “okl_cs_ast_addons_uv”

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

Overview

The view OKL_CS_AST_ADDONS_UV is an Oracle E-Business Suite (EBS) Leasing and Finance Management (OKL) dictionary object owned by the APPS schema and residing in the application database tier. It exposes asset add-on line information associated with contract line records, joining contract line structures to the corresponding system item master records. The name suffix "UV" designates a user-verified or user-facing view, indicating that it is intended for consumption by reporting layers, integrations, and extensions rather than purely internal processing logic. Within the OKL module, this view serves as a curated projection that links an asset line back to its parent contract line and enriches it with descriptive item attributes, thereby supporting reconciliation, asset listing, and add-on analysis that would otherwise require manual multi-table joins across OKC and OKX base structures.

Underlying Base Objects

The view is defined over the following documented base objects: OKX_ASSET_LINES_V (VIEW), OKC_K_LINES_B (accessed via synonym), OKC_LINE_STYLES_B (accessed via synonym), OKC_K_ITEMS_V (VIEW), and OKX_SYSTEM_ITEMS_V (VIEW). The join path is anchored on OKX_ASSET_LINES_V (alias A), whose PARENT_LINE_ID is resolved against OKC_K_LINES_B (alias B) on B.ID = A.PARENT_LINE_ID. A second contract line instance (alias C) is matched through C.CLE_ID = B.ID, and its line style is constrained by C.LSE_ID = ST_1.ID with the filter ST_1.LTY_CODE = 'ITEM' from OKC_LINE_STYLES_B. Further hierarchy traversal continues through aliases D and E, where D.CLE_ID = C.ID and E.CLE_ID = D.ID, before joining to OKX_SYSTEM_ITEMS_V (alias F) by converting F.ID1 and F.ID2 to character form to match E.OBJECT1_ID1 and E.OBJECT1_ID2. This chained join reflects the OKC contract line hierarchy pattern, where line-entity relationships are nested through CLE_ID references.

Key Columns

The view exposes four columns. PARENT_LINE_ID is the identifier of the parent contract line from OKX_ASSET_LINES_V, providing the linkage key back to the contract structure. ASSET_NUMBER carries the asset number from the asset lines source and is the primary business identifier for the add-on asset. NAME and DESCRIPTION are drawn from OKX_SYSTEM_ITEMS_V and provide the human-readable item name and description resolved through the OBJECT1_ID1 and OBJECT1_ID2 join conditions. Together these columns allow report authors to associate a contract line with a named, described asset item without exposing internal surrogate keys.

Common Use Cases and Queries

Typical usage includes asset add-on listings for a contract, reporting on items attached to parent lines, and integration extracts feeding downstream asset registers. A representative query is:

• SELECT parent_line_id, asset_number, name, description FROM okl_cs_ast_addons_uv WHERE parent_line_id = :p_line_id;
• SELECT asset_number, name FROM okl_cs_ast_addons_uv ORDER BY parent_line_id, asset_number;
• Joining to OKC_K_LINES_B on PARENT_LINE_ID to filter by contract or line attributes.

Note that, as documented, the view lacks an ORG_ID or contract identifier column, so contract-level filtering generally requires joining back to the contract line base tables. Users searching for the related object OKX_ASSET_LINES_V should recognize it as a foundational base view underlying this one.