Search Results get_cto_bom

Overview

MSC_ATP_CTO is an Oracle Advanced Supply Chain Planning and Order Management utility package that performs Configure-to-Order (CTO) available-to-promise processing. Its principal role is to interpret configured item structures — mandatory components, option classes, and option-dependent sourcing rules — so that ATP and capable-to-promise (CTP) calculations reflect the true buildability and sourcing of a configured item rather than treating the configuration as a single undifferentiated item. The package body is owned by APPS and is classified as an OTHER API, indicating that it is an internal support package not intended as a published integration interface.

The package operates tightly with the ATP stack, notably MRP_ATP_PUB (ATP record, supply/demand, period, and detail types) and MSC_ATP_UTILS, which stages request data into MRP_ATP_SCHEDULE_TEMP. The header indicates a shipped file (MSCCTOPB.pls, 120.9) and supports a debug facility driven by the MSC_ATP_DEBUG profile option, with trace output written through MSC_SCH_WB.ATP_DEBUG.

Key Procedures and Functions

• CHECK_LINES_FOR_CTO_ATP — Entry point for CTO ATP evaluation. It moves the ATP record into the temporary scheduling table via MSC_ATP_UTILS.PUT_INTO_TEMP_TABLE (REQUEST_MODE), then drives matching of CTO lines, except when the calling module is the specific internal caller identified by G_CALLING_MODULE = 724.
• MATCH_CTO_LINES — Performs matching of configured lines, resolving configuration structure and establishing which lines participate in CTO processing for the session.
• PROCESS_CTO_SOURCES — Applies sourcing logic for the matched configuration, determining how configured demand is satisfied.
• GET_MANDATORY_COMPONENTS — Retrieves the mandatory component set for a configuration, enabling ATP to consider only those components that must be present.
• VALIDATE_CTO_SOURCES — Validates the derived sourcing results before they are used in the ATP calculation.
• EXTEND_SOURCES_REC — Extends the sourcing record structure to accommodate CTO-derived sourcing entries.
• POPULATE_CTO_BOM — Loads configured bill-of-material component relationships used during matching.
• GET_CTO_BOM — Returns the CTO bill-of-material structure for the configuration under evaluation.
• MAINTAIN_OS_SOURCING — Maintains option-dependent (order-specific) sourcing information associated with the configuration.
• CHECK_BASE_MODEL_FOR_CAP_CHECK — Determines whether a base model is eligible for capacity checking during CTP.

Tables Accessed

The package reads and writes planning and configuration data through APPS synonyms. MRP_ATP_SCHEDULE_TEMP holds staged ATP supply/demand and period rows. MSC_CTO_BOM and MSC_BOM_COMPONENTS provide configured and standard bill-of-material component relationships; MSC_CTO_SOURCES supplies CTO sourcing rules; MSC_OPERATION_COMPONENTS supports component-level operation data; MSC_SHIP_SET_TEMP supports ship-set grouping; MSC_SYSTEM_ITEMS, MSC_ITEM_ID_LID, MSC_TP_ID_LID, MSC_TRADING_PARTNERS, and MSC_TRADING_PARTNER_SITES resolve item and trading partner identities; MSC_CALENDAR_DATES supplies working-day context for ATP timing; and PLITBLM is used for LOB handling. The heavy reliance on MSC_ prefixed tables confirms the package is part of the Advanced Planning Foundation data model.

Usage Notes

MSC_ATP_CTO is invoked indirectly. It is referenced by seven other packages, most directly from the ATP calculation flow that calls CHECK_LINES_FOR_CTO_ATP, and is therefore reached during sales order scheduling, order line ATP/CTP requests, and planning ATP runs rather than from a standalone concurrent program. Custom code should call the supported scheduling APIs (for example, MRP_ATP_PUB procedures) rather than this package directly. When diagnosing behaviour, set the MSC_ATP_DEBUG profile to Y or C to obtain the internal trace markers emitted by CHECK_LINES_FOR_CTO_ATP, MATCH_CTO_LINES, and related routines.