Search Results mrp_ap_rept_items_sn

Overview

MRP_AP_REPT_ITEM_SUPPLIES_V is a reporting view belonging to the Oracle Master Scheduling/MRP (MRP) product family. It presents supply-side information for items associated with repetitive manufacturing schedules, combining item master attributes, repetitive schedule header details, and work-in-process (WIP) scrap and operation data into a single denormalized structure. The view is part of the broader MRP_AP_REPT_* family, whose members (including MRP_AP_REPT_ITEMS_SN, MRP_AP_REPT_SCHDS_SN, MRP_AP_SYS_ITEMS_SN, MRP_AP_MRP_PARAS_SN, and MRP_AP_WOPRS_SN) supply the constituent rows used to assemble repetitive supply data for planning and reporting.

In the context of Oracle EBS 12.1.1 and 12.2.2, this object is documented as not implemented in the EBS database itself. It is instead a supply-chain planning schema object (note the AP suffix convention associated with Advanced Planning/collection-style reporting), surfaced for reference through ETRM. As a result, it is primarily consumed by planning engines, data collection programs, and custom reports that need repetitive supply quantities and dates without joining the underlying transactional tables directly.

Underlying Base Objects

Per the documented view text, MRP_AP_REPT_ITEM_SUPPLIES_V is defined over the following objects:

• MRP_AP_WOPRS_SN — outer-joined (via the (+) operator) on REPETITIVE_SCHEDULE_ID and ORGANIZATION_ID to supply scrap quantity, operation sequence number, and a row number (RN) used for aggregation.
• MRP_AP_REPT_ITEMS_SN (WRI) — the driving repetitive item source, providing primary item ID, organization, WIP entity ID, repetitive schedule ID, line ID, and row-number values.
• MRP_AP_REPT_SCHDS_SN (WRS) — joined on WIP_ENTITY_ID, ORGANIZATION_ID, and LINE_ID to provide schedule dates, processing days, daily rate, BOM revision, status, firm planned flag, quantity completed, and demand class.
• MRP_AP_SYS_ITEMS_SN (MSI) — joined on ORGANIZATION_ID and INVENTORY_ITEM_ID = PRIMARY_ITEM_ID to supply FULL_LEAD_TIME and a row number.
• MRP_AP_MRP_PARAS_SN (MP) — joined on ORGANIZATION_ID to supply an additional row number for query parameterization.

No base tables outside these MRP_AP_* staging sources are documented as referenced objects.

Key Columns

• PRIMARY_ITEM_ID / ORGANIZATION_ID — inventory item and operating unit/inventory organization keys.
• WIP_ENTITY_ID / REPETITIVE_SCHEDULE_ID / LINE_ID — identity of the repetitive schedule and production line.
• FIRST_UNIT_START_DATE / FIRST_UNIT_COMPLETION_DATE / LAST_UNIT_START_DATE / LAST_UNIT_COMPLETION_DATE — scheduling window for the repetitive supply.
• PROCESSING_WORK_DAYS / DAILY_PRODUCTION_RATE — capacity and throughput attributes of the schedule.
• BOM_REVISION — bill revision associated with the supply.
• STATUS_CODE (STATUS_TYPE) / FIRM_PLANNED_FLAG — schedule state and firming indicator.
• QUANTITY_COMPLETED / QUANTITY_SCRAPPED — completed and scrapped quantities, with NVL applied to suppress nulls.
• FULL_LEAD_TIME — cumulative lead time sourced from the system item record.
• OPERATION_SEQ_NUM — operation sequence from the WIP repetitive scrap source.
• DEMAND_CLASS — demand classification for the supply.
• RN1–RN5 — internal row-number columns used to control grouping and ranking within the query.

Common Use Cases and Queries

The view is typically used to report repetitive supply by item and organization, to compare completed versus scrapped quantities, or to feed planning extracts with schedule dates and lead times.

• Repetitive supply listing for a given organization and item.
• Completed versus scrapped quantity comparison per schedule.
• Schedule window and throughput reporting for a production line.

Sample query:

SELECT primary_item_id, organization_id, repetitive_schedule_id, first_unit_start_date, last_unit_completion_date, daily_production_rate, quantity_completed, quantity_scrapped, full_lead_time, demand_class FROM mrp_ap_rept_item_supplies_v WHERE organization_id = :org_id AND primary_item_id = :item_id ORDER BY first_unit_start_date;

Because the object is not implemented in the EBS database in either 12.1.1 or 12.2.2, such queries are relevant only where the MRP_AP_* staging schema is present. Standard EBS repetitive supply reporting relies instead on WIP and MRP base tables.