Search Results load_bis115

Overview

MSC_CL_OTHER_PULL is a collection package in the Oracle Advanced Supply Chain Planning (ASCP) schema (APPS) that supports the data pull phase of the planning data collection process. Its name follows the ETRM convention for "collection layer" packages, where MSC_CL designates the planning collection subsystem and OTHER_PULL indicates that the package gathers miscellaneous, low-volume reference and attribute data that does not belong to a dedicated collection program. In Oracle EBS 12.1.1 and 12.2.2, ASCP relies on the collections manager to extract transactional and setup data from source applications into the MSC staging tables before a plan can be run.

This package is one of several "pull" programs that feed that staging area. Rather than owning a single large business object (such as items or bills of material), MSC_CL_OTHER_PULL consolidates a number of smaller reference entities — schedules, subinventories, sourcing rules, project references, planners, demand classes, and currency conversion attributes — into a single reusable driver. The header comment ($Header: MSCPOTHS.pls, version 120.2, dated 2008) confirms it is an established, longstanding component of the planning collection framework. It is classified as an OTHER API, meaning it is not a public integration API but an internal collections utility.

Key Procedures and Functions

The package specification exposes twenty documented procedures, each responsible for loading a specific planning reference entity into the collection schema:

• LOAD_SCHEDULE — loads production schedules used for supply timing.
• LOAD_SUB_INVENTORY — loads subinventory definitions associated with inventory organizations.
• LOAD_SOURCING — loads sourcing rules and assignments used to determine supply sources.
• LOAD_UNIT_NUMBER — loads unit-number effectivity information for item-supply relationships.
• LOAD_SAFETY_STOCK — loads safety stock levels by item and organization.
• LOAD_PROJECT — loads project and task references so that project-based demand and supply can be planned. This is the procedure most commonly associated with the search term "load_project."
• LOAD_BIS107, LOAD_BIS110, LOAD_BIS115 — load business intelligence / historical demand data maintained in the BIS (Business Intelligence System) schemas for pre-11.5.10, 11.5.10, and 11.5.10+ variants.
• LOAD_ATP_RULES — loads available-to-promise rules for order promising.
• LOAD_PLANNERS — loads planner assignments and buyer/planner codes.
• LOAD_DEMAND_CLASS — loads demand class definitions for priority-based planning.
• LOAD_TRIP — loads trip and transportation lane information.
• LOAD_SALES_CHANNEL — loads sales channel reference data.
• LOAD_FISCAL_CALENDAR — loads fiscal calendar definitions used for bucketing.
• LOAD_CURRENCY_CONVERSION — loads currency conversion rates (bug # 6469722).
• LOAD_DELIVERY_DETAILS — loads delivery detail records (bug # 6730983).
• LOAD_IB_CONTRACTS, LOAD_SHORT_TEXT, LOAD_LONG_TEXT — load installed-base contracts and item descriptive text attributes.

No parameter lists are documented, and none should be assumed; callers invoke these procedures as part of the collection program flow rather than through direct parameterized calls.

Tables Accessed

The ETRM metadata records that this package references tables exclusively through APPS synonyms, consistent with Oracle's synonym-based coding standard. The specific underlying base tables are not individually enumerated in the extract. Based on the operation names, the package writes into MSC staging tables (the MSC_% collection family) after reading from source tables such as MTL_SAFETY_STOCKS, MTL_SECONDARY_INVENTORIES, MTL_SCHEDULES, BOM_SOURCING_RULES, PJM_PROJECTS, FND_CURRENCIES, WSH_DELIVERY_DETAILS, and the BIS historical tables. The global variables G_MSC_HUB_CURR_CODE, G_MSC_CURR_CONV_TYPE, G_MSC_FUTURE_DAYS, and G_MSC_PAST_DAYS are populated from FND_PROFILE values at package initialization and drive currency conversion behavior.

Usage Notes

MSC_CL_OTHER_PULL is invoked by the ASCP collections manager and by the three other packages documented as referencing it. It is not intended for direct ad-hoc execution by end users; the individual LOAD_* procedures are called internally during the "Pull" phase of a collections run. Customizations should avoid duplicating its logic, and any modifications must preserve the package's role as an internal collections utility. Because currency-conversion globals are read at package load time, profile option changes require a new session before they take effect.