Search Results last_version_code

Overview

GR_ITEM_GENERAL_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the GR – Process Manufacturing Regulatory Management product family. It exposes a denormalized, convergence-model representation of regulatory item detail, combining master inventory item attributes with regulatory explosion properties. The view is documented as VALID and is intended for read-only consumption by reports, concurrent programs, and integration interfaces that require item-level regulatory data without navigating the normalized underlying tables directly.

Because it is a view rather than a table, it holds no data of its own; all content is derived at runtime from its base objects. Its principal design purpose is to present a consistent, uniform column layout for regulatory items so that downstream consumers—particularly those migrating or reconciling data under the Convergence model introduced in later releases—can query a single source. Many columns in the projection are defined as literal NULL placeholders, indicating that the view conforms to a broader interface contract while only a subset of those columns are populated by the Process Manufacturing Regulatory Management implementation.

Underlying Base Objects

The view is defined over two documented base objects, both referenced through APPS synonyms:

• MTL_SYSTEM_ITEMS_KFV – the key flexfield view over MTL_SYSTEM_ITEMS, supplying organization, inventory item, item code (concatenated segments), CAS number, and standard WHO-column audit fields.
• GR_ITEM_EXPLOSION_PROPERTIES – the regulatory table supplying ingredient flag, explode ingredient flag, and actual hazard attributes.

The join is an outer join driven from MTL_SYSTEM_ITEMS_KFV: A.INVENTORY_ITEM_ID = B.INVENTORY_ITEM_ID(+) and A.ORGANIZATION_ID = B.ORGANIZATION_ID(+). This ensures every inventory item in the master organization view is returned even where no regulatory explosion properties exist, with the GR-sourced columns appearing as NULL in those rows. The inner query text aliases the item master as A and the regulatory properties as B.

Key Columns

• ORGANIZATION_ID / INVENTORY_ITEM_ID – the composite key identifying the item within an inventory organization; used for all joins back to inventory and regulatory tables.
• ITEM_CODE – the concatenated flexfield segments from MTL_SYSTEM_ITEMS_KFV, providing the human-readable item identifier.
• PRIMARY_CAS_NUMBER – mapped from A.CAS_NUMBER, the Chemical Abstracts Service registry number for the regulatory item.
• INGREDIENT_FLAG / EXPLODE_INGREDIENT_FLAG – regulatory flags from GR_ITEM_EXPLOSION_PROPERTIES indicating whether the item is treated as an ingredient and whether its ingredients should be exploded.
• ACTUAL_HAZARD – the hazard classification sourced from the explosion properties table.
• FORMULA_SOURCE_INDICATOR – a hard-coded literal 'P', denoting the Process Manufacturing source in the convergence model.
• USER_ID – aliased from A.CREATED_BY, identifying the creating user.
• Audit columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) – standard EBS WHO columns inherited from the item master.
• Placeholder columns – ITEM_GROUP_CODE, INTERNAL_REFERENCE_NUMBER, PRODUCT_LABEL_CODE, VERSION_CODE, LAST_VERSION_CODE, PRODUCT_CLASS, PRINT_INGREDIENT_PHRASES_FLAG, ATTRIBUTE_CATEGORY, and ATTRIBUTE1 through ATTRIBUTE30 are all defined as NULL to satisfy the convergence interface contract.

Common Use Cases and Queries

Typical usage includes regulatory item listings, ingredient-flag reporting, and convergence reconciliation extracts. Because placeholder columns return NULL, filtering or ordering should rely only on populated columns. A representative query is:

SELECT organization_id, inventory_item_id, item_code, primary_cas_number, ingredient_flag, explode_ingredient_flag, actual_hazard FROM apps.gr_item_general_v WHERE organization_id = :p_org AND ingredient_flag = 'Y';

Analysts commonly join the view back to MTL_SYSTEM_ITEMS_KFV for descriptions, or to GR_ITEM_EXPLOSION_PROPERTIES for additional regulatory attributes not projected here. When migrating data between 12.1.1 and 12.2.2, the view offers a stable column set that shields downstream extracts from schema drift between the two releases.