Search Results msc_assignment_sets_s

Overview

MSC_CL_OTHER_ODS_LOAD is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema and classified under the OTHER API category. Within the Advanced Supply Chain Planning (ASCP) and related MSC schemas, the MSC_CL_* family of packages implements the collection-layer load routines that populate the Operational Data Store (ODS) consumed by the planning engine. This particular package handles "other" collection entities — reference, setup, and control data that do not belong to the primary item, demand, or supply collection streams handled by companion packages such as MSC_CL_ITEM_ODS_LOAD.

The package's core business function is to extract source-system setup and reference data, stage it through the MSC_ST_* staging tables, and merge it into the corresponding MSC_* ODS tables so that planning data is built on a consistent, validated set of calendars, sourcing rules, assignment sets, safety stocks, planners, and currency conversions. Because these entities define the planning context, the package is typically invoked early in the collection run, before transactional data loads. The object is VALID in the documented environment and is referenced by one other package, indicating it is part of a coordinated collection call graph.

Key Procedures and Functions

The documented package exposes 29 public procedures, of which the following are identified by name. Each loads or maintains a specific ODS entity:

• Configuration and reference loaders: LOAD_FISCAL_CALENDAR (fiscal calendar periods), LOAD_CURRENCY_CONVERSION and PURGE_STALE_CURRENCY_CONV (currency conversion rates and removal of obsolete rate rows), LOAD_PLANNERS (planner definitions), and LOAD_DEMAND_CLASS (demand class hierarchies and optionally sales channel data).
• Planning-rule loaders: LOAD_SOURCING (sourcing rules and assignments), LOAD_ATP_RULES (available-to-promise rules), and LOAD_SAFETY_STOCK (safety stock levels).
• Organizational and inventory loaders: LOAD_SUB_INVENTORY, LOAD_PROJECT, LOAD_UNIT_NUMBER, and LOAD_SALES_CHANNEL.
• Business-intelligence loaders: LOAD_BIS_PFMC_MEASURES, LOAD_BIS_TARGET_LEVELS, LOAD_BIS_TARGETS, LOAD_BIS_BUSINESS_PLANS, and LOAD_BIS_PERIODS, which populate performance measure, target, and business plan data used by planning analytics.
• Logistics loaders: LOAD_TRIP, LOAD_VISITS, and LOAD_DELIVERY_DETAILS, which stage transportation and delivery execution data for planning visibility.

No parameter lists are documented in the ETRM metadata; callers should reference the package specification for exact signatures.

Tables Accessed

The package reads and writes a broad set of MSC ODS and staging tables. Referenced entities include MSC_ASSIGNMENT_SETS and MSC_ASSIGNMENT_SETS_S (planning assignment sets), MSC_ATP_RULES, MSC_BIS_BUSINESS_PLANS, MSC_BIS_PERFORMANCE_MEASURES, MSC_BIS_PERIODS, MSC_BIS_TARGETS, and MSC_BIS_TARGET_LEVELS, MSC_CALENDARS and MSC_CALENDAR_MONTHS (planning calendars), MSC_CARRIER_SERVICES, MSC_CURRENCY_CONVERSIONS, MSC_CATEGORY_SET_ID_LID, and MSC_APPS_INSTANCES (instance registry). Source-side or staging counterparts include MSC_ST_ASSIGNMENT_SETS, MSC_ST_ATP_RULES, MSC_ST_BIS_BUSINESS_PLANS, MSC_ST_BIS_PERIODS, MSC_ST_CALENDAR_MONTHS, MSC_ST_CARRIER_SERVICES, MSC_ST_CURRENCY_CONVERSIONS, MSC_ST_DELIVERY_DETAILS, MSC_ST_DEMAND_CLASSES, MSC_ST_INTERORG_SHIP_METHODS, MSC_ST_PLANNERS, MSC_ST_PROJECTS, MSC_ST_PROJECT_TASKS, MSC_ST_REGIONS, MSC_ST_REGION_LOCATIONS, MSC_ST_REGION_SITES, MSC_ST_SAFETY_STOCKS, MSC_ST_SALES_CHANNEL, MSC_ST_SOURCING_RULES, MSC_ST_SR_ASSIGNMENTS, MSC_ST_SR_RECEIPT_ORG, MSC_ST_SR_SOURCE_ORG, MSC_ST_SUB_INVENTORIES, MSC_ST_TRIPS, MSC_ST_TRIP_STOPS, MSC_ST_UNIT_NUMBERS, MSC_ST_VISITS, and MSC_ST_WORK_BREAKDOWN_STRU. Utility dependencies include FND_MESSAGE, FND_PROFILE, FND_REQUEST, FND_USER, MSC_GET_NAME, MSC_ANALYSE_TABLES_PK, and the companion packages MSC_CL_COLLECTION, MSC_CL_EXCHANGE_PARTTBL, MSC_CL_ITEM_ODS_LOAD, and MSC_CL_OTHER_PULL.

Usage Notes

MSC_CL_OTHER_ODS_LOAD is invoked indirectly by the ASCP data collection infrastructure, normally as part of the "Load Other ODS" step initiated through the planning collection concurrent programs, rather than being called directly from an Oracle Forms UI. The calls to FND_REQUEST and FND_PROFILE indicate it submits or coordinates sub-requests and reads site/profile options such as instance identity, while FND_MESSAGE and FND_USER support error reporting and audit attribution. Because the searched object, MSC_ASSIGNMENT_SETS_S, appears among its dependencies, the package's assignment-set loader is the relevant dependency for that lookup. Custom code should not call this package directly; instead, use the standard collection manager flow or the supported MSC_CL_* interfaces, as internal call order and staging-table integrity assumptions are managed by the collection framework.