Results for “cst_eam_estimation_status”

14 results




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

Overview

The APPS.WIP_EAM_ENTITIES_V view is a consolidated reporting construct within Oracle E-Business Suite that exposes Enterprise Asset Management (EAM) work orders alongside their associated discrete job definitions, asset instances, item attributes, and status descriptions. It is owned by the APPS schema and is built primarily as a join across WIP_ENTITIES and WIP_DISCRETE_JOBS, supplemented by EAM-specific tables and descriptive lookups. The view filters WIP_ENTITIES.ENTITY_TYPE to values 6 and 7, which correspond to the EAM work order entity types, and restricts MAINTENANCE_OBJECT_TYPE to 3, the maintenance object type that denotes an asset instance.

The view's principal role is to present EAM work orders in a reporting-friendly form, translating coded values into human-readable meanings. In this context the column ESTIMATION_STATUS_MEANING is particularly relevant: it is derived from MFG_LOOKUPS using the lookup type CST_EAM_ESTIMATION_STATUS, decoded against WIP_DISCRETE_JOBS.ESTIMATION_STATUS with a default of 1 when no status is set. This permits report and integration consumers to filter or display work orders by their costing/estimation state without decoding lookup codes manually. The view is defined as a UNION ALL of two queries, the second of which repeats the same projection for a distinct set of EAM rows.

Underlying Base Objects

The ETRM documentation lists the following referenced base objects: BOM_DEPARTMENTS (synonym), CSI_ITEM_INSTANCES (synonym), EAM_WORK_ORDER_DETAILS_V (view), FND_MESSAGE (package), MFG_LOOKUPS (view), MTL_PARAMETERS (synonym), MTL_SYSTEM_ITEMS_B (synonym), MTL_SYSTEM_ITEMS_B_KFV (view), WIP_DISCRETE_JOBS (synonym), and WIP_ENTITIES (synonym).

Structurally:

Key Columns

  • WIP_ENTITY_ID, ORGANIZATION_ID, WIP_ENTITY_NAME — the work order identity and organization context.
  • ENTITY_TYPE and ENTITY_TYPE_MEANING — the coded and decoded entity type; only values 6 and 7 are surfaced.
  • PRIMARY_ITEM_ID, ASSET_GROUP_ID, CLASS_CODE, BOM_REVISION, REBUILD_ITEM_ID — asset and job identification attributes.
  • ESTIMATION_STATUS and ESTIMATION_STATUS_MEANING — the raw estimation status code and the corresponding lookup meaning from CST_EAM_ESTIMATION_STATUS, defaulted to code 1.
  • USER_DEFINED_STATUS_ID and WORK_ORDER_STATUS — the EAM user-defined status of the work order.
  • DEPARTMENT_CODE — the owning department code.
  • PRIMARY_UOM_CODE — the primary unit of measure for the item.
  • Instance and serial identifiers: INSTANCE_NUMBER and SERIAL_NUMBER resolved through CSI_ITEM_INSTANCES.
  • Standard audit columns: DATE_CLOSED, LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, and the program/request columns.

Common Use Cases and Queries

Typical usage centers on operational reporting for EAM work orders, status tracking, and asset instance reconciliation. A representative query for status reporting — directly relevant to the estimation_status_meaning search — follows:

  • Listing EAM work orders with their decoded estimation status:
    SELECT WIP_ENTITY_NAME, ENTITY_TYPE_MEANING, ESTIMATION_STATUS, ESTIMATION_STATUS_MEANING, WORK_ORDER_STATUS, DEPARTMENT_CODE FROM APPS.WIP_EAM_ENTITIES_V WHERE ORGANIZATION_ID = :org_id ORDER BY WIP_ENTITY_NAME;
  • Filtering work orders by estimation state, for example those pending estimation:
    SELECT WIP_ENTITY_ID, WIP_ENTITY_NAME, ESTIMATION_STATUS_MEANING FROM APPS.WIP_EAM_ENTITIES_V WHERE ESTIMATION_STATUS_MEANING = 'Pending';
  • Joining to asset instances for serialized reporting by extracting SERIAL_NUMBER and INSTANCE_NUMBER alongside the work order.
  • Auditing job attributes such as CLASS_CODE, BOM_REVISION, and REBUILD_ITEM_ID for rebuild or refurbishment analysis.

Because the view already resolves lookup meanings and restricts to EAM entity types and maintenance object type 3, it is well suited as a direct source for concurrent programs, OBIEE/BI Publisher reports, and integration extracts, avoiding the need to re-implement the underlying lookup joins.