Results for “fa_rx_rep_columns_vl”
18 results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
The view APPS.FA_RX_REP_COLUMNS_VL is a translated (Multi-Language Support, MLS) view in Oracle E-Business Suite belonging to the OFA – Assets product family. It stores attribute definitions for the Report eXchange (RX) reporting framework, which is the technology underpinning the standard Oracle Assets reports and user-defined Report eXchange reports. Each row in the view defines a report attribute (column) available to a given Report eXchange report definition, describing how the attribute is laid out, formatted, ordered, and displayed on the report output.
The view follows the standard Oracle EBS MLS pattern, combining a base table (FA_RX_REP_COLUMNS_B) containing language-independent data with a translation table (FA_RX_REP_COLUMNS_TL) containing language-specific text. The _VL suffix indicates that the view returns the translatable attribute names joined to the base rows, filtered to the session's language via USERENV('LANG'). The view has a status of VALID and is owned by the APPS schema, which is the standard entry point for reporting and integration access in EBS 12.1.1 and 12.2.2.
Underlying Base Objects
According to the documented ETRM metadata, FA_RX_REP_COLUMNS_VL is defined over two base objects, both exposed in the APPS schema as synonyms:
- FA_RX_REP_COLUMNS_B — the base (non-translated) table holding the language-independent attribute definition columns, including report identifiers, column names, ordering, and display attributes.
- FA_RX_REP_COLUMNS_TL — the translation table holding the language-specific attribute name (
ATTRIBUTE_NAME) keyed by language.
The join is performed on the composite key (REPORT_ID, ATTRIBUTE_SET, COLUMN_NAME), with the translation table additionally filtered on T.LANGUAGE = USERENV('LANG') so that only rows in the current session's language are returned. The ROWID of the base table is exposed as ROW_ID, preserving a handle back to the underlying base row.
Key Columns
The view exposes the following significant columns:
- REPORT_ID — identifies the parent Report eXchange report definition to which the attribute belongs.
- COLUMN_NAME — the internal name of the report attribute/column.
- ATTRIBUTE_NAME — the translated, user-facing label for the attribute, sourced from the translation table.
- ATTRIBUTE_SET — groups related attributes together within a report definition.
- ATTRIBUTE_COUNTER — sequence counter used to distinguish attribute instances.
- ORDERING — controls the display order of the attribute on the report.
- DISPLAY_LENGTH — the display width of the attribute, relevant to the user's search term; controls how many characters are rendered for the column on report output.
- DISPLAY_FORMAT, FORMAT_MASK, PRECISION — define how numeric and formatted values are rendered.
- DISPLAY_STATUS — indicates whether the attribute is shown or hidden.
- CURRENCY_COLUMN, UNITS, MINIMUM_ACCOUNTABLE_UNIT — flag currency and unit-bearing attributes.
- BREAK, BREAK_GROUP_LEVEL — control report break/grouping behaviour.
- CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, LAST_UPDATE_LOGIN — standard EBS auditing columns.
Common Use Cases and Queries
This view is used to interrogate the Report eXchange attribute catalog — for example, to extract column definitions for a specific report, to audit display lengths and formats, or to build custom reporting on top of the RX metadata. A representative query listing the ordered attributes for a report is:
SELECT report_id, attribute_set, column_name, attribute_name, ordering, display_length, display_format, display_status FROM apps.fa_rx_rep_columns_vl WHERE report_id = :report_id ORDER BY attribute_set, ordering;
To inspect only visible columns and their rendered widths:
SELECT column_name, attribute_name, display_length FROM apps.fa_rx_rep_columns_vl WHERE display_status = 'Y' AND report_id = :report_id;
Because the view already filters on the session language, no additional language predicate is normally required. All queries should be executed against the APPS schema or a synonym, respecting standard EBS security and the MO: Security Profile / responsibility access rules. In both 12.1.1 and 12.2.2 the definition and behaviour are consistent, as the object is documented as VALID in the ETRM 12.2.2 repository.
-
View: FA_RX_REP_COLUMNS_VL 12.1.1
Stores attribute definitions for Report eXchange report attributes (translated MLS view)
APPS.FA_RX_REP_COLUMNS_VL·↳ FA_RX_REP_COLUMNS_B·↳ FA_RX_REP_COLUMNS_TL·Explore OFA module →
-
View: FA_RX_REP_COLUMNS_VL 12.2.2
Stores attribute definitions for Report eXchange report attributes (translated MLS view)
APPS.FA_RX_REP_COLUMNS_VL·↳ FA_RX_REP_COLUMNS_B·↳ FA_RX_REP_COLUMNS_TL·Explore OFA module →
-
12.1.1 FND Design Data 12.1.1
-
12.2.2 FND Design Data 12.2.2
-
eTRM - OFA Tables and Views 12.1.1
-
eTRM - OFA Tables and Views 12.2.2
-
12.2.2 DBA Data 12.2.2
-
12.1.1 DBA Data 12.1.1
-
eTRM - OFA Tables and Views 12.1.1
-
eTRM - OFA Tables and Views 12.2.2