Search Results fa_rx_dynamic_columns_pk

Overview

FA_RX_DYNAMIC_COLUMNS is a table in the FA (Assets) schema of Oracle E-Business Suite, owned by the OFA – Assets product. It stores configuration metadata that defines the dynamic columns used by RX reports in Oracle Assets. RX reports are the XML Publisher–based reporting framework that replaced several legacy Oracle Assets reports, and they rely on a flexible column model so that the set of displayed columns can be tailored to the reporting request rather than being hard-coded. This table holds the per-request definitions of those columns.

Under the heuristic Data Vault classification derived from its foreign key structure, the object is identified as standalone. This indicates that FA_RX_DYNAMIC_COLUMNS does not participate in the hub-link-satellite pattern through enforced referential relationships to other FA tables within the documented schema; it functions as an independent configuration/reference table whose rows are scoped by request rather than by an enterprise business key. Modeling efforts should treat it as a descriptive configuration store rather than a core business entity.

Key Information Stored

The table contains 13 documented columns. Its primary key, FA_RX_DYNAMIC_COLUMNS_PK, is a composite surrogate key defined on REQUEST_ID and ATTRIBUTE_NAME; there are no separately documented unique business-key indexes beyond this primary key. The most significant columns are:

• REQUEST_ID — Identifies the RX report submission (concurrent request) to which the dynamic column definitions belong. This column forms part of the composite primary key and bounds each row set to a specific report execution.
• ATTRIBUTE_NAME — The logical attribute name of the column, forming the second component of the primary key.
• COLUMN_NAME — The physical or display column name associated with the attribute, used by the report layout to render the value.
• ORDERING — The sequence position that determines the left-to-right display order of the columns in the report output.
• BREAK — Controls whether a page or section break is applied in relation to the column, supporting grouped RX report layouts.
• DISPLAY_LENGTH — The width allocated to the column in the rendered report.
• DISPLAY_FORMAT — The formatting mask applied to the column (for example, numeric or date formatting).
• DISPLAY_STATUS — Indicates whether the column is displayed or suppressed for the given request.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY, LAST_UPDATE_LOGIN — The standard Oracle EBS audit columns capturing who created and last modified each configuration row and when.

Common Use Cases and Queries

Typical uses center on diagnosing and reproducing RX report layouts. Support and functional analysts query this table to determine which columns were selected for a particular report run and in what order. A representative query retrieves the active column layout for a request:

• SELECT request_id, attribute_name, column_name, ordering, display_length, display_format, display_status FROM fa.fa_rx_dynamic_columns WHERE request_id = :request_id ORDER BY ordering;

Because the primary key is (REQUEST_ID, ATTRIBUTE_NAME), lookups by request alone should be ordered by ORDERING to reflect the actual layout. Reporting use cases include comparing layouts across requests to verify configuration changes, auditing suppressed columns via DISPLAY_STATUS, and validating that expected attribute names are present before a report is executed. The audit columns support change-tracking queries filtered by LAST_UPDATED_BY or LAST_UPDATE_DATE.

Related Objects

FA_RX_DYNAMIC_COLUMNS is related to the RX reporting framework in Oracle Assets. The most significant related objects include:

• FND_CONCURRENT_REQUESTS — join on REQUEST_ID to resolve the concurrent request that produced the layout.
• FA_RX_REPORTS / RX report definition objects — provide the report templates that consume the dynamic column definitions.
• FA_RX_* RX report parameter and column objects — sibling configurations that collectively drive an RX report run.
• FA_BOOKS_CONTROLS and other FA reporting tables — supply the underlying asset data selected by the report.
• FND_LOOKUPS — may resolve coded values used in DISPLAY_FORMAT or DISPLAY_STATUS.

As a standalone table, it is referenced primarily through the FA RX report engine rather than through declared foreign keys to other FA entities.