Results for “operational_status_code”

1 result




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

Overview

The EAM_CHECKED_OUT_ASSETS_V view is an Oracle E-Business Suite dictionary object owned by the APPS schema. In ETRM metadata for release 12.2.2 it is recorded with a status of VALID and classified under the EAM — Enterprise Asset Management product family. The documented description states that the view "provides information of all Checked Out Assets which is used by Oracle Service Management/Depot Repair product."

Functionally, the view publishes the population of asset instances whose custody has been transferred away from the owning organization — typically through an outbound material transaction — so that downstream service, depot repair, and customer-facing processes can identify which units are currently held externally, by whom, and under what return expectations. Because the view projects the complete CSI attribute set, it also acts as a reporting and integration surface for third-party applications that need a single, stable query interface over the checked-out asset population without joining the underlying transaction and parameter tables directly.

Underlying Base Objects

The ETRM documented metadata for this view lists three referenced base objects, all resolved through APPS synonyms:

  • CSI_ITEM_INSTANCES — the primary source of instance-level data. The view text confirms this, since every exposed column carries the CII alias and the row identifier is derived from CII.ROWID.
  • EAM_ASSET_OPERATION_TXN — the asset operation transaction table that records checkout and check-in activity, used to restrict the instance set to assets currently dispatched or otherwise checked out.
  • MTL_PARAMETERS — the inventory organization parameters table, used to qualify instances against valid inventory organizations.

The view therefore does not materialize data; it is a runtime join of instance attributes with operational checkout context.

Key Columns

Because the projection is taken entirely from CSI_ITEM_INSTANCES, the column semantics follow the CSI data model:

Note that asset_criticality_code is not a documented column of this view; criticality is not projected in the ETRM view text, and the search term should be validated against the relevant CSI or asset definition tables rather than assumed present here.

Common Use Cases and Queries

Typical usages include depot repair worklists, overdue return reporting, and integration extracts for external service systems. A representative query follows:

  • SELECT instance_id, serial_number, inventory_item_id, return_by_date, actual_return_date FROM apps.eam_checked_out_assets_v WHERE actual_return_date IS NULL AND return_by_date < SYSDATE; — identifies checked-out assets past their expected return date.
  • SELECT inventory_item_id, COUNT(*) FROM apps.eam_checked_out_assets_v GROUP BY inventory_item_id; — summarizes outstanding checkout volume by item.
  • SELECT instance_id, inventory_item_id, attribute1, attribute2 FROM apps.eam_checked_out_assets_v; — extracts descriptive and extensible attribute data for downstream processing.