Search Results revision_reason




Overview
Explore in AI Chat

Overview

APPS.GMF_XLA_ITEM_REVISIONS_V is a reporting and integration view in Oracle E-Business Suite that exposes item revision data for consumption by the eXtensible Layered Architecture (XLA) and General Manufacturing (GMF) product suites. In Oracle EBS 12.1.1 and 12.2.2, the view serves as a simplified, read-only projection over the revision records maintained for inventory items, stripping away the administrative and audit columns that are not required by downstream subledger accounting, costing, or integration logic. Its principal role is to provide a stable, named interface through which subledger accounting events and manufacturing applications can resolve the revision identifier, revision name, revision label, and revision reason associated with a given inventory item and organization. Because object naming in EBS follows the GMF_XLA prefix, the view is closely tied to the XLA subledger accounting engine and to the process manufacturing (OPM/GMF) item master, making it relevant wherever revision-level transaction attribution is required. The presence of the REVISION_REASON column, which is the term most frequently searched by implementers, reflects the view's intended use in capturing the business justification recorded whenever an item revision is created or changed.

Underlying Base Objects

The view is defined over a single documented base object, MTL_ITEM_REVISIONS, which is referenced in the ETRM metadata through a synonym. MTL_ITEM_REVISIONS is the core Oracle Inventory table that stores one row for each revision of each inventory item, keyed by inventory item, organization, and revision. The view performs a direct projection: it does not join additional tables, aggregate rows, or apply filters. Consequently, the granularity of GMF_XLA_ITEM_REVISIONS_V is identical to that of MTL_ITEM_REVISIONS — one row per item revision per organization. No WHERE clause or DISTINCT is present, so all revisions, including obsolete or inactive ones, remain visible unless the caller restricts them. Because the view inherits the MTL_ITEM_REVISIONS synonym owned or exposed under APPS, access is governed by the standard APPS schema grants and any custom menu or responsibility-level exclusions applied to that synonym.

Key Columns

  • INVENTORY_ITEM_ID — The surrogate primary key of the inventory item, joining to MTL_SYSTEM_ITEMS_B.
  • ORGANIZATION_ID — The inventory organization in which the revision is defined, joining to ORG_ORGANIZATION_DEFINITIONS.
  • REVISION_ID — The unique identifier of the revision record; exposed with the same alias as its source column.
  • ITEM_REVISION — The revision code (for example, A, B, C) used to identify the revision in transactions.
  • REVISION_LABEL — The descriptive label associated with the revision, typically the revision name displayed to users.
  • REVISION_REASON — The free-text or coded reason explaining why the revision was created, the column most often referenced in compliance and change-control reporting.

Common Use Cases and Queries

Typical uses include revision reason analysis for quality and change control, subledger accounting lookups during XLA event processing, and integration extracts feeding downstream manufacturing or PLM systems. A simple lookup by item and organization returns:

  • SELECT 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;
  • Reporting all revisions that carry a specific reason: SELECT inventory_item_id, item_revision, revision_reason FROM apps.gmf_xla_item_revisions_v WHERE revision_reason = :reason;
  • Joining to MTL_SYSTEM_ITEMS_B to resolve the item number when building a revision master extract.

Because the view contains no filtering logic, consumers should add their own predicates on organization and item to avoid full scans of the revision table in large implementations.