Results for “sr_customer_id”

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

Overview

MSD_DP_ASCP_SCN_ENTRIES_V is a PL/SQL view owned by the APPS schema within the MSD (Demand Planning) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its documented purpose is to provide the integration API with Advanced Supply Chain Planning (ASCP) for scenario entries. In practice, the view acts as the publication surface through which a released demand plan scenario is exposed to the ASCP planning server, flattening the hierarchical, level-based structure of demand planning data into a form that the planning engine can consume as input.

The object carries a VALID status in the report metadata, indicating the definition compiles and resolves against the underlying synonyms and packages. Because it is an integration view rather than a transactional table, it exposes no updateable columns and is intended strictly for read access by the ASCP collection process and for diagnostic querying by technical consultants. Users searching for the term forecast_error in connection with this object will find that the view exposes a column of that name sourced from the scenario revisions table, making it one of the few integration surfaces where forecast accuracy information is published to the planning engine.

Underlying Base Objects

The view is defined over a set of APPS synonyms rather than base tables directly. The documented referenced objects are:

• MSD_DP_SCENARIO_ENTRIES — the primary source of scenario entry facts.
• MSD_DP_SCENARIOS — supplies plan/scenario identity and the PUBLISH_FLAG used to restrict output to released scenarios.
• MSD_DP_SCENARIO_REVISIONS — source of revision context and the ERROR_TYPE and FORECAST_ERROR columns.
• MSD_DEMAND_PLANS — provides plan-level attributes such as ROUNDOFF_DECIMAL_PLACES.
• MSC_SYSTEM_ITEMS — the ASCP-side item master, joined for UOM codes, inventory item ID, list price, and average discount.
• MSD_DP_SCN_ENTRIES_DENORM — a denormalized helper object referenced in the definition.
• MSC_APPS_INSTANCES — instance-level context.
• MSD_COMMON_UTILITIES — a package supplying UOM conversion and hierarchy parent lookup functions.

The view text shows an explicit index hint on MSC_SYSTEM_ITEMS (MSC_SYSTEM_ITEMS_U3) and joins MSC_SYSTEM_ITEMS with PLAN_ID = -1, which is the conventional marker for the ASCP master item definition rather than a plan-specific copy. The WHERE clause also restricts ORGANIZATION_LVL_ID to 7 and PRODUCT_LVL_ID to (1, 3), and requires DS.PUBLISH_FLAG = 'Y' together with MDSE.REVISION = DS.LAST_REVISION, so only the latest published revision of an eligible scenario passes through.

Key Columns

The projection includes identity, time, quantity, hierarchy, and accuracy attributes:

• DEMAND_PLAN_ID, SCENARIO_ID, ENTRY_ID — composite identifiers for the scenario entry.
• TIME_LVL_VAL_FROM / TIME_LVL_VAL_TO — the time bucket range, with the time level mapped via DECODE on TIME_LVL_ID (9 to 1, 1 to 2, otherwise 3).
• QUANTITY — the total quantity converted to the item's UOM through MSD_COMMON_UTILITIES.MSD_UOM_CONVERT and rounded to the plan's ROUNDOFF_DECIMAL_PLACES (default 6).
• SR_ORGANIZATION_LVL_PK, SR_PRODUCT_LVL_PK, and the geography-level columns — surrogate hierarchy keys, nulled to -1 when non-numeric, with parent-level resolution applied at GEOGRAPHY_LVL_ID 11.
• ERROR_TYPE — drawn from MSD_DP_SCENARIO_REVISIONS, indicating the revision error classification.
• FORECAST_ERROR — the forecast error measure associated with the scenario entry, exposed directly from MSD_DP_SCENARIO_ENTRIES for consumption by ASCP.
• FORECAST_PRIORITY, DEMAND_CLASS, TOTAL_QUANTITY_UOM, UOM_CODE — planning classification and unit attributes.
• INVENTORY_ITEM_ID — the ASCP item key from MSC_SYSTEM_ITEMS.
• The final AMOUNT-derived column returns unit price from MDSE.AMOUNT / MDSE.TOTAL_QUANTITY, falling back to LIST_PRICE adjusted by AVERAGE_DISCOUNT.

Common Use Cases and Queries

Typical usage is validating what a published scenario will hand to ASCP, and investigating forecast error and its relationship to demand quantities. A basic inspection query is:

• SELECT DEMAND_PLAN_ID, SCENARIO_ID, ENTRY_ID, TIME_LVL_VAL_FROM, QUANTITY, FORECAST_ERROR FROM APPS.MSD_DP_ASCP_SCN_ENTRIES_V;

To isolate entries carrying forecast error within a specific plan:

• SELECT SCENARIO_ID, ENTRY_ID, SR_PRODUCT_LVL_PK, QUANTITY, FORECAST_ERROR, ERROR_TYPE FROM APPS.MSD_DP_ASCP_SCN_ENTRIES_V WHERE DEMAND_PLAN_ID = :plan_id AND FORECAST_ERROR IS NOT NULL;

For release verification, joining back to MSD_DP_SCENARIOS confirms the PUBLISH_FLAG and LAST_REVISION alignment, while comparing row counts against MSD_DP_SCN_ENTRIES_DENORM helps detect hierarchy-level filtering effects. Because the view depends on MSD_COMMON_UTILITIES functions, query performance is sensitive to UOM conversion calls, and restricting by DEMAND_PLAN_ID is advisable before applying any additional predicates.