Results for “days_from_today”

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

Overview

The APPS.MRPBV_PLAN_DEMANDS view is a reporting and integration construct within the Oracle E-Business Suite Master Scheduling/MRP (MRP) product family. It presents a consolidated, denormalized projection of planned demand information drawn from the MRP planning engine's gross requirements and associated disposition, supply, and scheduling records. The view carries a "Retrofitted" description status, indicating that it was adapted for compatibility with the multi-org and ledger structures that evolved across the 11i to 12.1.1 and 12.2.2 releases. It exposes demand-side planning data — quantities, dates, origination types, and disposition identifiers — alongside organization, item, and project context, making it suitable for downstream reporting, ad-hoc inquiry, and integration extracts that require planned demand visibility without directly navigating the normalized MRP schema. Because it joins the plan definition table to the gross requirements rows, the view is inherently plan-scoped and is typically filtered by compile designator and organization.

Underlying Base Objects

The view is defined over thirteen referenced objects. The central fact source is MRP_GROSS_REQUIREMENTS, aliased as MGR, which supplies the demand quantity, dates, firm status, origination type, planning group, end-item unit number, and demand identifier. Plan context is provided by MRP_PLANS (PLAN), which contributes the compile designator, and by MRP_PLAN_ORGANIZATIONS (PLANORG). Item and organization resolution comes from MRP_SYSTEM_ITEMS (MRPITEM) joined to MTL_SYSTEM_ITEMS (SYSITEM) on organization and inventory item, and from MTL_PARAMETERS (PA) on organization. Disposition detail is enriched through outer joins to MRP_RECOMMENDATIONS (SUPPLY), MRP_ITEM_PURCHASE_ORDERS (IPO), and MRP_ITEM_WIP_ENTITIES (IWE), all keyed on MGR.DISPOSITION_ID with organization and item companions. Scheduling dates and the MPS transaction linkage are supplied by MRP_SCHEDULE_DATES (DATES), while MTL_SALES_ORDERS (SO) contributes sales order context. Decoded origination meanings are retrieved from MFG_LOOKUPS (LKUP). All non-view references are synonyms resolving to their APPS base tables. The joins are predominantly primary-key/foreign-key relationships anchored on the gross requirement row.

Key Columns

• COMPILE_DESIGNATOR — identifies the MRP plan under which the demand was generated.
• MEANING — decoded origination type description sourced from MFG_LOOKUPS.
• USING_ASSEMBLY_DEMAND_DATE — the effective demand date used by the planning engine.
• DAILY_DEMAND_RATE / USING_REQUIREMENTS_QUANTITY — quantity basis for the demand; the view negates this value to represent demand as a negative contribution.
• FIRM_DATE and FIRM_QUANTITY — the firming horizon and firm quantity for the requirement.
• ASSEMBLY_DEMAND_COMP_DATE, OLD_DEMAND_DATE, OLD_DEMAND_QUANTITY — comparison and historical demand fields.
• DEMAND_ID — primary identifier of the gross requirement row.
• ORGANIZATION_ID, INVENTORY_ITEM_ID, PLANNING_GROUP, END_ITEM_UNIT_NUMBER — planning context attributes.
• PROJECT_ID, TASK_ID, LENDING_PROJECT_ID, LENDING_TASK_ID — project and task accounting context.
• SOURCE_ORGANIZATION_ID — originating organization for inter-org demand.
• Derived WIP entity, transaction, and MPS transaction identifiers — resolved conditionally by origination type via DECODE.

Common Use Cases and Queries

A typical use is extracting firm planned demands for a specific plan and organization, for example:

SELECT compile_designator, organization_id, inventory_item_id,
       using_assembly_demand_date, daily_demand_rate, demand_id
FROM   apps.mrpbv_plan_demands
WHERE  compile_designator = :plan
AND    organization_id = :org
ORDER  BY using_assembly_demand_date;

Users searching for new_quantity should note that the view does not expose a column literally named NEW_QUANTITY; the quantity semantics are carried by DAILY_DEMAND_RATE and USING_REQUIREMENTS_QUANTITY, which are returned negated. Queries seeking a "new" quantity should therefore alias these columns accordingly. The view is also commonly used to reconcile demand against supply recommendations, to feed custom planning dashboards, and to integrate planned demand into external reporting or data-warehouse loads, always constrained by compile designator and organization for performance.