Search Results check_existence

Overview

RG_REPORT_AXIS_CONTENTS_PKG is a server-side PL/SQL package in the Oracle E-Business Suite Applications (APPS) schema that encapsulates business logic for the RG_REPORT_AXIS_CONTENTS table. The package is part of the Oracle Financials reporting infrastructure, specifically the RG (Report Generator) product family used to define and generate financial reports such as FSG (Financial Statement Generator) reports. Its stated purpose, per the package header, is "to include all server side procedures and packages for table RG_REPORT_AXIS_CONTENTS." In practical terms, the package manages the flexfield assignments that define what content appears along the rows and columns (axes) of a financial report. Each axis—whether a row axis or a column axis—is identified by a set identifier and a sequence number, and the axis contents determine the account ranges, balances, or other flexfield-based definitions attached to that axis. The package is declared with AUTHID CURRENT_USER, meaning it executes with the privileges of the calling user rather than the definer, which is consistent with many older report generator utilities that are invoked in the context of an authenticated APPS session. The package was originally created in November 1993 and carries a header revision date of 2003, indicating it is a long-standing, stable component of the RG codebase that has been carried forward through EBS 12.1.1 and 12.2.2.

Key Procedures and Functions

The ETRM metadata documents two public program units within this package:

• CHECK_EXISTENCE — A function that checks whether a given axis has flexfield content defined. It accepts an axis set identifier and an axis sequence, and returns a Boolean result indicating the presence or absence of flex assignments for that axis. This is typically used by the Report Generator or FSG forms to determine whether an axis is populated before allowing further processing, row or column generation, or before permitting deletion.
• DELETE_ROWS — A procedure that deletes all flexfield assignments from a row or a column. It similarly takes an axis set identifier and an axis sequence to target the specific axis whose contents should be removed. This supports the editing of report definitions, where users redefine or clear the content of a report axis.

The package does not expose additional documented program units beyond these two; the header indicates it was designed as a focused utility for a single table. The Boolean-returning nature of CHECK_EXISTENCE means it is generally called from PL/SQL rather than directly bound to a form item, though forms can wrap it in a PL/SQL block.

Tables Accessed

The only documented table accessed is RG_REPORT_AXIS_CONTENTS, reached through an APPS synonym. This table stores the flexfield assignments that make up the contents of each report axis. The package reads it to satisfy CHECK_EXISTENCE and writes to it (via deletion) in DELETE_ROWS. No other tables are documented as referenced by this package, which reflects its narrow, single-table utility role. The package is also referenced by one other package in the ETRM repository, indicating it participates in a larger call chain within the Report Generator code, most likely from the FSG or report definition validation logic.

Usage Notes

In Oracle EBS 12.1.1 and 12.2.2, this package is typically invoked from the Report Generator and FSG-related forms and concurrent programs when report definitions are created, validated, or modified. CHECK_EXISTENCE is used as a guard condition—for example, before attempting to generate a report or before permitting a delete—to confirm that an axis actually has content. DELETE_ROWS is invoked when a user clears or redefines a row or column definition, removing the associated flex assignments in a controlled manner. Because the package uses AUTHID CURRENT_USER, callers must have appropriate privileges on the underlying table, which is normally satisfied in APPS sessions. Custom code extending FSG functionality should call these programs rather than issuing direct DML against RG_REPORT_AXIS_CONTENTS, to preserve the integrity of the axis content model. Given the age and stability of the package, no significant behavioral changes are expected between 12.1.1 and 12.2.2.