Search Results create_config_item_wf

Overview

APPS.CTO_WORKFLOW is a manufacturing and order-management PL/SQL package body in Oracle E-Business Suite (documented against 12.2.2, with equivalent behavior in 12.1.1). Its source header (CTOWKFLB.pls) and changelog show it was authored by Oracle Manufacturing to drive the Configure-to-Order (CTO) fulfillment flow. The package encapsulates the workflow-invoked business logic that, given an ATO/PTO configuration line, creates the configuration item, checks inventory reservation status, builds the bill of material and routing, rolls up costs, evaluates supply type, sets lead-time and work-order parameters, and submits concurrent programs. It is a workflow-callable utility (API classification OTHER) rather than a public open interface, and is referenced by seven other packages. The historical bug fixes visible in the header (e.g., 1381938 link-item handling, 1861812 restricting rsv_before_booking_wf to ATO items, 1799874 internal-order demand source, 1874380 ATO under PTO as 'OPTION') confirm its role as the procedural backbone of the CTO ordering workflow.

Key Procedures and Functions

• CREATE_CONFIG_ITEM_WF — creates the configured item for an order line; fixed to handle link items.
• CHECK_RESERVATION_STATUS_WF — the user-referenced procedure; verifies whether reservation exists for the configuration line and returns status used to gate subsequent workflow steps.
• CREATE_RESERVATION — establishes the material reservation for the configured item.
• CREATE_FLOW_SCHEDULE_WF — creates the flow schedule / work order for the configured assembly.
• CALCULATE_COST_ROLLUP_WF_ML — performs multi-language cost rollup for the configuration.
• SET_PARAMETER_LEAD_TIME_WF_ML — sets lead-time parameters during workflow execution.
• CHECK_SUPPLY_TYPE_WF — evaluates supply type for the model line.
• SET_PARAMETER_WORK_ORDER_WF — sets work-order-related workflow parameters.
• SUBMIT_CONC_PROG_WF / SUBMIT_AND_CONTINUE_WF — submit host concurrent programs and continue the workflow.
• VALIDATE_LINE, VALIDATE_CONFIG_LINE, CONFIG_LINE_EXISTS — validate order/configuration lines.
• RESERVATION_EXISTS, CHECK_INV_RSV_EXISTS, CHECK_RSV_EXISTS, RSV_BEFORE_BOOKING_WF, CHK_RSV_AFTER_AFAS_WF — reservation existence and timing checks, including pre-booking and post-AFAS verification.
• FLOW_SCH_EXISTS — checks for existing flow schedules.
• PURCHASE_PRICE_CALC_WF — Buyer/price calculation for buy items.

Tables Accessed

Access is via APPS synonyms. BOM_CTO_ORDER_LINES links configuration model lines. MTL_RESERVATIONS, MTL_SYSTEM_ITEMS, and BOM_OPERATIONAL_ROUTINGS support reservation and BOM/routing creation. Order data comes from OE_ORDER_HEADERS_ALL, OE_ORDER_LINES_ALL, MTL_SALES_ORDERS, and transaction type tables (OE_TRANSACTION_TYPES_ALL/TL). WIP_FLOW_SCHEDULES, WIP_JOB_SCHEDULE_INTERFACE, and WIP_INTERFACE_ERRORS handle flow scheduling and error reporting. FND_USER and FND_LANGUAGES provide user and multi-language context.

Usage Notes

CTO_WORKFLOW procedures are invoked from the CTO order workflow (hence the _WF suffix) rather than directly from forms. They execute when a configured order line is entered and processed in Order Management, or when flow schedules are generated for ATO/PTO items. RSV_BEFORE_BOOKING_WF is gated to ATO items only (bug 1861812). Internal orders and ATO assemblies nested beneath a PTO (item_type_code = 'OPTION') are handled explicitly. Because the package is referenced by other packages and its procedures are not a supported open interface, custom code should not call them directly; extensions should follow Oracle's CTO workflow rather than bypassing it.