Search Results from_location_code

Overview

MRP_ATP_SD_TEMP_V is an APPS-owned database view within the Oracle E-Business Suite Master Scheduling/MRP (MRP) product family. It exposes the working contents of the ATP (Available-to-Promise) supply and demand temporary staging area used by the planning and scheduling engine. The underlying table MRP_ATP_DETAILS_TEMP stores in-progress supply and demand records generated during ATP, planning, and scheduling runs, and this view presents those records in a denormalized, presentation-ready form by resolving item, organization, department, resource, supplier, customer, and lookup meanings.

Because the object is a view and not a table, it holds no data of its own. Its rows reflect the current state of the underlying temporary structure for a given SESSION_ID, SCENARIO_ID, or ORDER_LINE_ID. This makes it valuable for diagnostics, reconciliation, and custom reporting on ATP results, particularly when standard concurrent program output is insufficient. The view is documented as VALID and owned by APPS, so it should be referenced with the APPS schema prefix in custom code. The inclusion of TO_LOCATION_CODE — the term the user searched — confirms that the view supports supply/demand records that carry both a from-location and a to-location, typical of transfer and shipping-related pegging.

Underlying Base Objects

The documented metadata lists three referenced base objects:

• MRP_ATP_DETAILS_TEMP (SYNONYM) — the primary source. In the view text it is aliased as MADT, and nearly every select-list column originates here.
• MFG_LOOKUPS (VIEW) — used for decoding lookup meanings, aliased as ML, ML1, and ML2. It resolves fields such as supply/demand source type and disposition into readable descriptions, and is applied via NVL to fall back across multiple lookup joins.
• MSC_SCH_WB (PACKAGE) — the scheduling workbench package. Although not joined directly in the excerpted SELECT text, it is documented as a referenced object and is relevant to how the temporary data is populated and interpreted.

The view text also references MAST and MADT1 aliases, which join to resolve organization, department, resource, and inventory item descriptions not stored directly on the row. Lookup translations are combined through DECODE and NVL logic to produce human-readable output.

Key Columns

• ORDER_LINE_ID, SESSION_ID, SCENARIO_ID — identify the ATP/scheduling context that produced the row.
• PEGGING_ID, PARENT_PEGGING_ID, END_PEGGING_ID — establish the pegging hierarchy linking supplies to their demands.
• INVENTORY_ITEM_ID / INVENTORY_ITEM_NAME, REQUEST_ITEM_ID / REQUEST_ITEM_NAME — the item being planned.
• ORGANIZATION_ID / ORGANIZATION_CODE, DEPARTMENT_ID / DEPARTMENT_CODE, RESOURCE_ID / RESOURCE_CODE — the source or consuming entity.
• FROM_LOCATION_ID / FROM_LOCATION_CODE, TO_LOCATION_ID / TO_LOCATION_CODE — origin and destination locations, central to transfer and shipment pegging. The searched term TO_LOCATION_CODE is the resolved, readable location identifier.
• SUPPLIER_ID / SUPPLIER_NAME, SUPPLIER_SITE_ID / SUPPLIER_SITE_NAME, CUSTOMER_ID / CUSTOMER_NAME — trading partner context.
• SUPPLY_DEMAND_TYPE, SUPPLY_DEMAND_DATE, SUPPLY_DEMAND_QUANTITY, SUPPLY_DEMAND_SOURCE_TYPE — the core supply/demand fact data.
• PERIOD_START_DATE, PERIOD_END_DATE, PERIOD_QUANTITY, CUMULATIVE_QUANTITY — time-phased ATP quantities.
• DISPOSITION_TYPE, DISPOSITION_NAME, DEMAND_CLASS, CLASS — classification and resolution status.

Common Use Cases and Queries

Typical uses include diagnosing why ATP failed to confirm a request, reconciling pegged supply against demand, and building custom transfer or shipping reports that require from/to location detail.

• Listing all supply/demand rows for a session, showing resolved locations.
• Filtering records by TO_LOCATION_CODE to audit inbound transfers.
• Reconciling period quantities against total supply and demand.

SELECT order_line_id,
       inventory_item_name,
       from_location_code,
       to_location_code,
       supply_demand_type,
       supply_demand_quantity
  FROM apps.mrp_atp_sd_temp_v
 WHERE session_id = :p_session_id
   AND to_location_code = :p_to_location
 ORDER BY supply_demand_date;

Because the view reads live temporary data, queries should always be constrained by SESSION_ID, SCENARIO_ID, or ORDER_LINE_ID to avoid scanning uncleared rows from unrelated runs.