Search Results insert_wip_interface

Overview

APPS.CTO_WIP_UTIL is a utility package body in Oracle E-Business Suite that creates work orders for Assemble-to-Order (ATO) configurations. It is part of the Oracle Manufacturing product family and is classified as a utility (UTIL) package. Its central responsibility is to bridge Configure-to-Order sales order demand with Work in Process (WIP) supply by inserting records into the WIP mass load interface for subsequent work order creation.

The package header comment identifies insert_wip_interface as the primary documented entry point. This procedure inserts a record into WIP_JOB_SCHEDULE_INTERFACE so that the WIP_MASS_LOAD process can create work orders for ATO configurations. The package therefore supports the flow from sales order booking and configuration through to discrete job creation and execution on the shop floor.

Key Procedures and Functions

• INSERT_WIP_INTERFACE — Inserts a record into WIP_JOB_SCHEDULE_INTERFACE on behalf of the WIP_MASS_LOAD program so that work orders can be generated for ATO configurations. It is the procedure most directly associated with the user search term and is the package's principal public routine.
• VALIDATE_DELIVERY_ID — Validates a delivery identifier, presumably against WSH delivery data, to ensure that referenced delivery information is legitimate before interface processing proceeds.
• DEPARTURE_PLAN_REQUIRED — Determines whether a departure plan is required for the delivery scenario being processed, supporting partial final assembly shipment (partial FAS) logic that the package history indicates was added in May 2001.
• DELIVERY_PLANNED — Establishes whether the relevant delivery has already been planned, allowing the package to avoid duplicate work order creation or premature interface insertion.

The package header history records multiple corrective fixes, including sourcing WSH delivery details with a source_code of 'OE' to exclude inbound and dropship lines, comparing ordered_quantity rather than ordered quantity minus cancelled quantity, converting ordered quantity to the primary unit of measure before comparing against reserved quantity, and inserting BOM revision information into WIP_JOB_SCHEDULE_INTERFACE. A Multi-Level Supply (ML Supply) feature was also added in December 2002.

Tables Accessed

The package reads and writes a set of manufacturing, order management, and shipping tables, all accessed through APPS synonyms:

• WIP_JOB_SCHEDULE_INTERFACE — The target interface table populated by INSERT_WIP_INTERFACE for WIP_MASS_LOAD.
• BOM_OPERATIONAL_ROUTINGS and BOM_PARAMETERS — Provide routing and BOM parameter defaults used when constructing the interface record.
• BOM_CALENDAR_DATES — Supplies calendar dates, likely for scheduling and departure planning.
• MTL_SYSTEM_ITEMS, MTL_PARAMETERS, and MTL_CUSTOMER_ITEMS — Provide item attributes, organization parameters, and customer item relationships needed to validate and build work order interface rows.
• OE_ORDER_LINES_ALL — Supplies sales order line demand for ATO configurations.
• WIP_PARAMETERS — Provides WIP parameter values such as default work order settings.
• WSH_DELIVERY_ASSIGNMENTS — Links delivery details to deliveries, supporting the delivery validation and partial FAS logic.

Usage Notes

This package is not typically invoked directly by end users. Instead, it is called programmatically by other Oracle applications utilities or by custom extensions that automate ATO work order creation. It is commonly invoked from concurrent program logic or from custom PL/SQL that processes ATO configurations after sales order booking, populating WIP_JOB_SCHEDULE_INTERFACE and then running the WIP_MASS_LOAD concurrent program to create discrete jobs.

Because the package writes to an interface table rather than directly creating work orders, any custom code using it must subsequently invoke WIP_MASS_LOAD and handle interface errors. Callers should also respect the source_code filtering and unit of measure conversion requirements reflected in the package's bug fix history to avoid including inbound or dropship lines or miscalculating reserved quantities. In both 12.1.1 and 12.2.2, the package remains an APPS-owned utility, referenced by at least one other package, and should be treated as internal Oracle functionality subject to change.