Results for “mps_net_quantity”

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

Overview

MRP_WIP_JOBS_VIEW is an APPS-owned database view in the Oracle E-Business Suite Master Scheduling/MRP product family. Its documented purpose is to serve as a WIP job supply view — that is, it consolidates discrete jobs and flow schedules from Work in Process and exposes them in a form the MRP planning engine and supply/demand inquiries can consume as supply. The view is valid in both Oracle EBS 12.1.1 and 12.2.2 and is defined in the APPS schema, meaning it is normally queried through APPS responsibilities and synonyms rather than accessed directly by end users.

Because MRP works with nettable supply, this view precomputes and normalizes several derived quantities, most notably the remaining open quantity to be completed. For discrete jobs these are derived from MPS_NET_QUANTITY and NET_QUANTITY; for flow schedules they are derived from PLANNED_QUANTITY. Negative results are clamped to zero using GREATEST(0, ...), and shrinkage is applied only to discrete jobs (JOB_TYPE = 1) using the item shrinkage rate — negative or null rates are treated as zero via DECODE(SIGN(...)) and NVL.

Underlying Base Objects

The documented base objects referenced by the view are MRP_SYSTEM_ITEMS, WIP_DISCRETE_JOBS, WIP_ENTITIES, and WIP_FLOW_SCHEDULES (all accessed as SYNONYMs). The view is a UNION ALL of two branches:

• Discrete job branch: joins WIP_ENTITIES, MRP_SYSTEM_ITEMS, and WIP_DISCRETE_JOBS on ORGANIZATION_ID and WIP_ENTITY_ID, with the item matched on INVENTORY_ITEM_ID = PRIMARY_ITEM_ID.
• Flow schedule branch: reads WIP_FLOW_SCHEDULES with WIP_ENTITIES and MRP_SYSTEM_ITEMS, again keying on organization, WIP entity, and primary item.

WIP_ENTITIES provides the WIP_ENTITY_NAME (the job or schedule name and number), while MRP_SYSTEM_ITEMS supplies planning-relevant item attributes including shrinkage rate, full pegging flag, and compile designator. The join effectively restricts the output to planned, nettable organizations and items.

Key Columns

• PRIMARY_ITEM_ID, ORGANIZATION_ID, COMPILE_DESIGNATOR — item and organization keys; the compile designator supports planning in a specific configured context.
• WIP_ENTITY_ID, WIP_ENTITY_NAME — the WIP job/schedule identifier and its user-facing name.
• MPS_NET_QUANTITY / MPS_SCHEDULED_COMPLETION_DATE — MPS-level supply quantity and its truncated completion date.
• NET_QUANTITY / SCHEDULED_COMPLETION_DATE — MRP-level supply quantity and truncated completion date.
• QUANTITY_COMPLETED, QUANTITY_SCRAPPED — quantities already completed and scrapped, subtracted from net quantities to derive open supply.
• Derived open-quantity columns — GREATEST(0, quantity − completed − scrapped), with separate MPS and MRP variants, plus corresponding shrinkage-adjusted values for discrete jobs.
• FIRM_PLANNED_FLAG — indicates whether the job is firmed, affecting how MRP treats it as a firm supply.
• SCHEDULED_START_DATE, BOM_REVISION, STATUS_TYPE, JOB_TYPE, DEMAND_CLASS — planning and identification attributes; JOB_TYPE distinguishes discrete jobs from flow schedules.
• PROJECT_ID, TASK_ID, SCHEDULE_GROUP_ID, BUILD_SEQUENCE, LINE_ID, ALTERNATE_ROUTING_DESIGNATOR, ALTERNATE_BOM_DESIGNATOR, FULL_PEGGING, END_ITEM_UNIT_NUMBER — project/task references, scheduling sequencing, routing/BOM alternates, pegging and end-item unit attributes.

Common Use Cases and Queries

Typical uses include reconciliation of WIP supply as seen by MRP, supply/demand and pegging analysis, and custom planning reports. A basic query listing open discrete job supply by organization and item might read:

• SELECT organization_id, primary_item_id, wip_entity_name, mps_net_quantity, net_quantity, scheduled_completion_date FROM mrp_wip_jobs_view WHERE organization_id = :org_id ORDER BY scheduled_completion_date;

For MPS-level analysis the MPS_NET_QUANTITY and MPS_SCHEDULED_COMPLETION_DATE columns are used in place of the net_quantity columns. To isolate firmed supply, filter with firm_planned_flag = 1. To distinguish discrete jobs from flow schedules, filter on job_type. Because the view already applies the completed/scrapped and shrinkage logic, planners should not re-derive open supply from raw WIP tables. Access is normally granted through APPS synonyms for MRP reports and custom concurrent programs.