Search Results rollover_fund_id

Overview

The IGF_AW_FRLOG_ALL table is a core data repository within the Oracle E-Business Suite's Grants Accounting (IGF) module, specifically for the Financial Aid (Award) component. Its primary role is to serve as a detailed audit and tracking log for financial aid fund rollover transactions. As documented, it "Holds details of all the funds which got rolled over." This table is a multi-org object (indicated by the '_ALL' suffix and the ORG_ID column), storing data for all operating units within an EBS instance. It is essential for maintaining a historical record of how funds from one period are transferred or "rolled over" into subsequent periods, ensuring financial traceability and compliance.

Key Information Stored

The table's structure is designed to log the rollover event and its participants. The key transactional columns are:

• FRLOG_ID: The table's primary key, serving as a unique identifier for each log entry.
• FROL_ID: The foreign key linking to the master rollover transaction (IGF_AW_FUND_ROLLOVER_ALL), identifying the specific rollover batch or event.
• FUND_ID: The identifier for the original source fund being rolled over, referencing the fund master table (IGF_AW_FUND_MAST_ALL).
• ROLLOVER_FUND_ID: The identifier for the newly created destination fund resulting from the rollover, also referencing the fund master table.
• ORG_ID: The operating unit identifier, enabling multi-org partitioning of the data.

The table also includes a full suite of standard EBS WHO columns (CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN) and concurrent program WHO columns (PROGRAM_APPLICATION_ID, PROGRAM_ID, PROGRAM_UPDATE_DATE, REQUEST_ID) for auditing and process tracking.

Common Use Cases and Queries

This table is central to reporting and reconciliation activities related to fund rollovers. A common use case is generating a detailed report of all funds affected by a specific rollover event. For example, to audit the results of a rollover identified by a specific FROL_ID (the user's search term), the following query pattern is typical:

SELECT frlog.FRLOG_ID, frlog.FROL_ID, src_fund.FUND_CODE AS SOURCE_FUND, dest_fund.FUND_CODE AS ROLLOVER_FUND
FROM IGF.IGF_AW_FRLOG_ALL frlog,
IGF.IGF_AW_FUND_MAST_ALL src_fund,
IGF.IGF_AW_FUND_MAST_ALL dest_fund
WHERE frlog.FUND_ID = src_fund.FUND_ID
AND frlog.ROLLOVER_FUND_ID = dest_fund.FUND_ID
AND frlog.FROL_ID = :p_frol_id
AND frlog.ORG_ID = :p_org_id;


Another critical use case is tracing the lineage of a specific fund to understand its rollover history, querying where the FUND_ID or ROLLOVER_FUND_ID matches a given fund. The table is also queried extensively during period-end close processes to validate that all intended rollover activities have been successfully logged and completed.

Related Objects

IGF_AW_FRLOG_ALL is a central link between the master rollover header and fund tables, as defined by its foreign key constraints:

• Primary Key: IGF_AW_FRLOG_ALL_PK on column FRLOG_ID.
• Foreign Key (References IGF_AW_FUND_ROLLOVER_ALL): The FROL_ID column links each detailed log entry to its parent rollover transaction header. This relationship allows navigation from the summary rollover event to all its constituent fund movements.
• Foreign Key (References IGF_AW_FUND_MAST_ALL): The FUND_ID and ROLLOVER_FUND_ID columns each reference the IGF_AW_FUND_MAST_ALL table. This creates two distinct relationships: one to identify the original source fund and another to identify the newly created destination fund, enabling complete bi-directional tracing of fund rollovers.

As a foundational transactional table, it is referenced by various forms, reports, and potentially interfaces within the Grants Accounting module to present and process rollover history.