Search Results func_curr_code

Overview

RG_DSS_VARIABLES_V is a reporting view owned by the APPS schema in Oracle E-Business Suite, delivered as part of the RG (Application Report Generator) product. Its status is VALID, and the object is documented as "Retrofitted," indicating that it was carried forward into the 12.1.1 and 12.2.2 code lines with minimal structural change while preserving backward compatibility for dependent reports and integrations. The view exposes the definition of financial statement variables used by the Application Report Generator and its Decision Support System (DSS) components, resolving each variable against its owning ledger, budget version, encumbrance type, and lookup values.

The view does not store data independently; it is a denormalized projection over RG_DSS_VARIABLES joined to general ledger reference tables. This makes it the primary dictionary of variable metadata for report rows that draw balances, budgets, or encumbrance amounts from the General Ledger. The presence of the alias FUNC_CURR_CODE, drawn from GL_LEDGERS.CURRENCY_CODE, is particularly relevant to users searching for func_curr_code, since this view is the documented source of the functional currency code associated with each variable's ledger.

Underlying Base Objects

The view is documented as referencing four base objects in the 12.2.2 metadata: GL_BUDGET_VERSIONS, GL_ENCUMBRANCE_TYPES, GL_LEDGERS, and GL_LOOKUPS, all resolved through synonyms except GL_LOOKUPS, which is itself a view. The driving table is RG_DSS_VARIABLES (APPS synonym), the master table of variable definitions.

• GL_LEDGERS — joined on LEDGER_ID, supplying the ledger name, the average balance flag (ADB_FLAG), and the functional currency code exposed as FUNC_CURR_CODE.
• GL_BUDGET_VERSIONS — outer-joined on BUDGET_VERSION_ID, supplying BUDGET_NAME where a budget version is defined.
• GL_ENCUMBRANCE_TYPES — outer-joined on ENCUMBRANCE_TYPE_ID, supplying the encumbrance type description.
• GL_LOOKUPS — joined with LOOKUP_TYPE = 'GL_DSS_ENCUMBRANCE_TYPE' and LOOKUP_CODE = 'TOTAL', used by a DECODE to substitute a lookup meaning when ENCUMBRANCE_TYPE_ID equals -1.

Because only the ledger join is non-outer, a variable lacking a valid LEDGER_ID will not appear in the result set; budget and encumbrance attributes tolerate nulls.

Key Columns

• ROW_ID — the ROWID of the underlying RG_DSS_VARIABLES row, useful for direct row access.
• VARIABLE_ID, NAME, DESCRIPTION — the identifier, display name, and descriptive text of the report variable.
• LEVEL_CODE, STATUS_CODE — classification and activation state of the variable.
• OBJECT_NAME, COLUMN_LABEL — the source object and column from which balances are drawn.
• BALANCE_TYPE, CURRENCY_TYPE, CURRENCY_CODE — define whether the variable returns actual, budget, or encumbrance balances, and the currency basis of the amount.
• FUNC_CURR_CODE — the functional currency code of the associated ledger; this is the column matching the user's search term func_curr_code.
• LEDGER_ID, LEDGER_NAME, ADB_FLAG — the ledger context, including whether average balances are enabled.
• BUDGET_VERSION_ID, BUDGET_NAME — the budget context, where applicable.
• ENCUMBRANCE_TYPE_ID, ENCUMBRANCE_TYPE — the encumbrance classification, with -1 resolved via lookup to 'TOTAL'.
• ID_FLEX_CODE, ID_FLEX_NUM, SEGMENT1_TYPE through SEGMENT30_TYPE — key flexfield context and per-segment type indicators for account-based variables.
• Standard WHO columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) and ATTRIBUTE1–15 and CONTEXT for descriptive flexibility.

Common Use Cases and Queries

Typical usage is metadata lookup and validation rather than transactional reporting. Report developers query the view to confirm the functional currency and balance configuration of a variable before executing a financial statement, and DBAs use it to audit variables whose ledger, budget, or encumbrance references may have become stale.

To retrieve functional currency information for all variables on a given ledger:

• SELECT variable_id, name, func_curr_code, balance_type, currency_type FROM apps.rg_dss_variables_v WHERE ledger_name = :ledger_name;

To locate variables whose currency configuration may be invalid:

• SELECT variable_id, name, func_curr_code, currency_code FROM apps.rg_dss_variables_v WHERE func_curr_code <> currency_code AND currency_type = 'F';

To list encumbrance-bearing variables with their resolved type, including the 'TOTAL' lookup substitution:

• SELECT name, ledger_name, encumbrance_type FROM apps.rg_dss_variables_v WHERE encumbrance_type_id IS NOT NULL ORDER BY ledger_name, name;

Because the view joins only on indexed ledger, budget, and encumbrance identifiers, queries are inexpensive and suitable for embedding in validation scripts or report-definition maintenance utilities.