Search Results translate_booking_data

Overview

MSD_TRANSLATE_FACT_DATA is an APPS-owned PL/SQL package within the Oracle EBS Advanced Planning / Demand Planning (MSD) schema family. Its role is to "translate" staged fact data — raw demand, supply, shipment, booking, pricing, forecast, and opportunity records loaded from external or operational sources — into the canonical fact structures consumed by the planning engines. In ETRM terms it is classified as OTHER, indicating it is an internal processing package rather than a public, versioned API. It is referenced by four other packages, confirming its position as an infrastructure utility invoked by higher-level planning programs rather than by end users directly.

The package header (msdtfcts.pls, version 120.3, dated 2005) still ships essentially unchanged into 12.1.1 and 12.2.2. It declares a large family of collection types (for example a_forecast_designator_type, a_item_type, a_inv_org_type, a_forecast_date_type, a_current_quantity_type, and many sr_* surrogate key types) over columns of MSD_MFG_FORECAST. These arrays support bulk (FORALL) processing of forecast fact rows. Two ISO constants, SYS_YES and SYS_NO, and a C_ALL constant (used for "all levels" processing) are also declared.

Key Procedures and Functions

The documented interface exposes twelve procedures and functions:

• TRANSLATE_SHIPMENT_DATA — converts staged shipment fact rows into planning fact format.
• TRANSLATE_BOOKING_DATA — equivalent translation for booking (order) data.
• TRANSLATE_UOM_CONVERSION — applies unit-of-measure conversion factors to fact quantities.
• TRANSLATE_CURRENCY_CONVERSION — applies currency conversion to monetary fact values such as pricing and bookings.
• TRANSLATE_OPPORTUNITIES_DATA — translates opportunity (sales pipeline) records into demand-planning facts; this is the object surfaced by the search term translate_opportunities_data, and it should not be mistaken for a standalone API.
• TRANSLATE_SALES_FORECAST — translates sales forecast facts.
• TRANSLATE_MFG_FORECAST — translates manufacturing forecast facts into MSD_MFG_FORECAST, using the declared collection types.
• TRANSLATE_PRICING_DATA — translates price list facts, working with MSD_PRICE_LIST.
• MFG_POST_PROCESS — performs post-load processing after manufacturing forecast translation.
• POPULATE_CALENDAR — populates the planning calendar (MSD_ST_TIME) used as the time dimension.
• IS_POST_PROCESS_REQUIRED — a function returning a flag indicating whether post-processing is needed for the current load.
• CLEAN_FACT_DATA — removes or resets staging fact data after translation.

No parameter lists are documented; callers should reference the package specification in the target instance.

Tables Accessed

Through APPS synonyms the package reads and writes:

• MSD_MFG_FORECAST — primary target of manufacturing forecast translation and the source of the declared collection types.
• MSD_CS_DATA, MSD_CS_DATA_HEADERS, MSD_CS_DATA_HEADERS_S, MSD_CS_DEFINITIONS — the collection/staging schema holding incoming fact rows, headers, and column definitions.
• MSD_DP_PARAMETERS — Demand Planning parameters that govern translation behaviour.
• MSD_PRICE_LIST — source for pricing fact translation.
• MSD_ST_TIME — the planning time dimension populated by POPULATE_CALENDAR.
• MSD_UOM_CONVERSIONS and MSD_ST_UOM_CONVERSIONS — conversion factors applied by TRANSLATE_UOM_CONVERSION.
• MSC_APPS_INSTANCES — identifies source application instances for multi-instance loads.
• DUAL and PLITBLM — utility references (PLITBLM is the standard EBS PL/SQL index-by table for ID lists).

Usage Notes

MSD_TRANSLATE_FACT_DATA is not intended for direct invocation from Oracle Forms. In 12.1.1 and 12.2.2 it is called by the collection-plan / Demand Planning concurrent programs that load data from the MSD_CS_* staging tables into the fact tables. The typical sequence is: staging load, then the appropriate TRANSLATE_* procedure, followed by IS_POST_PROCESS_REQUIRED, optional MFG_POST_PROCESS, and finally CLEAN_FACT_DATA. Custom integrations that bypass the standard loaders may call these procedures directly, but doing so requires that MSD_DP_PARAMETERS, the calendar (MSD_ST_TIME), and UOM/currency conversion tables be populated first. Because the specification has been stable since 2005 but the package is internally referenced, upgrade testing should verify signature compatibility rather than assuming the documented procedure names remain the only entry points.