Results for “revision_reason”

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

Overview

GMF_XLA_ITEM_REVISIONS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite. It belongs to the GMF (Process Manufacturing Financials) product family and is documented with a status of VALID in both release 12.1.1 and 12.2.2. The view exists to expose item revision data as a source for Subledger Accounting (SLA) Accounting Derived Reporting (ADR) attributes. In the SLA architecture, ADR sources supply descriptive and identifying information that the accounting engine attaches to subledger journal entries, enabling downstream reconciliation, audit, and reporting without the journal having to re-derive the values from operational tables.

The view presents a narrow, purpose-built projection of revision data rather than a fully denormalized item master. Its role is therefore integration-oriented: it feeds SLA configuration, ADR source definitions, and custom reports that need revision identifiers and descriptive revision attributes alongside the item and organization context.

Underlying Base Objects

The view is defined over a single base object, documented in the ETRM metadata as MTL_ITEM_REVISIONS, exposed in the APPS schema as a synonym. MTL_ITEM_REVISIONS is the standard Oracle Inventory table that stores revision definitions for revision-controlled items, keyed by inventory item and organization. Because the view references only this one table and performs no joins, it is a direct, lightweight pass-through. No aggregation, filtering, or outer joins are applied in the documented view text, so row cardinality and grain match the underlying revision records exactly. This simplicity is intentional: SLA ADR sources must resolve deterministically to a single revision row for a given item and organization combination.

Key Columns

The view exposes six columns, as documented in the ETRM view text:

• INVENTORY_ITEM_ID — The surrogate key of the inventory item for which the revision is defined. This is the primary join key to MTL_SYSTEM_ITEMS_B and to transaction and accounting tables.
• ORGANIZATION_ID — The inventory organization that owns the revision record. Item revisions are organization-specific, so this column is essential for correct resolution in multi-org environments.
• REVISION_ID — The unique identifier of the revision row. This is the column most relevant to the user's search term "revision_id," and it is the primary key of MTL_ITEM_REVISIONS. In SLA contexts it is the value persisted on journal lines or ADR source assignments.
• ITEM_REVISION — The revision code or number, aliased from the underlying REVISION column. This is the human-readable revision identifier (for example, "A" or "01").
• REVISION_LABEL — The descriptive label associated with the revision, used for display and reporting.
• REVISION_REASON — The reason code or description explaining why the revision was created.

Common Use Cases and Queries

Typical usage centers on resolving revision context for accounting and reconciliation reports. A common pattern joins the view to MTL_SYSTEM_ITEMS_B and to transaction tables using INVENTORY_ITEM_ID and ORGANIZATION_ID, while REVISION_ID provides the exact revision linkage.

To retrieve all revisions for a specific item and organization:

• SELECT inventory_item_id, organization_id, revision_id, item_revision, revision_label, revision_reason FROM apps.gmf_xla_item_revisions_v WHERE inventory_item_id = :item_id AND organization_id = :org_id;

To resolve the revision code from a stored REVISION_ID, as when reconciling an SLA journal line:

• SELECT item_revision, revision_label FROM apps.gmf_xla_item_revisions_v WHERE revision_id = :revision_id;

To validate ADR source assignments during SLA setup, query the view filtered by organization to confirm that revision values are available to the accounting derivation rules. Because the view is a synonym-based pass-through with no filters, it returns all revision records visible to the APPS schema, so WHERE clauses on organization or item are strongly recommended in production queries.