Search Results fa_rx_reports_v




Overview
Explore in AI Chat

Overview

FA_RX_REPORTS_V is a view owned by the APPS schema in Oracle E-Business Suite, belonging to the OFA (Oracle Assets) product. The ETRM metadata designates its status as VALID and carries a "Retrofitted" designation, indicating the object was carried forward across release boundaries and remains supported in both 12.1.1 and 12.2.2. The view does not store data of its own; instead it provides a consolidated, presentation-ready projection of the FA_RX_REPORTS configuration table, joining it to FND foundation views so that report-registration metadata is exposed in human-readable form.

Functionally, FA_RX_REPORTS_V describes the linkage between Oracle Assets reports and their execution context. Each row identifies a report registration and resolves that registration either to a concurrent program or to a responsibility, supplying the corresponding application name, program name, and user-facing program name. This makes the view the logical access point for diagnostics, personalization, and internal reporting on how Oracle Assets reports are wired to the concurrent manager and to responsibility-based navigation.

Underlying Base Objects

The view is defined over a UNION ALL of two branches, both anchored on FA_RX_REPORTS (exposed as a synonym). The first branch joins FND_CONCURRENT_PROGRAMS_VL on APPLICATION_ID and CONCURRENT_PROGRAM_ID and is filtered by NVL(RX.CONCURRENT_PROGRAM_FLAG,'N') = 'Y', producing rows for report registrations that are driven by a concurrent program. The second branch joins FND_RESPONSIBILITY_VL on APPLICATION_ID and RESPONSIBILITY_ID and is filtered by NVL(RX.CONCURRENT_PROGRAM_FLAG,'N') = 'N', producing rows for registrations that are tied to a responsibility rather than to a concurrent program. FND_APPLICATION_ALL_VIEW is joined in both branches to resolve APPLICATION_ID to APPLICATION_NAME.

The documented referenced objects are FA_RX_REPORTS (SYNONYM), FND_APPLICATION_ALL_VIEW (VIEW), FND_CONCURRENT_PROGRAMS_VL (VIEW), FND_GLOBAL (PACKAGE), and FND_RESPONSIBILITY_VL (VIEW). FND_GLOBAL is referenced for session context resolution. Because FND_CONCURRENT_PROGRAMS_VL and FND_RESPONSIBILITY_VL are themselves multilingual views over the corresponding _TL tables, FA_RX_REPORTS_V surfaces application-context names rather than internal identifiers.

Key Columns

  • ROW_ID — the ROWID of the underlying FA_RX_REPORTS row; rows appear twice, once per UNION ALL branch, when both program and responsibility configurations exist.
  • REPORT_ID — the primary identifier of the report registration.
  • APPLICATION_ID / APPLICATION_NAME — the owning application of the registration, resolved through FND_APPLICATION_ALL_VIEW.
  • RESPONSIBILITY_ID / RESPONSIBILITY_NAME — populated only in the responsibility branch; set to NULL in the concurrent-program branch.
  • CONCURRENT_PROGRAM_FLAG — the discriminator governing which branch a row originates from; NVL to 'N' is applied in both filters.
  • CONCURRENT_PROGRAM_ID / CONCURRENT_PROGRAM_NAME / USER_PROGRAM_NAME — concurrent program identity and its user-facing label; NULL in the responsibility branch.
  • REQUEST_GROUP_ID — exposed as TO_NUMBER(NULL) in the program branch and not selected in the responsibility branch, reflecting its legacy placement.
  • INTERFACE_TABLE, WHERE_CLAUSE_API, PURGE_API — the interface table and PL/SQL APIs used to build the where clause and to purge the report's staging data.
  • Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE, LAST_UPDATE_LOGIN, inherited directly from FA_RX_REPORTS.

Common Use Cases and Queries

A frequent scenario is auditing which Oracle Assets report registrations are bound to concurrent programs versus responsibilities. Because the union collapses both configurations into one row set, a simple filter on CONCURRENT_PROGRAM_FLAG separates them:

  • List all program-driven registrations: SELECT report_id, application_name, concurrent_program_name, user_program_name, interface_table FROM fa_rx_reports_v WHERE concurrent_program_flag = 'Y';
  • List responsibility-bound registrations: SELECT report_id, application_name, responsibility_name, concurrent_program_name FROM fa_rx_reports_v WHERE concurrent_program_flag = 'N';
  • Locate registrations for a given program: SELECT report_id, application_name, user_program_name, where_clause_api FROM fa_rx_reports_v WHERE concurrent_program_name = :program_name;
  • Identify rows lacking a custom where clause or purge routine: SELECT report_id, application_name, where_clause_api, purge_api FROM fa_rx_reports_v WHERE where_clause_api IS NULL OR purge_api IS NULL;
  • Enumerate distinct reports per application: SELECT application_name, COUNT(DISTINCT report_id) FROM fa_rx_reports_v GROUP BY application_name;

Because the view joins multilingual foundation views, it honors the session language for APPLICATION_NAME, CONCURRENT_PROGRAM_NAME, and RESPONSIBILITY_NAME, making it suitable for user-facing diagnostics as well as for internal troubleshooting of Oracle Assets report registration.