Results for “msd_audit_report”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

APPS.MSD_AUDIT_SQL_STATEMENTS_V is a reporting view owned by the APPS schema in Oracle E-Business Suite. It exposes the configuration metadata that drives the Oracle EBS Audit Reporting and Audit Trails functionality implemented by the MSD (Mobile Supply Chain / Discrete Manufacturing) product family. Each row in the view describes a single registered audit SQL statement — an audit report definition consisting of a parameterized SQL statement, its associated application context, its functional grouping, and messaging attributes used when the statement is executed from an audit report or concurrent program.

The view is most commonly encountered by administrators and technical users searching for the term msd_audit_report, which corresponds to the FND lookup type that classifies each audit statement. In EBS 12.1.1 and 12.2.2 the view serves as a foundation for audit reporting and integration: it provides a stable, presentation-oriented read interface that joins statement definitions to human-readable application names and lookup meanings, allowing users and downstream programs to enumerate the audit statements available for a given application or function without directly querying the underlying transactional table.

Underlying Base Objects

The view is defined over three documented objects:

• MSD_AUDIT_SQL_STATEMENTS (referenced as a synonym in the APPS schema) — the driving table holding the statement identifier, statement text fragments (FROM and WHERE clauses), summary messaging configuration, and the enabled flag.
• FND_APPLICATION_VL (view) — the application definition view, supplying the descriptive application name via the APPLICATION_SHORT_NAME join.
• FND_LOOKUP_VALUES_VL (view) — the translated lookup values view, supplying the user-facing meaning of the FUNCTION column where LOOKUP_TYPE equals 'MSD_AUDIT_REPORT'.

The join relationship is a combination of equalities: AD.APPLICATION_CODE = APP.APPLICATION_SHORT_NAME, and AD.FUNCTION = FLV.LOOKUP_CODE with the lookup type restricted to MSD_AUDIT_REPORT. Because two of the three sources are _VL views, the output is automatically language-sensitive, returning application names and lookup meanings in the session's current language.

Key Columns

• STATEMENT_ID, STATEMENT_NAME, STATEMENT_DESCRIPTION — identifier, internal name, and descriptive text for the audit statement.
• FUNCTION and MEANING — the lookup code assigned to the statement and its translated, user-facing label derived from the MSD_AUDIT_REPORT lookup type.
• APPLICATION_CODE and APPLICATION_NAME — the owning application's short name and its descriptive name, useful for grouping statements by product.
• COLUMN1–COLUMN11 and DESCRIPTION1–DESCRIPTION11 — generic parameter and label slots that allow the same statement definition to be reused across different audit scenarios.
• FROM_CLAUSE and WHERE_CLAUSE — the dynamic SQL fragments executed when the audit statement is run.
• ERROR_MESSAGE, SUMMARY_MESSAGE, SUMMARY_MESSAGE_ONLY — messaging configuration that controls what is displayed to the user when the audit produces findings.
• SUMMARY_TOKEN1–3 and SUMMARY_TOKEN1_VALUE–3_VALUE — token substitution metadata used to build the summary message dynamically.
• TRANSLATE and ENABLED — flags controlling translation handling and whether the statement is active for execution.

Common Use Cases and Queries

A frequent requirement is to list all enabled audit statements grouped by application, to confirm which audits are active in a given 12.1.1 or 12.2.2 instance. The following query returns the statement identity, its translated meaning, and its owning application for all enabled statements:

• SELECT statement_id, statement_name, meaning, application_name FROM apps.msd_audit_sql_statements_v WHERE enabled = 'Y' ORDER BY application_name, meaning;

Investigating report definitions for a specific product, or searching by the audit report lookup type the user encountered, can be performed as follows:

• SELECT statement_name, function, meaning, from_clause, where_clause FROM apps.msd_audit_sql_statements_v WHERE application_code = 'MSD';
• SELECT statement_id, statement_name, description1, column1 FROM apps.msd_audit_sql_statements_v WHERE function IN (SELECT lookup_code FROM fnd_lookup_values_vl WHERE lookup_type = 'MSD_AUDIT_REPORT');

Because the view already joins application and lookup descriptions, it is well suited to being used directly as the data source for custom concurrent programs or BI Publisher reports that document the audit inventory. Oracle-proprietary and confidential usage terms apply.