Results for “g_dp_cs_req_data”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

MSD_CL_PRE_PROCESS is an Oracle E-Business Suite PL/SQL package owned by the APPS schema that functions as the pre-processing stage for the Microsoft/MSC (Advanced Supply Chain Planning) collections interface. In the context of Oracle EBS 12.1.1 and 12.2.2, this package prepares and stages data extracted from transactional source systems before it is loaded into the planning engine's staging and interface tables. The "CL" in the name denotes "Collections," and the package is part of the data collection infrastructure that feeds the Demantra/MSC planning and demand management schemas.

The package is classified under the ETRM API classification category "OTHER," meaning it is not a published, customer-facing Open Interface API but rather an internal processing utility. It carries a header revision marker of $Header: MSDCLPPS.pls 120.3 2007/09/07, reflecting that it originated in the 11i/early R12 development cycle and has been carried forward largely unchanged into the 12.1.1 and 12.2.2 releases. It is referenced by zero other packages, confirming its role as a top-level driver rather than a shared library called by downstream routines.

The package defines a substantial set of constants that reveal its operating model. Error and warning severities (G_ERROR, G_WARNING, G_SEV3_ERROR, G_SEV_ERROR), sentinel values for null representation (NULL_CHAR, NULL_VALUE), request-type identifiers (G_NEW_REQUEST, G_DP_LV_REQ_DATA, G_DP_CS_REQ_DATA), process status flags (G_NEW, G_IN_PROCESS, G_ERROR_FLG, G_VALID), and calendar/bucket classifications (G_BUCKET_TYPE, G_MFG_CAL, G_FISCAL_CAL, G_COMPOSITE_CAL) collectively indicate that the package supports batch-driven, multi-step data staging with calendar and time-bucket awareness. The calling module constants G_APS and G_DP distinguish between Advanced Planning and Demand Planning invocation contexts.

The global variable v_link is declared to carry a linkage or batch correlation identifier across the loading procedures.

Key Procedures and Functions

The package exposes 23 documented procedures, all following a consistent pattern of returning ERRBUF and RETCODE out parameters plus an instance identifier and, in several cases, a batch identifier. Representative documented procedures include:

• LOAD_ORG_CUST — stages organization and customer (trading partner) data for the collections cycle.
• LOAD_ITEMS — stages item master records destined for the planning interface.
• LOAD_CATEGORY — loads item category assignments, accepting an additional linkage parameter.
• LOAD_SITE — stages site-level organizational or customer site data.
• LOAD_LEVEL_VALUE, LOAD_LEVEL_ASSOC, LOAD_LEVEL_ORG_ASSCNS — populate hierarchy level values, level associations, and the organization-to-level associations used for planning hierarchies.
• LOAD_BOOKING_DATA and LOAD_SHIPMENT_DATA — stage booking and shipment transactional facts.
• LOAD_MFG_FORECAST, LOAD_MFG_TIME, LOAD_FISCAL_TIME, LOAD_COMPOSITE_TIME — populate forecast data and the manufacturing, fiscal, and composite calendar/time dimension buckets.
• LOAD_CURRENCY_CONV, LOAD_UOM_CONV — stage currency conversion rates and unit-of-measure conversion factors.
• LOAD_CS_DATA — loads custom stream (CS) data, consistent with the G_DP_CS_REQ_DATA request constant.
• LOAD_PRICE_LIST, LOAD_SETUP_PARAMETER, LOAD_ITEM_RELATIONSHIP, LOAD_DEMAND_CLASS — stage price lists, setup parameters, item relationships, and demand class definitions.

Each procedure is designed to be invoked independently as a sub-request within a larger collections run.

Tables Accessed

The package reads and writes a mixture of MSC (planning interface) and MSD (Demantra/collections staging) tables accessed through APPS synonyms:

• MSC_APPS_INSTANCES, MSC_COMPANIES, MSC_TRADING_PARTNERS — instance and organizational entity context.
• MSC_SYSTEM_ITEMS, MSC_ST_SYSTEM_ITEMS — item master and staging copy.
• MSC_ERRORS, MSC_LOCAL_ID_SETUP — error logging and local identifier configuration.
• MSD_HIERARCHY_LEVELS, MSD_LEVEL_VALUES, MSD_LEVEL_ASSOCIATIONS — planning hierarchy definitions.
• MSD_LOCAL_ID_SETUP, MSD_SETUP_PARAMETERS — collections configuration.
• MSD_ST_BATCH_ID_S, MSD_ST_BOOKING_DATA, MSD_ST_BOOKING_DATA_S — batch sequencing and booking staging.

Usage Notes

MSD_CL_PRE_PROCESS is typically invoked by concurrent programs within the Advanced Supply Chain Planning and Demand Planning collections flows, either as a parent that dispatches each LOAD_* procedure as a sub-request or as individual program calls per data category. Because it lacks an Open Interface classification, it should not be called directly from custom code without validating the expected ERRBUF/RETCODE contract and the batch/instance context. Parameter names vary per procedure (some take p_instance_id and p_batch_id, LOAD_CATEGORY adds p_link), so callers must reference the package specification. The package has remained stable across 12.1.1 and 12.2.2, with no documented dependents, meaning database upgrades are unlikely to alter its behavior.