Results for “msc_po_reschedule_header_v”

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

Overview

The view MSC_PO_RESCHEDULE_HEADER_V is owned by the APPS schema and resides in the MSC (Advanced Supply Chain Planning) product family. Its documented status is VALID. The view presents the header-level information of a purchase order that has been rescheduled within the Advanced Supply Chain Planning process. As stated in the Oracle EBS 12.2.2 metadata, the view "contains the header information of a rescheduled purchase order" and is "used in XML-outbound" processing. In practical terms, this view does not store data of its own; it is a query layer that surfaces a consolidated, externally usable projection of rescheduled purchase order headers, joining the planning reschedule interface to the application instance definitions. Because it is exposed as a VIEW in the APPS schema and is referenced for XML outbound integration, it functions as a controlled read interface for exporting purchase order reschedule header data to external systems or downstream XML consumers.

Underlying Base Objects

Per the documented view text, MSC_PO_RESCHEDULE_HEADER_V is defined over two base objects, both referenced through synonyms in Oracle EBS 12.2.2:

• MSC_PO_RESCHEDULE_INTERFACE (SYNONYM) — aliased as MPR. This is the primary interface table holding the rescheduled purchase order records, contributing PURCHASE_ORDER_ID, PO_NUMBER, SR_INSTANCE_ID, and SOURCE_LINE_ID.
• MSC_APPS_INSTANCES (SYNONYM) — aliased as MAI. This provides the application instance context, contributing INSTANCE_CODE.

The two objects are related by the join condition MPR.SR_INSTANCE_ID = MAI.INSTANCE_ID, which links each rescheduled purchase order to its source application instance. The view is declared SELECT DISTINCT, so any duplicate combinations arising from the interface-to-instance relationship are collapsed into unique rows. This join-to-instance pattern is characteristic of MSC interface views, which typically resolve instance identifiers into readable instance codes for outbound messaging and reporting.

Key Columns

The documented columns exposed by the view, and their meanings, are as follows:

• PURCHASE_ORDER_ID — The unique identifier of the rescheduled purchase order header. This is the column most commonly used to join back to purchase order tables and is the term the user searched for.
• PO_NUMBER — The human-readable purchase order number corresponding to the order.
• SR_INSTANCE_ID — The identifier of the source application instance from which the reschedule record originated; it is the join key to MSC_APPS_INSTANCES.INSTANCE_ID.
• INSTANCE_CODE — The readable code of the source application instance, resolved via the join to MSC_APPS_INSTANCES. This identifies the originating EBS instance.
• SOURCE_LINE_ID — The identifier of the source line associated with the reschedule header, providing line-level linkage.

Common Use Cases and Queries

This view is primarily consumed by XML-outbound integrations that must transmit rescheduled purchase order header information, and by diagnostic or reporting queries that need to inspect reschedule activity across instances. Typical access includes validating what headers are pending/available for outbound, confirming the instance context, and joining the purchase order identifier back to core purchasing objects.

Retrieve reschedule header rows with instance context:

• SELECT purchase_order_id, po_number, sr_instance_id, instance_code, source_line_id FROM apps.msc_po_reschedule_header_v;

Locate a specific purchase order by its identifier or number:

• SELECT po_number, instance_code, source_line_id FROM apps.msc_po_reschedule_header_v WHERE purchase_order_id = :p_po_id;
• SELECT purchase_order_id, sr_instance_id, instance_code FROM apps.msc_po_reschedule_header_v WHERE po_number = :p_po_number;

Filter by originating instance using the resolved code:

• SELECT DISTINCT po_number, purchase_order_id FROM apps.msc_po_reschedule_header_v WHERE instance_code = :p_instance_code ORDER BY po_number;

Because the objects are documented as APPS-owned synonyms and the view is valid in the 12.2.2 environment, queries should be schema-qualified in the form APPS.MSC_PO_RESCHEDULE_HEADER_V.