Results for “current_phase_id”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

MTL_ITEM_REVISIONS_VL is a multilingual (ML) view owned by the APPS schema in Oracle E-Business Suite. It is registered under the INV – Inventory product and carries a VALID status in the ETRM repository for releases 12.1.1 and 12.2.2. The view presents item revision information for inventory items in a language-aware format, exposing both the revision attributes and the translated revision description. As a "_VL" view, it follows the standard Oracle EBS multilingual pattern: it joins a "_B" (base) table containing language-independent columns with a "_TL" (translation) table containing language-dependent descriptive columns, filtered to the session language.

Within Oracle EBS reporting and integration, this view functions as the canonical read interface for revision data. It shields consumers from the underlying partitioned storage model, so reports, concurrent programs, OAF pages, and external integrations can query a single object rather than performing the join themselves. Because the row identifier is derived from the base table's ROWID, the view is generally treated as read-only.

Underlying Base Objects

Per the documented view text, MTL_ITEM_REVISIONS_VL is defined over two synonyms referencing the base tables:

• MTL_ITEM_REVISIONS_B — the base table supplying language-independent columns such as INVENTORY_ITEM_ID, ORGANIZATION_ID, REVISION_ID, REVISION, dates, DFF attributes, and WHO/audit columns.
• MTL_ITEM_REVISIONS_TL — the translation table supplying language-dependent columns, principally DESCRIPTION.

The join condition matches the three-part key (INVENTORY_ITEM_ID, ORGANIZATION_ID, REVISION_ID) between the two objects, with a filter restricting the translation row to the current session language via T.LANGUAGE = USERENV('LANG'). The base alias B contributes the ROWID (aliased ROW_ID) and all non-translated columns; the TL alias T contributes only DESCRIPTION. This structure mirrors other item-related _VL views in the INV product and is consistent across both 12.1.1 and 12.2.2.

Key Columns

• ROW_ID — ROWID of the base table row; a unique identifier for the revision record.
• INVENTORY_ITEM_ID, ORGANIZATION_ID, REVISION_ID — the composite key identifying the revision within a given organization.
• REVISION, REVISION_LABEL — the revision code and its display label.
• REVISION_REASON — reason associated with the revision.
• CHANGE_NOTICE, ECN_INITIATION_DATE — engineering change notice reference and its initiation date.
• IMPLEMENTATION_DATE, EFFECTIVITY_DATE — when the revision takes effect.
• REVISED_ITEM_SEQUENCE_ID — sequence identifier for the revision ordering.
• LIFECYCLE_ID, CURRENT_PHASE_ID — lifecycle and phase identifiers for the item revision.
• ATTRIBUTE_CATEGORY and ATTRIBUTE1–ATTRIBUTE15 — descriptive flexfield context and segments.
• OBJECT_VERSION_NUMBER — optimistic locking column used by the OAF/BC4J layer.
• WHO columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, and concurrent program columns (REQUEST_ID, PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE).
• DESCRIPTION — the language-dependent revision description sourced from the TL table.

Common Use Cases and Queries

Typical uses include enumerating all active revisions for an item, verifying effectivity, extracting revision descriptions for reporting, and joining revision information to item master or on-hand queries for version control.

SELECT inventory_item_id, organization_id, revision, revision_label, description
FROM   apps.mtl_item_revisions_vl
WHERE  inventory_item_id = :p_item_id
AND    organization_id  = :p_org_id
ORDER  BY revised_item_sequence_id;

SELECT mir.organization_id, mir.inventory_item_id, mir.revision,
       mir.effectivity_date, mir.description
FROM   apps.mtl_item_revisions_vl mir
WHERE  mir.implementation_date IS NOT NULL
AND    mir.effectivity_date <= SYSDATE;

Because DESCRIPTION is filtered by user language, applications should not persist it beyond the session; where multi-language output is required, querying MTL_ITEM_REVISIONS_TL directly with an explicit LANGUAGE is the safer approach.