Search Results cst_eam_estimation_status




Overview

APPS.WIP_EAM_CST_HEADER_V is a reporting and integration view in Oracle E-Business Suite (EBS) 12.1.1 and 12.2.2 that consolidates Enterprise Asset Management (EAM) work order cost header information. It joins discrete job records in WIP_DISCRETE_JOBS to their parent entities in WIP_ENTITIES, asset instance data from CSI_ITEM_INSTANCES, department and status lookups, and the EAM work order details view. The view is primarily consumed by costing, maintenance, and estimation reporting flows that must associate cost accumulation with the correct maintenance asset and its parent work order.

The view behaves as a UNION ALL construct, producing two result sets: the first for jobs whose maintenance object type is 3 (a serialized asset instance), returning instance number and serial number, and the second for jobs where the asset is not tied to a specific instance, returning NULL instance columns. This dual structure allows a single query to retrieve cost headers for both asset-instance-backed and non-instance-backed work orders. The column parent_wip_entity_name is of particular interest to users and provides the name of the parent work order entity, derived from WIP_ENTITIES.

Underlying Base Objects

The documented base objects referenced by the view are:

  • WIP_DISCRETE_JOBS (synonym) — the driving table supplying job header attributes such as wip_entity_id, organization_id, primary_item_id, scheduled_completion_date, asset_group_id, rebuild_item_id, estimation_status, and parent_wip_entity_id.
  • WIP_ENTITIES (synonym) — joined via parent_wip_entity_id (outer join, we.wip_entity_id (+)) to supply the parent job name, aliased as parent_wip_entity_name.
  • CSI_ITEM_INSTANCES (synonym) — supplies instance_number and serial_number when the maintenance object is a serialized instance.
  • BOM_DEPARTMENTS (synonym) — external joined to provide the owning_department code.
  • MFG_LOOKUPS (view) — filtered on lookup_type like CST_EAM_ESTIMATION_STATUS to decode estimation_status into a meaning.
  • EAM_WORK_ORDER_DETAILS_V (view) — supplies work order status (job_status) and, in the first branch, the user_defined_status_id.
  • FND_MESSAGE (package) — referenced for message resolution in the view’s dependency chain.

Key Columns

  • wip_entity_id / organization_id — primary identifiers of the EAM work order.
  • job_status — work order status from EAM_WORK_ORDER_DETAILS_V.
  • parent_wip_entity_name — name of the parent work order from WIP_ENTITIES; a key search target for users tracing cost rollups or rebuild relationships.
  • estimation_status / estimation_status meaning — decoded via MFG_LOOKUPS using CST_EAM_ESTIMATION_STATUS.
  • owning_department — department code from BOM_DEPARTMENTS.
  • primary_item_id / rebuild_item_id — item identifiers for the job and its rebuild item.
  • asset_group_id, instance_number, serial_number — asset instance identifiers returned on the instance-backed branch.
  • last_estimation_req_id / last_estimation_date — estimation tracking information.

Common Use Cases and Queries

The view supports EAM costing reports that require parent-child work order relationships and asset serialization context. A typical query to retrieve cost headers with parent work order names is:

SELECT wip_entity_id, organization_id, parent_wip_entity_name,
       job_status, estimation_status, owning_department, serial_number
FROM   apps.wip_eam_cst_header_v
WHERE  parent_wip_entity_name = :parent_name;

Another common scenario filters by organization and estimation status to review estimation activity:

SELECT wip_entity_id, parent_wip_entity_name, last_estimation_date
FROM   apps.wip_eam_cst_header_v
WHERE  organization_id = :org_id
AND    estimation_status = 1;

Because the view is owned by APPS and built on EAM-specific ETRM objects, it should be queried in a read-only fashion and joined to WIP cost tables or CSI asset tables as needed for extended reporting.