Search Results get_dit_count




Overview
Explore in AI Chat

Overview

CTO_CONFIG_BOM_PK is a core Oracle EBS package in the APPS schema that supports Configure-to-Order (CTO) processing by managing the bill of material (BOM) structures generated during configuration of ATO (Assemble-to-Order) and PTO (Pick-to-Order) models. When an order line references a configured item, the CTO process must translate the customer's chosen options into a concrete BOM representation that manufacturing and fulfillment can consume. This package performs that translation: it creates and maintains BOM headers and components tied to the configuration, resolves lead-time and routing attributes, and validates the resulting structure for consistency.

The package is tightly coupled to the broader CTO family, including CTO_BOM_RTG_PK, CTO_CONFIG_ITEM_PK, CTO_CONFIG_ROUTING_PK, CTO_UPDATE_BOM_RTG_PK, CTO_UTILITY_PK, CTO_WORKFLOW, and CZ_BOM_CONFIG_EXPLOSIONS_PKG. It in turn depends on foundational BOM tables (BOM_BILL_OF_MATERIALS, BOM_INVENTORY_COMPONENTS) and on OE_ORDER_LINES to link BOM records back to the originating sales order. The package status is VALID in the documented environment.

Key Procedures and Functions

The ETRM metadata documents nine callable units:

  • GET_DIT_COUNT — Returns a count related to DIT (drop-in-the-basket / deliver-in-transit) processing for a configuration, used to determine whether specific handling is required.
  • GET_DROPPED_COMPONENTS — Retrieves the list of components that have been dropped from a configuration, allowing downstream logic to reconcile what has been removed.
  • RESET_DROPPED_COMPONENTS — Clears or resets the recorded dropped-component state so the configuration can be re-evaluated.
  • CREATE_BOM_ML — Creates the multi-lingual (ML) BOM structure records for a configuration, ensuring language-dependent descriptions align with the generated BOM.
  • CREATE_BOM_DATA_ML — Creates the associated multi-lingual BOM data records, complementing CREATE_BOM_ML.
  • GET_MODEL_LEAD_TIME — Derives the lead time for the configured model, factoring in the configuration's components and calendar considerations.
  • INHERIT_OP_SEQ_ML — Manages inheritance of operation sequence values across multi-lingual routing/BOM records.
  • BMLUPID_UPDATE_ITEM_DESC — Updates item descriptions in the context of a BOM line-up identifier (BMLUPID), keeping descriptions synchronized.
  • CHECK_BOM — Validates the constructed BOM for correctness and completeness before it is committed.

Tables Accessed

The package reads and writes several BOM and order tables through APPS synonyms. OE_ORDER_LINES links configuration data to sales order lines, providing the transactional anchor. BOM_BILL_OF_MTLS_INTERFACE and BOM_INVENTORY_COMPS_INTERFACE are interface tables used to stage BOM data prior to loading. BOM_ALTERNATE_DESIGNATORS, BOM_REFERENCE_DESIGNATORS, and BOM_SUBSTITUTE_COMPONENTS support designator and substitution logic within the configuration. BOM_CALENDAR_DATES provides calendar data for lead-time calculations, while BOM_EXPLOSION_TEMP and BOM_CTO_ORDER_LINES hold intermediate and order-specific explosion results. BOM_DEPENDENT_DESC_ELEMENTS handles dependency-element descriptions, and BOM_INVENTORY_COMPONENTS_S supplies the component definitions. FND_ID_FLEX_STRUCTURES, FND_PROFILE_OPTIONS, FND_PROFILE_OPTION_VALUES, and FND_USER provide key flexfield and profile-option context for the session.

Usage Notes

CTO_CONFIG_BOM_PK is invoked indirectly through the CTO package hierarchy rather than by end users. The Configure-to-Order workflow, the configuration item and routing packages, and the CZ_BOM_CONFIG_EXPLOSIONS_PKG all depend on it. It is typically called from the Bill of Materials and Order Management CTO processing paths, and from concurrent programs that create or validate configuration BOMs during order booking or release. Custom extensions should call the public procedures only after the configuration item has been created and the source order line is available; direct DML against the underlying interface tables is not supported and bypasses validation performed by CHECK_BOM.