Results for “plan_maintenance”

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

Overview

The WIP_JOB_SCHEDULE_INTERFACE table in the WIP (Work in Process) schema is the open interface staging table used to create or modify discrete jobs, repetitive schedules, and related work orders in Oracle E-Business Suite. Rows inserted into this table represent requests that are subsequently processed by the WIP Job and Schedule Interface concurrent program, which validates each record and calls the Work in Process application programming interfaces to create or update the corresponding production entities. The table is central to bulk job creation, external system integration, and mass maintenance scenarios where jobs must be generated or amended without manual entry through the Work in Process forms.

The table operates on a request-processing model. Each row carries an INTERFACE_ID, a PROCESS_PHASE, and a PROCESS_STATUS that together track the lifecycle of the request from initial insertion through validation and final creation. The Data Vault classification heuristic suggests this object functions primarily as a link table, since its foreign key structure binds together organization parameters, accounting classes, bills of material, routings, kanban cards, and existing WIP entities. This classification is a modeling suggestion rather than a fixed architectural rule.

Key Information Stored

The column set numbers 119 in the 12.2.2 documented schema. The most significant columns fall into several functional groups:

• INTERFACE_ID — the surrogate primary key, enforced by unique index WIP_JOB_SCHEDULE_INTERFACE_U1. This is the row-level identifier used by the concurrent program to track processing.
• GROUP_ID, PROCESS_PHASE, PROCESS_STATUS, LOAD_TYPE, STATUS_TYPE — control the interface run, grouping rows submitted in a single batch and recording validation and completion outcomes.
• ORGANIZATION_ID, ORGANIZATION_CODE — identify the manufacturing organization in which the job is created; the foreign key to WIP_PARAMETERS resolves organization-level defaults.
• PRIMARY_ITEM_ID, PRIMARY_ITEM_SEGMENTS, BOM_REFERENCE_ID, ROUTING_REFERENCE_ID — define the assembly being built and its associated bill and routing structures, referencing BOM_STRUCTURES_B and BOM_OPERATIONAL_ROUTINGS.
• ALTERNATE_BOM_DESIGNATOR, ALTERNATE_ROUTING_DESIGNATOR, BOM_REVISION, ROUTING_REVISION — specify which alternate and revision of the structure applies to the job.
• CLASS_CODE — the accounting class assigned to the job, with a foreign key to WIP_ACCOUNTING_CLASSES.
• NET_QUANTITY, START_QUANTITY, FIRST_UNIT_START_DATE, FIRST_UNIT_COMPLETION_DATE, LAST_UNIT_START_DATE, LAST_UNIT_COMPLETION_DATE, DAILY_PRODUCTION_RATE, SCHEDULING_METHOD — carry the scheduling attributes for repetitive and discrete requests.
• WIP_ENTITY_ID, REPETITIVE_SCHEDULE_ID, KANBAN_CARD_ID, SCHEDULE_GROUP_ID, LINE_ID — reference existing entities when the purpose is modification rather than creation.
• COMPLETION_SUBINVENTORY, COMPLETION_LOCATOR_ID, WIP_SUPPLY_TYPE, FIRM_PLANNED_FLAG, PRIORITY, DUE_DATE — supply completion and planning attributes carried onto the resulting job.
• PROJECT_ID, TASK_ID, END_ITEM_UNIT_NUMBER, DEMAND_CLASS, ASSET_NUMBER, ASSET_GROUP_ID, PM_SCHEDULE_ID — support project, unit-number, and Enterprise Asset Management integration, including references to PJM_UNIT_NUMBERS and EAM_PM_SCHEDULINGS.
• ATTRIBUTE1 through ATTRIBUTE15 — the standard descriptive flexfield columns for extensibility.

Common Use Cases and Queries

The principal use case is bulk job creation from an external planning or shop-floor system. Rows are populated with source codes, organization, item, and quantity data, then the WIP Job and Schedule Interface program is launched. A typical diagnostic query identifies rows that failed validation:

SELECT interface_id, organization_code, primary_item_segments, process_status, process_phase FROM wip_job_schedule_interface WHERE group_id = :group_id AND process_status = 'ERROR';

A second scenario retrieves all pending requests for a given organization before processing:

SELECT * FROM wip_job_schedule_interface WHERE organization_id = :org_id AND process_status = 'PENDING';

Reporting use cases include reconciliation of submitted versus successfully created jobs, auditing of interface errors by source system, and tracking of schedule group or kanban-driven requests. Queries frequently join the interface table to WIP_DISCRETE_JOBS and WIP_REPETITIVE_SCHEDULES on the entity identifiers to confirm that jobs were actually created.

Related Objects

The foreign key structure reveals the most significant related objects, all joined on the columns documented below:

• WIP_DISCRETE_JOBS — joined on WIP_ENTITY_ID; the target of discrete job creation and modification requests.
• WIP_REPETITIVE_SCHEDULES — joined on REPETITIVE_SCHEDULE_ID; the target for repetitive schedule requests.
• WIP_PARAMETERS — joined on ORGANIZATION_ID; supplies organization-level WIP defaults.
• WIP_ACCOUNTING_CLASSES — joined on CLASS_CODE and ORGANIZATION_ID; resolves the accounting class attributes.
• BOM_STRUCTURES_B and BOM_OPERATIONAL_ROUTINGS — joined on PRIMARY_ITEM_ID, ORGANIZATION_ID, and the respective alternate designators; resolve the bill and routing references.
• WIP_LINES and WIP_SCHEDULE_GROUPS — joined on LINE_ID and SCHEDULE_GROUP_ID; define production line and scheduling group context.
• MTL_KANBAN_CARDS — joined on KANBAN_CARD_ID; supports kanban replenishment job creation.
• PJM_UNIT_NUMBERS and EAM_PM_SCHEDULINGS — joined on END_ITEM_UNIT_NUMBER and PM_SCHEDULE_ID; support project unit-number and asset maintenance integration.

The primary consumer of this table is the WIP Job and Schedule Interface concurrent program, which reads validated rows and invokes the Work in Process APIs to persist the resulting jobs and schedules.