Search Results amw_statements_v




Overview

AMW_STATEMENTS_V is a database view historically shipped with the Oracle Internal Controls Manager (AMW) product, now classified as obsolete. Its documented purpose is to expose all Row Set definitions used by the Oracle Financial Statement Generator (FSG), so that AMW's compliance and certification functionality could reference and evaluate FSG row set metadata alongside financial statement content. In the Oracle EBS 12.1.1 and 12.2.2 file systems, this object is part of the archived AMW schema rather than an active runtime component.

The view is defined as a filtered projection of the FSG view RG_REPORT_AXIS_SETS_V. Because internal controls management relied on identifying which FSG "axis sets" (row sets) were relevant to a given financial statement, the view restricts its output to rows where AXIS_SET_TYPE equals 'R', isolating row set definitions from the broader set of axis set records (such as column sets). This makes AMW_STATEMENTS_V a convenience abstraction for downstream reporting or integration that needs only row-oriented FSG definitions.

Underlying Base Objects

The single documented base object is RG_REPORT_AXIS_SETS_V, a Financial Statement Generator view that consolidates axis set definitions sourced from the underlying FSG schema tables (RG_REPORT_AXIS_SETS and related segment, period, and column definitions). AMW_STATEMENTS_V does not introduce its own storage; it selects a predefined column list from that source view and applies the predicate AXIS_SET_TYPE = 'R'.

No additional base tables are documented against AMW_STATEMENTS_V, and its implementation status is recorded as "Not implemented in this database." Consequently, the view carries no rows and no runtime dependency in a 12.2.2 environment where AMW has been decommissioned. Any attempt to query it will either return no data or fail, depending on whether the inherited RG_REPORT_AXIS_SETS_V object remains valid in the instance.

Key Columns

The projected column list mirrors the FSG axis set attributes, with the leading column labelled AXIS_SET_ID in the view text and documented as FINANCIAL_STATEMENT_ID in the column listing:

  • AXIS_SET_ID / FINANCIAL_STATEMENT_ID — the primary identifier for the row set definition; the metadata reflects both names, an inconsistency typical of re-used FSG views adapted for AMW.
  • AXIS_SET_TYPE — discriminates the set category; always 'R' in this view, denoting a row set.
  • NAME, DESCRIPTION, COLUMN_SET_HEADER — descriptive attributes of the row set, including the header used when combined with a column set.
  • PERIOD_SET_NAME — the accounting period set associated with the row set's reporting context.
  • DISPLAY_IN_LIST_FLAG — controls whether the set appears in FSG selection lists.
  • SEGMENT_NAME, ID_FLEX_CODE, STRUCTURE_ID — identify the accounting flexfield segment and structure targeted by the row set.
  • CONTEXT and ATTRIBUTE1 through ATTRIBUTE15 — descriptive flexfield context and segment values carried through from the FSG definition.
  • Audit columnsCREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE, and LAST_UPDATE_LOGIN record standard EBS who-column audit information.

Common Use Cases and Queries

In legacy AMW deployments, the view supported identification of FSG row sets for control testing and certification evidence. A typical query joins it to related FSG views to assemble a complete statement definition:

  • Listing all row sets visible in FSG pick lists: SELECT name, description, period_set_name FROM amw_statements_v WHERE display_in_list_flag = 'Y';
  • Finding row sets for a specific accounting flexfield: SELECT axis_set_id, name FROM amw_statements_v WHERE id_flex_code = 'GL#' AND structure_id = :structure_id;
  • Auditing recently modified definitions: SELECT name, last_updated_by, last_update_date FROM amw_statements_v ORDER BY last_update_date DESC;

Because the object is obsolete and not implemented, these queries are only meaningful for historical migration analysis. For current 12.2.2 reporting, the equivalent and supported approach is to query RG_REPORT_AXIS_SETS_V directly with the same AXIS_SET_TYPE = 'R' filter.