Search Results msc_designators_s

Overview

MSC_CL_DEMAND_ODS_LOAD is a PL/SQL package body owned by the APPS schema that supports the Oracle Advanced Supply Chain Planning (ASCP) collection layer in Oracle E-Business Suite 12.1.1 and 12.2.2. Its core purpose is to load demand-related data from operational source tables into the MSC staging and Open Data Store (ODS) tables used by the planning engine. The package participates in the collections process that extracts sales orders, forecasts, reservations, and related demand constructs from the transactional EBS database and transforms them into the canonical planning schema.

The object is classified as OTHER in the ETRM repository and is currently VALID. The documented metadata lists sixteen procedures, confirming that the package is a broad demand-loading utility rather than a narrow single-purpose routine. It depends on supporting packages including MSC_CL_COLLECTION, MSC_CL_ITEM_ODS_LOAD, MSC_CL_EXCHANGE_PARTTBL, MSC_UTIL, MSC_ANALYSE_TABLES_PK, FND_PROFILE, and MSC_GET_NAME. It is not referenced by any database object, indicating it is invoked by higher-level collection orchestration rather than called at runtime by dependent packages.

Key Procedures and Functions

• LOAD_ODS_DEMAND — primary entry point that orchestrates loading demand records into the ODS.
• LOAD_DEMAND — loads general demand records into the planning demand table.
• LOAD_SALES_ORDER — loads sales order demand from the operational sales order tables.
• LOAD_HARD_RESERVATION — loads hard reservations into the planning reservation structures.
• LOAD_DESIGNATOR — loads designator records, reading from and populating MSC_DESIGNATORS and MSC_DESIGNATORS_S, the tables referenced by the user's search term.
• LOAD_FORECASTS and LOAD_ITEM_FORECASTS — load forecast demand at the aggregate and item levels respectively.
• LOAD_CMRO_EAM_FORECASTS — loads forecasts originating from CMRO and EAM sources.
• LOAD_PAYBACK_DEMANDS — loads payback demand records.
• LINK_PARENT_SALES_ORDERS and LINK_PARENT_SALES_ORDERS_MDS — establish parent-child relationships between sales order demand lines, including the MDS variant.
• LINK_SUPP_SO_DEMAND_EXT, LINK_SUPP_SO_DEMAND_110, and LINK_SUPP_SO_DEMAND_11I2 — version-specific routines that link supplying sales order demand across release levels.
• DROP_DEMANDS_TMP_IND and DROP_SALES_ORDERS_TMP_IND — remove temporary indexes created during bulk load operations.

Tables Accessed

The package reads from and writes to the following documented tables (accessed through APPS synonyms): MSC_ST_DEMANDS, MSC_DEMANDS, MSC_ST_SALES_ORDERS, MSC_SALES_ORDERS, MSC_ST_RESERVATIONS, MSC_RESERVATIONS, MSC_ST_DESIGNATORS, MSC_DESIGNATORS, and MSC_DESIGNATORS_S. The MSC_ST_* tables serve as staging areas that receive data before it is promoted to the corresponding MSC_* planning tables. MSC_DESIGNATORS_S is the denormalized designator staging table referenced directly in the user's search and is populated by LOAD_DESIGNATOR.

Supporting lookups include MSC_ITEM_ID_LID, MSC_TP_ID_LID, and MSC_TP_SITE_ID_LID for identifier mapping; MSC_APPS_INSTANCES and FND_PROFILE for environment and profile context; AD_DDL and DUAL for utility operations; and PLITBLM for temporary index handling.

Usage Notes

MSC_CL_DEMAND_ODS_LOAD is invoked indirectly through the ASCP collections concurrent programs, most notably the demand and sales order collection programs that populate the planning ODS. It is not exposed through a standard form and should not be called directly from custom code unless the caller fully replicates the collection context, including profile settings and staging table state. Because temporary indexes are created and dropped within the load process, concurrent invocation against the same staging tables must be avoided. Any customization should be limited to the documented procedures, and version-specific routines such as LINK_SUPP_SO_DEMAND_11I2 versus LINK_SUPP_SO_DEMAND_110 confirm that behavior differs across EBS releases, so testing must target the specific patch level in use.