Search Results okl_asset_cndtns_all




Overview
Explore in AI Chat

Overview

The table OKL_ASSET_CNDTNS_ALL is a core data object within the Oracle E-Business Suite (EBS) module OKL (Lease and Finance Management). It serves as the primary repository for condition reports associated with leased or financed assets. In the context of asset management and lease servicing, this table is critical for documenting the physical state of an asset at specific points in its lifecycle, such as at lease inception, during periodic inspections, or upon return. Its role is to provide an auditable history of asset conditions, which is essential for maintenance planning, dispute resolution, and determining financial obligations like damage charges or refurbishment costs at lease termination.

Key Information Stored

While the provided metadata does not list specific columns, the table's primary key is the ID column, which uniquely identifies each condition report record. Based on the documented foreign key relationships and its description, the table is designed to store header-level information for a condition report. Key fields typically include identifiers to link the report to the relevant business entities, such as CLM_ID (likely referencing a claim or service request) and KLE_ID (linking the report to a specific lease line in the OKL_K_LINES table). Other common columns in such a structure would include creation dates, report status, the asset identifier, the party responsible for the report, and the date of the condition assessment.

Common Use Cases and Queries

This table is central to asset inspection and condition tracking processes. A primary use case is generating a history of all condition reports for a specific leased asset to track deterioration or damage over time. Another critical scenario is retrieving the initial and final condition reports for a lease line to assess changes and calculate any applicable end-of-lease charges. For reporting, one might join this table to asset and lease line details to produce summaries of asset conditions across a portfolio. A sample query pattern to find condition reports for a lease line would be:

  • SELECT acd.* FROM okl_asset_cndtns_all acd WHERE acd.kle_id = <lease_line_id> ORDER BY acd.creation_date;

Similarly, to find all detailed condition lines for a specific report header, one would join to the related lines table, OKL_AST_CNDTN_LNS_ALL_B.

Related Objects

The table maintains defined relationships with several other key objects in the OKL schema, as per the provided metadata:

  • Primary Key: OKL_ASSET_CNDTNS_ALL_PK on the ID column.
  • Foreign Keys (Outgoing):
    • References OKL_K_LINES via the KLE_ID column, linking the condition report to a specific lease line.
    • References another column within its own table (CLM_ID), which may indicate a hierarchical relationship or a link to a claim identifier.
  • Foreign Keys (Incoming):
    • Referenced by OKL_AST_CNDTN_LNS_ALL_B via the ACD_ID column. This is a critical one-to-many relationship where the header record in OKL_ASSET_CNDTNS_ALL has many detailed condition line items in OKL_AST_CNDTN_LNS_ALL_B.