Results for “jg_zz_ap_tmp_bal”

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

Overview

JG_ZZ_AP_TMP_BAL is a temporary sub-ledger balance table owned by the AP schema and delivered as part of the JG (Regional Localizations) product family in Oracle E-Business Suite 12.1.1 and 12.2.2. Its stated purpose is to hold temporary sub-ledger balances for Payables, most commonly serving as a staging structure used by regional localization and statutory reporting processes — for example, generating period-end Payables sub-ledger extracts, regional balance reports, or jurisdiction-specific statutory filings that must be produced outside the permanent Oracle Payables balance model.

The table is documented as VALID in the ETRM repository and contains 19 physical columns. It carries a single primary key constraint, JG_ZZ_AP_TMP_BAL_PK, defined over six columns: SET_OF_BOOKS_ID, CODE_COMBINATION_ID, CURRENCY_CODE, PERIOD_NAME, VENDOR_ID, and VENDOR_SITE_ID. Under a heuristic Data Vault classification, this object is best modeled as a standalone structure — the metadata does not identify any incoming or outgoing foreign key relationships, so it is not naturally a hub, link, or satellite connected to the rest of the warehouse model. It is more accurately described as a transient aggregate or staging snapshot, loaded and consumed within a single localization process run rather than persisted as durable master or transaction data.

Key Information Stored

The grain of the table is one row per combination of set of books, accounting code combination, currency, accounting period, vendor, and vendor site. The most significant columns are:

• SET_OF_BOOKS_ID — the ledger/set of books context; a primary key member and the principal partitioning attribute for multi-organization deployments.
• CODE_COMBINATION_ID — the accounting flexfield combination the balance relates to; the primary natural join key to GL_CODE_COMBINATIONS.
• CURRENCY_CODE — the denominating currency of the entered and accounted amounts.
• PERIOD_NAME — the accounting period for which the balance is computed.
• VENDOR_ID and VENDOR_SITE_ID — the supplier and supplier site dimension carried through from Payables.
• BEGIN_BAL_ENTERED_DR / BEGIN_BAL_ENTERED_CR — opening balances in entered (transaction) currency.
• BEGIN_BAL_ACCOUNTED_DR / BEGIN_BAL_ACCOUNTED_CR — opening balances in ledger/accounted currency.
• PERIOD_NET_ENTERED_DR / PERIOD_NET_ENTERED_CR — period activity in entered currency.
• PERIOD_NET_ACCOUNTED_DR / PERIOD_NET_ACCOUNTED_CR — period activity in accounted currency.
• POSTED_TO_GL_FLAG — indicator of whether the balance has been transferred to the General Ledger, controlling downstream reconciliation.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, CREATION_DATE, CREATED_BY — standard EBS WHO columns for audit and concurrency traceability.

The six-column primary key JG_ZZ_AP_TMP_BAL_PK serves as the composite business key; there is no separate single-column surrogate key documented. The entered versus accounted debit/credit pairs provide a double-representation of each balance, allowing localization reports to reconcile transaction currency against ledger currency without re-deriving rates.

Common Use Cases and Queries

Typical usage centers on period-end Payables sub-ledger reporting and localization-specific statutory extracts. Because the table is rebuildable from source Payables data, queries are generally read-oriented and scoped tightly by ledger and period:

• Extracting opening and period activity balances for a given ledger and period.
• Reconciling accounted and entered amounts to detect exchange-rate-driven variances.
• Listing balances not yet posted to GL using the POSTED_TO_GL_FLAG indicator.
• Vendor-level and code-combination-level trending across periods.

A representative query pattern:

• SELECT set_of_books_id, period_name, vendor_id, code_combination_id, SUM(begin_bal_accounted_dr - begin_bal_accounted_cr) opening, SUM(period_net_accounted_dr - period_net_accounted_cr) activity FROM ap.jg_zz_ap_tmp_bal WHERE set_of_books_id = :ledger AND period_name = :period GROUP BY set_of_books_id, period_name, vendor_id, code_combination_id;

For unpivoted reporting, the entered and accounted DR/CR pairs are often flattened before being loaded into a reporting layer. Because the object is temporary, consumers should treat its contents as post-run snapshot data and not assume persistence between localization executions.

Related Objects

Although the metadata lists JG_ZZ_AP_TMP_BAL as standalone with no documented foreign keys, its columns imply functional dependencies on core Payables and General Ledger reference objects:

• AP_SUPPLIERS / AP_SUPPLIER_SITES_ALL — joined via VENDOR_ID and VENDOR_SITE_ID for supplier and site attributes.
• GL_CODE_COMBINATIONS — joined via CODE_COMBINATION_ID for account descriptions and flexfield segments.
• GL_LEDGERS / GL_SETS_OF_BOOKS — joined via SET_OF_BOOKS_ID to resolve ledger name, currency, and chart of accounts.
• AP_INVOICES_ALL, AP_INVOICE_DISTRIBUTIONS_ALL, AP_PAYMENT_SCHEDULES_ALL — the Payables sub-ledger source likely aggregated into this temporary balance.
• FND_CURRENCIES — joined via CURRENCY_CODE for currency names and precision.
• AP_ACCOUNTING_EVENTS_ALL / XLA_AE_HEADERS — the Subledger Accounting context that produces accounted amounts.

These join paths should be validated against the deployment's actual JG localization implementation, since the documented metadata declares no enforced referential constraints on this table.