Search Results generate_item_keys
Overview
MSC_CL_ITEM_ODS_LOAD is an Oracle EBS PL/SQL package owned by the APPS schema and classified as an "OTHER" API within the ETRM repository. Its documented purpose is to load item-related master and transactional data into the MSC (Advanced Supply Chain Planning / Oracle Planning) operational data store. The package header, last revised in 2007 (MSCLITES.pls, version 120.0), exposes a set of procedures and one function that collectively populate key item attributes needed by the planning engine, including item keys, lead times, substitute relationships, supplier sourcing entries, ABC classifications, and category assignments.
In Oracle EBS 12.1.1 and 12.2.2, the MSC schema underpins Advanced Supply Chain Planning and related planning products. MSC_CL_ITEM_ODS_LOAD sits in the collection/load layer that gathers source item data from EBS master data and stages it for planning consumption. The "_ODS_LOAD" naming convention indicates the package targets an Operational Data Store staging area, using "ST" (staging) tables such as MSC_ST_* to receive raw extracts before they are processed into the final MSC_* planning tables.
Key Procedures and Functions
- GENERATE_ITEM_KEYS — Generates the internal item keys required to uniquely identify items during the ODS load process, taking an instance identifier to scope the generation to a specific planning instance.
- ITEM_NAME — A function that returns the item name for a supplied item identifier, providing a reusable lookup used by other routines in the package.
- ADD_NEW_IMPL_ITEM_ASL — Adds new implemented-item approved supplier list entries into the planning data set, ensuring newly sourced items are visible to planning.
- UPDATE_LEADTIME — Refreshes lead-time data for items so planning calculations use current procurement and manufacturing lead times.
- LOAD_ITEM — The central routine (the target of a "load_item" search) that loads item master records and associated attributes into the ODS structures.
- LOAD_SUPPLIER_CAPACITY — Loads supplier capacity information used for capacity-constrained sourcing decisions.
- LOAD_ABC_CLASSES — Loads ABC classification data, supporting prioritization and analysis within planning.
- LOAD_ITEM_SUBSTITUTES — Loads item substitute relationships so the planner can model alternate-item scenarios.
- LOAD_CATEGORY — Loads category and category-set assignments for items, enabling category-based planning and reporting.
Tables Accessed
The package reads and writes a range of MSC tables via APPS synonyms. Final planning tables include MSC_ITEMS and MSC_ITEMS_S (item master and its translated/secure variant), MSC_ITEM_ID_LID (the item identifier list), MSC_ITEM_SUBSTITUTES, MSC_ITEM_SUPPLIERS, MSC_ITEM_CATEGORIES, MSC_CATEGORY_SETS and MSC_CATEGORY_SETS_S, MSC_CATEGORY_SET_ID_LID, and MSC_ROUTINGS. Corresponding staging tables — MSC_ST_CATEGORY_SETS, MSC_ST_ITEM_CATEGORIES, MSC_ST_ITEM_SUBSTITUTES, MSC_ST_ITEM_SUPPLIERS, and MSC_ST_SUPPLIER_CAPACITIES — receive the raw extracted data prior to processing. Collectively these tables hold the item, category, substitute, supplier, and routing dimensions that the planning engine requires.
Usage Notes
MSC_CL_ITEM_ODS_LOAD is not typically called directly by end users. It is invoked as part of the planning data collection and load cycle, generally through concurrent programs or higher-level collection orchestration packages that populate the ODS before the planning engine consumes the data. Because the package is referenced by eight other packages, it functions as a shared dependency within the MSC load framework. Customizations should avoid modifying the package directly; instead, call the documented procedures through supported collection processes. When troubleshooting item load issues, the LOAD_ITEM procedure and the MSC_ITEMS/MSC_ST_* table pairings are the logical starting points, since they represent the core item data path.
-
PACKAGE: APPS.MSC_CL_ITEM_ODS_LOAD
12.2.2
-
PACKAGE: APPS.MSC_CL_ITEM_ODS_LOAD
12.1.1
-
PACKAGE BODY: APPS.MSC_CL_ITEM_ODS_LOAD
12.2.2
-
PACKAGE BODY: APPS.MSC_CL_ITEM_ODS_LOAD
12.1.1
-
PACKAGE: APPS.MSC_CL_COLLECTION
12.1.1
-
PACKAGE: APPS.MSC_CL_COLLECTION
12.2.2
-
APPS.MSC_CL_ITEM_ODS_LOAD dependencies on MSC_CATEGORY_SETS
12.1.1
-
APPS.MSC_CL_ITEM_ODS_LOAD dependencies on MSC_CATEGORY_SETS
12.2.2
-
APPS.MSC_CL_ITEM_ODS_LOAD dependencies on FND_MESSAGE
12.1.1
-
APPS.MSC_CL_ITEM_ODS_LOAD dependencies on FND_MESSAGE
12.2.2
-
APPS.MSC_CL_COLLECTION dependencies on MSC_CL_ITEM_ODS_LOAD
12.1.1
-
APPS.MSC_CL_COLLECTION dependencies on MSC_CL_ITEM_ODS_LOAD
12.2.2
-
APPS.MSC_CL_COLLECTION dependencies on MSC_UTIL
12.1.1
-
APPS.MSC_CL_ITEM_ODS_LOAD dependencies on MSC_ITEMS
12.2.2
-
APPS.MSC_CL_ITEM_ODS_LOAD dependencies on MSC_ITEMS
12.1.1
-
APPS.MSC_CL_COLLECTION dependencies on MSC_UTIL
12.2.2
-
APPS.MSC_CL_ITEM_ODS_LOAD dependencies on MSC_UTIL
12.2.2
-
APPS.MSC_CL_ITEM_ODS_LOAD dependencies on MSC_UTIL
12.1.1
-
APPS.MSC_CL_ITEM_ODS_LOAD dependencies on MSC_ITEM_ID_LID
12.1.1
-
APPS.MSC_CL_ITEM_ODS_LOAD dependencies on MSC_ITEM_ID_LID
12.2.2
-
PACKAGE BODY: APPS.MSC_CL_COLLECTION
12.1.1
-
PACKAGE BODY: APPS.MSC_CL_COLLECTION
12.2.2
-
APPS.MSC_CL_ITEM_ODS_LOAD dependencies on MSC_CL_COLLECTION
12.1.1
-
APPS.MSC_CL_ITEM_ODS_LOAD dependencies on MSC_CL_COLLECTION
12.2.2