Search Results mrp_ap_interorg_ship_methods_v

Overview

The view MRP_AP_INTERORG_SHIP_METHODS_V is a reporting and integration object within the Oracle E-Business Suite Master Scheduling/MRP (MRP) module. It exposes inter-organization shipping method definitions, including transportation lead time, capacity, and cost attributes that drive the planning and execution of material transfers between two inventory organizations. In EBS 12.1.1 and 12.2.2, this view functions as a simplified, read-oriented projection over the underlying snapshot entity that Oracle Advanced Supply Chain Planning and related MRP processes use to model shipment routing.

The view is significant because it surfaces the INTRANSIT_TIME column, the attribute most frequently associated with the user search term "intransit_time." This column represents the planned transit duration for a given ship method between a source and destination organization, expressed in the unit identified by TIME_UOM_CODE. Transit time directly influences replenishment planning, transfer lead-time offsetting, and available-to-promise calculations. The view carries no documented description of its own and is marked as not implemented in the source metadata database, indicating that the documentation set records its definition and structure rather than an active deployment in that particular instance.

Underlying Base Objects

The documented view text selects exclusively from MRP_AP_IOS_MTHDS_SN, aliased as X. This base object is the shipping methods snapshot table that stores inter-organization shipment definitions used by MRP planning engines. The view performs a one-to-one projection of that snapshot without joins, filters, aggregations, or transformations, meaning every row and column in the view maps directly to a corresponding row and column in MRP_AP_IOS_MTHDS_SN. No other base tables or views are documented as referenced by this object.

Because the view is a thin passthrough, its data freshness, retention, and scope are entirely governed by the parent snapshot table. Consumers should recognize that the snapshot nature implies the content may reflect a planning cycle snapshot rather than live transactional state.

Key Columns

• FROM_ORGANIZATION_ID — Source inventory organization for the shipment lane.
• TO_ORGANIZATION_ID — Destination inventory organization for the shipment lane.
• SHIP_METHOD — Identifier of the shipping method code applied to the lane.
• INTRANSIT_TIME — Planned transit duration for the shipment, the central attribute for lead-time planning.
• TIME_UOM_CODE — Unit of measure in which INTRANSIT_TIME is expressed (for example, days or hours).
• DEFAULT_FLAG — Indicates whether the ship method is the default for the lane.
• FROM_LOCATION_ID and TO_LOCATION_ID — Optional location-level granularity within the source and destination organizations.
• DAILY_LOAD_WEIGHT_CAPACITY, LOAD_WEIGHT_UOM_CODE — Daily weight capacity and its unit of measure.
• DAILY_VOLUME_CAPACITY, VOLUME_UOM_CODE — Daily volume capacity and its unit of measure.
• COST_PER_UNIT_LOAD_WEIGHT, COST_PER_UNIT_LOAD_VOLUME — Costing factors applied per unit of weight and volume shipped.

Common Use Cases and Queries

Typical uses include validating inter-organization transit lead times, auditing default ship method assignments, and feeding downstream reporting or integration layers that must replicate planning master data. A common query retrieves transit time for a specific lane:

• SELECT from_organization_id, to_organization_id, ship_method, intransit_time, time_uom_code FROM mrp_ap_interorg_ship_methods_v WHERE from_organization_id = :src AND to_organization_id = :dest;
• Filtering defaults: add AND default_flag = 'Y' to isolate the default method per lane.
• Capacity analysis: select the capacity and cost columns alongside ship_method to evaluate lane throughput and freight economics.

Because there are no joins or filters in the view definition, query performance is essentially that of a full scan or indexed access on MRP_AP_IOS_MTHDS_SN, and all predicate pushdown applies directly to the base snapshot.