Results for “fv_opac_audit”
6 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The FV_OPAC_AUDIT view is a reporting object within the Oracle E-Business Suite Federal Financials (FV) module. It exposes audit-related run history for the OPAC (Offset/Payment Application Control or equivalent federal processing) batch process, surfacing batch identifiers, run dates, ledger context, and organizational context. In Oracle EBS 12.1.1 and 12.2.2, the view functions as a Multi-Org secured (organization-secured) presentation layer over the underlying audit table FV_OPAC_AUDIT_ALL, filtering rows by the organization context established in the user's session.
The view is primarily consumed for auditing and troubleshooting batch processing runs: identifying when a batch was executed, which set of books and organization it belonged to, and when it was last run. It is a read-only reporting construct rather than a data entry object, and the documented metadata confirms it is not implemented in every database, reflecting that its presence depends on whether the OPAC audit feature has been deployed in a given environment.
Underlying Base Objects
The documented view text defines FV_OPAC_AUDIT entirely over a single base table: FV_OPAC_AUDIT_ALL, the organization-striped ("_ALL") table that stores audit rows across all organizations. The view contains no joins and no referenced objects beyond that table.
The defining SELECT projects five columns — BATCH_NUMBER, RUN_DATE, SET_OF_BOOKS_ID, ORG_ID, and LAST_RUN_DATE — from FV_OPAC_AUDIT_ALL and applies a WHERE predicate that restricts returned rows to the current organization. The predicate compares NVL(ORG_ID, ...) against the organization identifier derived from USERENV('CLIENT_INFO'), defaulting unmatched or null contexts to -99. This is the standard Multi-Org view pattern used throughout Oracle EBS: the base table holds all organizations, and the view enforces row-level security so that a user session sees only its own organization's records.
Because the view is defined with the organization-security predicate directly in its text, it behaves as an "O" (organization) secured view for Multi-Org purposes.
Key Columns
- BATCH_NUMBER — Identifier for the OPAC processing batch. Together with the run date, it uniquely identifies a processing run for auditing purposes.
- RUN_DATE — The date and time on which the batch was executed. This is the primary column sought by users searching on "run_date," and it anchors most audit and troubleshooting queries.
- SET_OF_BOOKS_ID — Foreign key to the ledger (set of books) associated with the batch run, enabling reporting by accounting ledger.
- ORG_ID — The operating unit/organization identifier. This column governs the Multi-Org security filter applied by the view's
WHEREclause. - LAST_RUN_DATE — The most recent execution timestamp recorded for the batch, useful for distinguishing the latest run from prior runs and for detecting stale or overdue processing.
Common Use Cases and Queries
The view is most often queried to reconstruct the execution history of OPAC batches, to confirm that a batch ran, and to reconcile run dates against ledger and organization context. Typical scenarios include federal period-close audit trails, diagnosing missing or duplicated batch runs, and reporting the last successful execution per ledger or organization.
A basic query retrieving recent runs, ordered by the run date, is:
SELECT batch_number, run_date, set_of_books_id, org_id, last_run_date FROM fv_opac_audit ORDER BY run_date DESC;
To restrict to a specific batch and inspect its most recent execution:
SELECT batch_number, run_date, last_run_date FROM fv_opac_audit WHERE batch_number = :batch_number;
To identify the latest run per ledger:
SELECT set_of_books_id, MAX(run_date) FROM fv_opac_audit GROUP BY set_of_books_id;
Because the view already applies organization security, additional filtering on ORG_ID is generally unnecessary for the logged-in session; users requiring cross-organization visibility must query the base table FV_OPAC_AUDIT_ALL directly, subject to appropriate privileges.
-
View: FV_OPAC_AUDIT 12.2.2
Not implemented in this database·Explore FV module →
-
View: FV_OPAC_AUDIT 12.1.1
Not implemented in this database·Explore FV module →
-
12.2.2 FND Design Data 12.2.2
-
12.1.1 FND Design Data 12.1.1
-
PACKAGE BODY: APPS.AD_MORG 12.1.1
-
PACKAGE BODY: APPS.AD_MORG 12.2.2