Search Results load_parameter

Overview

MSC_CL_SETUP_PULL is a setup data extraction package in the Oracle E-Business Suite Advanced Supply Chain Planning (ASCP) module, owned by the APPS schema and classified as an OTHER API type. Its declared purpose is to "pull" configuration and reference data from the operational E-Business Suite instance into the MSC (Advanced Planning) staging tables that feed the planning data repository. The package header, identified internally as MSCPSTPS.pls (version 120.0), is defined with AUTHID CURRENT_USER and exposes a specification containing five standalone procedures. Unlike many planning APIs, it does not expose functions or a central dispatcher; each procedure handles a discrete collection domain, allowing the collections engine or a concurrent program to invoke only the subset of setup data required for a given planning run.

The package forms part of the broader "setup pull" layer used during planning data collection. Operational setup entities such as calendars, trading partners, units of measure, buyer contacts, and planning parameters must be replicated into the planning schema before demand and supply are exploded. MSC_CL_SETUP_PULL provides the programmatic entry points for that replication, isolating the extraction logic from the collections engine itself.

Key Procedures and Functions

The specification documents five public procedures, each responsible for loading a specific class of setup data:

• LOAD_BUYER_CONTACT — Extracts buyer and buyer-contact information from the source applications so that planning results can be attributed to the correct procurement or planning contact.
• LOAD_CALENDAR_DATE — Populates calendar and date reference data, providing the working-day and bucket definitions required for time-phased planning and scheduling calculations.
• LOAD_TRADING_PARTNER — Loads trading partner definitions, supporting supplier, customer, and inter-organization relationship resolution during planning and sourcing.
• LOAD_PARAMETER — Loads planning and system parameters. This is the procedure most frequently associated with the search term load_parameter, since it transfers the profile and planning option settings that govern collection and plan behavior.
• LOAD_UOM — Extracts unit-of-measure definitions and conversions so that planning quantities can be normalized across items and organizations.

No parameter lists are documented in the package specification; each procedure is declared without arguments, implying that selection criteria are derived from profile options or from the current collection session context rather than passed explicitly by the caller.

Tables Accessed

The ETRM metadata does not enumerate specific base tables for this package; references are made through APPS synonyms, which is standard for ASCP collection code that must remain independent of the underlying schema owner. Functionally, the procedures target the MSC staging and setup tables in the planning schema, writing rows extracted from source setup entities. LOAD_PARAMETER writes planning parameter records, LOAD_UOM writes unit-of-measure and conversion records, LOAD_CALENDAR_DATE writes calendar and date rows, and LOAD_TRADING_PARTNER and LOAD_BUYER_CONTACT write partner and contact reference rows. Because the specification carries no DML or cursor definitions, precise table names cannot be confirmed from the header alone and would require inspection of the package body.

Usage Notes

MSC_CL_SETUP_PULL is not intended for direct end-user invocation. It is typically called by the ASCP collections framework or by a concurrent program that orchestrates a full or partial setup refresh during a planning data collection cycle. The package is documented as being referenced by one other package, which suggests it is a leaf-level extraction component rather than a top-level orchestrator. Because the procedures accept no parameters, they depend on session and profile context established by the calling program.

For both Oracle EBS 12.1.1 and 12.2.2, the package header is unchanged apart from the online patching editioning considerations that apply to 12.2. The version stamp (120.0, dated 2007) indicates the specification has been stable across releases. Customers extending planning collections should treat these procedures as reference implementations and avoid modifying the seeded APPS package; custom logic should be placed in a separate package that calls these procedures or replicates their extraction patterns.