Search Results igf_aw_dml_operation




Overview

IGF_AW_COA_HIST_V is a supplementary view owned by the APPS schema in Oracle E-Business Suite, registered under FND Design Data as IGF.IGF_AW_COA_HIST_V and reported with a status of VALID. It belongs to the IGF product family, which supports the Award management and grants accounting functionality delivered with Oracle Grants Accounting / Oracle E-Business Suite financials. The view exposes the change history of Chart of Accounts (COA) distributions associated with award-related base records, allowing historical auditing of how a given distribution was altered over time.

Its View Type is documented as a supplementary view intended to simplify Forms coding. Oracle explicitly cautions that this view is not intended for direct querying or data manipulation, and that its definition may change dramatically in subsequent minor or major releases. Consequently, it should be treated strictly as an internal forms-support object rather than a stable integration interface.

In release 12.1.1 and 12.2.2 the object retains this classification; no public API contract is attached to it. It is not referenced by any database object, confirming its role as a terminal, presentation-layer construct.

Underlying Base Objects

The view is defined over a combination of awards and person-related entities. The documented dependencies include: IGF_AW_COA_HIST, the primary history table holding the change records; IGF_AP_FA_BASE_REC, which stores the base award record referenced by BASE_ID; FND_USER, used to resolve the identity of the last updating user; HZ_PARTIES, for party-level person data; IGS_CA_INST, the calendar instance table resolving the calendar type and sequence values; IGS_PE_ALT_PERS_ID and IGS_PE_PERSON_ID_TYP, which supply alternate person identifiers; and IGF_LOOKUPS_VIEW, which resolves lookup codes into their descriptions.

The driving table is IGF_AW_COA_HIST, keyed by COAH_ID, with BASE_ID linking each history row to its associated base record. Calendar context is provided through CI_CAL_TYPE / CI_SEQUENCE_NUMBER and LD_CAL_TYPE / LD_SEQUENCE_NUMBER, resolved against IGS_CA_INST. Person attributes are joined through the IGS_PE person identifier tables and HZ_PARTIES. No database object depends on this view.

Key Columns

  • COAH_ID — Primary identifier of the change-history record.
  • BASE_ID — Foreign key to the associated award base record in IGF_AP_FA_BASE_REC.
  • PERSON_NUMBER, PERSON_NAME, SSN — Person identification attributes derived through the IGS_PE and HZ_PARTIES joins.
  • TRAN_DATE — The date the COA change transaction occurred; this is the column most commonly retrieved when searching for "tran_date".
  • ITEM_CODE — The item or distribution element affected by the change.
  • CI_CAL_TYPE, CI_SEQUENCE_NUMBER, LD_CAL_TYPE, LD_SEQUENCE_NUMBER, LD_ALTERNATE_CODE — Calendar context identifying the change and load periods.
  • OPERATION_TXT, OPERATION_DESC — The operation performed and its decoded description.
  • OLD_VALUE, NEW_VALUE — The prior and resulting numeric values of the changed element, enabling value-level audit comparison.
  • REQUEST_ID — Concurrent request that produced the change.
  • LAST_UPDATED_BY, LAST_UPDATED_USER — Audit columns identifying the responsible user and the resolved user name.

Common Use Cases and Queries

The principal use case is historical auditing: reconstructing how a specific award distribution changed, when it changed, and who changed it. Analysts commonly filter by TRAN_DATE to isolate changes within a reporting period.

To retrieve recent changes for a base record:

  • SELECT coah_id, base_id, tran_date, item_code, operation_desc, old_value, new_value, last_updated_user FROM apps.igf_aw_coa_hist_v WHERE base_id = :p_base_id AND tran_date BETWEEN :p_from AND :p_to ORDER BY tran_date;

To inspect all history produced by a single concurrent request:

  • SELECT base_id, tran_date, item_code, old_value, new_value FROM apps.igf_aw_coa_hist_v WHERE request_id = :p_request_id;

Because the view is a forms-support object, production reporting should prefer the underlying IGF_AW_COA_HIST base table joined explicitly to required lookups, ensuring resilience against definition changes across EBS releases.