Search Results msc_po_requisitions_interface




Overview
Explore in AI Chat

Overview

The MSC_PO_REQUISITIONS_INTERFACE table resides in the MSC schema and forms part of Oracle Advanced Supply Chain Planning (ASCP) in Oracle E-Business Suite 12.1.1 and 12.2.2. It functions as the Requisition Import interface table, acting as the staging ground through which planning recommendations—principally planned orders for buy items—are translated into requisition records that the Purchasing module subsequently imports. The Planning Manager and related concurrent programs write to this table; the Requisition Import process reads it, validates the rows, and creates actual requisitions and requisition lines in PO_REQUISITIONS_INTERFACE and downstream PO_REQUISITION_HEADERS_ALL / PO_REQUISITION_LINES_ALL.

From a dimensional modelling perspective, the heuristic Data Vault classification mined from the foreign-key structure is standalone, indicating that the table presents no enforced parent-child relationships in its own right and functions as an independent staging satellite. Where ETL or warehouse modelling is applied, it is best treated as a transient interface stage rather than a durable hub or link, given that rows are consumed and purged by the import process.

Key Information Stored

The table carries 35 documented columns. The most operationally significant include:

No surrogate primary key or unique business index is documented in the supplied metadata; the table is populated as an interface and keyed operationally by the combination of BATCH_ID, GROUP_CODE, and SOURCE_LINE_ID where available.

Common Use Cases and Queries

Typical uses include diagnosing failed requisition imports, reconciling planning output against purchasing demand, and auditing sourcing recommendations.

SELECT batch_id, org_id, item_id, quantity, uom_code,
       source_organization_id, need_by_date, suggested_vendor_id
FROM   msc_po_requisitions_interface
WHERE  batch_id = :p_batch_id;

A second common pattern joins the interface to PO_LINE_TYPES_B to resolve line type descriptions, and to MTL_SYSTEM_ITEMS_B to render item names for reporting. Rows can be aggregated by source_organization_id and destination_organization_id to size planned replenishment volume per organization, or filtered on AUTOSOURCE_FLAG and VMI_FLAG to isolate vendor-managed or automatically sourced demand.

Related Objects

  • PO_LINE_TYPES_B – Referenced through MSC_PO_REQUISITIONS_INTERFACE.LINE_TYPE_ID; supplies line type semantics.
  • PO_REQUISITIONS_INTERFACE – The Purchasing interface table populated as the immediate next step in the import chain.
  • PO_REQUISITION_HEADERS_ALL – Target header table for created requisitions.
  • PO_REQUISITION_LINES_ALL – Target line table carrying the imported demand.
  • MTL_SYSTEM_ITEMS_B – Resolves ITEM_ID to item definitions.
  • HR_LOCATIONS_ALL – Resolves DELIVER_TO_LOCATION_ID.
  • PER_ALL_PEOPLE_F – Resolves PREPARER_ID and DELIVER_TO_REQUESTOR_ID.
  • PO_VENDORS / PO_VENDOR_SITES_ALL – Resolve suggested vendor and vendor site identifiers.