Results for “purch_line_num”

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

Overview

MSC_PO_RESCHEDULE_DETAILS_V is a PL/SQL view owned by the APPS schema within the MSC – Advanced Supply Chain Planning product of Oracle E-Business Suite, and is documented as valid in release 12.1.1 and 12.2.2. The view exposes line-level detail for purchase orders that Advanced Supply Chain Planning has flagged for rescheduling. Its documented purpose is to serve as the data source for XML-outbound integration, meaning that external systems or middleware consumers receive a flattened, denormalized representation of a rescheduled purchase order line rather than querying the underlying interface and supply tables directly. The view consolidates attributes that would otherwise require joining several planning and purchasing tables, allowing downstream integrations to obtain the purchase order reference, supplier identity, item identity, and reschedule timing information in a single query.

Underlying Base Objects

The view is defined over four documented objects and one PL/SQL package. The primary driver is MSC_PO_RESCHEDULE_INTERFACE, aliased MPR, which supplies the reschedule transaction records, including the source line identifier, purchase order identifier, quantity, UOM, and need-by date. MSC_SUPPLIES, aliased S, is joined on SOURCE_LINE_ID equal to TRANSACTION_ID and additionally on PLAN_ID and SR_INSTANCE_ID; this join is what produces the PURCH_LINE_NUM value along with organization and supplier references. MSC_SYSTEM_ITEMS, aliased MSI, is joined on inventory item, plan, organization, and source instance to resolve item names. MSC_APPS_INSTANCES, aliased MAI, is joined on SR_INSTANCE_ID to provide the instance code. The MSC_ST_UTIL package is invoked inline to resolve the organization code, partner name, and partner site code through its RET_ORG_CODE, RET_PARTNER_NAME, and RET_PARTNER_SITE functions. All joins are performed on the combination of PLAN_ID, ORGANIZATION_ID, and SR_INSTANCE_ID, reflecting the multi-organization, multi-instance architecture of Advanced Supply Chain Planning.

Key Columns

• PURCH_LINE_NUM — The purchase order line number from MSC_SUPPLIES, the column most commonly used to correlate the reschedule record to a specific PO line.
• PO_NUMBER / PURCHASE_ORDER_ID / LINE_ID — The purchase order header and line identifiers carried from MSC_PO_RESCHEDULE_INTERFACE.
• SOURCE_LINE_ID — The supply transaction identifier that links the reschedule record to MSC_SUPPLIES.
• SUPPLIER_ID and SUPPLIER_NAME — Resolved through NVL against SUPPLIER_ID and SOURCE_SUPPLIER_ID, then passed to RET_PARTNER_NAME.
• SUPPLIER_SITE_ID and SUPPLIER_SITE_CODE — Similarly resolved through RET_PARTNER_SITE.
• ORG_CODE and ORGANIZATION_ID — The destination organization derived from RET_ORG_CODE and the supplies record.
• INVENTORY_ITEM_ID and ITEM_NAME — Item identity resolved from MSC_SYSTEM_ITEMS.
• QUANTITY, UOM, NEED_BY_DATE — The reschedule quantity, unit of measure, and required date.
• SR_INSTANCE_ID and INSTANCE_CODE — The source planning instance, allowing consumers to distinguish records when multiple instances are consolidated.

Common Use Cases and Queries

The principal use case is XML-outbound extraction of rescheduled purchase order lines. A typical query filters by source instance and need-by date so that only actionable reschedules are transmitted:

• SELECT PO_NUMBER, PURCH_LINE_NUM, SUPPLIER_NAME, ITEM_NAME, QUANTITY, UOM, NEED_BY_DATE FROM MSC_PO_RESCHEDULE_DETAILS_V WHERE TRUNC(NEED_BY_DATE) <= TRUNC(SYSDATE) + 30;
• SELECT INSTANCE_CODE, COUNT(*) FROM MSC_PO_RESCHEDULE_DETAILS_V GROUP BY INSTANCE_CODE;
• SELECT PURCHASE_ORDER_ID, PURCH_LINE_NUM, ORG_CODE, SUPPLIER_SITE_CODE FROM MSC_PO_RESCHEDULE_DETAILS_V WHERE PO_NUMBER = :po_number;

Because the view resolves organization, supplier, and site codes through MSC_ST_UTIL functions, it should be queried with representative bind values when performance-tuned, and reports should account for the possibility of null supplier identifiers when neither SUPPLIER_ID nor SOURCE_SUPPLIER_ID is populated.