Results for “jg_zz_ap_balances”

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

Overview

AP.JG_ZZ_AP_BALANCES is a Regional Localizations (product code JG) table that stores sub-ledger balances for Oracle Payables. It is registered as VALID in the AP schema and is documented across both Oracle E-Business Suite 12.1.1 and 12.2.2. The table acts as a summarized payables balance repository, organized by accounting period and by the accounting flexfield combination against which liability, prepayment, or expense balances are accumulated. Because Oracle Payables itself does not persist period-end sub-ledger balances in a single standard table, localization extensions such as this one typically capture the beginning balance and net period activity needed for statutory reporting, reconciliation, and period-close processes required by regional fiscal authorities.

From a Data Vault modeling perspective, the heuristic classification derived from the foreign-key structure is standalone. This suggests that JG_ZZ_AP_BALANCES is best modeled as an independent satellite-like snapshot table rather than as a hub or link. The absence of enforced foreign keys to parent entities means the table stands on its own composite key, and any dimensional context (set of books, account, vendor, site, period, currency) is carried as descriptive attributes of the balance snapshot.

Key Information Stored

The table contains 19 documented columns. The primary key, JG_ZZ_AP_BALANCES_PK, is a composite key whose columns are also exposed as the unique business-key candidate JG_ZZ_AP_BALANCES_U1. Unlike many EBS tables, there is no single surrogate *_ID column; the key itself is the business identifier. The most important columns are:

• SET_OF_BOOKS_ID — identifies the ledger (set of books) to which the balance belongs; part of the primary key and the natural partition for reporting.
• CODE_COMBINATION_ID — the accounting flexfield combination to which the payable balance is posted; part of the primary key.
• CURRENCY_CODE — the transaction currency of the balances; part of the primary key, allowing multi-currency balances to coexist for the same account and period.
• PERIOD_NAME — the accounting period (e.g., JAN-24) for which the balance is reported; part of the primary key.
• VENDOR_ID and VENDOR_SITE_ID — the supplier and supplier site dimensions; the finest granularity of the balance record.
• BEGIN_BAL_ENTERED_DR / BEGIN_BAL_ENTERED_CR — opening entered debit and credit balances for the period.
• BEGIN_BAL_ACCOUNTED_DR / BEGIN_BAL_ACCOUNTED_CR — opening accounted (ledger currency) debit and credit balances.
• PERIOD_NET_ENTERED_DR / PERIOD_NET_ENTERED_CR — net entered debit and credit activity within the period.
• PERIOD_NET_ACCOUNTED_DR / PERIOD_NET_ACCOUNTED_CR — net accounted activity within the period.
• POSTED_TO_GL_FLAG — indicates whether the balance or period activity has been transferred to the General Ledger.

The remaining audit columns — LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, and CREATED_BY — follow the standard EBS WHO-column convention and support change tracking and concurrency.

Common Use Cases and Queries

Typical scenarios include period-end statutory balance reporting, payables sub-ledger-to-GL reconciliation, aged vendor balance analysis, and localization-specific audit extracts. A common query aggregates net period movement by ledger, account, and period:

SELECT set_of_books_id, period_name, code_combination_id, currency_code,
       SUM(period_net_accounted_dr - period_net_accounted_cr) net_accounted
FROM   ap.jg_zz_ap_balances
WHERE  set_of_books_id = :p_sob
AND    period_name = :p_period
GROUP BY set_of_books_id, period_name, code_combination_id, currency_code;

To identify items pending transfer to the GL, filter on the posting flag:

SELECT * FROM ap.jg_zz_ap_balances
WHERE  posted_to_gl_flag = 'N';

Vendor-level rollups join on the composite key dimensions to summarize beginning plus net activity for a supplier and site across periods.

Related Objects

The documented metadata classifies this table as standalone, so no enforced foreign keys are published. In practice, its columns reference the following standard Payables, General Ledger, and supplier objects:

• GL_SETS_OF_BOOKS — joined on SET_OF_BOOKS_ID to resolve ledger name and currency.
• GL_CODE_COMBINATIONS — joined on CODE_COMBINATION_ID to expand the accounting flexfield.
• AP_SUPPLIERS — joined on VENDOR_ID for supplier detail.
• AP_SUPPLIER_SITES_ALL — joined on VENDOR_SITE_ID for site detail.
• AP_INVOICES_ALL and AP_INVOICE_DISTRIBUTIONS_ALL — source documents whose accounted amounts feed the sub-ledger balances.
• AP_PAYMENT_SCHEDULES_ALL — supporting liability and payment scheduling data.
• GL_JE_BATCHES and GL_JE_HEADERS — target of the posting indicated by POSTED_TO_GL_FLAG.
• FND_PERIODS / GL_PERIODS — period validation against PERIOD_NAME.

Because there are no hard foreign keys, referential integrity is maintained by the localization program logic that populates and consumes this table, making careful data validation essential in any extract or migration involving JG_ZZ_AP_BALANCES.