Results for “igf_aw_coa_item_category”

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

Overview

APPS.IGF_AW_ITEM_V is a reporting and integration view within the Oracle E-Business Suite (EBS) Grants Accounting / ETRM (Enterprise Tracking and Reporting Module) product family. Its principal purpose is to expose item master records, along with a decoded description of each item's category, in a form suitable for reporting, concurrent programs, and integration interfaces. The view consolidates the raw item definition stored in the base table IGF_AW_ITEM with a lookup-based translation of the category code, using the IGF_AW_GEN.LOOKUP_DESC function against the lookup type IGF_AW_COA_ITEM_CATEGORY.

The view is read-only and does not own any data; it is a projection over the base item table. Because it is defined in the APPS schema, it is accessible to standard EBS responsibility and user-based access patterns and can be queried through any tool that connects to the EBS database, including Oracle Forms-based inquiry screens, Oracle Reports, BI Publisher, and ad hoc SQL environments.

Underlying Base Objects

The documented view definition references exactly one base table: IGF_AW_ITEM. The view selects the row identifier, business key, descriptive, status, and audit columns from this table, aliased as ITEM. The ETRM metadata lists no additional referenced base objects, confirming that the category description is not sourced from a joined table but is instead resolved at runtime by a database function.

The decode of the item category is performed by IGF_AW_GEN.LOOKUP_DESC, an EBS utility function that returns the display meaning associated with a lookup code for a given lookup type. The lookup type passed in the view is IGF_AW_COA_ITEM_CATEGORY, which is the same value the user searched for. This lookup type enumerates the valid item categories used in the Chart of Accounts (COA) context for grants and awards items. As a result, the view's category description is consistent with the descriptive flexfield and lookup-driven behavior of the surrounding ETRM modules, and any change to the lookup meaning in the ETRM Lookups setup is reflected automatically on the next query.

Key Columns

• ROW_ID – The physical ROWID of the underlying row in IGF_AW_ITEM. Useful as a unique handle when the view is used by a block with a ROWID-based data source.
• ITEM_CODE – The business key or code identifying the item. This is the value most application logic and cross-references rely upon.
• DESCRIPTION – The free-text description of the item.
• ACTIVE – The enabled/disabled flag indicating whether the item is currently valid for selection.
• ITEM_CATEGORY_CODE – The stored category code for the item, drawn directly from IGF_AW_ITEM.ITEM_CATEGORY_CODE.
• ITEM_CATEGORY_DESC – The decoded meaning of ITEM_CATEGORY_CODE, retrieved via IGF_AW_GEN.LOOKUP_DESC for lookup type IGF_AW_COA_ITEM_CATEGORY.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN – Standard Oracle EBS audit columns, retained in the view so that reports can surface creation and modification history.

Common Use Cases and Queries

The view is most often used to present user-friendly item listings where the category is shown by description rather than by code, and to support validation in grants and awards setup screens. A typical listing of active items follows:

• SELECT item_code, description, item_category_code, item_category_desc FROM apps.igf_aw_item_v WHERE active = 'Y' ORDER BY item_category_desc, item_code;

To report the count of items grouped by category description:

• SELECT item_category_desc, COUNT(*) FROM apps.igf_aw_item_v WHERE active = 'Y' GROUP BY item_category_desc;

To find all items that have been changed since a given date, the audit columns are used:

• SELECT item_code, item_category_desc, last_updated_by, last_update_date FROM apps.igf_aw_item_v WHERE last_update_date >= :p_date;

Because the category description is resolved through the IGF_AW_COA_ITEM_CATEGORY lookup, the view is also convenient for diagnosing category setup issues: querying the view alongside the lookup definition quickly reveals items whose category code is no longer associated with a valid meaning.