Search Results auto_create_pur_req

Overview

APPS.CTO_WORKFLOW_API_PK is a configuration-to-order (CTO) workflow application programming interface package that centralizes Oracle Workflow interactions for the Configure-to-Order process in Oracle E-Business Suite Release 12.1.1 and 12.2.2. Its documented API classification is OTHER, placing it among the internal engine packages rather than the public, fully documented Open Interfaces. In EBS, CTO workflows drive the orchestration of configure-to-order activities: ATO/PTO model configuration, item creation and change propagation, inventory reservation checks, procurement requisition generation, and status transitions across order and work-in-process workflows.

Rather than scattering direct calls to the Workflow Engine (WF_ITEM_ACTIVITY_STATUSES, WF_PROCESS_ACTIVITIES) throughout the CTO suite, the application consolidates them here. This package is central to that design: the dependency metadata confirms that it is referenced by ten other packages, including the auto dropship, auto procure, change order, manual link configuration, match-and-reserve, order management workflow API, WIP workflow API, and reservation processing packages, as well as by CTO_WORKFLOW itself. It exposes nineteen documented procedures and functions, making it the principal integration point between CTO business logic and the Oracle Workflow runtime.

Key Procedures and Functions

The documented procedures span four functional groupings. Workflow status and completion utilities include QUERY_WF_ACTIVITY_STATUS and GET_ACTIVITY_STATUS, which retrieve the current state of a workflow activity; DISPLAY_WF_STATUS, which surfaces that status for inspection or error reporting; and COMPLETE_ACTIVITY, which marks a workflow activity complete and thereby advances the process. These are the core mechanisms by which CTO processes signal progress to the Workflow Engine.

Configuration lifecycle handlers include CONFIGURATION_ITEM_CREATED, CONFIGURATION_CREATED, CONFIGURATION_CREATED_FOR_PTO, TOP_ATO_MODEL, CONFIG_LINE, and UPDATE_CONFIG_LINE. Collectively these routines respond to the creation of configured items and models — distinguishing the ATO top-level model from the PTO variant — and manage the configuration line records associated with a configured order line. CHANGE_STATUS_BATCH provides batch status movement, useful when many configuration lines must be transitioned together.

Inventory and reservation routines include INVENTORY_RESERVATION_CHECK, INVENTORY_UNRESERVATION_CHECK, WF_UPDATE_AFTER_INV_RESERV, WF_UPDATE_AFTER_INV_UNRESERV, and RESERVATION_EXISTS. These check and confirm the reservation state of configuration items and then synchronize workflow state after a reservation or unreservation event, keeping the workflow aligned with supply-chain reality.

Procurement and launch routines include START_MODEL_WORKFLOW, which instantiates the process for a model; AUTO_CREATE_PUR_REQ, which drives automatic requisition creation; and CHK_BUY_ATO_ITEM, which determines whether an ATO item is a buy item subject to procurement.

Tables Accessed

The package interacts with tables across several EBS schemas through APPS synonyms. Workflow runtime tables WF_ITEM_ACTIVITY_STATUSES and WF_PROCESS_ACTIVITIES are read and updated to query, display, and complete workflow activities. Order data is drawn from OE_ORDER_HEADERS_ALL and OE_ORDER_LINES_ALL and the OE_ORDER_LINES view, supporting configuration line handling and status updates. Inventory and reservation logic uses MTL_RESERVATIONS, MTL_SYSTEM_ITEMS, and WIP_FLOW_SCHEDULES, confirming reservation existence and checking item attributes and flow schedule status. Procurement operations reference PO_REQUISITIONS_INTERFACE_ALL, PO_HEADERS_ALL, and PO_LINES_ALL when automatically creating requisitions for buy ATO items, with OE_DROP_SHIP_SOURCES identifying drop-ship capable sources. FND_CONCURRENT_PROGRAMS supports concurrent program lookups, and DUAL, PLITBLM, and SYS.STANDARD are used for standard PL/SQL and utility operations.

Usage Notes

CTO_WORKFLOW_API_PK is normally invoked indirectly. It is called by the CTO configuration, procurement, dropship, reservation, change order, and OM/WIP workflow packages rather than directly by end users; the dependency listing shows ten dependent packages. It is therefore executed during order entry and order management workflow processing, when configured items are created or reserved, when automatic requisition generation runs, and when configured lines change status through batch or concurrent processes. Customizations should avoid modifying this package and should instead call the documented procedures or the higher-level business APIs that wrap it. Because the package is VALID and owned by APPS, its behavior is covered by Oracle support under the EBS 12.1.1 and 12.2.2 code lines, and it should be treated as an internal component of the CTO workflow infrastructure.