Search Results segment3_high

Overview

AMW_FIN_ITEMS_ACCOUNT_RANGE_V is a view in the Oracle E-Business Suite Internal Controls Manager (AMW) product. Its documented description is "The Account Range for a Row in FSG." The view is part of the AMW module, which is flagged as obsolete in Oracle EBS 12.1.1 and 12.2.2, meaning it is no longer actively supported or implemented in current installations. Despite its obsolescence, the view remains relevant for historical analysis, upgrade remediation, and understanding legacy integration patterns between Internal Controls Manager and the Financial Statement Generator (FSG).

The view exposes the account range associated with individual rows in an FSG report. FSG is the standard Oracle General Ledger reporting tool that allows users to define row sets, column sets, and content sets. Each row in a report can specify an account range defined by low and high values across up to 30 accounting segments. AMW_FIN_ITEMS_ACCOUNT_RANGE_V surfaces that row-level account range definition, along with the associated axis set identifier, sequence, and ledger identifier, providing a consolidated picture of how FSG rows map to account ranges.

Underlying Base Objects

The documented view text joins three sources:

• RG_REPORT_AXIS_CONTENTS (aliased CTS) — stores the account range contents for each row of an FSG report, including low/high values and types for each segment.
• RG_REPORT_AXES_V (aliased AXE) — provides the report axis definitions, filtered by DISPLAY_FLAG = 'Y'.
• RG_REPORT_AXIS_SETS_V (aliased AXI) — supplies the axis set header, filtered by AXIS_SET_TYPE = 'R' (row axis).

The join condition links AXE.AXIS_SET_ID = AXI.AXIS_SET_ID, AXE.AXIS_SET_ID = CTS.AXIS_SET_ID, and AXE.SEQUENCE = CTS.AXIS_SEQ. This structure restricts the result to row-type axis sets and only those axes marked for display, yielding the account range values for each displayed row. The view references no additional documented base objects beyond these three FSG source objects, so all columns are derived from them.

Key Columns

The view exposes the following categories of columns:

• AXIS_SET_ID — identifier of the axis set, joining the row and content records.
• SEQUENCE — the row sequence within the axis set.
• LEDGER_ID — the ledger to which the account range applies.
• SEGMENT1_LOW through SEGMENT30_LOW — the low value of the account range for each of up to 30 accounting segments.
• SEGMENT1_HIGH through SEGMENT30_HIGH — the high value of the range for each segment.
• SEGMENT1_TYPE through SEGMENT30_TYPE — the range type or operator applied to each segment (for example, a range, a single value, or a wildcard).

The documented column listing also mentions FINANCIAL_STATEMENT_ID, which associates the range with a financial statement definition. This column, together with AXIS_SET_ID and SEQUENCE, allows users to trace an account range back to the specific FSG report and row. The per-segment LOW/HIGH/TYPE triplet is the core payload, enabling control testing, reconciliation, and reporting over the exact accounts that feed each FSG row.

Common Use Cases and Queries

Because the view is obsolete and not implemented in current databases, its primary practical use is in legacy environments, migration projects, or documentation of historical AMW configurations. Typical scenarios include auditing which account ranges were assigned to FSG rows, comparing row-level account ranges across ledgers, and extracting segment range definitions for control testing.

A representative query to inspect row-level account ranges is:

• SELECT LEDGER_ID, AXIS_SET_ID, SEQUENCE, SEGMENT1_LOW, SEGMENT1_HIGH, SEGMENT1_TYPE FROM AMW_FIN_ITEMS_ACCOUNT_RANGE_V WHERE LEDGER_ID = :ledger_id ORDER BY AXIS_SET_ID, SEQUENCE;
• SELECT AXIS_SET_ID, SEQUENCE, FINANCIAL_STATEMENT_ID FROM AMW_FIN_ITEMS_ACCOUNT_RANGE_V WHERE SEGMENT1_LOW = :account_low AND SEGMENT1_HIGH = :account_high;
• SELECT COUNT(*) FROM AMW_FIN_ITEMS_ACCOUNT_RANGE_V WHERE SEGMENT1_TYPE = :range_type;

Given the obsolete status, these queries are best used for read-only historical analysis rather than as part of active production reporting. Analysts upgrading from earlier releases should verify whether equivalent functionality now resides in the current GL FSG tables or AMW successor structures.