Search Results bud_enc_name




Overview

GL_ALLOC_FORMULA_LINES_V is an APPS-owned view within the Oracle General Ledger (GL) module. As documented in the ETRM metadata, the object carries the description "10SC ONLY," indicating it is a specialized, context-restricted view rather than a general-purpose dictionary object. It exposes allocation formula line definitions — the individual components that make up an allocation formula used by the GL Allocations engine to distribute balances across accounts, cost centers, or ledgers.

Because allocation formulas are configured in a highly structured way (each line carries an operator, an amount source, a target segment range, and currency attributes), the view denormalizes these line records and joins them to lookup and reference tables so that codes are presented alongside their descriptive meanings. This makes it suitable for reporting, diagnostics, and integration scenarios where a functional user or downstream process needs to interpret allocation configuration without manually resolving lookup codes. The presence of the derived column SEGMENT_TYPES_KEY_FULL, which concatenates LEDGER_ACTION_CODE with a portion of SEGMENT_TYPES_KEY, reflects the composite key semantics that the allocation engine relies on when matching formula lines to segment ranges.

Underlying Base Objects

The view is defined over four documented referenced objects:

The view therefore acts as a descriptive overlay: it preserves the structural columns of the formula line table while resolving foreign-key references and lookup codes into human-readable values. Notably, the query exposes both the raw code (LEDGER_ACTION_CODE, SEGMENT_TYPES_KEY) and the concatenated composite (SEGMENT_TYPES_KEY_FULL).

Key Columns

  • ALLOCATION_FORMULA_ID / LINE_NUMBER — identify the parent formula and sequence within it.
  • LINE_TYPE / OPERATOR / AMOUNT — define the arithmetic behavior of the line (e.g., fixed amount versus relative allocation) and the value applied.
  • ACTUAL_FLAG / SHOW_ACTUAL_FLAG — indicate whether the line draws on actuals, budget ('B'), or encumbrance ('E') balances, with the decoded meaning surfaced.
  • BUDGET_NAME / ENCUMBRANCE_TYPE / BUD_ENC_NAME — descriptive identifiers for the budget or encumbrance source, with BUD_ENC_NAME selecting the appropriate one via DECODE.
  • CURRENCY_TYPE / TRANSACTION_CURRENCY / LEDGER_CURRENCY / ENTERED_CURRENCY — the currency basis on which the allocation amount is interpreted.
  • AMOUNT_TYPE / SHOW_AMOUNT_TYPE — the balance measure being allocated, with decoded meaning.
  • LEDGER_ACTION_CODE — the action category applied to the target ledger, and a component of SEGMENT_TYPES_KEY_FULL.
  • SEGMENT_TYPES_KEY / SEGMENT_TYPES_KEY_FULL / SEGMENT_BREAK_KEY — describe how target segment ranges are constructed and matched.
  • SEGMENT1_LOW through SEGMENTn_LOW — the low-bound range values for each accounting flexfield segment on the line.
  • PERIOD_NAME / RELATIVE_PERIOD — the period context for the line's calculation.

Common Use Cases and Queries

A frequent requirement is auditing how a specific allocation formula is configured, particularly where a user has searched on ledger_action_code to understand which ledger action a formula line invokes. The following retrieves lines for a given formula with their decoded flags:

  • SELECT allocation_formula_id, line_number, line_type, operator, amount, show_actual_flag, ledger_action_code, segment_types_key_full FROM apps.gl_alloc_formula_lines_v WHERE allocation_formula_id = :formula_id ORDER BY line_number;
  • SELECT l.allocation_formula_id, l.line_number, l.ledger_action_code, l.bud_enc_name, l.currency_type FROM apps.gl_alloc_formula_lines_v l WHERE l.ledger_action_code = :action_code;

Other practical uses include verifying segment range coverage, reconciling budget and encumbrance references before running an allocation, and extracting formula definitions for migration or documentation. Because the object is marked "10SC ONLY," consumers should confirm its availability in their specific environment before embedding it in a production integration.