Search Results create_atp_bom

Overview

CTO_ATP_INTERFACE_PK is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified under the ETRM repository as an OTHER API. It provides the interface layer between Configure-to-Order (CTO) order capture and the Available-to-Promise (ATP) engine. The package coordinates the assembly of ATP-eligible bill of material structures, resolves sourcing rules for configured models, and generates the demand records required for ATP supply/demand matching. Its scope covers model-level configuration, ship set handling, mandatory component population, and integration with MRP_ATP_PUB public data types. The package header, identified as $Header: CTOATPIS.pls 115.9 2002/11/19, declares AUTHID CURRENT_USER and is documented identically in ETRM for both 12.1.1 and 12.2.2.

Key Procedures and Functions

• GET_MODEL_SOURCING_ORG — The procedure most associated with the search term "get_model_sourcing_org." It resolves the sourcing organization for a configured model based on inventory item and organization inputs, and returns the sourcing rule existence flag, sourcing organization, source type, transit lead time, along with standard return status, plus optional line and ship set context.
• CREATE_ATP_BOM — Constructs an ATP bill of materials record for a configured assembly using the MRP_ATP_PUB.atp_bom_rec_typ structure.
• EXTEND_ATP_BOM — Augments an existing ATP BOM record, supporting nested configurations.
• POPULATE_MANDATORY_COMPONENTS — Fills in mandatory component details for a given ATP BOM record by index.
• GET_ATP_BOM — Retrieves the ATP BOM for a ship set, accepting an ATP_REC_TYP ship set record and returning the BOM record.
• CREATE_CTO_MODEL_DEMAND — Creates model-level demand from a ship set and its status, used as input to the ATP engine.
• CREATE_CTO_ITEM_DEMAND — Generates item-level demand records consequent to the model demand.

Tables Accessed

• BOM_CTO_ORDER_DEMAND / BOM_CTO_ORDER_DEMAND_S1 — Primary store for CTO order demand rows, including the sequence used by demand generation.
• CZ_ATP_REQUESTS — Configuration/ATP request linkage for configured items.
• MRP_ATP_DETAILS_TEMP — Temporary ATP detail working area used during BOM and demand assembly.
• MRP_ASSIGNMENT_SETS — Source of sourcing assignment sets underlying GET_MODEL_SOURCING_ORG logic.
• MTL_SYSTEM_ITEMS / MTL_PARAMETERS — Item and organization attribute lookup, including ATP and source type flags.
• OE_ORDER_LINES / OE_ORDER_LINES_ALL / OE_SYSTEM_PARAMETERS_ALL — Order line context and OE profile values used to resolve validation organization.
• BOM_CALENDAR_DATES — Calendar reference for lead time and scheduling calculations.

Usage Notes

CTO_ATP_INTERFACE_PK is invoked internally by the ATP and CTO scheduling flows rather than directly by end users. In practice it is called from Oracle Order Management during order line booking and scheduling, when model and mandatory component ATP checks are required. Custom extensions should call the public procedures using the documented MRP_ATP_PUB record types; parameter lists are not reproduced here. The package is referenced by zero other packages per ETRM, but depends on MRP_ATP_PUB, OE, BOM, and MTL schemas. The global G_OE_VALIDATION_ORG caches the OE validation organization for the session. Because behavior is stable across 12.1.1 and 12.2.2, the same call patterns apply. Direct DML against BOM_CTO_ORDER_DEMAND is discouraged; demand should always be created through this package to preserve ATP integrity.