Results for “rpc_org_id”

8 results




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

Overview

The OKL_AM_ASSET_CNDTN_LNS_UV view is a reporting and integration object in the Oracle E-Business Suite (EBS) Leasing and Finance Management (OKL) module. It is an APPS-owned, VALID database view that presents asset condition line information in a denormalized, user-friendly form. Asset condition lines in OKL capture the physical state of leased assets, including damage or wear identified during inspections, the recommended and approved repair actions, and the resulting repair cost estimates. The view consolidates the base transaction line data with its translated (language-dependent) descriptions, repair cost definitions, lookup-based code meanings, and tax/AR invoice linkage, so that the data can be consumed without joining numerous tables. This role is particularly valuable for operational reporting, ad-hoc querying, and integrations where a single, flat source of asset condition lines is required. The view is defined with outer joins to the repair cost tables, ensuring that condition lines without a defined repair cost are still returned.

Underlying Base Objects

The view is defined over a combination of base tables, synonyms, and a package. The core translatable line data is stored in OKL_ASSET_CNDTN_LNS_B (base) and OKL_ASSET_CNDTN_LNS_TL (translated), which are joined on ID and restricted to the session language via USERENV('LANG'). The condition header is sourced from OKL_ASSET_CNDTNS. Repair cost definitions are joined from OKL_REPAIR_COSTS_ALL_B (base) and OKL_REPAIR_COSTS_TL (translated), linked by RPC_ID with outer joins to allow optional repair costs. The OKL_TXL_AR_INV_LNS_B object is outer joined on ACN_ID_COST to supply the associated tax/AR invoice line cost. The FND_LOOKUPS view supplies three separate lookup meanings for status, condition, and damage type, while FND_GLOBAL (PACKAGE) provides the session environment used for language filtering.

Key Columns

The column set combines transactional identifiers, codes, descriptions, and rolled-up values:

Common Use Cases and Queries

Typical use cases include asset condition reporting, repair cost analysis, and tracing repair cost references across condition lines. A frequent pattern is filtering by RPC_ID to identify all condition lines associated with a given repair cost definition:

  • SELECT id, acd_id, rpc_id, cdn_code, damage_description, estimated_repair_cost, repair_cost, status_desc FROM okl_am_asset_cndtn_lns_uv WHERE rpc_id = :p_rpc_id;
  • SELECT acd_id, SUM(NVL(repair_cost,0)) total_repair FROM okl_am_asset_cndtn_lns_uv GROUP BY acd_id;
  • SELECT id, rpc_org_id, acn_org_id, kle_id FROM okl_am_asset_cndtn_lns_uv WHERE damage_desc IS NOT NULL AND approved_yn = 'Y';

Because the view already resolves lookup descriptions and language-specific text, it is well suited to custom concurrent programs, OBIEE/BIP reports, and integration extracts that need repair-cost and damage details without complex multi-table joins.