Results for “end_project_number”

50+ results




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

Overview

MRP_FLP_ONHAND_V is a view owned by the APPS schema in Oracle E-Business Suite, documented under the MRP (Master Scheduling/MRP) product family. It is described in the ETRM metadata simply as a "View of on hand information," and it sits within the broader set of MRP reporting and pegging objects used by Oracle's planning and scheduling modules. The view consolidates current on-hand inventory balances with associated supply and demand detail, exposing a flattened, readable projection of pegging and allocation data that is otherwise distributed across the planning tables.

Its object name follows the MRP_FLP_* naming convention, where "FLP" is associated with the planning engine's full pegging and lead-time/flow logic. The view mixes on-hand quantities (from the MRP_ONHAND_QUANTITIES source) with pegging relationships derived from MRP_FULL_PEGGING and gross requirements from MRP_GROSS_REQUIREMENTS. As a result, MRP_FLP_ONHAND_V is used primarily in custom reporting and diagnostic queries to correlate an item's existing stock with the demands and supplies that have been pegged against it.

Underlying Base Objects

The documented view is defined over a joinset that includes both tables and synonyms resolving to other MRP views and tables. Documented base objects include:

  • MRP_FULL_PEGGING (synonym) — provides the pegging relationships that drive the parent/child demand structure.
  • MRP_ONHAND_QUANTITIES (synonym) — the primary source of on-hand quantity information, referenced as MFP2.NETTABLE_QUANTITY.
  • MRP_GROSS_REQUIREMENTS (synonym) — contributes the gross demand records.
  • MRP_ITEM_PURCHASE_ORDERS (synonym) — supplies purchase order and item procurement context (aliased MIP3).
  • MRP_SCHEDULE_DATES (synonym) — supplies scheduling/demand date data.
  • MTL_DEMAND (synonym) — source for demand class and demand attributes (SL3).
  • MTL_ITEM_FLEXFIELDS (view) — item number and description lookups (MIF2, MIF3).
  • MTL_PARAMETERS (synonym) — organization code lookups (MP2, MP3).
  • MTL_SALES_ORDERS and OE_ORDER_LINES_ALL (synonyms) — sales order context for demand origination.
  • WIP_ENTITIES (synonym) — work-in-process entity names for job/schedule origination types (WE3).
  • MFG_LOOKUPS (view) — decode meanings for demand/supply types (ML2, ML3).
  • MRP_GET_PROJECT (package) — invoked as a function to resolve project and task identifiers for both on-hand and demand rows.

Because it references multiple synonyms resolving to views, the view is a relatively heavy join and is best used with selective filters on organization and item.

Key Columns

The structure is largely a projection of the parent pegging record alongside a decoded child demand record. Significant columns include:

  • COMPILE_DESIGNATOR — the plan or compilation identifier; filters the pegging snapshot to a specific planning run.
  • ORGANIZATION_ID — inventory organization context.
  • PEGGING_ID / PREV_PEGGING_ID — identifies the pegging relationship and its parent link within the plan.
  • DEMAND_ID / DEMAND_DATE / DEMAND_QUANTITY — the demand record pegged to the on-hand supply.
  • END_ITEM_USAGE — a critical column representing the quantity of the end item consumed, used to apportion allocated quantity across the end-item structure. A derived column computes ROUND(ALLOCATED_QUANTITY / END_ITEM_USAGE, 2), guarded by DECODE(..., NULL, 0, ...).
  • INVENTORY_ITEM_ID and item number/organization concatenation — identify the component supply item.
  • NETTABLE_QUANTITY — the on-hand quantity available to planning, rounded to two decimals.
  • ALLOCATED_QUANTITY — the portion of on-hand allocated to consuming demands.
  • SUPPLY_TYPE / SUPPLY_DATE — the type and date of the supply (with special handling when DEMAND_ID = -1, treated as a supply record).
  • Demand-class and attribute columns (DEMAND_CLASS_CODE, ATTRIBUTE1–ATTRIBUTE15) — sourced from MTL_DEMAND for segmentation and reporting.
  • Origination columns — decoding via MGR3.ORIGINATION_TYPE to return WIP_ENTITY_NAME, PO_NUMBER, or sales order SEGMENT1.
  • Project/task and end-item-unit-number columns — resolved through MRP_GET_PROJECT and the pegging records.

Common Use Cases and Queries

Typical uses include reconciling on-hand inventory to pegged demand, validating allocation to end items through END_ITEM_USAGE, and diagnosing supply/demand imbalances within a plan. A representative query:

SELECT organization_id,
       inventory_item_id,
       end_item_usage,
       demand_quantity,
       allocated_quantity,
       nettable_quantity,
       supply_type
FROM   apps.mrp_flp_onhand_v
WHERE  organization_id = :org_id
AND    inventory_item_id = :item_id;

Because END_ITEM_USAGE appears directly in the view, it is frequently selected alongside the derived allocation-per-usage ratio to determine how many component units are consumed per end item in multi-level pegging scenarios. The view is read-only, so it should be used strictly for querying and reporting rather than transaction processing.