Search Results mrp_ap_wreq_oprs_sn

Overview

MRP_AP_REPT_ITEM_DEMANDS_V is a reporting view within the Oracle EBS Master Scheduling/MRP (MRP) module. The "AP" infix and the "_SN" suffix on its underlying objects identify it as part of the Oracle Advanced Planning / constrained planning snapshot collection, a set of denormalized staging tables populated during a planning run. The view consolidates component-level demand from work in process (WIP) and repetitive schedules into a single flat structure suitable for reporting and integration, exposing the quantity required, the quantity issued, and the resulting allocated (open) quantity for each inventory item against a discrete job or repetitive schedule.

Because its source tables are snapshot collections rather than live transactional tables, the view reflects the state of demand captured at the moment the planning snapshot was taken. It is not a real-time operational view; results are only meaningful while the associated planning data is populated and current. Oracle documents this object with no base objects and no implementation in the database in the corresponding ETRM entry, confirming that it is a functional/documented definition rather than one requiring separate DBA implementation.

Underlying Base Objects

The view is defined over six objects, each aliased in the view text:

• WIP_ENTITIES (WE) — supplies the work order identifier and the WIP entity name.
• MRP_AP_MRP_PARAS_SN (MP) — snapshot MRP planning parameters, joined by organization.
• MRP_AP_SYS_ITEMS_SN (MSIK) — snapshot item master information, joined by inventory item and organization.
• MRP_AP_WREQ_OPRS_SN (WRO) — snapshot WIP requirement operations, providing required quantity, quantity issued, and quantity per assembly.
• MRP_AP_REPT_SCHDS_SN (WRS) — snapshot repetitive schedules, providing completion dates, demand class, and the repetitive schedule identifier.
• MRP_AP_REPT_ITEMS_SN (WRI) — snapshot repetitive items, providing the job reference item and line identifier.

Joins are keyed on organization, WIP entity, line, and repetitive schedule identifiers. The filter WRO.MRP_NET_FLAG = 1 restricts output to requirement operations flagged as nettable for planning purposes.

Key Columns

• INVENTORY_ITEM_ID / ORGANIZATION_ID — identify the demanded component and the owning inventory organization.
• WIP_ENTITY_ID / WIP_ENTITY_NAME — the discrete job or repetitive schedule supplying the demand.
• REQUIRED_QUANTITY — total component quantity required by the job or schedule.
• QUANTITY_ISSUED — a derived net figure: NVL(QUANTITY_ISSUED,0) minus (NVL(QUANTITY_COMPLETED,0) multiplied by NVL(QUANTITY_PER_ASSEMBLY,0)).
• ALLOCATED_QUANTITY — the open balance, computed as REQUIRED_QUANTITY minus QUANTITY_ISSUED.
• JOB_REFERENCE_ITEM_ID — the primary item of the assembly being built.
• WIP_ENTITY_TYPE — hard-coded to 2, denoting a repetitive schedule context.
• ORIGINATION_TYPE — hard-coded to the literal value 4. This is the column most frequently searched under the "origination_type" keyword, and it is important to note that it is a constant, not a populated descriptive field.
• DEMAND_CLASS, FIRST_UNIT_START_DATE, LAST_UNIT_COMPLETION_DATE — planning attributes carried from the schedule snapshot.
• RN1 through RN5 — internal row-number columns retained from the source snapshot queries.

Common Use Cases and Queries

Typical usage centers on component shortage and open-demand analysis against WIP and repetitive schedules within a planning snapshot.

• Listing open allocated component demand for a given organization.
• Identifying jobs with significant unissued component quantities.
• Feeding demand and supply data into custom planning or reporting extracts.

SELECT inventory_item_id,
       organization_id,
       wip_entity_name,
       required_quantity,
       quantity_issued,
       allocated_quantity,
       demand_class,
       origination_type
  FROM mrp_ap_rept_item_demands_v
 WHERE organization_id = :org_id
   AND allocated_quantity > 0
 ORDER BY wip_entity_name;

Because ORIGINATION_TYPE and WIP_ENTITY_TYPE are constants in this view, queries filtering on origination_type = 4 will return all rows; consumers relying on that column for categorization should source it from a transactional WIP or demand table instead.