Results for “translated_flag”

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

Overview

APPS.GL_BUDGET_DETAIL_BALANCES_V is a General Ledger (GL) reporting view in Oracle E-Business Suite 12.1.1 and 12.2.2. As documented in the ETRM metadata, the view is described as "10SC ONLY," indicating it is a specialized object originally scoped to a specific localization or internal use case, but it remains a valid object within the APPS schema in the documented releases. Its purpose is to expose budget balance information at the detail code combination level while simultaneously linking those detail accounts to their corresponding summary (parent) code combinations via the account hierarchy.

The view joins budget balances to account hierarchies so that a single row carries both the detail account context and the summary account to which it rolls up. This makes it useful for hierarchical budget reporting, where totals must be presented against both the leaf-level account and the parent aggregation. It is referenced by report and inquiry logic rather than by transactional processing, and it acts primarily as a read-only reporting and integration surface.

Underlying Base Objects

Per the documented view text, the view is defined over two base objects:

• GL_BALANCES (exposed through the APPS synonym) — supplies the actual budget balance rows. The view filters this table with ACTUAL_FLAG = 'B', which restricts the result set to budget balances; TEMPLATE_ID IS NULL to exclude template rows; and NVL(TRANSLATED_FLAG,'X') NOT IN ('Y','N') to exclude translated or non-translatable balance records.
• GL_ACCOUNT_HIERARCHIES (exposed through the APPS synonym) — supplies the detail-to-summary account relationship, contributing the SUMMARY_CODE_COMBINATION_ID and the ROW_ID (the hierarchy row identifier).
• BUDGET_INQUIRY_PKG — a packaged PL/SQL function referenced in the projection. The view invokes BUDGET_INQUIRY_PKG.GET_FACTOR to divide raw debit/credit amounts, applying the appropriate accounting factor for the ledger and currency.

The join predicate links both tables on LEDGER_ID and on CODE_COMBINATION_ID = DETAIL_CODE_COMBINATION_ID. The header hints (ORDERED USE_NL, with the account hierarchy unique index and the balances index) indicate the optimizer is directed to drive from the hierarchy and probe balances via nested loops.

Key Columns

• LEDGER_ID — the ledger to which the balance and hierarchy row belong.
• CODE_COMBINATION_ID — the detail (leaf) account combination of the balance.
• SUMMARY_CODE_COMBINATION_ID — the parent account contributed by the account hierarchy.
• CURRENCY_CODE, TRANSLATED_FLAG, REVALUATION_STATUS — currency and translation context for the balance.
• PERIOD_NAME, PERIOD_YEAR, PERIOD_NUM, PERIOD_TYPE — the accounting period identifying the balance.
• BUDGET_VERSION_ID — the budget version the balance pertains to.
• PERIOD_NET_AMOUNT, BEGIN_BALANCE_AMOUNT, QUARTER_TO_DATE_AMOUNT, PROJECT_TO_DATE_AMOUNT, YEAR_TO_DATE_AMOUNT — derived amounts computed as net debit minus net credit divided by GET_FACTOR. These expose period, beginning, quarter-to-date, project-to-date, and year-to-date budget figures.
• ROW_ID — the hierarchy row identifier, useful for navigating account hierarchy structure.

Common Use Cases and Queries

Typical scenarios include hierarchical budget inquiry, rollup reconciliation between detail and summary accounts, and extracting budget balances for downstream reporting. A representative query retrieving year-to-date budget amounts by period and summary account is shown below:

• Budget inquiry by summary account: select SUMMARY_CODE_COMBINATION_ID, PERIOD_NAME, YEAR_TO_DATE_AMOUNT for a given LEDGER_ID and BUDGET_VERSION_ID.
• Detail-to-summary reconciliation: group PERIOD_NET_AMOUNT by SUMMARY_CODE_COMBINATION_ID and compare to the parent account's own balance.
• Period reporting: filter on PERIOD_NAME, PERIOD_YEAR, and PERIOD_NUM to isolate a specific accounting period's budget activity.

Because the view enforces budget-only, non-template, non-translated balances, queries need not repeat those predicates. Access should be restricted to read-only reporting, and administrators should confirm the object remains valid in the target environment, since its "10SC ONLY" designation may limit its relevance outside the contexts for which it was originally documented.