Search Results load_trading_partner

Overview

MSC_CL_SETUP_ODS_LOAD is an Oracle E-Business Suite PL/SQL package owned by the APPS schema and classified as a collection/setup data loading utility within the Advanced Supply Chain Planning (ASCP) module — indicated by the MSC prefix and the ODS (Operational Data Store) naming convention. Its documented header comment references MSCLSTPS.pls, supplied by Oracle as a "noship" (non-shipped, restricted) file. The package serves as a staging and transformation layer that moves supply chain planning setup data into the MSC operational data store prior to plan execution. Functions such as cleanse, transform, and key-generation routines confirm that its primary business purpose is to normalize, validate, and prepare upstream setup and transactional data so that the planning engine receives consistent, deduplicated information. It also supports trading partner resolution and liability agreement cleanup, both essential for multi-organization and supplier collaboration scenarios.

Key Procedures and Functions

• LINK_SUPPLY_TOP_LINK_ID — returns a Boolean indicating success of linking supply records to their top-level link identifier.
• CLEANSE_DATA — returns a Boolean flag after purging or correcting invalid staging data.
• TRANSFORM_KEYS — returns a Boolean after translating source keys into planning-compatible key values.
• LOAD_CALENDAR_SET_UP — loads calendar set definitions into the ODS.
• LOAD_CALENDAR_DATE — populates calendar date detail records.
• LOAD_TRADING_PARTNER — loads trading partner setup records.
• LOAD_PARAMETER — loads planning parameters.
• LOAD_UOM — loads unit-of-measure setup data.
• CLEAN_LIAB_AGREEMENT — cleanses the msc_asl_auth_details table as part of liability agreement maintenance.
• GENERATE_TRADING_PARTNER_KEYS — the routine most relevant to the user's search; generates trading partner keys, accepting an error buffer, a return code, and an instance identifier, and is typically driven from a concurrent program that requires completion status feedback.
• GET_COLL_PARAM — overloaded procedure retrieving collection parameters; one variant returns a MSC_CL_EXCHANGE_PARTTBL.CollParamREC record by instance ID.

Tables Accessed

The package reads and writes setup data through APPS synonyms. Calendar-related logic touches MSC_CALENDARS, MSC_CALENDAR_ASSIGNMENTS, MSC_CALENDAR_DATES, MSC_CALENDAR_SHIFTS, MSC_CAL_WEEK_START_DATES, and MSC_CAL_YEAR_START_DATES. Trading partner and organizational resolution involve MSC_COMPANIES, MSC_ITEM_SUPPLIERS, MSC_LOCATION_ASSOCIATIONS, and MSC_INSTANCE_ORGS. Instance and parameter control tables include MSC_APPS_INSTANCES, MSC_COLL_PARAMETERS, and MSC_PARAMETERS. Key transformation and mapping use MSC_ITEM_ID_LID, while liability agreement cleanup targets MSC_ASL_AUTH_DETAILS. These accesses collectively stage setup, calendar, supplier, and parameter data required for a valid planning run.

Usage Notes

MSC_CL_SETUP_ODS_LOAD is typically invoked by ASCP collection and setup concurrent programs rather than directly by end users. The procedures returning Boolean or OUT NOCOPY parameters — notably GENERATE_TRADING_PARTNER_KEYS with its ERRBUF and RETCODE — are structured for scheduled concurrent execution, where the error buffer and return code surface status to the concurrent manager log. In Oracle EBS 12.1.1 and 12.2.2, the package operates against the APPS schema and should only be called through supported concurrent programs or sanctioned custom wrappers; direct invocation outside that framework can leave ODS staging data inconsistent. Because the header file is marked noship and the API classification is OTHER, the package is not a public, released API. Customizations should avoid calling internal routines directly and instead rely on the standard planning data collection flows that call this package. Application of patches or upgrades may alter undocumented behavior without notice.