Search Results populate_cto_bom

Overview

MSC_ATP_CTO is an Oracle Applications (APPS) PL/SQL package within the Advanced Supply Chain Planning (ASCP) and Available-to-Promise (ATP) module. Its primary purpose is to support Available-to-Promise processing for Configure-to-Order (CTO) items in Oracle E-Business Suite 12.1.1 and 12.2.2. In a CTO environment, the end product is assembled only after a customer selects specific options and features, which means ATP checks must be evaluated against the underlying mandatory components and their sourcing rules rather than against a pre-defined finished-good inventory. MSC_ATP_CTO provides the logic needed to explode a configured item into its component-level ATP requirements, to gather CTO sources, and to validate that the appropriate Bill of Material structure exists for a valid availability check.

The package is classified as OTHER in the ETRM repository and holds a VALID status. It operates in the APPS schema and is tightly coupled with both the planning-side ATP infrastructure (MRP_ATP_PUB, MRP_ATP_PVT) and the input/output side packages such as MSC_ATP_PROC, MSC_ATP_PUB, MSC_ATP_PVT, MSC_ATP_REQ, MSC_ATP_SUBST, and MSC_ATP_UTILS.

Key Procedures and Functions

• CHECK_LINES_FOR_CTO_ATP — Determines whether ATP processing for CTO items must be performed for the lines in the current working set.
• MATCH_CTO_LINES — Matches CTO demand lines against the corresponding component or configured item records.
• PROCESS_CTO_SOURCES — Applies sourcing rules to CTO components so availability is evaluated against valid suppliers or supply sources.
• GET_MANDATORY_COMPONENTS — Retrieves the mandatory (non-optional) components of a model or configuration, which must be satisfied for ATP success.
• VALIDATE_CTO_SOURCES — Validates that the sourcing information associated with the CTO structure is complete and admissible.
• EXTEND_SOURCES_REC — Extends or expands the sourcing record set to include the additional CTO-related sources.
• POPULATE_CTO_BOM — Populates the CTO Bill of Material working structure (MSC_CTO_BOM) used during ATP evaluation.
• GET_CTO_BOM — Retrieves the CTO BOM definition for the configured item so components can be checked.
• MAINTAIN_OS_SOURCING — Maintains the order-sourcing information for CTO configurations.
• CHECK_BASE_MODEL_FOR_CAP_CHECK — Determines whether the base model should participate in a capacity check.

Tables Accessed

The package reads and writes several key staging and planning tables. MSC_CTO_BOM and MSC_CTO_SOURCES hold the exploded BOM and sourcing structures for configured items. MSC_BOM_COMPONENTS and MSC_OPERATION_COMPONENTS supply component and routing details. MSC_SYSTEM_ITEMS, MSC_ITEM_ID_LID, and MSC_TP_ID_LID provide item and trading-partner identifiers. MSC_TRADING_PARTNERS and MSC_TRADING_PARTNER_SITES provide sourcing/vendor context. MRP_ATP_SCHEDULE_TEMP and MSC_SHIP_SET_TEMP are used as temporary ATP and ship-set working structures, while MSC_CALENDAR_DATES supplies calendar information needed to schedule availability. PLITBLM is a standard PL/SQL index-by table used for intermediate processing.

Usage Notes

MSC_ATP_CTO is invoked indirectly as part of the ATP engine. Oracle ASCP ATP concurrent programs and the online ATP form trigger the calling chain through MSC_ATP_PROC, MSC_ATP_PUB, and MSC_ATP_PVT, which in turn reference this package. The dependency metadata confirms that MSC_ATP_CTO references CTO_OSS_SOURCE_PK, MRP_ATP_PUB, and MRP_ATP_PVT, and is itself referenced by MSC_ATP_PROC, MSC_ATP_PUB, MSC_ATP_PVT, MSC_ATP_REQ, MSC_ATP_SUBST, MSC_ATP_UTILS, and MSC_SCH_WB. Custom code should not call the package directly; instead it should use the public ATP APIs to preserve supported behavior. Because the package is CONFIDENTIAL Oracle proprietary code, it should not be modified, and any changes to CTO sourcing or BOM data should be made through the supported CTO and ATP user interfaces or APIs.