Results for “st_1”

4 results




Overview
Explore in AI Chat

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

Overview

APPS.OKL_CS_AST_ADDONS_UV is a reporting and integration view in the Oracle E-Business Suite (EBS) covering lease and contract management data. The object resides in the APPS schema and is available in both EBS 12.1.1 and 12.2.2. The UV suffix follows the Oracle convention for a "user view" — a denormalized, presentation-oriented layer intended for inquiry screens, concurrent programs, and downstream extracts rather than for direct transactional processing.

The view joins an asset line to the contract line, item, and inventory item hierarchy that sits beneath it, exposing the parent line identifier, the asset number, and the descriptive attributes of the associated system item. Its practical role is to answer the question: which assets are attached to which contract lines, and what item is that contract line ultimately associated with? Because it resolves both the asset-level and item-level identifiers in a single row, it is convenient for reporting on add-on assets associated with leases and service agreements without the caller needing to reconstruct the multi-level line structure.

Underlying Base Objects

The documented base objects referenced by the view are OKX_ASSET_LINES_V, OKC_K_LINES_B, OKC_LINE_STYLES_B, OKC_K_ITEMS_V, and OKX_SYSTEM_ITEMS_V. In the ETRM metadata, OKC_K_LINES_B, OKC_LINE_STYLES_B are recorded as synonyms, while OKX_ASSET_LINES_V, OKC_K_ITEMS_V, and OKX_SYSTEM_ITEMS_V are views.

The join path traverses the contract line hierarchy: OKC_K_LINES_B appears three times (aliased B, C, and D) to walk from the parent line down through successive child lines. OKC_LINE_STYLES_B (aliased ST_1) supplies the line style and is filtered to LTY_CODE = 'ITEM', ensuring only item-style lines are returned. OKC_K_ITEMS_V links the line to its item record, and OKX_SYSTEM_ITEMS_V supplies the item name and description. The asset side enters through OKX_ASSET_LINES_V, whose PARENT_LINE_ID is equated to the root OKC_K_LINES_B.ID. The final predicates convert item identifiers to character form (TO_CHAR(F.ID1) = E.OBJECT1_ID1 and TO_CHAR(F.ID2) = E.OBJECT1_ID2) to complete the item match.

Key Columns

  • PARENT_LINE_ID — The identifier of the contract line to which the asset is attached; drawn from OKX_ASSET_LINES_V and used as the entry point of the join chain.
  • ASSET_NUMBER — The asset number from OKX_ASSET_LINES_V, identifying the physical or logical asset associated with the line.
  • NAME — The item name from OKX_SYSTEM_ITEMS_V, describing the system item resolved through the line and item hierarchy.
  • DESCRIPTION — The item description from OKX_SYSTEM_ITEMS_V, providing the descriptive text associated with the resolved item.

The view therefore projects a deliberately narrow column set: one line key, one asset key, and two descriptive item attributes. This narrowness reflects its purpose as a lookup or supplemental view rather than a full contract-line reporting source.

Common Use Cases and Queries

Typical usage includes reporting on assets associated with item-style contract lines, validating that asset-to-line attachments resolve to a known system item, and feeding extracts that require a flattened asset plus item description pairing. A representative query filters or projects the exposed columns:

  • SELECT parent_line_id, asset_number, name, description FROM apps.okl_cs_ast_addons_uv WHERE asset_number = :asset_number;
  • SELECT parent_line_id, COUNT(*) FROM apps.okl_cs_ast_addons_uv GROUP BY parent_line_id;
  • SELECT a.asset_number, a.name FROM apps.okl_cs_ast_addons_uv a WHERE a.parent_line_id = :line_id;

Because the view is read-only and joins several contract and item objects, queries against it for large line populations should be filtered by PARENT_LINE_ID or ASSET_NUMBER to avoid broad scans across the OKC_K_LINES_B hierarchy.