Search Results msc_interorg_ship_methods_u1




Overview
Explore in AI Chat

Overview

The MSC.MSC_INTERORG_SHIP_METHODS table is an Oracle Advanced Supply Chain Planning (ASCP) data object that stores the shipment methods available between sourcing organizations and their associated capacity, cost, and lead time attributes. It is a planning-engine table owned by the MSC schema (FND Design Data: MSC.MSC_INTERORG_SHIP_METHODS), stored in the APPS_TS_TX_DATA tablespace with PCTFREE 10, and marked VALID in Oracle EBS 12.1.1 and 12.2.2. The table supports inter-org sourcing decisions by defining which transportation options exist between an origin (FROM) and destination (TO) organization/location, including time, weight, volume, and cost characteristics that the planning engine uses when evaluating replenishment and distribution alternatives. The documented physical schema contains 59 columns.

Relationship metadata classifies this object as standalone based on a heuristic analysis of the foreign-key structure. In Data Vault terms, this suggests a modeling approach where the table may not exhibit a clean hub/link/satellite decomposition; instead, it functions as a self-contained planning reference populated by the planning data collection process (REFRESH_NUMBER, COLLECTED_FLAG, TRANSACTION_ID are consistent with this pattern). Where a Data Vault model is desired, the composite business key could be treated as a candidate hub, with capacity, cost, and lead time attributes as satellite content.

Key Information Stored

The primary key is defined as MSC_INTERORG_SHIP_METHODS_PK on (FROM_ORGANIZATION_ID, SR_INSTANCE_ID, TO_ORGANIZATION_ID, SR_INSTANCE_ID2, PLAN_ID, FROM_LOCATION_ID, TO_LOCATION_ID, SHIP_METHOD). This composite key identifies a unique shipment method per plan, source instance, origin/destination organization, and origin/destination location.

The two unique indexes represent business-key candidates:

Notable attribute columns include: FROM_ORGANIZATION_ID / TO_ORGANIZATION_ID (origin and destination organizations), SHIP_METHOD (ship method code), SHIP_METHOD_TEXT (descriptive text), INTRANSIT_TIME with TIME_UOM_CODE (lead time and its unit of measure), DEFAULT_FLAG (indicates the default method), WEIGHT_CAPACITY / WEIGHT_UOM and VOLUME_CAPACITY / VOLUME_UOM (capacity limits), COST_PER_WEIGHT_UNIT and COST_PER_VOLUME_UNIT (costing), and LEADTIME_VARIABILITY. Audit and collection columns include LAST_UPDATE_DATE, CREATED_BY, REQUEST_ID, PROGRAM_ID, TRANSACTION_ID, REFRESH_NUMBER, and COLLECTED_FLAG. Location/region columns (FROM_LOCATION_ID, TO_LOCATION_ID, FROM_REGION_ID, TO_REGION_ID) enable geographic granularity, and 15 ATTRIBUTE columns provide DFF extensibility.

Common Use Cases and Queries

Typical usage centers on planning analysis and shipment method maintenance. A common query retrieves all available methods between two organizations for a given plan:

  • SELECT ship_method, intransit_time, time_uom_code, cost_per_weight_unit FROM msc.msc_interorg_ship_methods WHERE plan_id = :p AND from_organization_id = :o1 AND to_organization_id = :o2;
  • Identifying default methods: filter on DEFAULT_FLAG = 1 using index N3, which covers PLAN_ID, DEFAULT_FLAG, FROM_ORGANIZATION_ID, SR_INSTANCE_ID, TO_ORGANIZATION_ID, SR_INSTANCE_ID2, TO_REGION_ID.
  • Capacity planning / constraint reporting: aggregate WEIGHT_CAPACITY and VOLUME_CAPACITY against SHIPMENT_WEIGHT / SHIPMENT_VOLUME to detect over-utilization, correlating with TRANSPORT_CAP_OVER_UTIL_COST.
  • Cost analytics: compare COST_PER_WEIGHT_UNIT and COST_PER_VOLUME_UNIT across methods to optimize distribution lanes.
  • Data collection monitoring: use REFRESH_NUMBER, COLLECTED_FLAG, and LAST_UPDATE_DATE to verify plan data freshness.

The unique and nonunique indexes (N1 through N4) are designed around PLAN_ID leading columns, so queries should always constrain PLAN_ID first for efficient access.

Related Objects

Because the table is classified as standalone, explicit FK relationships are limited, but the following objects interact logically through shared planning columns:

  • MSC.MSC_PLANS — joined via PLAN_ID; defines the plan context for each shipment method record.
  • MSC.MSC_SYSTEM_ITEMS — shares organization and planning scope for item-level sourcing.
  • MSC.MSC_SR_LOCATIONS and MSC.MSC_SR_LOCATION_ASSOCIATIONS — link through FROM_LOCATION_ID / TO_LOCATION_ID for location context.
  • MSC.MSC_TRADING_PARTNERS — provides organization/partner detail for FROM_ORGANIZATION_ID and TO_ORGANIZATION_ID.
  • PO.SHIPPING_METHODS / FND_LOOKUPS — provide the ship method code reference used by SHIP_METHOD.
  • MSC.MSC_INTERORG_SHIP_METHODS_TL (where present) — for translated ship method text.
  • ASCP collection programs (MSCDWxxx engines) that populate this table via SR_INSTANCE_ID / SR_INSTANCE_ID2 identifiers.

Reporting views commonly join PLAN_ID and organization columns to sourcing rules and allocation logic to produce distribution network reports.