Search Results mtl_interorg_ship_methods




Overview
Explore in AI Chat

Overview

MTL_INTERORG_SHIP_METHODS is an Oracle Inventory (INV) transactional configuration table that defines the relationships between shipping networks and shipment methods for inter-organization transfers within Oracle E-Business Suite 12.1.1 and 12.2.2. Each row links a source organization, a destination organization, an optional source and destination location, and a shipping method, thereby enabling Oracle Shipping and Inventory to determine transit time, capacity constraints, and costing characteristics for the movement of goods between internal organizations.

The table is owned by the INV schema and holds 40 documented columns in the 12.2.2 ETRM physical schema. It is a configuration rather than a transactional object, meaning its rows are populated during implementation setup and maintained infrequently compared to high-volume inventory transaction tables. From a dimensional or Data Vault modeling perspective, the metadata classifies this object heuristically as a link, since it resolves relationships among multiple business entities (from/to organizations, from/to locations) rather than acting as an independent entity hub or a descriptive satellite.

Key Information Stored

The following columns carry the most functional weight:

The documented primary key, MTL_INTERORG_SHIP_METHODS_PK, is a composite business key over (FROM_ORGANIZATION_ID, TO_ORGANIZATION_ID, FROM_LOCATION_ID, TO_LOCATION_ID, SHIP_METHOD). No separate surrogate key column is documented; therefore the composite columns themselves serve as the unique identifier. Standard audit columns (LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN) and the fifteen ATTRIBUTE columns provide extensibility and change tracking.

Common Use Cases and Queries

Shipping and distribution teams consult this table when configuring inter-org transfer networks, validating that a shipment method exists for a given lane, or analyzing transit times and carrier capacity. Typical SQL patterns include:

  • Retrieving all methods for a specific source-to-destination lane: SELECT ship_method, intransit_time, time_uom_code FROM mtl_interorg_ship_methods WHERE from_organization_id = :src AND to_organization_id = :dest;
  • Joining to MTL_PARAMETERS twice to resolve organization names for reporting.
  • Joining to HR_LOCATIONS_ALL to confirm the physical source and destination sites.
  • Filtering on DEFAULT_FLAG to identify the standing method per network, or on capacity columns to evaluate load planning feasibility.
  • Referencing CURRENCY_CODE with FND_CURRENCIES to convert cost values in multi-currency implementations.

Related Objects

  • MTL_PARAMETERS – Referenced by FROM_ORGANIZATION_ID and TO_ORGANIZATION_ID; supplies organization definitions.
  • HR_LOCATIONS_ALL – Referenced by FROM_LOCATION_ID and TO_LOCATION_ID; supplies location details.
  • FND_CURRENCIES – Referenced by CURRENCY_CODE; supplies currency definitions.
  • MTL_INTERORG_SHIP_METHODS_PK – The composite primary key constraint enforcing uniqueness.
  • Shipping and Inventory transfer APIs – Inter-org transfer and shipping execution logic read this table to determine method, transit time, and capacity defaults.