Search Results dflt_allocation_enabled_flag

Overview

INL_SHIP_LINE_TYPES_VL is a multilingual (ML) style database view owned by the APPS schema in Oracle E-Business Suite Release 12.1.1 and 12.2.2. It belongs to the INL product family, Oracle Landed Cost Management. The view exposes shipment line type definitions—the configuration records that classify and control the behavior of shipment lines processed within Landed Cost Management—rendered in the language of the current user session.

Landed Cost Management captures charges such as freight, duty, insurance, and handling that are incurred when goods are received into inventory. Shipment line types determine whether a given shipment line is eligible for default landed cost treatment and whether allocation processing is enabled for it. Because these definitions are user-facing reference data, Oracle stores translatable attributes in a translation table and surfaces them through this _VL view. Rather than joining the base and translation tables manually, reporting tools, concurrent programs, and integration interfaces can query the view directly and receive descriptions automatically resolved to the session language.

The object holds VALID status and is documented in the ETRM (Electronic Technical Reference Manual) for release 12.2.2, with equivalent availability in 12.1.1. It is defined as a view over two synonyms and is not itself a table; no DML should be directed at it.

Underlying Base Objects

The documented base objects referenced by the view are:

• INL_SHIP_LINE_TYPES_B (SYNONYM) — the base table holding language-independent columns, including the primary key SHIP_LINE_TYPE_ID, the code, the active date range, the seeded indicator columns, and the standard WHO audit and descriptive flexfield (attribute) columns.
• INL_SHIP_LINE_TYPES_TL (SYNONYM) — the translation table holding the language-dependent SHIP_LINE_TYPE_NAME for each language installed in the instance.

The view joins the two on SHIP_LINE_TYPE_ID and filters the translation row with the condition T.LANGUAGE = USERENV('LANG'). USERENV('LANG') returns the language code of the current database session, so a single query returns one row per shipment line type, with the name appearing in the user's own language. If a translation for the session language does not exist, the corresponding name will not be returned, which is a normal characteristic of ML views. The internal join also produces the ROW_ID pseudocolumn from the base table's ROWID, exposing it as ROW_ID for tools that require a row identifier.

Key Columns

• ROW_ID — the ROWID of the base table row, used as a surrogate identifier by EBS forms and APIs.
• SHIP_LINE_TYPE_ID — primary key and foreign key to the base table; the identifier used in all programmatic references.
• SHIP_LINE_TYPE_CODE — the language-independent code, suitable for joins, interfaces, and validation logic.
• SHIP_LINE_TYPE_NAME — the translatable display name from the TL table, resolved to the session language.
• DFLT_LANDED_COST_FLAG — indicates whether the type defaults landed cost behavior on new shipment lines.
• DFLT_ALLOCATION_ENABLED_FLAG — indicates whether allocation is enabled by default for lines of this type.
• ACTIVE_FROM_DATE / ACTIVE_TO_DATE — the effective date range governing when the type may be used.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard WHO audit columns.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield segments available for customer-defined reference information.

Common Use Cases and Queries

Typical uses include validating shipment line type codes during inbound data conversion, driving LOV queries in custom forms and OAF pages, and producing configuration listings for landed cost setups. The following query lists all active shipment line types in the session language:

• SELECT ship_line_type_id, ship_line_type_code, ship_line_type_name, dflt_landed_cost_flag, dflt_allocation_enabled_flag FROM inl_ship_line_types_vl WHERE SYSDATE BETWEEN NVL(active_from_date, SYSDATE) AND NVL(active_to_date, SYSDATE);
• SELECT ship_line_type_code, ship_line_type_name FROM inl_ship_line_types_vl ORDER BY ship_line_type_name;
• SELECT h.ship_line_type_id, v.ship_line_type_name FROM inl_ship_lines h, inl_ship_line_types_vl v WHERE h.ship_line_type_id = v.ship_line_type_id;

Because the view resolves language through USERENV('LANG'), reports intended for multi-language environments should not hard-code language filters; instead, ensure the reporting responsibility session is set to the desired language so names are returned correctly.