Search Results user_program_name




Overview
Explore in AI Chat

Overview

APPS.FA_RX_CR_REPORTS_V is a reporting view in the Oracle E-Business Suite (EBS) Fixed Assets module, available in releases 12.1.1 and 12.2.2. It consolidates configuration data that links Fixed Assets report definitions to Oracle Application Object Library (FND) concurrent program and request group metadata. The view is designed to expose, in a single queryable structure, the association between a report registered in FA_RX_REPORTS and the concurrent program, application, and request group through which that report is submitted or purged.

Its principal purpose is to support purge and interface processing logic for Fixed Assets report executions, where the system must determine which concurrent program and request group correspond to a given report definition. Because the view exposes USER_CONCURRENT_PROGRAM_NAME (aliased USER_PROGRAM_NAME), it is frequently consulted in queries that resolve user-facing program names — the term a user searched for — back to the underlying report and responsibility configuration.

Underlying Base Objects

The view is defined over a UNION of two nearly identical SELECT statements, each joining the following documented base objects:

The two UNION branches differ in their join paths: the first matches RX.APPLICATION_ID to RGU.APPLICATION_ID, while the second matches RX.APPLICATION_ID to RGU.UNIT_APPLICATION_ID with the filter RGU.REQUEST_UNIT_TYPE = 'A' (application-type request units). This design captures report-to-program mappings that may reside under either an application-level or a unit-level request group association.

Key Columns

  • ROW_ID — the ROWID of the FA_RX_REPORTS row, preserved for update/purge targeting.
  • REPORT_ID — primary identifier of the Fixed Assets report definition.
  • APPLICATION_ID / APPLICATION_NAME — the owning application and its display name.
  • RESPONSIBILITY_ID / RESPONSIBILITY_NAME — responsibility context; RESPONSIBILITY_NAME is returned as TO_CHAR(NULL) in the documented text.
  • REQUEST_GROUP_ID — the request group through which the report is made available.
  • CONCURRENT_PROGRAM_FLAG — indicates whether the entry represents a concurrent program.
  • CONCURRENT_PROGRAM_ID / CONCURRENT_PROGRAM_NAME — the concurrent program and its internal name.
  • USER_PROGRAM_NAME — the user-facing concurrent program name (USER_CONCURRENT_PROGRAM_NAME), the column most relevant to searches for "user_program_name".
  • INTERFACE_TABLE, WHERE_CLAUSE_API, PURGE_API — the table and PL/SQL APIs used for report interface and purge operations.
  • Audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATED_BY, CREATION_DATE, LAST_UPDATE_LOGIN.

Common Use Cases and Queries

Typical scenarios include resolving a user-visible program name to its report definition, identifying the request group for a report, and driving purge routines. A representative query is:

  • SELECT report_id, application_name, concurrent_program_name, user_program_name, request_group_id FROM apps.fa_rx_cr_reports_v WHERE user_program_name LIKE 'Fixed Assets%';
  • SELECT report_id, interface_table, purge_api FROM apps.fa_rx_cr_reports_v WHERE concurrent_program_id = :program_id;

Because the view exposes both internal and user-facing program names alongside report and purge metadata, it is a convenient join source when building custom Fixed Assets purge utilities or diagnostic reports without querying each FND object separately.