Results for “ax_balances_srs_v”

AI-generated from documented ETRM metadata — verify critical details on the linked pages.

Overview

The AX_BALANCES_SRS_V view belongs to the AX - Global Accounting Engine product within Oracle E-Business Suite (12.1.1 / 12.2.2). It is a reporting-oriented database view designed to improve the performance of balance-related queries executed by reports. Rather than forcing report processes to join the transactional AX_BALANCES table against vendor, customer, site, and period-status tables at runtime, the view pre-defines those joins so that standard reporting tools can retrieve consolidated balance information through a single, simpler object.

The view exposes accounting balances enriched with third-party (supplier and customer) identification details and general ledger period attributes. Its purpose is to support subledger and reporting extracts — particularly SRS (Oracle Reports) style outputs — that need balance amounts broken down by third party, site, account combination, and period. Because the view is explicitly documented as existing "to improve performance of queries of balances by reports," it is not intended as an operational interface but as a read-only reporting convenience layer.

Underlying Base Objects

The ETRM metadata states that the referenced base objects are not documented, and the excerpt notes that the view is "Not implemented in this database." The view text, however, reveals its constituent tables through the SQL definition. The view is a UNION of at least two query branches combining:

• AX_BALANCES (aliased AXB) — the core source of balance amounts, account segments, code combination, period, and third-party/sub identifiers.
• GL_PERIOD_STATUSES (aliased GPS) — supplies period name, period year, period number, and effective period number, filtered by APPLICATION_ID and ADJUSTMENT_PERIOD_FLAG = 'N'.
• PO_VENDOR_SITES_ALL (PVS) and PO_VENDORS (PV) — provide supplier third-party identifiers and site-level sub identifiers for supplier balances.
• Receivables customer and site-usage tables (aliased RC, RSU, RA in the second branch) — provide customer third-party identifiers and concatenated address-based site names for customer balances.

Joins are driven by matching APPLICATION_ID, SET_OF_BOOKS_ID, PERIOD_NAME, THIRD_PARTY_ID = VENDOR_ID, and SUB_ID = VENDOR_SITE_ID. The two UNION branches are distinguished by the literal APPLICATION_ID values 200 (suppliers) and 222 (customers).

Key Columns

• APPLICATION_ID — literal discriminator: 200 for supplier balances, 222 for customer balances.
• SET_OF_BOOKS_ID — set of books (ledger) identifier covering the balance.
• CODE_COMBINATION_ID — accounting flexfield combination identifying the account.
• PERIOD_NAME, PERIOD_YEAR, PERIOD_NUM — period attributes sourced from GL_PERIOD_STATUSES.
• EFFECTIVE_PERIOD_NUM — the effective accounting period sequence number, the column most relevant to period-sequenced reporting and to the search term "effective_period_num."
• THIRD_PARTY_ID, THIRD_PARTY_NAME, THIRD_PARTY_NUMBER — supplier or customer identity.
• SUB_ID, SUB_NAME — supplier site or customer site-usage identity.
• BALANCE_SEGMENT, ACCOUNT_SEGMENT — segment values classifying the balance.
• PERIOD_NET_DR, PERIOD_NET_CR — period-to-date debit and credit movement.
• END_BALANCE_DR, END_BALANCE_CR — ending debit and credit balances for the period.

Common Use Cases and Queries

Typical usage centers on period-banded balance reporting. A report can select all balances for a vendor site within a set of books and period, ordering by EFFECTIVE_PERIOD_NUM to produce a chronological balance trend.

• Supplier balance listing for a ledger and period.
• Customer balance listing via the 222 branch.
• Period-sequenced trend reports using EFFECTIVE_PERIOD_NUM.
• Debit/credit movement versus ending balance analysis.

Example query retrieving supplier balances ordered by effective period:

SELECT set_of_books_id, period_name, effective_period_num, third_party_number, third_party_name, sub_name, end_balance_dr, end_balance_cr FROM ax_balances_srs_v WHERE application_id = 200 AND set_of_books_id = :sob AND period_name = :period ORDER BY effective_period_num, third_party_number;

Example customer balance query:

SELECT set_of_books_id, period_name, effective_period_num, third_party_name, sub_name, period_net_dr, period_net_cr FROM ax_balances_srs_v WHERE application_id = 222 AND set_of_books_id = :sob ORDER BY effective_period_num;

Because the view is documented as not implemented in the reference database, availability should be verified in the target instance before use; where absent, the equivalent joins against AX_BALANCES, GL_PERIOD_STATUSES, and the supplier/customer tables must be constructed manually.