Search Results item_rev_fk

Overview

APPS.EDW_ITEMS_ITEM_REV_FKV is a public Oracle E-Business Suite view owned by the APPS schema and registered under the FND Design Data identifier ENG.EDW_ITEMS_ITEM_REV_FKV. It exists within the Enterprise Data Warehouse (EDW) family of item-related reporting objects, whose purpose is to expose inventory item data in a denormalized, join-friendly form. The view holds internal item id, organization id, and item revision associations, providing a single flattened source for resolving the revision context of an item within a given inventory organization.

The view carries a VALID status in the ETRM metadata and is classified as a public view that may be useful for custom reporting or other data requirements. Its inclusion of a pre-computed foreign-key column makes it particularly suited to downstream integration scenarios, where a surrogate key representing the combination of item, organization, and revision is required. The view is not referenced by any other database object, confirming its role as a terminal reporting artifact rather than a building block for additional APPS objects. It is available in both Oracle EBS 12.1.1 and 12.2.2, though the underlying table usage should be confirmed against the specific instance.

Underlying Base Objects

The documented dependency list identifies three APPS base objects over which EDW_ITEMS_ITEM_REV_FKV is defined:

• MTL_ITEM_REVISIONS — the transactional table storing revision definitions for items, including revision labels, effective dates, and lifecycle status. This is the primary source of the REVISION value.
• MTL_SYSTEM_ITEMS_KFV — the key flexfield view over MTL_SYSTEM_ITEMS, supplying item identity and organization context, and resolving the concatenated item key segments.
• MTL_PARAMETERS — the organization parameters table, typically joined to confirm the inventory organization and its attribute control settings.

The view therefore sits on top of the core inventory item and revision model: MTL_SYSTEM_ITEMS provides the item-organization grain, MTL_ITEM_REVISIONS provides the revision detail for that grain, and MTL_PARAMETERS supplies organization-level qualification. Because the view is defined over these standard tables, it reflects the same revision data maintained by the Inventory and Engineering modules, without introducing its own persistence.

Key Columns

• INVENTORY_ITEM_ID (NUMBER) — the internal identifier of the item. This is the primary internal key used to join to MTL_SYSTEM_ITEMS and other inventory objects.
• ORGANIZATION_ID (NUMBER) — the internal identifier of the inventory organization in which the item revision association applies. Combined with INVENTORY_ITEM_ID, it establishes the item-organization grain.
• REVISION (VARCHAR2) — the item revision label, such as a revision letter or code, as defined in MTL_ITEM_REVISIONS.
• ITEM_REV_FK (VARCHAR2, length 48) — a foreign key representing the item revision. This derived column encapsulates the item-organization-revision relationship in a single attribute, simplifying joins and supporting reporting key generation.

No columns are documented as mandatory, which is consistent with a view rather than a base table; consumers should nonetheless treat INVENTORY_ITEM_ID, ORGANIZATION_ID, and REVISION as the essential components of the record.

Common Use Cases and Queries

The view is typically used for revision-level reporting on inventory items, such as listing all revisions defined for an item within an organization, or driving downstream extracts that require a stable foreign key for the revision. A straightforward query follows the documented query text:

• SELECT INVENTORY_ITEM_ID, ORGANIZATION_ID, REVISION, ITEM_REV_FK FROM APPS.EDW_ITEMS_ITEM_REV_FKV;
• Filter by organization: SELECT INVENTORY_ITEM_ID, REVISION FROM APPS.EDW_ITEMS_ITEM_REV_FKV WHERE ORGANIZATION_ID = :org_id;
• Resolve revision by item: SELECT REVISION, ITEM_REV_FK FROM APPS.EDW_ITEMS_ITEM_REV_FKV WHERE INVENTORY_ITEM_ID = :item_id AND ORGANIZATION_ID = :org_id;

Typical scenarios include engineering change impact analysis, revision audit extracts, and data warehouse loads that require a compact mapping of item, organization, and revision. Because the view is not referenced by other database objects, it may be customized or extended for reporting without risk of breaking dependent APPS code, though standard change-control practices should still apply.