Search Results to_location_code




Overview
Explore in AI Chat

Overview

The APPS.INVFV_INTERORG_LEAD_TIMES view is a read-only reporting object within the Oracle E-Business Suite Inventory (INV) module. It exposes inter-organization shipping method definitions alongside the associated in-transit lead times maintained between pairs of inventory organizations. The view is marked as retrofitted, indicating it was carried forward from earlier release baselines to remain available in Oracle EBS 12.1.1 and 12.2.2. Its primary role is to provide a denormalized, human-readable representation of the MTL_INTERORG_SHIP_METHODS data, resolving internal identifiers into organization codes, organization names, ship method meanings, and location codes so that reporting and integration consumers do not need to join the base tables themselves. Because the view text is defined WITH READ ONLY, it is intended strictly for query and extract purposes and cannot be used as a DML target. The view is owned by the APPS schema and is flagged VALID in the data dictionary.

Underlying Base Objects

The view is defined over a mixture of base tables, synonyms, and supporting packages. The central driving object is the synonym MTL_INTERORG_SHIP_METHODS, aliased as MSM, which stores the from/to organization pairs, ship method, time unit of measure, in-transit time, default flag, and audit columns. Organization codes and names are resolved through the synonym MTL_PARAMETERS (MP1 and MP2) and the synonym HR_ALL_ORGANIZATION_UNITS (HOU1 and HOU2), each joined on the respective from and to organization identifiers. Address information is supplied by the HR_LOCATIONS view (HRL1 and HRL2) using outer joins, so rows remain visible even when no from or to location is defined. The ship method lookup meaning is obtained from the FND_COMMON_LOOKUPS view (FCL) restricted to APPLICATION_ID 401 and LOOKUP_TYPE 'SHIP_METHOD'. The documented referenced objects also include the FND_GLOBAL and HR_GENERAL packages, which supply the security and lookup context evaluated at runtime. Additional internal security predicates are embedded in the view text to enforce organization-level access.

Key Columns

Common Use Cases and Queries

Typical uses include validating inter-organization transit times for planning, auditing ship method setups, and feeding downstream planning or logistics extracts. A representative query is:

SELECT from_organization_code, to_organization_code, ship_method, time_uom_code, intransit_time FROM apps.invfv_interorg_lead_times ORDER BY from_organization_code, to_organization_code;

Analysts frequently filter by organization pair or ship method, for example restricting to records where DEFAULT_FLAG is set, or joining the view to MTL_SYSTEM_ITEMS to correlate lead times with item sourcing rules. Because the view resolves codes and names, it is also convenient for reporting tools and BI Publisher extracts that cannot easily replicate the multi-table joins against MTL_PARAMETERS, HR_ALL_ORGANIZATION_UNITS, and FND_COMMON_LOOKUPS.