Results for “automatic_encumbrance_flag”

12 results




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

Overview

GL_BUDGET_ASSIGNMENTS is a General Ledger table in the Oracle E-Business Suite 12.1.1 / 12.2.2 schema (owner GL) that stores budget organization accounts. It defines which accounting code combinations are assigned to a budget organization (budget entity) and tracks the range and currency context under which those accounts participate in budgeting and funds checking.

Each row links a ledger, a code combination, and a currency to a budget entity, a budget assignment range, and an optional funding budget version. The table also carries flags controlling automatic encumbrance and funds check behavior per account, which is fundamental to budgetary control processing in GL.

In Data Vault terms, the FK structure suggests a link classification, as the table primarily resolves many-to-many relationships between budget entities, code combinations, and ranges. The primary key GL_BUDGET_ASSIGNMENTS_PK is composed of LEDGER_ID, CODE_COMBINATION_ID, and CURRENCY_CODE. A secondary unique index GL_BUDGET_ASSIGNMENTS_U1 covers CODE_COMBINATION_ID, LEDGER_ID, CURRENCY_CODE, and RANGE_ID, serving as an alternate business-key candidate.

Key Information Stored

The table contains 30 documented columns. The most significant are:

  • LEDGER_ID – the ledger that owns the budget assignment.
  • CODE_COMBINATION_ID – the accounting flexfield combination assigned to the budget entity.
  • CURRENCY_CODE – the currency in which budget amounts and funds checks are performed.
  • BUDGET_ENTITY_ID – the budget organization to which the account belongs.
  • RANGE_ID – the assignment range defining how the combination falls within the budget organization.
  • FUNDING_BUDGET_VERSION_ID – the budget version that funds this assignment.
  • AUTOMATIC_ENCUMBRANCE_FLAG – controls whether encumbrances are created automatically.
  • FUNDS_CHECK_LEVEL_CODE – defines the level at which funds availability is validated.
  • AMOUNT_TYPE and BOUNDARY_CODE – classification and range boundary indicators.
  • ENTRY_CODE and ORDERING_VALUE – sequence and entry classification for assignment ranges.
  • REQUEST_ID – the concurrent request that created or updated the assignment.
  • LAST_UPDATE_DATE, CREATED_BY, LAST_UPDATED_BY – standard audit columns.

Common Use Cases and Queries

Typical reporting scenarios include identifying all accounts assigned to a budget organization, verifying funds check configuration, and reconciling budget version funding. A representative query joining GL_CODE_COMBINATIONS and GL_BUDGET_ENTITIES might appear as:

  • SELECT gba.LEDGER_ID, gba.CODE_COMBINATION_ID, gba.CURRENCY_CODE, gbe.BUDGET_ENTITY_NAME FROM GL_BUDGET_ASSIGNMENTS gba, GL_BUDGET_ENTITIES gbe WHERE gba.BUDGET_ENTITY_ID = gbe.BUDGET_ENTITY_ID AND gba.LEDGER_ID = :ledger.
  • Reporting accounts with AUTOMATIC_ENCUMBRANCE_FLAG = 'Y' for a given ledger to audit encumbrance behavior.
  • Listing assignments whose FUNDS_CHECK_LEVEL_CODE differs from a standard profile to diagnose funds check discrepancies.
  • Cross-checking RANGE_ID against GL_BUDGET_ASSIGNMENT_RANGES to validate boundary and ordering definitions.

Because the table sits between budget setup and funds checking during transaction processing, it is frequently used in reconciliation reports when purchase requisitions or invoices are unexpectedly failing funds checks.

Related Objects

The following objects are formally related through foreign key and primary key relationships:

  • GL_CODE_COMBINATIONS – joined on CODE_COMBINATION_ID; provides account descriptions.
  • GL_BUDGET_ENTITIES – joined on BUDGET_ENTITY_ID; defines the budget organization.
  • GL_BUDGET_VERSIONS – joined on FUNDING_BUDGET_VERSION_ID; identifies the funding budget.
  • GL_BUDGET_ASSIGNMENT_RANGES – joined on RANGE_ID; defines account ranges.
  • FND_CURRENCIES – joined on CURRENCY_CODE; validates currency context.
  • FND_CONCURRENT_REQUESTS – joined on REQUEST_ID; traces the originating concurrent program.

These relationships establish GL_BUDGET_ASSIGNMENTS as the operational bridge between budget definition and actual ledger account assignment in Oracle General Ledger.