Search Results func_end_balance

Overview

JA_CN_ACCOUNT_BALANCES_V is an Oracle EBS application view owned by the APPS schema and registered under the FND - Application Object Library product. It exposes summarized account balance data by ledger, legal entity, accounting period, cost center, third party, project, and account segment. The view is associated with the China localization (JA_CN) solution set and is intended to present period-level beginning balances, period activity, and ending balances in both functional and original (entered) currency, alongside a derived account type classification.

Its principal role is to provide a reporting and integration layer over stored balances, enabling external reports, reconciliations, and downstream extracts to consume balances without directly querying base tables. Because it joins dimensional attributes with debit/credit and net amounts, it is well suited to financial statement generation and localization-specific statutory reporting.

Underlying Base Objects

According to the documented ETRM metadata (12.2.2), the view is defined over a single referenced base object: JA_CN_ACCOUNT_BALANCES, exposed in the APPS schema as a synonym. The view therefore acts as a projection and derivation layer over that base object rather than consolidating multiple tables.

The view's SELECT list maps directly to columns in JA_CN_ACCOUNT_BALANCES for all stored dimension and amount attributes. Derived columns (such as FUNC_BEGIN_BALANCE, ORIG_BEGIN_BALANCE, FUNC_END_BALANCE, and ORIG_END_BALANCE) are not stored; they are computed at query time using DECODE expressions against ACCOUNT_TYPE and NVL-guarded arithmetic over the debit/credit pairs, ensuring sign conventions appropriate to asset/expense versus other account types.

Key Columns

• LEDGER_ID – Ledger context for the balances.
• LEGAL_ENTITY_ID – Legal entity associated with the balance.
• COMPANY_SEGMENT, COST_CENTER, ACCOUNT_SEGMENT – Accounting flexfield segments used for reporting groupings.
• PERIOD_NAME, PERIOD_MON – Accounting period and its numeric month indicator.
• CURRENCY_CODE – Currency of the recorded balances.
• THIRD_PARTY_TYPE, THIRD_PARTY_ID, THIRD_PARTY_NUMBER – Third-party (for example, customer or supplier) attribution.
• PROJECT_ID, PROJECT_NUMBER, PROJECT_SOURCE – Project attribution where balances are project-related.
• PERSONNEL_ID, PERSONNEL_NUMBER – Personnel attribution where applicable.
• FUNC_* / ORIG_*_BEGIN_BALANCE_DR/CR – Beginning balances and period activity by debit/credit in functional and original currency.
• ACCOUNT_TYPE – Account classification driving sign logic. Values such as 'A' (asset) and 'E' (expense) yield a debit-positive convention (debit minus credit), while other types (for example, liabilities, equity, revenue) yield credit-positive results.
• FUNC_BEGIN_BALANCE / ORIG_BEGIN_BALANCE – Signed beginning balances derived from the DR/CR pairs.
• FUNC_END_BALANCE_DR/CR and ORIG_END_BALANCE_DR/CR – Ending balances computed as beginning balance plus period net activity, by side.
• FUNC_END_BALANCE / ORIG_END_BALANCE – Signed ending balances applying the same ACCOUNT_TYPE sign convention.

Common Use Cases and Queries

Typical uses include producing localized trial balances, reconciling functional versus original currency balances, and feeding statutory or management reports filtered by ledger, legal entity, and period. The following examples illustrate common patterns.

• Ending balances for a ledger and period:

SELECT accounting_period, account_segment, currency_code, FUNC_END_BALANCE FROM APPS.JA_CN_ACCOUNT_BALANCES_V WHERE ledger_id = :p_ledger AND period_name = :p_period ORDER BY account_segment;

• Comparison of functional versus original currency beginning balances by account type:

SELECT account_type, SUM(FUNC_BEGIN_BALANCE) func_begin, SUM(ORIG_BEGIN_BALANCE) orig_begin FROM APPS.JA_CN_ACCOUNT_BALANCES_V WHERE ledger_id = :p_ledger AND period_name = :p_period GROUP BY account_type;

• Project-level period activity extract:

SELECT project_number, cost_center, FUNC_PERIOD_NET_DR, FUNC_PERIOD_NET_CR FROM APPS.JA_CN_ACCOUNT_BALANCES_V WHERE project_id IS NOT NULL AND period_name = :p_period;

Because derived columns are computed at runtime, queries should constrain on indexed columns such as LEDGER_ID and PERIOD_NAME to maintain performance, particularly when aggregating across legal entities or projects.