Search Results select_program_name

Overview

FA_RX_REPORTS is a table in the OFA (Oracle Assets) product schema within Oracle E-Business Suite 12.1.1 and 12.2.2. It stores Report eXchange report definitions, serving as the metadata registry for reports that can be registered, parameterized, and executed against the Oracle Assets data model. Each row corresponds to a single Report eXchange definition, tying a report to a concurrent program, an application, and a set of configurable parameters.

From a Data Vault modeling perspective, the ETRM FK structure classifies this table as satellite-leaning. This is a modeling suggestion: FA_RX_REPORTS carries descriptive attributes dependent on a report identifier rather than acting as a pure hub of business keys, though the presence of a partial unique key on (REPORT_ID, ZD_EDITION_NAME) reflects the edition-tracking pattern used in newer 12.2.2 schema definitions. The table is the parent of both attribute-set and parameter child tables, making it a central anchor for report configuration.

Key Information Stored

The table contains 17 columns. The single-column primary key FA_RX_REPORTS_PK is REPORT_ID, which is a system-generated surrogate identifier for each report definition. A unique index, FA_RX_REPORTS_U1, covers (REPORT_ID, ZD_EDITION_NAME), indicating the edition-qualified business-key candidate used for edition-aware access.

• REPORT_ID — surrogate primary key identifying the Report eXchange definition.
• APPLICATION_ID — owning application, used both as a FK to FND_APPLICATION and as part of the composite FK to FND_CONCURRENT_PROGRAMS.
• CONCURRENT_PROGRAM_ID and CONCURRENT_PROGRAM_NAME — the concurrent program that executes the report and its user-facing name.
• INTERFACE_TABLE — the interface or source table targeted by the report definition.
• CONCURRENT_PROGRAM_FLAG — indicator of whether the report runs as a concurrent program.
• SELECT_PROGRAM_NAME — the selection program associated with the report.
• RESPONSIBILITY_ID — the responsibility under which the report is intended to be run.
• VERSION_NUMBER — version stamp for the report definition.
• WHERE_CLAUSE_API and PURGE_API — API entry points supplying the filtering predicate and purge logic.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, CREATED_BY, CREATION_DATE — standard WHO audit columns.
• ZD_EDITION_NAME — edition qualifier, part of the unique index FA_RX_REPORTS_U1.

Common Use Cases and Queries

Typical usage centers on report discovery, troubleshooting, and configuration reporting. Administrators query the table to determine which concurrent program backs a given Report eXchange report, or which reports run a specific API for filtering and purging.

• Listing reports for a concurrent program:

  SELECT r.report_id, r.concurrent_program_name, r.select_program_name
  FROM   fa.fa_rx_reports r
  WHERE  r.application_id = :app_id
  AND    r.concurrent_program_id = :prog_id;

• Identifying reports with a custom purge or where-clause API:

  SELECT report_id, where_clause_api, purge_api
  FROM   fa.fa_rx_reports
  WHERE  purge_api IS NOT NULL;

• Reporting parameter and attribute-set coverage by joining to the child tables on REPORT_ID.
• Joining to FND_APPLICATION to resolve the application short name for user-facing report listings.

Related Objects

The table sits at the center of the Report eXchange configuration model and references or is referenced by the following documented objects:

• FA_RX_ATTRSETS_B — child table; joins on FA_RX_ATTRSETS_B.REPORT_ID = FA_RX_REPORTS.REPORT_ID, holding attribute-set definitions for the report.
• FA_RX_REP_PARAMETERS — child table; joins on FA_RX_REP_PARAMETERS.REPORT_ID = FA_RX_REPORTS.REPORT_ID, holding the configurable report parameters.
• FND_APPLICATION — referenced via APPLICATION_ID; supplies application identity and short name.
• FND_CONCURRENT_PROGRAMS — referenced via the composite (APPLICATION_ID, CONCURRENT_PROGRAM_ID) FK; supplies the executable program definition.