Results for “mrpbv_mps_entries”

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

Overview

MRPBV_MPS_ENTRIES is an APPS-owned read-only view in the Oracle E-Business Suite Master Scheduling/MRP (MRP) product family. It presents Master Production Schedule (MPS) entries in a denormalized, reporting-friendly format by joining schedule date records to their owning schedule items, schedule designators, and lookup meanings. In the ETRM 12.2.2 metadata the object is documented as a retrofitted view, meaning it was preserved across release upgrades to maintain backward compatibility for custom reports, integrations, and concurrent programs that reference it by name.

The view exposes only MPS-type schedules. The predicate SCDE.SCHEDULE_TYPE = 2 restricts output to MPS designators, excluding MRP and other schedule types held in the same underlying tables. Because the view text carries the WITH READ ONLY clause, it cannot be used as a DML target. Its primary role is to support inquiry, extraction, and interface extracts of MPS quantities, dates, and originating transaction context.

Underlying Base Objects

The view is defined over four referenced objects: MFG_LOOKUPS, MRP_SCHEDULE_DATES, MRP_SCHEDULE_ITEMS, and MRP_SCHEDULE_DESIGNATORS. MFG_LOOKUPS is itself a view in the APPS schema; the remaining three are accessed through APPS synonyms over the MRP base tables.

• MRP_SCHEDULE_DATES (SCDA) — the driving table, supplying schedule dates, quantities, comments, unit numbers, transaction identifiers, and org context.
• MRP_SCHEDULE_ITEMS (SCIT) — joined on inventory item, organization, and schedule designator, defining which items participate in a given schedule.
• MRP_SCHEDULE_DESIGNATORS (SCDE) — joined on organization and schedule designator, providing the schedule type used to filter to MPS.
• MFG_LOOKUPS (LKUP) — joined on lookup code and the lookup type MRP_SCHEDULE_ORIG, supplying the meaning of the schedule origination type.

The final predicate, '_SEC:SCDA.ORGANIZATION_ID' IS NOT NULL, implements organization-level (multi-org) security filtering on the schedule dates table.

Key Columns

• SCHEDULE_DATE / END_DATE — the effective date of the MPS entry and its rate end date.
• CURRENT_QUANTITY — the scheduled quantity for the entry; the column most frequently targeted by searches such as "current_quantity". It corresponds to SCHEDULE_QUANTITY in MRP_SCHEDULE_DATES.
• ORIGINAL_QUANTITY — the original schedule quantity prior to revision.
• REPETITIVE_ITEM_DAILY_RATE — daily rate for repetitive MPS items.
• ORIGINATION_TYPE — the lookup meaning describing how the entry was created (for example, manually entered or copied from a forecast).
• MPS_ENTRY_ID, PLAN_SUPPLY_ID, FORECAST_ENTRY_ID — surrogate identifiers linking the entry to its source MPS transaction, plan supply, and forecast.
• INVENTORY_ITEM_ID, ORGANIZATION_ID, SCHEDULE_NAME — the item, operating unit organization, and schedule identity.
• SOURCE_FORECAST_NAME, SOURCE_SCHEDULE_NAME, SOURCE_ORGANIZATION_ID — traceability to the originating forecast or schedule when the entry was copied or referenced.
• PROJECT_ID, TASK_ID, LINE_ID — project and task accounting references.
• LAST_UPDATE_DATE, CREATED_BY and related audit columns — standard EBS who-columns.

Common Use Cases and Queries

Typical uses include MPS quantity inquiries, reconciliation of current versus original quantities, and extraction feeds to planning or reporting systems. A basic current-quantity query:

• SELECT schedule_name, inventory_item_id, schedule_date, current_quantity, original_quantity, origination_type FROM apps.mrpbv_mps_entries WHERE organization_id = :org_id AND schedule_date BETWEEN :start_date AND :end_date ORDER BY schedule_date;

To isolate entries whose quantity has been revised:

• SELECT mps_entry_id, inventory_item_id, schedule_date, current_quantity, original_quantity FROM apps.mrpbv_mps_entries WHERE current_quantity <> original_quantity AND organization_id = :org_id;

To summarize forecast-originated supply by item:

• SELECT inventory_item_id, source_forecast_name, SUM(current_quantity) FROM apps.mrpbv_mps_entries WHERE origination_type = :lookup_meaning GROUP BY inventory_item_id, source_forecast_name;

Because the view is read-only and secured by organization, all queries should bind ORGANIZATION_ID and are best executed through the MRP responsibility so that organization security is applied consistently.