Search Results financial_statement_id




Overview
Explore in AI Chat

Overview

The view RCI_FINANCIAL_LINE_V belongs to the Oracle E-Business Suite product AMW — Internal Controls Manager, a module that is marked obsolete in the ETRM reference set for releases 12.1.1 and 12.2.2. Its documented purpose is to expose the definition of the Organization Financial Line Item dimension, which is the reporting dimension used to align internal control records against the financial statement line items of an organization. Rather than storing transactional data, the view functions as a resolution layer: it maps the internal financial line identifiers used within the controls model to the descriptive names and the parent financial statement context required by downstream reporting, inquiry screens, and integration extracts.

Because the definition is a view rather than a table, no physical storage is allocated and no row-level data is owned by the object itself. The ETRM metadata explicitly records the object as "Not implemented in this database," meaning that in the surveyed environment the underlying dependency chain was not present, and the view could not be created or queried. This status is consistent with the obsolete classification of the AMW product, since Internal Controls Manager functionality was superseded by later governance, risk, and compliance offerings. When the view is present, it behaves as a read-only data source for financial line item selection lists and reporting joins.

Underlying Base Objects

The view is constructed from two principal sources joined together. The first is the base table AMW_FIN_STMNT_ITEMS_B, which supplies the association between a financial statement definition and its member financial items. The second is an inline derived set, aliased AFIV, built from the views RG_REPORT_AXES_V (aliased AXE) and RG_REPORT_AXIS_SETS_V (aliased AXI). That inline set is filtered to axis sets of type 'R' and to axes where DISPLAY_FLAG = 'Y', and it is joined to the axis set on AXIS_SET_ID.

The join predicate links AFSI.FINANCIAL_ITEM_ID to AFIV.FINANCIAL_ITEM_ID, and a correlated subquery restricts the result to the latest statement group for each financial statement by selecting MAX(STATEMENT_GROUP_ID) from AMW_FIN_STMNT_ITEMS_B for the matching FINANCIAL_STATEMENT_ID. The metadata notes that no referenced base objects are separately documented for the view, so the view text above is the authoritative statement of its dependencies. The reliance on RG_REPORT_AXES_V and RG_REPORT_AXIS_SETS_V ties the object to the report axis infrastructure shared across the reporting components of the suite.

Key Columns

  • ID — Exposes AFIV.FINANCIAL_ITEM_ID, derived from the axis SEQUENCE, and serves as the financial line item identifier used to join to control records.
  • VALUE — Exposes AFIV.NAME, the display name of the financial line item presented to users in lists and reports.
  • FINANCIAL_STATEMENT_ID — Exposes the AXIS_SET_ID from the report axis set, identifying the financial statement to which the line item belongs.

The inline derived set also carries DESCRIPTION, DISPLAY_FLAG, and a PARENT_FINANCIAL_ITEM_ID that is hard-coded to NULL, although only the three columns above are projected by the view. The NULL parent value means the view exposes a flat rather than hierarchical line item list.

Common Use Cases and Queries

The view is typically used to populate financial line item selection lists and to enrich control documentation with statement context. A common query resolves line names for a known statement:

  • SELECT id, value FROM rci_financial_line_v WHERE financial_statement_id = :statement_id ORDER BY value;
  • SELECT financial_statement_id, COUNT(*) FROM rci_financial_line_v GROUP BY financial_statement_id; — counts available line items per statement.
  • SELECT l.id, l.value, l.financial_statement_id FROM rci_financial_line_v l, amw_fin_stmnt_items_b b WHERE l.id = b.financial_item_id; — joins back to the base table for extended attributes.

Before relying on the view, confirm that it exists in the target database, since the ETRM metadata records it as unimplemented in the documented environment and the product itself is obsolete.