Glfrcreportsb -

To most, it was a dry collection of data points on soil acidity and spruce budworm migration. To Elias, it was a time machine.

@Repository public class GLReportRepository

The table contains both "content dates" ( LAST_MODIFIED_DATE ) and "system transaction dates" ( LAST_UPDATE_DATE ). The LAST_MODIFIED_DATE reflects changes to the report within the BI catalog (e.g., the report design). The LAST_UPDATE_DATE reflects when the table row itself was last updated by a system process. These can differ. glfrcreportsb

Accessible mid-month without initiating a formal ledger close process.

return record;

if (report.isEmpty()) return ResponseEntity.noContent().build();

1. The Enterprise Accounting Perspective: Financial Rate Codes and General Ledger Modules To most, it was a dry collection of

: Indicates the category of the report (e.g., BIP, Dashboard, or Analysis).

When you create, register, or publish a new report—whether it is a complex Financial Report (FR), an Oracle Transactional Business Intelligence (OTBI) analysis, or a BI Publisher (BIP) report—the metadata for that report is stored in this table. This allows the system to quickly query and display reports within the FRC. Schema: FUSION Owner: GL Table Type: Base table (indicated by the ‘_B’ suffix) The LAST_MODIFIED_DATE reflects changes to the report within

Organizations often experience "report sprawl" — an accumulation of outdated, unused, or duplicated reports. By querying LAST_ACCESSED_DATE , you can identify which reports have not been run or accessed for a defined period (e.g., LAST_ACCESSED_DATE < SYSDATE - 365 ). This data provides the justification needed to archive or remove obsolete reports, reducing clutter and improving system performance.