Search Results debit_beginning_balance

Overview

AXBV_ACCOUNT_BALANCES is a reporting view in the Global Accounting Engine (AX) product of Oracle E-Business Suite, available in releases 12.1.1 and 12.2.2. It exposes summarized and period-level account balances for third-party accounting, aggregating debit and credit activity by application, ledger (set of books), trading partner, account, and accounting period. The view consolidates raw balance records from the AX_BALANCES table with period-status and account-qualifier information drawn from General Ledger, producing a denormalized result set suited to statement generation, reconciliation, and downstream integration.

The view is not implemented as a physical database object in every environment, as noted in the source metadata ("Not implemented in this database"). Where present, it functions as a read-only query surface over the Global Accounting Engine balance repository. Its most relevant practical application is the generation of third-party account statements — including balances communicated to trading partners or regulatory recipients — which aligns with user searches such as "batx account statement." The view is a common dependency for report definitions and extract programs that require a period-ordered, balancing-oriented representation of account activity.

Underlying Base Objects

The view is defined over three documented base objects:

• AX_BALANCES (A) — the primary source of balance, transaction, and historic balance amounts.
• GL_PERIOD_STATUSES (PS) — joined on PERIOD_NAME, APPLICATION_ID, and SET_OF_BOOKS_ID to attach the effective period number and period-close status.
• GL_CODE_COMBINATIONS (GCC) — joined on CODE_COMBINATION_ID to supply code combination context and support the key flexfield substitution token.

Joins are performed on all three key dimensions (period, application, and ledger) for the period status, and on code combination for the account. The view is declared WITH READ ONLY, preventing DML through the view. The `_KF:SQLGL:GL#:GCC` token in the SELECT list is a key-flexfield substitution directive that resolves the account segment structure at runtime for reporting consumers.

Key Columns

• APPLICATION_ID, SET_OF_BOOKS_ID — identify the source application and ledger.
• THIRD_PARTY_ID / TRADING_PARTNER_ID, TRADING_PARTNER_SITE_ID — the trading partner and site for which balances are reported.
• CODE_COMBINATION_ID / ACCOUNT_ID — the accounting flexfield combination.
• PERIOD_NAME — the accounting period, paired with PERIOD_NAME_SORT_NUMBER (mapped from PS.EFFECTIVE_PERIOD_NUM) for correct chronological ordering.
• ACCOUNT_SEGMENT, BALANCING_SEGMENT — derived account and balancing segment values used for statement grouping.
• BEGINNING_BALANCE, DEBIT_BEGINNING_BALANCE, CREDIT_BEGINNING_BALANCE — opening position for the period.
• TRANSACTION, DEBIT_TRANSACTION, CREDIT_TRANSACTION — net and side-specific period activity.
• ENDING_BALANCE, DEBIT_ENDING_BALANCE, CREDIT_ENDING_BALANCE — closing position.
• HISTORIC_BALANCE — the retained historic balance amount carried from AX_BALANCES.
• CREATED_BY, CREATION_DATE, LAST_UPDATED_BY, LAST_UPDATE_DATE — standard audit columns.

Common Use Cases and Queries

Typical uses include third-party statement generation, period-over-period balance analysis, and reconciliation of Global Accounting Engine balances to General Ledger. A representative query retrieving period-ending balances for a specific ledger and partner:

• SELECT PERIOD_NAME, ACCOUNT_SEGMENT, BALANCING_SEGMENT, DEBIT_ENDING_BALANCE, CREDIT_ENDING_BALANCE, ENDING_BALANCE FROM AXBV_ACCOUNT_BALANCES WHERE SET_OF_BOOKS_ID = :ledger AND THIRD_PARTY_ID = :partner AND PERIOD_NAME = :period ORDER BY PERIOD_NAME_SORT_NUMBER, ACCOUNT_SEGMENT;
• SELECT PERIOD_NAME, SUM(DEBIT_TRANSACTION), SUM(CREDIT_TRANSACTION) FROM AXBV_ACCOUNT_BALANCES WHERE SET_OF_BOOKS_ID = :ledger GROUP BY PERIOD_NAME ORDER BY PERIOD_NAME_SORT_NUMBER;
• SELECT ACCOUNT_SEGMENT, BEGINNING_BALANCE, TRANSACTION, ENDING_BALANCE FROM AXBV_ACCOUNT_BALANCES WHERE SET_OF_BOOKS_ID = :ledger AND APPLICATION_ID = :appl;

Because the view is read-only and aggregating, it is appropriate for ad hoc reporting and statement extracts rather than for transactional processing.