Search Results inl_ship_types_vl




Overview
Explore in AI Chat

Overview

INL_SHIP_TYPES_VL is a multilingual (language-specific) view in the APPS schema belonging to the Oracle Landed Cost Management (INL) product. It presents shipment type information—the classifications used to group and cost landed-cost shipments—in a single language determined at runtime by the user's session. The "_VL" suffix follows the standard Oracle EBS convention for views that join a "_B" (base) table to a "_TL" (translation) table, exposing descriptive, translatable columns alongside the non-translatable base columns while returning only one row per entity for the current language.

In Oracle EBS 12.1.1 and 12.2.2 the object is documented as VALID and owned by APPS. Reporting and integration layers reference it to retrieve shipment type names and codes without having to join the base and translation tables explicitly, making it the preferred access point for concurrent programs, BI Publisher reports, OBIEE extracts, and custom PL/SQL that must display shipment type text in the user's own language.

Underlying Base Objects

The view is defined over two documented base objects, referenced as synonyms in the APPS schema: INL_SHIP_TYPES_B and INL_SHIP_TYPES_TL. The view text joins them on SHIP_TYPE_ID and filters the translation table by the session language:

  • INL_SHIP_TYPES_B — the base table holding non-translatable attributes, including SHIP_TYPE_CODE, TRD_PTIES_ALWD_CODE, date-effective columns, audit columns, and the fifteen DFF attribute columns.
  • INL_SHIP_TYPES_TL — the translation table holding SHIP_TYPE_NAME per LANGUAGE. The join condition T.LANGUAGE = USERENV('LANG') restricts output to the runtime language, so exactly one translation row is returned per shipment type.

Because all business columns come from the base table and only the name is translated, the view preserves the referential integrity of the base while supplying the language-specific description.

Key Columns

  • SHIP_TYPE_ID — surrogate primary key of the shipment type; the join key between the B and TL tables and the value referenced by landed-cost transaction tables.
  • SHIP_TYPE_CODE — the user-defined, language-independent code that uniquely identifies the shipment type.
  • SHIP_TYPE_NAME — the translatable description returned in the session language; the principal column distinguishing the _VL view from its base table.
  • TRD_PTIES_ALWD_CODE — controls whether trading parties are allowed on shipments of this type.
  • ACTIVE_FROM_DATE / ACTIVE_TO_DATE — the effective date range governing when the shipment type may be used.
  • Audit columns — CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN.
  • ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — the descriptive flexfield (DFF) context and segment columns, available for any customer-defined extensions.

Common Use Cases and Queries

Typical uses include populating shipment type LOVs and report parameters, validating shipment type codes during data conversion, and extracting active shipment types for landed-cost analytics. The following query lists currently active shipment types:

SELECT ship_type_id, ship_type_code, ship_type_name, trd_pties_alwd_code
FROM apps.inl_ship_types_vl
WHERE TRUNC(SYSDATE) BETWEEN NVL(active_from_date, SYSDATE)
AND NVL(active_to_date, SYSDATE)
ORDER BY ship_type_name;

To resolve a single name from a known code, use:

SELECT ship_type_name
FROM apps.inl_ship_types_vl
WHERE ship_type_code = :p_code;

Because language filtering is internal, no explicit LANGUAGE predicate is required; the view returns text in the language of the connecting session. Callers should nonetheless treat INL_SHIP_TYPES_VL as read-only and avoid DML against it, since it is a view over two tables.