Results for “msc_supplies_outbound_v”

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

Overview

The view APPS.MSC_SUPPLIES_OUTBOUND_V is a reporting and integration object belonging to the Oracle Advanced Supply Chain Planning (MSC) product family. As documented in the ETRM metadata, its purpose is to list all supplies for a given plan, and it is specifically consumed by the XML-outbound process that publishes planning data to external systems. The view is owned by the APPS schema and is reported as VALID in both Oracle EBS 12.1.1 and 12.2.2 environments, where it is used primarily for read-only extraction of supply records rather than for transactional processing.

Because it is defined as a view over the planning staging and result tables, it does not store data itself. Instead, it consolidates supply rows from the MSC planning engine and joins them to item, organization, and trading-partner metadata to produce a flattened, integration-friendly record set. This makes it suitable both for the standard XML-outbound supply publication and for ad hoc queries against plan results.

Underlying Base Objects

The view is defined over the following documented base objects:

• MSC_SUPPLIES (SYNONYM) — the primary source of supply records. Columns such as SR_INSTANCE_ID, PLAN_ID, TRANSACTION_ID, ORGANIZATION_ID, and the schedule and quantity fields originate here.
• MSC_SYSTEM_ITEMS (SYNONYM) — joined on SR_INSTANCE_ID, INVENTORY_ITEM_ID, ORGANIZATION_ID, and PLAN_ID to retrieve INVENTORY_ITEM_ID, ITEM_NAME, and UOM_CODE.
• MSC_TRADING_PARTNERS (SYNONYM) — joined on SR_TP_ID = ORGANIZATION_ID (with PARTNER_TYPE = 3) to supply organization-level partner data and ORGANIZATION_CODE via MTP.
• MSC_APPS_INSTANCES (SYNONYM) — joined on SR_INSTANCE_ID = INSTANCE_ID to anchor the source instance identity.
• MSC_ST_UTIL (PACKAGE) — invoked through functions such as RET_PARTNER_NAME, RET_PARTNER_SITE, RET_PROJECT_NUMBER, and RET_TASK_NUMBER to resolve supplier, supplier site, project, and task identifiers into descriptive values.

The joins enforce that the view returns only supplies whose item, organization, and instance combinations are internally consistent within the same plan and source instance.

Key Columns

Significant columns exposed by the view include:

• SR_INSTANCE_ID, PLAN_ID, TRANSACTION_ID, ORGANIZATION_ID — the core plan and organization context for each supply.
• FIRM_FLAG / FIRM_PLANNED_TYPE — derived as DECODE(MSUP.FIRM_PLANNED_TYPE, 1, 'YES', 2, 'NO'), indicating whether the supply is firmed. This directly addresses the "firm_flag" search: the human-readable YES/NO value is exposed as FIRM_FLAG while the underlying numeric code is FIRM_PLANNED_TYPE.
• STATUS — derived from DISPOSITION_STATUS_TYPE, rendering 'CANCEL' when the value is 2.
• ORDER_QUANTITY — computed as NEW_ORDER_QUANTITY minus QUANTITY_IN_PROCESS and IMPLEMENTED_QUANTITY; OLD_ORDER_QUANTITY is also exposed.
• LINE_TYPE — from IMPLEMENT_AS, describing the implementation action.
• SUPPLIER_NAME, SUPPLIER_SITE_CODE, PROJECT_NUMBER, TASK_NUMBER — descriptive values resolved via MSC_ST_UTIL.
• NEW_SCHEDULE_DATE, NEW_SHIP_DATE, LAST_UNIT_START_DATE — planning dates relevant to scheduling.
• ITEM_NAME, ORGANIZATION_CODE, UOM_CODE, REVISION, UNIT_NUMBER — descriptive item and organization attributes.

Common Use Cases and Queries

The primary use case is the XML-outbound feed of plan supplies. Analysts also query it to review firmed versus unfirmed supplies or to reconcile order quantities against plan dates. A representative query filtered on the firm flag is:

• SELECT TRANSACTION_ID, ORGANIZATION_CODE, ITEM_NAME, ORDER_QUANTITY, FIRM_FLAG, NEW_SCHEDULE_DATE FROM APPS.MSC_SUPPLIES_OUTBOUND_V WHERE PLAN_ID = :plan_id AND FIRM_FLAG = 'YES';
• Filtering by source supplier or project: WHERE SUPPLIER_NAME = :supplier OR PROJECT_NUMBER = :project;
• Reviewing cancellations: WHERE STATUS = 'CANCEL';

Because the view performs function calls within its SELECT list, large unfiltered queries can be expensive; applying PLAN_ID and ORGANIZATION_ID predicates is recommended.