Search Results flow_sch_exists

Overview

APPS.CTO_WORKFLOW is the Oracle Manufacturing PL/SQL package that implements the workflow-facing interface for Configure-to-Order (CTO) and Assemble-to-Order (ATO) processing in Oracle E-Business Suite Release 12.1.1 and 12.2.2. Its header identifies the source file as CTOWKFLS.pls and states that the package creates procedures invoked for each ATO Workflow activity. In other words, the package acts as the bridge between the Oracle Workflow engine and the underlying BOM configuration, reservation, and scheduling APIs.

During an ATO sales order lifecycle, workflow activities must match a customer-selected configuration to a valid model, reserve the configured items, create routing and flow schedule records, calculate lead times and costs, and validate that prerequisites such as reservations exist. CTO_WORKFLOW exposes discrete entry points for each of these activities, delegating the substantive business logic to packages such as BOM_CTO_WF_API and BOM_MATCH_CONFIG while controlling flow direction, error handling, and workflow state updates. The package is classified as OTHER in the ETRM metadata and is referenced by seven other packages, confirming its role as a shared integration layer rather than a standalone application component.

Key Procedures and Functions

The ETRM metadata documents twenty-two procedures and functions. Their principal groupings are as follows.

• Configuration creation and matching: CREATE_CONFIG_ITEM_WF is the earliest documented entry point, taking the workflow item type, item key, activity ID, and function mode. It supports creation of the configured item instance associated with the order line.
• Reservation processing: CREATE_RESERVATION, CHECK_RESERVATION_STATUS_WF, RESERVATION_EXISTS, CHECK_INV_RSV_EXISTS, CHECK_RSV_EXISTS, RSV_BEFORE_BOOKING_WF, and CHK_RSV_AFTER_AFAS_WF collectively create reservations, test whether inventory or supply reservations already exist, and validate reservation state before and after booking and after AutoCreate Final Assembly Schedule (AFAS). The CHK_RSV_AFTER_AFAS_WF node was added per bug 2327972 to insert a warning-path check after the autocreate FAS activity.
• Scheduling and work order flow: CREATE_FLOW_SCHEDULE_WF, FLOW_SCH_EXISTS, SET_PARAMETER_WORK_ORDER_WF, and CHECK_SUPPLY_TYPE_WF create repetitive flow schedules, test for their existence, and set workflow parameters relating to work orders and supply type.
• Costing and lead time: CALCULATE_COST_ROLLUP_WF_ML and SET_PARAMETER_LEAD_TIME_WF_ML handle cost rollup and lead-time parameter assignment in a multi-lingual context.
• Line validation: VALIDATE_LINE, VALIDATE_CONFIG_LINE, and CONFIG_LINE_EXISTS verify that an order line and its configuration are eligible for the requested activity.
• Concurrent and pricing utilities: SUBMIT_CONC_PROG_WF and SUBMIT_AND_CONTINUE_WF submit concurrent programs from workflow, while PURCHASE_PRICE_CALC_WF derives purchase price information during configuration processing.

Procedure set_parameter_lead_time_wf was removed at version 120.1 per bug 3202825, and a NOCOPY hint was applied to all OUT parameters in June 2005.

Tables Accessed

The package reads and writes through APPS synonyms. Order and configuration data reside in OE_ORDER_HEADERS_ALL, OE_ORDER_LINES, OE_ORDER_LINES_ALL, OE_TRANSACTION_TYPES_ALL, and OE_TRANSACTION_TYPES_TL, together with BOM_CTO_ORDER_LINES for CTO-specific line attributes. Reservation and inventory information is held in MTL_RESERVATIONS, MTL_SYSTEM_ITEMS, and MTL_SALES_ORDERS. Manufacturing scheduling touches WIP_FLOW_SCHEDULES, WIP_JOB_SCHEDULE_INTERFACE, WIP_INTERFACE_ERRORS, and BOM_OPERATIONAL_ROUTINGS. FND_USER and FND_LANGUAGES supply the session user and language context.

Usage Notes

CTO_WORKFLOW is not intended for direct invocation by end users. It is called by the Oracle Workflow engine as the ATO order process executes each function and notification activity, with the order line identifier normally supplied as the workflow item key. Because the package is public and referenced by seven other PL/SQL units, it may also be called from custom workflow definitions or extensions that add or reorder ATO activities. In all cases, callers must supply a valid workflow item type and activity context, and should treat the underlying table writes as part of the standard order-to-manufacturing transaction, subject to the same validation and error-handling rules as Oracle's seeded ATO process.