Search Results cto_change_order_pk




Overview
Explore in AI Chat

Overview

APPS.CTO_CHANGE_ORDER_PK is a PL/SQL package in the Oracle E-Business Suite Applications schema that supports the Configure-to-Order (CTO) change order process within Oracle Order Management and Oracle Bills of Material. In a CTO environment, customers order configured items whose final structure is determined by selected options and features. Changes to an existing sales order configuration—such as adding or removing options, changing quantities, or modifying a model—must be propagated correctly to dependent supply chain entities, including work orders, reservations, and MRP planning records. This package provides the server-side logic that validates and orchestrates those change activities. In ETRM documentation the package is classified under the generic API category OTHER, indicating it is primarily an internal utility package rather than a published public API. The package is VALID in the APPS schema and is available in both EBS 12.1.1 and 12.2.2, with dependencies on standard Oracle schemas such as SYS, APPS, and FND.

Key Procedures and Functions

The documented package exposes six procedures and functions:

  • CHANGE_NOTIFY — Handles notification logic associated with a change to a configured order line, alerting downstream processes or users that a configuration change has occurred.
  • RESERVATION_EXISTS — Determines whether inventory reservations exist against the affected item or order line, allowing callers to assess the impact of a configuration change before proceeding.
  • START_WORK_FLOW — Initiates the Oracle Workflow process associated with the CTO change order so that approvals or dependent activities are launched.
  • IS_ITEM_ML_OR_MO — Evaluates whether an item is a model or an option (ML/MO), a key determination in CTO configuration validation.
  • DELETE_FROM_REQ_INTERFACE — Removes records from the requisition interface that pertain to the changed configuration, preventing stale supply requests from being processed.
  • GET_USER_NAME — Retrieves the user name from FND_USER for display or audit purposes during change order processing.

The metadata does not document parameter lists; the descriptions above reflect the functional intent implied by each name and its referenced tables.

Tables Accessed

The package reads and writes a range of operational tables via APPS synonyms. FND_USER supplies user identity information used by GET_USER_NAME. MTL_SYSTEM_ITEMS and MTL_SYSTEM_ITEMS_KFV provide item attributes needed to classify models and options and to validate configuration items. OE_ORDER_LINES is central to the change order process, holding the sales order line being modified. BOM_PARAMETERS supplies Bills of Material configuration parameters, while MTL_RESERVATIONS supports the RESERVATION_EXISTS check. MTL_SALES_ORDERS, MRP_SR_ASSIGNMENTS, MRP_SR_RECEIPT_ORG, and MRP_SR_SOURCE_ORG are referenced in the context of supply chain scheduling and sourcing. HZ_CUST_ACCOUNTS and HZ_PARTIES provide customer information, MTL_PLANNERS supports planner lookups, MTL_UNITS_OF_MEASURE supplies UOM validation, and FND_LANGUAGES supports multilingual item descriptions.

Usage Notes

CTO_CHANGE_ORDER_PK is generally invoked indirectly. Within Oracle Order Management, configuration change activities on a sales order trigger the package through the Order Management forms and the configuration utility OE_CONFIG_UTIL, which is documented as referencing this package. CTO_CONFIG_ITEM_PK also references it, confirming that it sits beneath the configuration item layer. Because the package is classified as OTHER rather than as a public API, direct calls from custom code should be approached with caution; customers extending the CTO change order flow typically invoke the higher-level configuration APIs that in turn call this package. Its dependencies on MRP and reservation tables mean it should be executed within the transactional context of the order change, ensuring that notifications, workflow starts, and requisition interface cleanup remain synchronized with the order line update.