Search Results user_line_num




Overview
Explore in AI Chat

Overview

PJM_PROJECT_OM_DEMAND_V is a seeded APPS view in Oracle EBS Project Manufacturing (PJM). It consolidates open sales order demand lines and presents them in a normalized demand format that can be consumed by planning, project manufacturing, and reservation logic. The view joins order management lines to inventory demand records so that sales order schedules appear as a single, planning-ready demand stream, with explicit references to PROJECT_ID, TASK_ID, and END_ITEM_UNIT_NUMBER for project and task-based manufacturing.

The view is exposed through the standard demand-source interface convention used across Oracle planning and supply chain modules. It returns a fixed literal DEMAND_SOURCE_TYPE of 2 (sales order) and a RESERVATION_TYPE of 1, which signals that this demand stream is intended for reservation and planning purposes rather than for transactional update.

Underlying Base Objects

The view is defined over two base sources and is assisted by several packages and synonyms:

Key Columns

  • PRIMARY_UOM_QUANTITY — the ordered quantity converted to the item's primary UOM using INV_DECIMALS_PUB.GET_PRIMARY_QUANTITY(SHIP_FROM_ORG_ID, INVENTORY_ITEM_ID, ORDER_QUANTITY_UOM, ORDERED_QUANTITY). This is the column most frequently searched for and the primary driver of on-hand and reservation analysis.
  • COMPLETED_QUANTITY — the shipped quantity similarly converted to primary UOM.
  • MRP_QUANTITY and MRP_DATE — the planning quantity and date derived from MRP_OE, used as demand input to MRP.
  • DEMAND_ID — set to LINE_ID, providing a unique demand identifier.
  • DEMAND_SOURCE_HEADER_ID / DEMAND_SOURCE_LINE — header resolution via INV_SALESORDER and the character form of LINE_ID.
  • RESERVATION_QUANTITY — NVL(MD.PRIMARY_UOM_QUANTITY, 0) from MTL_DEMAND.
  • PROJECT_ID / TASK_ID / END_ITEM_UNIT_NUMBER — project manufacturing identifiers carried directly from the order line.
  • AVAILABLE_TO_MRP / UPDATED_FLAG — planning control flags returned by MRP_OE.

Common Use Cases and Queries

Typical usage includes reservation verification, project demand reporting, MRP demand-source extraction, and reconciliation to MTL_DEMAND. The following query returns primary UOM quantities for a specific project:

  • Project demand analysis: SELECT inventory_item_id, demand_id, primary_uom_quantity, reservation_quantity, mrp_quantity, project_id, task_id FROM pjm_project_om_demand_v WHERE project_id = :project_id AND organization_id = :org_id;
  • Primary UOM quantity lookup for a specific order line: SELECT demand_source_header_id, demand_source_line, primary_uom_quantity, completed_quantity FROM pjm_project_om_demand_v WHERE demand_id = :line_id;
  • Comparing ordered versus reserved demand by item: SELECT inventory_item_id, SUM(primary_uom_quantity) ordered_qty, SUM(reservation_quantity) reserved_qty FROM pjm_project_om_demand_v WHERE organization_id = :org_id GROUP BY inventory_item_id;

Because the view relies on package functions per row, large queries should be restricted by INVENTORY_ITEM_ID, ORGANIZATION_ID, or PROJECT_ID to avoid performance degradation.