Search Results collect_model_bom_components




Overview
Explore in AI Chat

Overview

MSD_DEM_CTO is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that forms part of the Oracle Demantra (MSD) integration layer used for Configure-to-Order (CTO) data processing. In EBS 12.1.1 and 12.2.2, the MSD_DEM_* packages support the extraction, staging, and refresh of Demantra demand-planning and advanced-planning data from EBS transactional and configuration sources. MSD_DEM_CTO specifically manages the movement of CTO model and option-class structure into Demantra-compatible staging tables, so that configured-item relationships and their bill-of-material components are available to the Demantra engine for forecasting, modeling, and demand analysis.

The package is classified as API level OTHER in the ETRM metadata and was VALID at time of documentation. It participates in a tightly coupled family of utilities: it depends on APPS.MSD_DEM_COMMON_UTILITIES and SYS.STANDARD, and is referenced by MSD_DEM_COMMON_UTILITIES, MSD_DEM_DEMANTRA_UTILITIES, and recursively by itself. This bi-directional relationship with MSD_DEM_COMMON_UTILITIES indicates shared helper routines are invoked during staging and collection operations, which is the typical pattern in the Demantra collection framework.

Key Procedures and Functions

Three program units are documented for this package:

  • POPULATE_STAGING_TABLE — Drives the population of the package's staging table structures. It is responsible for assembling CTO-related source records into the intermediate staging area that the downstream Demantra collection process consumes. This is the entry point most commonly triggered by a collection or refresh cycle.
  • COLLECT_MODEL_BOM_COMPONENTS — Collects the bill-of-material components that belong to CTO models. This routine traverses model and option-class structures and associates the corresponding component items so that the full configured structure is captured for staging.
  • PURGE_CTO_GL_DATA — Purges CTO-related data, including the GL (general ledger) alignment data used during collection. Purging is used to clear stale data before a re-collection or to reduce table volume after a successful interface run.

No parameter lists are documented, and none are assumed here. In practice these units are called in sequence: model structures are collected, staging is populated, and prior data is purged.

Tables Accessed

Four tables are referenced via APPS synonyms:

  • MSD_DEM_CTO_BOM — The primary staging table for CTO bill-of-material component data. This is the target populated by COLLECT_MODEL_BOM_COMPONENTS and POPULATE_STAGING_TABLE, and the source of the purge operation.
  • MSD_DEM_ENTITY_QUERIES — Stores the entity query definitions used by the Demantra collection framework to identify source EBS data. This package reads it to determine which CTO entities to stage.
  • MSC_APPS_INSTANCES — The Applications instance registration table used by Advanced Supply Chain Planning and Demantra collection to identify the source instance and its connection context.
  • DUAL — The standard single-row utility table, used for simple lookups and control logic.

Usage Notes

MSD_DEM_CTO is an internal infrastructure package, not a user-invoked API. It is typically executed indirectly through the Demantra collection framework or from the Advanced Planning/collection concurrent programs that orchestrate MSD_DEM_COMMON_UTILITIES and MSD_DEM_DEMANTRA_UTILITIES. Because it references staging tables and is referenced by the common utilities package, custom code should not call its procedures directly; doing so risks bypassing the sequencing and commit logic enforced by the collection driver. When troubleshooting Demantra CTO collections, the package is most relevant during staging population and purge phases, and the MSD_DEM_CTO_BOM table should be inspected to verify successful collection.