Search Results wip_entity

Overview

The APPS.WIP_EAM_ENTITIES_V view is an Oracle Work in Process (WIP) reporting construct that consolidates Enterprise Asset Management (EAM) work order information into a single, denormalized result set. It exposes work order header attributes drawn from WIP_ENTITIES and WIP_DISCRETE_JOBS, enriched with lookup meanings, item definitions, asset instance details, department codes, and user-defined work order status. Because EAM work orders are stored as WIP entities of type 6 and 7, the view filters on those entity types, restricting its output to EAM-specific activities rather than standard discrete manufacturing jobs.

In Oracle EBS 12.1.1 and 12.2.2 the view serves as a reporting and integration layer. Developers building custom reports, Discoverer workbooks, or interfaces against EAM data can query a single view rather than joining a dozen base tables. Its DISTINCT semantics and UNION ALL composition reflect a design intent to present asset-related work orders uniformly, including estimated and rebuilt item scenarios. The view is owned by APPS and is marked VALID in the ETRM repository.

Underlying Base Objects

The documented referenced base objects include WIP_ENTITIES and WIP_DISCRETE_JOBS (both accessed via synonyms), which supply the core work order header and discrete job attributes. Item context is derived from MTL_SYSTEM_ITEMS_B (synonym) and MTL_SYSTEM_ITEMS_B_KFV, a key flexfield view providing concatenated item identification. Asset instance detail comes from CSI_ITEM_INSTANCES, joined to associate the maintenance object with its installed base record. Organization-level maintenance parameters are resolved through MTL_PARAMETERS.

Decoding of entity type and estimation status is performed against MFG_LOOKUPS (a view over lookup values). Department ownership is resolved via BOM_DEPARTMENTS. The EAM_WORK_ORDER_DETAILS_V view supplies user-defined status identifiers and work order status text, while FND_MESSAGE (a package) is referenced for message retrieval. The joins are predominantly outer joins on item and department, ensuring work orders without complete item or department references still appear.

Key Columns

• WIP_ENTITY_ID / ORGANIZATION_ID — Composite key identifying the work order within its inventory organization.
• WIP_ENTITY_NAME / DESCRIPTION — Work order number and descriptive text.
• ENTITY_TYPE / ENTITY_TYPE_MEANING — Numeric entity type (6 or 7) and its decoded lookup meaning.
• PRIMARY_ITEM_ID / CLASS_CODE / BOM_REVISION — Item being maintained, its class, and applicable bill revision.
• ASSET_GROUP_ID — Asset group associated with the maintenance activity.
• INSTANCE_NUMBER / SERIAL_NUMBER — Asset instance number (populated per EAM item type) and serial number from CSI_ITEM_INSTANCES.
• DEPARTMENT_CODE — Owning department of the work order.
• USER_DEFINED_STATUS_ID / WORK_ORDER_STATUS — EAM user-defined status and its textual value.
• PRIMARY_UOM_CODE — Primary unit of measure for the item.
• DATE_CLOSED / ESTIMATION_STATUS_MEANING — Closure date and decoded estimation status.
• Audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, REQUEST_ID, PROGRAM_ID, and related columns.
• REBUILD_ITEM_ID — Item resulting from a rebuild activity.

Common Use Cases and Queries

Typical scenarios include EAM work order status reporting, asset maintenance history, and maintenance cost or estimation tracking. A representative query lists open work orders for an organization:

• SELECT wip_entity_name, work_order_status, department_code FROM wip_eam_entities_v WHERE organization_id = :org AND date_closed IS NULL;
• SELECT instance_number, serial_number, primary_item_id, estimation_status_meaning FROM wip_eam_entities_v WHERE entity_type = 6;
• SELECT wip_entity_id, asset_group_id, class_code, rebuild_item_id FROM wip_eam_entities_v WHERE date_closed BETWEEN :from AND :to;

Because the view performs DISTINCT with UNION ALL branches, queries returning many rows across large organizations may benefit from filtering on ORGANIZATION_ID, WIP_ENTITY_ID, or DATE_CLOSED to constrain the underlying joins.