Search Results igf_db_pays_prg_t

Overview

IGF_DB_PAYS_PRG_T is a table in the IGF (Financial Aid) product module of Oracle E-Business Suite, documented as VALID in both release 12.1.1 and 12.2.2. The object resides in the IGF schema and is titled "Table: IGF_DB_PAYS_PRG_T." Based on its naming convention and column structure, it stores disbursement-to-program association records that link financial aid disbursement activity (identified by DBPAYS_ID) to academic program definitions via PROGRAM_CD and PRG_VER_NUM.

The ETRM metadata classifies this object heuristically as "standalone" within a Data Vault modeling framework, meaning no foreign key relationships were mined from the documented FK structure. In Data Vault terms, this suggests the object behaves most like a hub or reference table anchored on its own business key, rather than a dependent link or satellite. Modelers should treat this classification as a starting suggestion only; actual integration patterns in an institution's implementation may reveal implicit relationships not captured in the physical FK constraints.

The table contains 11 documented columns and carries a single primary key constraint, IGF_DB_PAYS_PRG_T_PK, defined on DBPAYS_ID.

Key Information Stored

The table's 11 columns divide into a surrogate identifier, a cluster of business-key attributes, and standard audit columns.

• DBPAYS_ID — The surrogate primary key, enforced by the unique index IGF_DB_PAYS_PRG_T_PK. This column uniquely identifies each disbursement-program record and is the most reliable join target.
• BASE_ID — A base identifier, likely referencing the underlying financial aid base record from which this program association derives.
• PROGRAM_CD — The academic program code, forming the primary business descriptor of the row. Together with PRG_VER_NUM, this represents a business-key candidate for the program dimension.
• PRG_VER_NUM — The program version number, qualifying PROGRAM_CD so that versioned program definitions remain distinguishable.
• UNIT_CD — The academic unit code associated with the program, typically representing a department, school, or organizational unit.
• UNIT_VER_NUM — The version number for the academic unit, paralleling PRG_VER_NUM for unit data.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — Standard EBS audit columns tracking who created and last modified each row and when, plus the session login identifier.

While IGF_DB_PAYS_PRG_T_PK is the only documented unique index, the combination of PROGRAM_CD, PRG_VER_NUM, UNIT_CD, and UNIT_VER_NUM functions as a practical business-key candidate for identifying the program-unit context of a disbursement.

Common Use Cases and Queries

Typical usage centers on reporting which academic programs and units received or are associated with specific disbursement records. A common query pattern joins this table to disbursement tables on DBPAYS_ID or BASE_ID to enrich aid reporting with program and unit context.

• Program-level disbursement reporting: Aggregate disbursement counts or amounts grouped by PROGRAM_CD and PRG_VER_NUM to analyze aid distribution across programs.
• Unit-level analysis: Group by UNIT_CD and UNIT_VER_NUM to evaluate disbursement activity by academic department or school.
• Audit and change tracking: Use LAST_UPDATED_BY and LAST_UPDATE_DATE to identify recently modified program associations for reconciliation.
• Version validation: Identify records where PRG_VER_NUM or UNIT_VER_NUM differ from current program or unit definitions, flagging stale associations.

A representative query grouping disbursements by program: SELECT PROGRAM_CD, PRG_VER_NUM, COUNT(DBPAYS_ID) FROM IGF.IGF_DB_PAYS_PRG_T GROUP BY PROGRAM_CD, PRG_VER_NUM;

Related Objects

The ETRM metadata documents no confirmed foreign key relationships, and the heuristic classification is standalone. Consequently, related objects must be inferred from column semantics rather than enforced constraints.

• IGF disbursement tables — Parent objects providing the DBPAYS_ID or BASE_ID values referenced here; join on DBPAYS_ID or BASE_ID.
• Program definition tables — Master tables holding PROGRAM_CD and PRG_VER_NUM; join on both columns to resolve program names.
• Academic unit tables — Reference data for UNIT_CD and UNIT_VER_NUM; join on these columns for department descriptions.
• IGF_DB_PAYS_PRG_T_PK — The primary key constraint/index, ensuring uniqueness on DBPAYS_ID.

Until FK metadata is confirmed, integrators should validate join cardinality against actual data before relying on any inferred relationship.