Results for “pell_coa”

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

Overview

IGF_AW_COA_GROUP is an Oracle E-Business Suite database view belonging to the IGF — Financial Aid product family, a module classified as obsolete in EBS 12.1.1 and 12.2.2. The view presents consolidated Chart of Accounts (COA) grouping data used by the financial aid award processing engine, particularly for need-analysis and award-calculation routines that must map institutional COA structures to federal or institutional aid rules. The suffix "AW" denotes its association with award calculation logic, while "COA_GROUP" indicates its purpose of exposing COA grouping identifiers and descriptions.

The view serves as a multi-organization (multi-org) secured read interface. It is intended for reporting and integration rather than transactional maintenance; the base table IGF_AW_COA_GROUP_ALL holds the actual records, and this view filters them according to the operating unit (ORG_ID) derived from the session's CLIENT_INFO context. In the ETRM metadata provided, the view is flagged as "Not implemented in this database," meaning it may exist only in installations where the legacy financial aid module was deployed and the relevant patch or schema objects were created.

Underlying Base Objects

The view is defined over a single documented base object:

• IGF_AW_COA_GROUP_ALL — the multi-org base table containing all COA group rows across operating units.

The view text selects from this alias (COAG) and applies a multi-org security predicate. The predicate compares NVL(COAG.ORG_ID, -99) against the ORG_ID parsed from USERENV('CLIENT_INFO'). When the session's CLIENT_INFO begins with a space, the decode returns NULL, which is then coalesced to -99 — the sentinel used for records not assigned to a specific organization. This design mirrors the standard "ALL" table plus org-secured view pattern used throughout Oracle EBS. No additional base objects are documented in the ETRM metadata, and no foreign key relationships are explicitly exposed.

Key Columns

The view exposes sixteen columns. Several are structural artifacts of the view definition rather than meaningful business attributes:

• ROW_ID — the ROWID of the underlying base-table row; not a business key.
• COA_CODE — the chart of accounts code identifying the COA structure to which the group belongs.
• CI_CAL_TYPE and CI_SEQUENCE_NUMBER — calendar type and sequence number, used to tie COA groups to a specific aid cycle or award year.
• RULE_ORDER, S_RULE_CALL_CD, RUL_SEQUENCE_NUMBER, PELL_COA, PELL_ALT_EXP — these column names appear in the documented column list but are populated by the view with NULL placeholders. They exist for structural compatibility with downstream consumers expecting the full column set, but carry no data in this view.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS audit columns.
• ORG_ID — the operating unit identifier used for multi-org security.
• COA_GRP_DESC — the COA group description. This is the column most frequently referenced by the search term "coa_grp_desc," and it provides the human-readable label for each COA grouping.

Common Use Cases and Queries

Typical use cases include financial aid reporting, data migration extraction, and integration with external need-analysis systems. A standard query lists COA groups for the current operating unit:

• SELECT coa_code, ci_cal_type, ci_sequence_number, coa_grp_desc, org_id FROM igf_aw_coa_group ORDER BY coa_code, ci_cal_type;

To search by the description column directly:

• SELECT coa_code, coa_grp_desc FROM igf_aw_coa_group WHERE UPPER(coa_grp_desc) LIKE UPPER('%&term%');

Because the view's org security is driven by CLIENT_INFO, queries executed outside a properly initialized EBS session (for example, from a generic SQL client) may return the null-org (-99) rows only. Integrations should therefore run within an initialized application session or query IGF_AW_COA_GROUP_ALL with an explicit ORG_ID predicate when cross-org visibility is required.