Search Results check_common_bom




Overview
Explore in AI Chat

Overview

CTO_DEACTIVATE_CONFIG_PK is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified under the OTHER API category. It supports the Configure-to-Order (CTO) subsystem by providing the logic required to deactivate ATO (Assemble-to-Order) configuration items that are no longer active, and to verify whether the supporting bills, routings, and item statuses permit safe deletion or deactivation. In Oracle EBS 12.1.1 and 12.2.2, this package addresses the lifecycle management of configuration models and their associated option items after they have been used on orders. Its procedures examine inventory conditions, manufacturing structures, and CTO sourcing relationships before allowing a configuration to be retired, thereby protecting referential integrity across order management, inventory, and bills of material tables.

Key Procedures and Functions

  • CTO_DEACTIVATE_CONFIGURATION — The primary driver procedure. It accepts organization, model, configuration, option item, and numeric-day parameters along with user and login context, then performs the deactivation workflow for a specified configuration. It is invoked in a concurrent-processing pattern, returning errbuf and retcode to signal completion status to the concurrent manager.
  • CHECK_DELETE_STATUS — Evaluates whether an inventory item within a given organization is in a delete status that would block deactivation. It returns a status code through an OUT parameter so that callers can branch accordingly.
  • CHECK_COMMON_ROUTING — Determines whether a common routing exists for the inventory item and organization, which influences whether configuration deactivation can proceed without breaking manufacturing structures.
  • CHECK_COMMON_BOM — Performs the analogous verification for a common bill of material, confirming that deactivation will not corrupt shared BOM definitions.

Tables Accessed

The package reads and writes a broad set of CTO, inventory, and manufacturing tables through APPS synonyms. BOM_ATO_CONFIGURATIONS and BOM_CTO_MODEL_ORGS anchor configuration and model-organization relationships, while BOM_CTO_ORDER_LINES and BOM_CTO_SRC_ORGS_B supply order-line and sourcing context. Routing checks draw on BOM_OPERATIONAL_ROUTINGS and BOM_OPERATION_SEQUENCES, and BOM_PARAMETERS supplies BOM profile settings. Inventory and item checks rely on MTL_SYSTEM_ITEMS, MTL_SYSTEM_ITEMS_KFV, MTL_ITEM_ATTRIBUTES, MTL_PARAMETERS, MTL_MATERIAL_TRANSACTIONS, MTL_PENDING_ITEM_STATUS, MTL_RESERVATIONS, and MTL_RESERVATIONS_INTERFACE. Together these tables support delete-status validation and reservation verification before a configuration is retired.

Usage Notes

This package is typically invoked from CTO-related concurrent programs and Oracle Forms that manage configuration deactivation, and it can be called from custom PL/SQL when administrators need to retire ATO configurations. The gDebugLevel global is initialized from the profile option ONT_DEBUG_LEVEL via FND_PROFILE.value at package load, so diagnostic output is controlled by that Order Management profile setting. Because the package is referenced by zero other packages, it functions as a standalone utility rather than a shared dependency. The header indicates a last revision in 2005, and the same source is documented for both 12.1.1 and 12.2.2, so behavior is consistent across those releases.