Results for “dmd_satisfied_date”

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

Overview

The MSC_CONSTRAINED_FORECAST_V view is a reporting and integration object in the MSC - Advanced Supply Chain Planning product of Oracle E-Business Suite (available in both 12.1.1 and 12.2.2). It is owned by the APPS schema and is documented with a status of VALID in the ETRM repository. The view exposes constrained forecast demand information derived from the Advanced Supply Chain Planning (ASCP) engine, presenting demand records together with descriptive item attributes in a flattened, query-friendly form suitable for ad-hoc reporting, dashboards, and downstream data extraction.

Unlike a base planning table, this view joins demand records against plan and item metadata, providing end users and developers with a consolidated picture of forecasted demand, the associated plan context, customer information, and item classification. Its role is primarily to serve as a denormalized read layer over the planning demand tables, avoiding the need to write complex multi-table joins repeatedly.

Underlying Base Objects

The view is defined over three referenced base objects, accessed through synonyms in the APPS schema:

• MSC_DEMANDS — the core planning table holding individual demand records, including quantity by due date, origination type, planning group, and satisfied dates.
• MSC_PLANS — the plan definition table providing plan-level attributes such as the compile designator.
• MSC_SYSTEM_ITEMS — the planning item master supplying descriptive and classification attributes such as item name, description, UOM code, planner code, and ABC class name.

The view is constructed as a UNION ALL of two SELECT statements over these objects. The first branch returns quantities from QUANTITY_BY_DUE_DATE where demand, plan, and item records align on plan ID, SR instance ID, organization ID, and inventory item ID, and where ORIGINATION_TYPE falls within a defined set (6, 7, 8, 9, 11, 29, 30, 42). The second branch derives a residual quantity from USING_REQUIREMENT_QUANTITY less the quantity by due date, capturing the portion of requirement not yet scheduled to a specific due date. Both branches exclude records where PLAN_ID = -1 and require that the inventory item matches the using assembly item.

Key Columns

The view exposes the following principal columns:

• DEMAND_ID, PLAN_ID, SR_INSTANCE_ID — identifiers linking the demand to its plan and source instance context.
• COMPILE_DESIGNATOR — the compiled plan designator from MSC_PLANS.
• ORGANIZATION_ID, INVENTORY_ITEM_ID — the organization and item keys.
• ITEM_NAME, DESCRIPTION, UOM_CODE, PLANNER_CODE, ABC_CLASS_NAME — descriptive item metadata from MSC_SYSTEM_ITEMS.
• QUANTITY — demand quantity, either from quantity by due date or the residual requirement quantity.
• END_DATE — the using assembly demand date, or the demand satisfied date in the residual branch.
• CUSTOMER_ID, CUSTOMER_SITE_ID — customer identification for demand records.
• PROJECT_ID, TASK_ID, PLANNING_GROUP — project and grouping attributes.
• ORIGINATION_TYPE, ORDER_NUMBER — the source type of the demand and its originating order number.

Common Use Cases and Queries

This view is typically used to report constrained forecast demand by plan, item, or customer. A representative query filters on a specific compiled plan:

• Forecast demand summaries by organization and item for a given plan.
• Customer-level demand analysis for supply planning reviews.
• Extraction feeds into external BI tools or custom planning dashboards.

Example SQL:

SELECT plan_id, inventory_item_id, item_name, SUM(quantity) quantity
FROM msc_constrained_forecast_v
WHERE compile_designator = :plan_name
GROUP BY plan_id, inventory_item_id, item_name
ORDER BY quantity DESC;

Because the view already resolves plan and item joins, consumers can focus on aggregation and filtering logic rather than reconstructing the underlying relationship between MSC_DEMANDS, MSC_PLANS, and MSC_SYSTEM_ITEMS.