Search Results wip_job_dtls_interface

Overview

WIP_JOB_DTLS_INTERFACE is a Work in Process (WIP) open interface table in the Oracle EBS schema WIP. It serves as the staging and processing surface for requests to add, delete, or modify material and resource requirements for discrete jobs and repetitive schedules. Rows written to this table are consumed by the WIP open interface concurrent programs, which validate the requested changes and apply them to the corresponding job or schedule in the live WIP tables (WIP_DISCRETE_JOBS, WIP_REQUIREMENT_OPERATIONS, WIP_OPERATIONS, and related resources/material tables).

The table is transactional in nature and follows the classic Oracle open-interface pattern: it enables bulk loading, mass maintenance, or programmatic modification of job detail records without directly touching the transactional WIP entities. Each logical change is staged against a WIP entity (job or schedule) identified by WIP_ENTITY_ID, with an associated GROUP_ID and REQUEST_ID tracking the processing batch.

From a modeling perspective, the heuristic Data Vault classification mined from the FK structure is standalone. No foreign keys to a parent hub are declared within the interface itself; instead it acts as a staging/link-like artifact that references multiple conformed dimensions (employee/owner, organization, department, activity, standard operation, setup, inventory item) by surrogate column identifiers. In Data Vault terms it is best modeled as a satellite-style staging table or, given its role connecting jobs to resource and material changes, a candidate link between the WIP job hub and the resource/item dimensions.

Key Information Stored

WIP_JOB_DTLS_INTERFACE contains 92 documented columns in the ETRM 12.2.2 physical schema. The most significant are:

• INTERFACE_ID — surrogate primary key, uniquely identifying each staged row; the natural candidate for the table's unique index.
• GROUP_ID — batch/grouping key used by the interface program to process related rows together.
• WIP_ENTITY_ID — the target job or schedule to which the change applies.
• ORGANIZATION_ID — owning inventory organization.
• OPERATION_SEQ_NUM / RESOURCE_SEQ_NUM — identifies the operation and resource row to be added, modified, or deleted.
• RESOURCE_ID_OLD / RESOURCE_ID_NEW — resource being replaced versus the replacement (modify/resource substitution).
• INVENTORY_ITEM_ID_OLD / INVENTORY_ITEM_ID_NEW — component item being replaced versus the replacement.
• QUANTITY_PER_ASSEMBLY / REQUIRED_QUANTITY — material requirement quantity fields.
• USAGE_RATE_OR_AMOUNT / ASSIGNED_UNITS — resource usage and assignment quantities.
• DEPARTMENT_ID — department context, FK to BOM_DEPARTMENTS.
• STANDARD_OPERATION_ID — FK to WSM_OPERATION_DETAILS.
• SETUP_ID — FK to BOM_SETUP_TYPES.
• LOAD_TYPE / PROCESS_PHASE / PROCESS_STATUS — control columns driving whether a row is processed and its current state.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — standard audit columns.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID — concurrent program provenance for traceability.

Business-key candidates center on the combination (GROUP_ID, WIP_ENTITY_ID, OPERATION_SEQ_NUM, RESOURCE_SEQ_NUM); INTERFACE_ID is the surrogate.

Common Use Cases and Queries

Typical uses include mass-updating resource requirements across many jobs, loading component additions from an external planning system, or programmatically swapping resources/items. A common debugging query inspects unprocessed rows:

• SELECT interface_id, group_id, wip_entity_id, organization_id, operation_seq_num, resource_seq_num, load_type, process_status FROM wip.wip_job_dtls_interface WHERE group_id = :group_id AND process_status IS NULL;
• Reporting on pending changes by request: SELECT request_id, COUNT(*) FROM wip.wip_job_dtls_interface WHERE request_id = :req GROUP BY request_id;
• Reconciling item substitutions: SELECT wip_entity_id, inventory_item_id_old, inventory_item_id_new FROM wip.wip_job_dtls_interface WHERE inventory_item_id_new IS NOT NULL;

Reporting use cases include tracking resource assignment changes, material addition/deletion audit trails, and open-interface processing status dashboards.

Related Objects

• BOM_DEPARTMENTS — joined on DEPARTMENT_ID.
• WSM_OPERATION_DETAILS — joined on STANDARD_OPERATION_ID.
• BOM_SETUP_TYPES — joined on SETUP_ID.
• WIP_DISCRETE_JOBS / WIP_ENTITIES — target job being modified, joined on WIP_ENTITY_ID.
• MTL_SYSTEM_ITEMS_B — resolved from INVENTORY_ITEM_ID_OLD / _NEW.
• BOM_RESOURCES — resolved from RESOURCE_ID_OLD / _NEW.
• FND_CONCURRENT_REQUESTS / FND_CONCURRENT_PROGRAMS — via REQUEST_ID, PROGRAM_ID.
• WIP_MOVE_TXN_INTERFACE / WIP_JOB_SCHEDULE_INTERFACE — companion WIP open interfaces in the same processing family.