Results for “previous_customer_id”

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

Overview

MRP_SO_UPDATES_SUMMARY_V is an APPS-owned database view in the Oracle E-Business Suite environment, delivered as part of the MRP (Master Scheduling/MRP) product family. It is documented as a "Sales order summary view" and is intended to expose a normalized, flattened representation of sales order demand relevant to the Material Requirements Planning engine. In practice, the view functions as a staging and reporting abstraction over the MTL_DEMAND_OMOE table, presenting only those demand records that are candidates for MRP processing according to a fixed set of filter predicates. Rather than requiring downstream consumers to re-implement the eligibility logic, the view encapsulates it, exposing a stable column layout that MRP components, diagnostics, and custom reports can query consistently across EBS 12.1.1 and 12.2.2. The view carries a status of VALID in the data dictionary and is not intended for direct DML, being read-only by construction.

The view is particularly relevant to users investigating the previous_ship_id column and related "PREVIOUS_*" attributes. These columns are characteristic of the MRP sales order update workflow, which captures before-and-after images of demand attributes so that scheduling changes can be tracked, sequenced, and reconciled by the planning engine.

Underlying Base Objects

The primary source object is MTL_DEMAND_OMOE, the order-management variant of the demand table, aliased as DEM in the view definition. The WHERE clause constrains records with AVAILABLE_TO_MRP = 1, DEMAND_SOURCE_TYPE IN (2, 8), non-null CUSTOMER_ID, SHIP_TO_SITE_USE_ID, and BILL_TO_SITE_USE_ID, PARENT_DEMAND_ID IS NULL, OPEN_FLAG = 'Y', and COMPLETED_QUANTITY = 0. This isolates open, MRP-eligible sales order demand at the line level.

The documented metadata further lists the following referenced base objects: INV_DECIMALS_PUB (PACKAGE), INV_SALESORDER (PACKAGE), MRP_CALENDAR (PACKAGE), and OE_ORDER_LINES_ALL (SYNONYM). These reflect the dependency chain used by the surrounding MRP logic — INV_DECIMALS_PUB supplies unit-of-measure precision handling, INV_SALESORDER and OE_ORDER_LINES_ALL provide sales order line context, and MRP_CALENDAR supports requirement-date calculations. The view itself is defined over MTL_DEMAND_OMOE, with the packages and synonym referenced by the broader MRP sales order update mechanism.

Key Columns

The view exposes the following columns, which map to demand attributes or fixed placeholders:

• INVENTORY_ITEM_ID — the planned item.
• ORDERED_ITEM_ID — populated via DECODE on DEMAND_TYPE, returning the item only when the demand type is 1.
• SALES_ORDER_ID — maps to DEMAND_ID.
• ORGANIZATION_ID — the inventory organization owning the demand.
• OLD_SCHEDULE_DATE / OLD_SCHEDULE_QUANTITY — prior schedule values used for update comparison.
• PREVIOUS_AVAILABLE_TO_MRP — fixed literal 'Y', marking prior eligibility.
• PREVIOUS_CUSTOMER_ID, PREVIOUS_SHIP_ID, PREVIOUS_BILL_ID — prior customer, ship-to, and bill-to identifiers.
• PREVIOUS_DEMAND_CLASS, LINE_NUM, BASE_MODEL_ID, PREVIOUS_TERRITORY_ID — prior classification and model context.
• UPDATE_SEQ_NUM — sequencing value (TO_NUMBER(NULL) placeholder in this definition).
• ERROR_MESSAGE, PROCESS_STATUS — messaging and status columns (TO_CHAR(NULL) and constant 5 respectively).

Common Use Cases and Queries

Typical usage includes diagnosing MRP sales order update errors and reconciling prior versus current demand attributes such as PREVIOUS_SHIP_ID.

• Reviewing pending updates for a given organization.
• Auditing ship-to changes against prior ship identifiers.
• Feeding custom planning extracts.

Sample query:

SELECT sales_order_id, inventory_item_id, organization_id, previous_ship_id, previous_bill_id, previous_customer_id, process_status FROM apps.mrp_so_updates_summary_v WHERE organization_id = :org_id;

A variant filtering by item:

SELECT sales_order_id, old_schedule_date, old_schedule_quantity, previous_available_to_mrp FROM apps.mrp_so_updates_summary_v WHERE inventory_item_id = :item_id;