Search Results cto_wip_util




Overview
Explore in AI Chat

Overview

CTO_WIP_UTIL is a utility package owned by APPS that supports the Configure-to-Order (CTO) and Assemble-to-Order (ATO) manufacturing flows in Oracle E-Business Suite 12.1.1 and 12.2.2. Its principal responsibility is to bridge the gap between order management and work order creation by populating the WIP_JOB_SCHEDULE_INTERFACE table so that the WIP Mass Load concurrent program can subsequently create discrete work orders for ATO configurations. The header comment in the source file (CTOWIPUS.pls, version 120.1) states explicitly that the package "creates the utilities that are required to create work orders for ATO configurations."

Rather than creating work orders directly through the WIP APIs, CTO_WIP_UTIL inserts staging rows into the interface table consumed by WIP_MASS_LOAD. This indirect approach reuses the standard WIP Mass Load validation and processing logic, ensuring consistent application of WIP parameters, routing, and scheduling rules. The package is declared AUTHID CURRENT_USER, meaning it executes with the privileges of the calling schema.

Key Procedures and Functions

  • INSERT_WIP_INTERFACE — The core procedure documented in the source excerpt. It inserts a single record into the WIP_JOB_SCHEDULE_INTERFACE table for creation of work orders. Parameters include the line identifier of the configuration item in OE_ORDER_LINES, a WIP sequence/group identifier used in the interface table, status and class code values, and several concurrent program context parameters (request ID, program ID, login ID, user ID, application concurrent program ID). It returns a status indicator along with error message and message name outputs for error handling.
  • VALIDATE_DELIVERY_ID — Validates a delivery identifier, supporting the linkage between order lines and shipping/delivery information relevant to the ATO fulfillment flow.
  • DEPARTURE_PLAN_REQUIRED — Determines whether a departure plan is required for the configuration, based on shipping and calendar considerations.
  • DELIVERY_PLANNED — Indicates whether delivery has already been planned, allowing calling code to avoid redundant planning or interface inserts.

Tables Accessed

  • WIP_JOB_SCHEDULE_INTERFACE — The primary write target. Rows inserted here are processed by WIP_MASS_LOAD to create discrete jobs.
  • OE_ORDER_LINES_ALL — Read to identify the model/configuration line from which work orders are derived.
  • MTL_SYSTEM_ITEMS and MTL_PARAMETERS — Provide item attribute and organization-level defaults used when staging the interface record.
  • MTL_CUSTOMER_ITEMS — Supplies customer item cross-reference information for ATO configurations.
  • BOM_OPERATIONAL_ROUTINGS, BOM_PARAMETERS, and BOM_CALENDAR_DATES — Supply routing, bill parameter, and calendar date data needed for scheduling and departure planning decisions.
  • WIP_PARAMETERS — WIP module defaults influencing job creation and scheduling rules.
  • WSH_DELIVERY_ASSIGNMENTS — Links deliveries to order lines, supporting the delivery validation and planning functions.

Usage Notes

CTO_WIP_UTIL is an internal utility (API classification: UTIL) rather than a public application programming interface. It is most commonly invoked from order management workflows, specifically the ATO/CTO work order creation process, and from concurrent programs that stage jobs for WIP Mass Load. The reference by one other package in the ETRM metadata confirms its role as a dependent utility rather than a top-level entry point.

Because INSERT_WIP_INTERFACE writes directly into WIP_JOB_SCHEDULE_INTERFACE, the rows it creates are not visible as work orders until WIP_MASS_LOAD runs and completes successfully. Custom code invoking this package must respect the concurrent program context parameters and should check the returned status and error message outputs before assuming success. Error handling was noted as incomplete in the original source comments, so callers should implement their own exception handling. As an AUTHID CURRENT_USER package referencing APPS synonyms, execution context and grants must be verified when calling from custom schemas.