Search Results unit_ver_num

Overview

IGF.IGF_DB_PAYS_PRG_T is a standalone table in the Oracle E-Business Suite (EBS) IGF schema, part of the Oracle Grants/Projects and financials product family. It stores program and unit versioning definitions tied to a base payroll or disbursement record, identifying which program code, program version, unit code, and unit version applies to a given disbursement/ID reference. The table resides in the APPS_TS_NOLOGGING tablespace with a PCT Free of 10, indicating its use in bulk or ETL-style insert workloads where redo generation is minimized. The object is marked VALID but carries the Oracle Internal Use Only warning: it must not be queried directly except through standard Oracle Applications programs.

From a Data Vault modeling perspective, the metadata's heuristic classification places this object as standalone, with no documented foreign key dependencies to or from other objects. In practical terms, IGF_DB_PAYS_PRG_T behaves like a satellite candidate — it carries descriptive attributes (PROGRAM_CD, UNIT_CD, versions) keyed by a surrogate identifier. Because it references no parent hub and is not referenced by other objects, it also functions as a self-contained reference/detail table for program-unit versioning data.

Key Information Stored

The table has 11 columns and one unique index, IGF_DB_PAYS_PRG_T_PK, defined on DBPAYS_ID. The most significant columns are:

• DBPAYS_ID (NUMBER 15) — the surrogate primary key and sole unique-index column; uniquely identifies each program-unit version record.
• BASE_ID (NUMBER 15) — a business-key candidate linking the row to its underlying base disbursement or source record.
• PROGRAM_CD (VARCHAR2) — the program code associated with the record, a primary business descriptor.
• PRG_VER_NUM (NUMBER) — the program version number, enabling versioned program tracking.
• UNIT_CD (VARCHAR2 10) — the unit code, another core business attribute.
• UNIT_VER_NUM (NUMBER) — the unit version number; this is the attribute most commonly used to distinguish successive unit revisions.
• CREATED_BY, CREATION_DATE — standard WHO audit columns capturing the creating user and timestamp.
• LAST_UPDATED_BY, LAST_UPDATE_DATE — WHO audit columns for the most recent modification.
• LAST_UPDATE_LOGIN (NUMBER 15) — the login identifier of the last updating session.

DBPAYS_ID serves as the surrogate key, while the combination of BASE_ID with PROGRAM_CD/PRG_VER_NUM and UNIT_CD/UNIT_VER_NUM represents the practical business-key candidate for identifying a unique program-unit version combination.

Common Use Cases and Queries

Typical usage involves resolving which program and unit versions apply to a disbursement record, supporting Grants/Projects reporting, audit trails, and version-reconciliation extracts. A representative query retrieves versioning detail by base record:

• SELECT DBPAYS_ID, BASE_ID, PROGRAM_CD, PRG_VER_NUM, UNIT_CD, UNIT_VER_NUM FROM IGF.IGF_DB_PAYS_PRG_T WHERE BASE_ID = :p_base_id;
• Filtering on UNIT_VER_NUM to identify the latest unit revision: SELECT * FROM IGF.IGF_DB_PAYS_PRG_T WHERE UNIT_CD = :p_unit AND UNIT_VER_NUM = (SELECT MAX(UNIT_VER_NUM) FROM IGF.IGF_DB_PAYS_PRG_T WHERE UNIT_CD = :p_unit);
• Audit reporting using CREATION_DATE/LAST_UPDATE_DATE ranges to trace record activity.

Because the table is unlogged (APPS_TS_NOLOGGING), it is best suited to read-mostly reporting rather than high-concurrency OLTP writes.

Related Objects

The ETRM dependency data documents that IGF_DB_PAYS_PRG_T does not reference any database object and is not referenced by other objects; its only documented relationship is the APPS synonym IGF_DB_PAYS_PRG_T, through which standard Oracle Applications programs access it. Practically, related objects would include the IGF program and unit definition tables supplying PROGRAM_CD, UNIT_CD, PRG_VER_NUM, and UNIT_VER_NUM, joined on those business columns, and the base disbursement/payroll table joined on BASE_ID. No foreign-key-constrained companions are documented, so joins should be constructed on the BASE_ID, PROGRAM_CD, and UNIT_CD business columns rather than on enforced constraints.