Search Results fnd_stat

Overview

APPS.AHL_ITEM_GROUPS_V is a read-only reporting and integration view in the Oracle E-Business Suite Applications (AHL) product family, which covers Product Information Management / item catalog functionality. The view presents item group definitions — groupings of items used to organize, categorize, and reference collections of items within Oracle EBS — together with their human-readable lookup meanings. It is constructed by joining the translated item-group view AHL_ITEM_GROUPS_VL against FND_LOOKUP_VALUES_VL twice: once to resolve the status code and once to resolve the type code.

Because the view translates internal codes (STATUS_CODE, TYPE_CODE) into descriptive meanings via Oracle's standard flexfields/lookups infrastructure, it is well suited for ad-hoc reporting, concurrent program output, and integration payloads where consumers require readable status and type descriptions rather than raw lookup codes. The metadata documents the view as owned by APPS and defined over both a translated (_VL) view and the FND lookup values view.

Underlying Base Objects

Two referenced base objects are documented for this view:

• AHL_ITEM_GROUPS_VL (VIEW) — the translated (language-specific) view that supplies the core item group attributes such as ROW_ID, ITEM_GROUP_ID, NAME, STATUS_CODE, TYPE_CODE, and audit columns.
• FND_LOOKUP_VALUES_VL (VIEW) — the standard Oracle lookups view, joined twice with outer joins (denoted by the (+) operator) to resolve STATUS_CODE against lookup type AHL_ITEMGROUP_STATUS and TYPE_CODE against lookup type AHL_ITEMGROUP_TYPE.

The outer join semantics are significant: if a lookup value is missing from FND_LOOKUP_VALUES_VL, the item group row still appears, but its corresponding *_MEANING column returns NULL. This preserves the completeness of item group records while decoupling them from lookup maintenance.

Key Columns

• ROW_ID — surrogate row identifier for the item group.
• ITEM_GROUP_ID — the primary business key identifying the item group.
• NAME — the user-defined item group name.
• OBJECT_VERSION_NUMBER — the optimistic locking version number used by the Applications framework.
• STATUS_CODE / STATUS_MEANING — the coded status (e.g., active/inactive) and its resolved lookup meaning from AHL_ITEMGROUP_STATUS.
• TYPE_CODE / TYPE_MEANING — the coded item group type and its resolved meaning from AHL_ITEMGROUP_TYPE.
• SOURCE_ITEM_GROUP_ID — reference to the source item group, supporting copy/derivation relationships.
• DESCRIPTION — free-text description of the item group.
• Standard audit columns — CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN.
• Descriptive flexfield columns — ATTRIBUTE_CATEGORY and ATTRIBUTE1 through ATTRIBUTE15.

Common Use Cases and Queries

Typical scenarios include reporting on item group usage, filtering groups by readable status or type, and feeding integrations that require descriptive values. Note that additional AHL tables linking items to groups (not documented in this metadata) are generally required to resolve the actual item memberships.

List all item groups with resolved status and type meanings:

• SELECT ITEM_GROUP_ID, NAME, STATUS_MEANING, TYPE_MEANING, DESCRIPTION FROM APPS.AHL_ITEM_GROUPS_V;

Retrieve active groups of a specific type:

• SELECT ITEM_GROUP_ID, NAME, TYPE_MEANING FROM APPS.AHL_ITEM_GROUPS_V WHERE STATUS_MEANING = 'Active' AND TYPE_CODE = '<type>' ORDER BY NAME;

Detect unmaintained lookup definitions where meanings are missing:

• SELECT ITEM_GROUP_ID, NAME, STATUS_CODE, TYPE_CODE FROM APPS.AHL_ITEM_GROUPS_V WHERE STATUS_MEANING IS NULL OR TYPE_MEANING IS NULL;

Because the view is defined over translated (_VL) views, query results are returned in the session's language, making the view appropriate for locale-aware reporting and integration extraction.