Search Results msc_locations_v




Overview
Explore in AI Chat

Overview

MSC_LOCATIONS_V is a view owned by the APPS schema within the MSC (Advanced Supply Chain Planning) product module of Oracle E-Business Suite, valid in releases 12.1.1 and 12.2.2. It exposes the distinct inter-organization shipping lanes that connect a source organization location to a destination organization location, as defined by inter-org shipping methods. Because it resolves organization names through the MSC_GET_NAME package rather than storing denormalized text, the view presents a normalized, plan-independent representation of supply chain network nodes.

The view is restricted to inter-org shipping methods that belong to the unplanned/default planning context (PLAN_ID = -1) and to trading partner sites of PARTNER_TYPE 3. It therefore acts as a reference data source for reporting and integration, providing both surrogate keys and descriptive labels for "from" and "to" locations. Downstream MSC planning engine logic, network design reporting, and custom extracts commonly rely on it to translate internal organization IDs into human-readable location and organization codes.

Underlying Base Objects

The view definition joins three base objects and references one package:

The joins correlate the shipping method to the trading partner site via SR_INSTANCE_ID, to the second site via SR_INSTANCE_ID2, and match organization IDs against the respective SR_TP_ID values. A DISTINCT clause removes duplicate rows created by the multi-way join.

Key Columns

  • FROM_LOCATION_ID — SR_TP_SITE_ID of the source trading partner site (from TPS).
  • FROM_LOCATION — the source site LOCATION value.
  • FROM_LOCATION_DESC — the organization code returned by MSC_GET_NAME.ORG_CODE for the source organization.
  • FROM_ORGANIZATION_ID — inventory organization ID of the shipping source.
  • SR_INSTANCE_ID — source application instance identifier associated with the from-side site.
  • TO_LOCATION_ID — SR_TP_SITE_ID of the destination trading partner site (from TPS1).
  • TO_LOCATION — the destination site LOCATION value.
  • TO_LOCATION_DESC — the organization code returned for the destination organization.
  • TO_ORGANIZATION_ID — inventory organization ID of the shipping destination.
  • SR_INSTANCE_ID2 — source application instance identifier associated with the to-side site.

Common Use Cases and Queries

Typical scenarios include validating inter-org shipping networks, driving location drop-downs in custom OAF/Forms extensions, and feeding planning extracts with readable from/to location labels. A representative query joins the view to organization master data:

SELECT from_location_id, from_location, from_location_desc, to_location_id, to_location, to_location_desc FROM apps.msc_locations_v WHERE from_organization_id = :p_org_id ORDER BY to_location;

To list all lanes for a given source organization code, filter on FROM_LOCATION_DESC; to enumerate inbound lanes, filter on TO_ORGANIZATION_ID. Because the view already de-duplicates and restricts to PARTNER_TYPE 3 and PLAN_ID = -1, it is generally safe to use directly in reports without additional DISTINCT logic. For cross-instance analysis, SR_INSTANCE_ID and SR_INSTANCE_ID2 distinguish the source systems of the two endpoints.