Search Results invbv_interorg_lead_times

Overview

INVBV_INTERORG_LEAD_TIMES is an APPS-owned read-only database view in the Oracle E-Business Suite Inventory (INV) module. Its name reflects its purpose: it exposes inter-organization lead time and in-transit information, a subject closely tied to the search term "intransit_time". The object is documented with the annotation "Retrofitted," indicating that it was reintroduced or re-pointed during an upgrade path, most notably across 12.1.1 and 12.2.2 environments where the underlying inventory schema was consolidated. The view carries a status of VALID and is delivered as part of the standard APPS schema in both releases referenced here.

The view functions as a reporting and integration surface rather than a transactional interface. Because it is defined WITH READ ONLY, consumers cannot perform DML against it; it exists purely to present a curated projection of shipping-method data. Its central value lies in the INTRANSIT_TIME column, which quantifies the expected transit duration between a source and destination organization for a given shipping method. This makes the view a practical source for planning reports, supply chain analytics, and custom integrations that need to estimate transfer durations.

Underlying Base Objects

The view is defined over a single base object, MTL_INTERORG_SHIP_METHODS, accessed via a synonym in the APPS schema. This is the Inventory table that stores shipping method definitions between organization pairs, including the transit time and its unit of measure.

The defining query applies several restrictive clauses. Rows are returned only when FROM_ORGANIZATION_ID and TO_ORGANIZATION_ID are both populated, and additional security predicates (_SEC tokens in the underlying text) enforce organization-level access controls at runtime. The query also embeds a lookup join token for DEFAULT_FLAG against the MFG_LOOKUPS lookup type SYS_YES_NO, resolving the stored flag into its human-readable meaning. The WITH READ ONLY clause prevents any insert, update, or delete operations. These constraints mean the view reflects only fully qualified, secure, and enabled inter-organization shipping method records.

Key Columns

• FROM_ORGANIZATION_ID – Source inventory organization for the shipping method.
• TO_ORGANIZATION_ID – Destination inventory organization.
• SHIP_METHOD_CODE – Identifier of the shipping method used between the two organizations.
• TIME_UOM_CODE – Unit of measure in which transit time is expressed (for example days or hours).
• INTRANSIT_TIME – The expected in-transit duration for the shipment; the primary measure exposed by the view and the column matched by the "intransit_time" search.
• DEFAULT_FLAG – Lookup-derived value indicating whether this shipping method is the default for the organization pair.
• FROM_LOCATION_ID / TO_LOCATION_ID – Optional location-level qualifiers for the method.
• Audit columns – CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, and LAST_UPDATE_DATE provide standard row-level audit information.

Common Use Cases and Queries

Typical scenarios include calculating transfer lead times for planning engines, validating configured shipping methods, and populating custom reports or interfaces that estimate delivery windows. A simple query returns all lead times for a specific organization pair:

• SELECT from_organization_id, to_organization_id, ship_method_code, time_uom_code, intransit_time FROM invbv_interorg_lead_times WHERE from_organization_id = :from_org AND to_organization_id = :to_org;
• SELECT ship_method_code, intransit_time, default_flag FROM invbv_interorg_lead_times WHERE default_flag = 'Y'; – isolates default shipping methods.
• SELECT to_organization_id, AVG(intransit_time) FROM invbv_interorg_lead_times GROUP BY to_organization_id; – summarizes average transit time by destination.

Because organization security is applied within the view definition, callers must be granted access to the relevant organizations or rows will be filtered out. The read-only nature and synonym-based reference to MTL_INTERORG_SHIP_METHODS make the view safe for ad hoc querying and reporting without risk of altering shipping method configuration.