Results for “begin_bal_accounted_dr”

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

Overview

The JG_ZZ_AR_BALANCES table is a Regional Localizations sub-ledger balances table owned by the AR (Receivables) schema in Oracle E-Business Suite 12.1.1 and 12.2.2. It stores summarized period-end sub-ledger balances for Receivables, broken down by accounting period, ledger, accounting flexfield combination, currency, and customer. As a localization object under the JG product family, it is typically used to support statutory reporting, fiscal reporting, or tax reconciliation requirements for specific countries (for example, Latin American or European localizations) where the standard Receivables balance tables do not provide a sufficiently granular snapshot for regulatory submissions.

Because the table is used for sub-ledger balance aggregation rather than transactional recording, it plays a supporting role to the core AR transaction and accounting tables. The ETRM metadata classifies this object heuristically as standalone within a Data Vault style model, meaning it has no documented foreign key dependencies participating in hub/link/satellite roles. In a Data Vault refactor this would suggest modelling it as an independent snapshot or balance satellite rather than as a link between business entities, though this is a modelling suggestion and not a documented fact.

Key Information Stored

The table has a documented physical schema of 19 columns. Its surrogate primary key, defined by JG_ZZ_AR_BALANCES_PK, is a composite. The business-key candidate is captured by the unique index JG_ZZ_AR_BALANCES_U1, which shares the same column set as the primary key: SET_OF_BOOKS_ID, CODE_COMBINATION_ID, CURRENCY_CODE, PERIOD_NAME, CUSTOMER_ID, and CUSTOMER_SITE_ID.

• SET_OF_BOOKS_ID — identifies the ledger (set of books) to which the balance belongs.
• CODE_COMBINATION_ID — the accounting flexfield combination used to classify the balance.
• CURRENCY_CODE — the transaction currency of the balance amounts.
• PERIOD_NAME — the accounting period for which the balance is reported.
• CUSTOMER_ID — the customer associated with the balance.
• CUSTOMER_SITE_ID — the specific customer site tied to the balance.
• BEGIN_BAL_ENTERED_DR / BEGIN_BAL_ENTERED_CR — opening balances in entered debit and credit amounts.
• BEGIN_BAL_ACCOUNTED_DR / BEGIN_BAL_ACCOUNTED_CR — opening balances in accounted (functional) debit and credit amounts.
• PERIOD_NET_ENTERED_DR / PERIOD_NET_ENTERED_CR — net period activity in entered debit and credit amounts.
• PERIOD_NET_ACCOUNTED_DR / PERIOD_NET_ACCOUNTED_CR — net period activity in accounted debit and credit amounts.
• POSTED_TO_GL_FLAG — indicates whether the balance has been posted to the General Ledger.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — standard audit columns.

Common Use Cases and Queries

Typical usage covers period-end receivables balance reporting, reconciliation between AR and GL, and statutory sub-ledger extracts. A representative query aggregates net period activity for a ledger and period:

• SELECT SET_OF_BOOKS_ID, PERIOD_NAME, CURRENCY_CODE, SUM(PERIOD_NET_ENTERED_DR - PERIOD_NET_ENTERED_CR) NET_ENTERED FROM JG_ZZ_AR_BALANCES WHERE SET_OF_BOOKS_ID = :ledger AND PERIOD_NAME = :period GROUP BY SET_OF_BOOKS_ID, PERIOD_NAME, CURRENCY_CODE;
• Drill down by customer and site: filter on CUSTOMER_ID and CUSTOMER_SITE_ID to produce customer-level statements.
• GL reconciliation: filter on POSTED_TO_GL_FLAG and compare accounted balances against GL balances by CODE_COMBINATION_ID and PERIOD_NAME.

Related Objects

• AR.GL_CODE_COMBINATIONS — joined on CODE_COMBINATION_ID to resolve accounting flexfield segments.
• GL.GL_LEDGERS / GL_SETS_OF_BOOKS — joined on SET_OF_BOOKS_ID to identify the ledger.
• AR.HZ_CUST_ACCOUNTS (via CUSTOMER_ID) and AR.HZ_CUST_ACCT_SITES_ALL (via CUSTOMER_SITE_ID) — resolve customer and site names.
• GL.GL_PERIODS / AR.AR_PERIODS — joined on PERIOD_NAME for period validation.
• AR.RA_CUSTOMER_TRX_ALL — source transactions underlying the summarized balances.
• AR.AR_CASH_RECEIPTS_ALL — receipts feeding period net activity.

Because the table is documented as standalone with no foreign keys, these relationships are enforced functionally rather than by database constraints, and must be applied explicitly when writing queries.