Search Results print_output

Overview

FND_AUDIT_REPORT is an Oracle E-Business Suite PL/SQL package body owned by the APPS schema and classified as an OTHER API within the ETRM repository. Its principal business function is to support audit schema validation by producing an exception report that verifies the integrity and completeness of the audit configuration defined in the FND audit tables. In effect, the package validates that audit groups, audit schemas, audit tables, and audit columns are correctly and consistently defined, and it reports any missing or inconsistent definitions as exceptions.

The package header comment identifies a date of 2013/03/05 and a file header of AFATRPTB.pls, confirming it is a long-standing component of the EBS technology stack. It is present and documented in both Oracle EBS 12.1.1 and 12.2.2, where it is used primarily as the underlying logic for a concurrent program that generates the audit validation exception report.

Key Procedures and Functions

• PRINT_OUTPUT — A helper procedure that writes a supplied data string either to the concurrent manager log file (via FND_FILE.PUT_LINE) or, when the log flag is not set, to DBMS_OUTPUT for debugging purposes. The documented logic shows that when the log indicator is 'Y' the text is written to the concurrent manager log file; otherwise the procedure performs no output by default, with the DBMS_OUTPUT path noted as an optional debugging alternative.
• AUDIT_GROUP_VALIDATION — The primary procedure of the package and the entry point for the concurrent program. It is a PL/SQL stored procedure concurrent program that creates an exception report for audit schema validation. It accepts an audit group name, a program name used for log file tagging, and a log flag, and returns the standard concurrent program ERRBUF and RETCODE outputs. Internally it uses local status flags to record whether each audited object is present or missing, and it applies FND_INSTALLATION.GET_APP_INFO to resolve application installation information such as status, industry, and schema.

Tables Accessed

The package reads from a defined set of audit and application metadata tables, referenced through APPS synonyms. FND_AUDIT_GROUPS, FND_AUDIT_SCHEMAS, FND_AUDIT_TABLES, and FND_AUDIT_COLUMNS supply the audit configuration that drives validation. FND_APPLICATION, FND_ORACLE_USERID, and FND_TABLES provide application and database object context. Dictionary views ALL_TAB_COLUMNS, DBA_TAB_COLUMNS, DBA_OBJECTS, and USER_SYNONYMS are queried to confirm the physical existence and definition of audited objects, while DUAL supports standalone evaluations. The package is read-only in nature; it does not write to application tables.

Usage Notes

FND_AUDIT_REPORT is typically invoked through its associated concurrent program, which calls AUDIT_GROUP_VALIDATION to produce the audit schema validation exception report and routes formatted output through PRINT_OUTPUT to the concurrent manager log. The LOG parameter allows the same logic to be exercised interactively with DBMS_OUTPUT for debugging. Because the package is documented as referenced by no other packages, it is intended to be called directly by the concurrent manager rather than as a dependency of other PL/SQL units. Administrators and technical consultants use it when diagnosing audit configuration problems or verifying that audit groups are correctly deployed across schemas.