Results for “account_segment”

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

Overview

AX_BALANCES is a subledger accounting balance table owned by the AX schema within the Global Accounting Engine (AX) product of Oracle E-Business Suite. It stores summarized balance information for subledger control accounts, capturing period-to-date and end-of-period debit and credit activity by ledger, application, accounting flexfield combination, period, and third party. In Oracle EBS 12.1.1 and 12.2.2, this table serves as the persistent repository that reconciles subledger activity against general ledger control account balances, enabling the Global Accounting Engine to validate that subledger postings agree with the balances carried in the general ledger.

Because the table's unique business key spans multiple referenced entities — SET_OF_BOOKS_ID, APPLICATION_ID, CODE_COMBINATION_ID, PERIOD_NAME, THIRD_PARTY_ID, and SUB_ID — the metadata's extracted Data Vault classification ("link") suggests modeling AX_BALANCES as a link (association) record that connects a ledger, a subledger application, a code combination, an accounting period, and a third party into a single balance row. Under this modeling suggestion, the balance measures (PERIOD_NET_DR, PERIOD_NET_CR, END_BALANCE_DR, END_BALANCE_CR) behave as satellite-style descriptive attributes carried on that link.

Key Information Stored

The table contains 25 documented columns. The primary key, AX_BALANCES_PK, is defined on the composite of SET_OF_BOOKS_ID, APPLICATION_ID, CODE_COMBINATION_ID, PERIOD_NAME, THIRD_PARTY_ID, and SUB_ID. The unique index AX_BALANCES_U1 is defined on the identical column set, making it the business-key candidate that enforces one balance row per ledger/application/account/period/third-party/sub-account combination rather than a synthetic surrogate identifier.

The most consequential columns are:

• SET_OF_BOOKS_ID — identifies the ledger to which the balance belongs, and participates in the foreign key to GL_PERIOD_STATUSES.
• APPLICATION_ID / PERIOD_NAME — identify the subledger application and accounting period; together with SET_OF_BOOKS_ID they form the join to GL_PERIOD_STATUSES.
• CODE_COMBINATION_ID — references GL_CODE_COMBINATIONS and identifies the accounting flexfield combination for the control account.
• PERIOD_NET_DR / PERIOD_NET_CR — period-to-date net debit and credit amounts for the subledger activity.
• END_BALANCE_DR / END_BALANCE_CR — cumulative end-of-period debit and credit balances.
• THIRD_PARTY_ID / SUB_ID — the third-party and subordinate identification that complete the unique business key.
• ORG_ID — the operating unit context for multi-org reporting.
• PERIOD_HISTORY_NUM / UPDATED_FLAG / HISTORIC_BALANCE — control columns governing balance versioning, update status, and historical retention.
• BALANCE_SEGMENT / ACCOUNT_SEGMENT — segment values used for balance-level classification.
• Audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN, REQUEST_ID, PROGRAM_ID) — standard WHO columns tracking the originating concurrent program.

Common Use Cases and Queries

Typical usage involves reconciling subledger activity to general ledger control account balances by period. A common pattern joins AX_BALANCES to GL_PERIOD_STATUSES to confirm the period is open or closed, and to GL_CODE_COMBINATIONS to retrieve the account segment values:

• Control-account reconciliation by ledger and period: SELECT ab.code_combination_id, ab.period_name, ab.period_net_dr, ab.period_net_cr, ab.end_balance_dr, ab.end_balance_cr FROM ax.ax_balances ab WHERE ab.set_of_books_id = :ledger AND ab.period_name = :period;
• Joining to period status to filter only open periods: ... JOIN gl.gl_period_statuses gps ON gps.set_of_books_id = ab.set_of_books_id AND gps.application_id = ab.application_id AND gps.period_name = ab.period_name WHERE gps.closing_status = 'O';
• Drill-down to the chart of accounts: join CODE_COMBINATION_ID to GL_CODE_COMBINATIONS to expand segment values for reporting.
• Third-party analysis: aggregate by THIRD_PARTY_ID and SUB_ID to isolate balances associated with specific customers, suppliers, or sub-accounts.

Reporting extracts generally run under read-only responsibility against the AX schema, filtering by ORG_ID to scope results to a single operating unit.

Related Objects

The documented foreign keys establish the principal relationships:

• GL_PERIOD_STATUSES — referenced via APPLICATION_ID, SET_OF_BOOKS_ID, and PERIOD_NAME; provides the ledger/period validity and closing status.
• GL_CODE_COMBINATIONS — referenced via CODE_COMBINATION_ID; supplies the accounting flexfield combination behind each control account.
• GL_BALANCES — the general ledger balance table against which AX_BALANCES is commonly compared for reconciliation.
• AX_BALANCE_LINES-family tables and other AX subledger tables — related balance detail managed by the Global Accounting Engine.
• GL_JE_HEADERS / GL_JE_LINES — journal sources used to trace the postings that feed these balances.
• AX Posting APIs / concurrent programs — the AX subledger posting and balance-population processes that write to this table.

Because AX_BALANCES is written by Global Accounting Engine processes and consumed primarily for reconciliation and reporting, direct DML on this table is not recommended; changes should be made through the standard AX and GL posting programs.