Search Results to_location_desc

Overview

APPS.MSC_LOCATIONS_V is a reporting and integration view in the Oracle E-Business Suite Advanced Supply Chain Planning (ASCP) schema. It presents a denormalized, human-readable perspective of inter-organization shipping relationships as defined for planning purposes. Rather than exposing raw organization identifiers, the view resolves each shipping source and destination into an organization code by invoking the MSC_GET_NAME.ORG_CODE function, and joins those organizations to their corresponding trading partner and trading partner site records. The view is restricted to planning-enabled shipping methods (PLAN_ID = -1) and to trading partners of PARTNER_TYPE = 3, which represents internal (inventory) organizations rather than external suppliers or customers. For consultants searching on the column name sr_tp_id, the view is notable because SR_TP_ID is the trading partner identifier — the internal surrogate key used throughout the ASCP planning tables to identify an organization as a trading partner. This view surfaces that identifier indirectly through the join predicates, and exposes the resulting partner site identifiers and locations.

Underlying Base Objects

The view is defined over four documented base objects, all within the APPS schema:

• MSC_INTERORG_SHIP_METHODS (synonym) — the driving table, aliased ISM. Supplies the shipping method records for the plan, including FROM_ORGANIZATION_ID and TO_ORGANIZATION_ID, which are the SR_TP_ID values of the source and destination trading partners.
• MSC_TRADING_PARTNERS (synonym) — aliased TP and TP1, representing the source and destination trading partners respectively. Joined on SR_INSTANCE_ID and SR_TP_ID.
• MSC_TRADING_PARTNER_SITES (synonym) — aliased TPS and TPS1, supplying the site-level detail (SR_TP_SITE_ID and LOCATION) for each trading partner.
• MSC_GET_NAME (package) — invoked as MSC_GET_NAME.ORG_CODE to translate an organization identifier plus source instance into a displayable organization code.

The view is therefore a self-join of the trading partner and trading partner site tables, chained to the inter-org ship methods table, with the naming package applied on both the from and to sides.

Key Columns

• SR_TP_SITE_ID (TPS and TPS1) — the trading partner site identifier for the from and to organizations.
• MSC_GET_NAME.ORG_CODE(...) — the resolved organization code for the from organization (using ISM.FROM_ORGANIZATION_ID and ISM.SR_INSTANCE_ID) and the to organization (using ISM.TO_ORGANIZATION_ID and ISM.SR_INSTANCE_ID2).
• LOCATION (TPS and TPS1) — the site location description associated with each trading partner site.
• FROM_ORGANIZATION_ID / TO_ORGANIZATION_ID — the SR_TP_ID values for the source and destination trading partners.
• SR_INSTANCE_ID / SR_INSTANCE_ID2 — the source system instance identifiers for the from and to sides.
• ORGANIZATION_TYPE (TP and TP1) — the organization type classification of each trading partner.

Common Use Cases and Queries

Typical scenarios include validating inter-organization shipping network definitions during ASCP diagnostics, resolving organization codes for a known SR_TP_ID, and reconciling ship methods against trading partner site setup. A representative query follows:

• SELECT sr_tp_site_id, location, from_organization_id, to_organization_id, organization_type FROM apps.msc_locations_v WHERE from_organization_id = :sr_tp_id;
• SELECT * FROM apps.msc_locations_v ORDER BY location; to enumerate all defined from/to location pairs.
• SELECT DISTINCT from_organization_id, organization_type FROM apps.msc_locations_v; to list distinct source trading partners and their types.

Because the view enforces PARTNER_TYPE = 3, it returns only internal inventory organization relationships and excludes supplier or customer trading partners.