Search Results configuration_created_for_pto

Overview

APPS.CTO_WORKFLOW_API_PK is the central PL/SQL package body within Oracle E-Business Suite that bridges Oracle Configurator / Configure-to-Order (CTO) processing with the Oracle Workflow engine. Its stated purpose, per the header of CTOWFAPB.pls, is to "contain all CTO and WF related APIs." The package operates primarily in the Oracle Order Management and Oracle Manufacturing domains, governing the lifecycle of configured models and their option items as they move through order entry, reservation, fulfillment, and procurement. It is closely tied to the Processing Constraints Framework provided by Oracle Order Entry (OE), which invokes one of its APIs to verify whether a configured item (model) has already been created before permitting subsequent changes. Because configured items spawn child lines, workflow activities, and dependent supply documents, this package acts as the authoritative arbiter of configuration state, ensuring that order lines, workflows, reservations, and purchase requisitions remain synchronized. The package is owned by APPS and is classified under the OTHER API category in ETRM. It is referenced by ten other database packages, confirming its role as a shared dependency rather than a standalone utility.

Key Procedures and Functions

The package exposes nineteen documented procedures and functions, organized functionally as follows.

• Workflow status inquiry: QUERY_WF_ACTIVITY_STATUS, GET_ACTIVITY_STATUS, and DISPLAY_WF_STATUS retrieve and present the state of workflow activities associated with a configured item. DISPLAY_WF_STATUS is of particular note — it appears in the package history as having been modified for multiple bug fixes (including bug#1895563 and bug#1874380), and it is the object most commonly associated with the search term "display_wf_status." It provides a diagnostic view of where a configuration currently sits in its workflow lifecycle.
• Workflow progression: COMPLETE_ACTIVITY, START_MODEL_WORKFLOW, and CHANGE_STATUS_BATCH drive workflow activities to completion, initiate the model's workflow, and perform batch status transitions respectively.
• Configuration state checks: CONFIGURATION_ITEM_CREATED, CONFIGURATION_CREATED, and CONFIGURATION_CREATED_FOR_PTO determine whether a configuration has been instantiated, including the specific case of an ATO item nested under a PTO. The header history explicitly documents the PTO nesting fix (bug#1874380), where an ATO item under a PTO carries item_type_code 'OPTION' and a non-null top_model_line_id, unlike a standard ATO order.
• Reservation handling: INVENTORY_RESERVATION_CHECK, WF_UPDATE_AFTER_INV_RESERV, INVENTORY_UNRESERVATION_CHECK, WF_UPDATE_AFTER_INV_UNRESERV, and RESERVATION_EXISTS validate and propagate inventory reservation and unreservation events back into workflow state.
• Line and model utilities: UPDATE_CONFIG_LINE, TOP_ATO_MODEL, and CONFIG_LINE assist in resolving and updating configuration line hierarchies.
• Procurement integration: AUTO_CREATE_PUR_REQ and CHK_BUY_ATO_ITEM support the automatic creation of purchase requisitions for buy-configured ATO items.

Tables Accessed

The package reads and writes a broad set of base tables through APPS synonyms, deliberately avoiding expensive views such as WSH_DELIVERY_LINE_STATUS_V (per the bug#1876997 change). Workflow state is read from WF_ITEM_ACTIVITY_STATUSES and WF_PROCESS_ACTIVITIES. Order and configuration data come from OE_ORDER_HEADERS_ALL, OE_ORDER_LINES, and OE_ORDER_LINES_ALL. Inventory and item validation touch MTL_SYSTEM_ITEMS and MTL_RESERVATIONS. Procurement logic references PO_HEADERS_ALL, PO_LINES_ALL, PO_REQUISITIONS_INTERFACE_ALL, and OE_DROP_SHIP_SOURCES. Manufacturing scheduling data is drawn from WIP_FLOW_SCHEDULES. FND_CONCURRENT_PROGRAMS supports concurrent program lookups, while DUAL and PLITBLM serve as utility and temporary storage references.

Usage Notes

CTO_WORKFLOW_API_PK is typically invoked indirectly rather than by end users. Oracle Order Management's Processing Constraints Framework calls CONFIGURATION_ITEM_CREATED to gate changes on configured lines. Inventory reservation and unreservation transactions trigger the WF_UPDATE_AFTER_INV_RESERV and WF_UPDATE_AFTER_INV_UNRESERV callbacks. Concurrent programs may invoke CHANGE_STATUS_BATCH for bulk workflow transitions. DISPLAY_WF_STATUS is frequently used by support and technical teams during troubleshooting to render the workflow status of a configuration, which explains its prominence in search queries. Custom extensions should call these documented APIs rather than manipulating workflow or order tables directly, since the package encapsulates the intricate logic relating configured models, option items under PTO structures, reservations, and buy-item requisitions.