Search Results wip_indicators_temp




Overview
Explore in AI Chat

Overview

WIP_INDICATORS_TEMP is a temporary working table owned by the WIP schema in Oracle E-Business Suite Work in Process. As its name and the ETRM description indicate, it is used to calculate production indicators from transaction information — typically as an intermediate staging area populated by a concurrent program or report before results are aggregated, displayed, or written elsewhere. It is not a transactional base table; it holds transient rows that support indicator computations for discrete and repetitive manufacturing resources, departments, and operations.

The Data Vault classification heuristic mined from the foreign key structure labels this table as standalone. In modeling terms, this suggests it functions neither as a hub nor as a link in a dimensional sense, but rather as a transient staging or work structure. The only documented foreign key, DEPARTMENT_ID → BOM_DEPARTMENTS, gives it a single, weak business reference; the table's real identity is tied to the WIP execution context (organization, entity, operation, resource) rather than to a persistent business key.

Key Information Stored

The table exposes 35 documented columns in the 12.2.2 ETRM schema. The most operationally significant are:

Common Use Cases and Queries

Typical queries filter by GROUP_ID (the run partition) and ORGANIZATION_ID to isolate a single indicator computation, and join to WIP_ENTITIES or BOM_DEPARTMENTS to resolve names.

SELECT w.group_id, w.organization_id, w.wip_entity_id,
       w.department_code, w.resource_code, w.transaction_date,
       w.standard_quantity, w.total_quantity, w.scrap_quantity,
       w.applied_units_prd, w.resource_cost
FROM   wip.wip_indicators_temp w
WHERE  w.group_id = :group_id
AND    w.organization_id = :org_id
ORDER  BY w.department_code, w.resource_code;

Because the table is populated by a concurrent request, the REQUEST_ID and PROGRAM_ID columns allow correlation back to the specific program invocation. Reporting solutions frequently use it as a source for resource efficiency, scrap, and utilization extracts, joining to BOM_DEPARTMENTS on DEPARTMENT_ID. In custom logic, it is safest to treat it as read-only after the populating program completes, since its contents are transient.

Related Objects

  • BOM_DEPARTMENTS — the sole documented foreign key target, joined via WIP_INDICATORS_TEMP.DEPARTMENT_ID = BOM_DEPARTMENTS.DEPARTMENT_ID.
  • WIP_ENTITIES — resolves WIP_ENTITY_ID to the work order header.
  • WIP_OPERATIONS — correlates OPERATION_SEQ_NUM to routing steps.
  • BOM_RESOURCES — resolves RESOURCE_ID / RESOURCE_CODE.
  • WIP_TRANSACTIONS — the source transaction data aggregated into indicators.
  • WIP_MOVE_TXN_INTERFACE / WIP_COST_TXN_INTERFACE — related transaction staging structures in the same module.
  • FND_CONCURRENT_REQUESTS — correlates REQUEST_ID to the populating concurrent program.

These relationships reflect the table's role as a temporary computational surface rather than a persistent entity, and its business meaning derives almost entirely from the WIP execution tables with which it is queried.