Results for “gl_budget_interface”

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

Overview

GL_BUDGET_INTERFACE is the General Ledger open interface table in Oracle E-Business Suite (12.1.1 and 12.2.2) used to upload budget data into Oracle General Ledger from external sources such as spreadsheets, legacy budgeting systems, feeder applications, or custom programs. Rows inserted into this table are validated and processed by the Budget Upload concurrent program, which transfers budget amounts into the GL_BUDGET_BALANCES staging structures associated with a specific budget, budget entity, and budget version. The table resides in the GL schema and is referenced under Data Vault classification as a link table — a heuristic suggesting it functions primarily as a transactional junction connecting budget definitions, accounting flexfield combinations, ledger/period context, and monetary amounts, rather than as a durable hub of business entities or a satellite of descriptive attributes.

Because it is an interface table, GL_BUDGET_INTERFACE is transient by design. Records are staged for processing, and successful rows are subsequently deleted or purged once the upload completes. Its structure therefore reflects the full set of inputs required by the Budget Upload program rather than a normalized operational entity.

Key Information Stored

The physical schema documented for 12.2.2 contains 107 columns. The most significant columns fall into four groups: budget identity, accounting context, period amounts, and processing control.

• BUDGET_NAME, BUDGET_ENTITY_NAME, BUDGET_ENTITY_ID — identify the target budget and its entity (e.g., revenue, expense) within GL_BUDGET_ENTITIES.
• BUDGET_VERSION_ID — the specific budget version to which amounts are posted, referencing GL_BUDGET_VERSIONS.
• SET_OF_BOOKS_ID and LEDGER_ID — the ledger context for the upload; SET_OF_BOOKS_ID is carried for 11i/12.1 compatibility while LEDGER_ID supports the 12.2 multiple-ledger architecture.
• CODE_COMBINATION_ID — the surrogate identifier of the accounting flexfield combination, referencing GL_CODE_COMBINATIONS. When populated, it supersedes the SEGMENT1 through SEGMENT30 columns.
• SEGMENT1 … SEGMENT30 — the individual accounting flexfield segment values. These form the surrogate primary key GL_BUDGET_INTERFACE_PK together with BUDGET_NAME, enabling one interface row per budget/account combination.
• CURRENCY_CODE — the currency of the budget amounts, validated against FND_CURRENCIES.
• PERIOD_TYPE and FISCAL_YEAR — the period type (e.g., Month, Quarter) and fiscal year against which amounts are distributed.
• PERIOD1_AMOUNT … PERIOD60_AMOUNT — the budget amounts allocated across up to sixty periods of the fiscal year.
• DR_FLAG and ACCOUNT_TYPE — indicate the debit/credit orientation and the natural account type derived from the combination.
• UPDATE_LOGIC_TYPE — controls whether uploaded amounts replace, add to, or subtract from existing budget balances.
• STATUS — the processing state of each interface row.
• REQUEST_ID — links the row to the concurrent request that processed it, referencing FND_CONCURRENT_REQUESTS.
• LAST_UPDATE_DATE, LAST_UPDATED_BY — standard audit columns.

The surrogate primary key is GL_BUDGET_INTERFACE_PK, defined over BUDGET_NAME and SEGMENT1 through SEGMENT30. Business-key uniqueness in practice is governed by the combination of BUDGET_NAME, BUDGET_ENTITY_ID, BUDGET_VERSION_ID, SET_OF_BOOKS_ID or LEDGER_ID, and CODE_COMBINATION_ID.

Common Use Cases and Queries

The primary use case is programmatic budget loading. A typical workflow inserts staged rows, runs the Budget Upload concurrent program, and reconciles results by STATUS and REQUEST_ID.

Verifying loaded data for a concurrent request:

SELECT budget_name, fiscal_year, period_type, status, request_id
FROM   gl_budget_interface
WHERE  request_id = :request_id;

Summing period amounts by budget and account to validate a load before submission:

SELECT budget_name, code_combination_id,
       period1_amount + period2_amount + period3_amount AS q1_amount
FROM   gl_budget_interface
WHERE  budget_name = :budget_name;

Identifying interface rows that failed processing:

SELECT code_combination_id, segment1, segment2, status
FROM   gl_budget_interface
WHERE  status <> 'P' AND request_id = :request_id;

Common reporting scenarios include comparing external source totals against the interface table prior to upload, auditing which user and request populated each batch through LAST_UPDATED_BY and REQUEST_ID, and resolving accounting flexfield errors when CODE_COMBINATION_ID is null because the segment combination does not exist in GL_CODE_COMBINATIONS.

Related Objects

The following objects are the most significant dependencies of GL_BUDGET_INTERFACE, based on its documented foreign keys and primary key relationships.

• GL_CODE_COMBINATIONS — joined on CODE_COMBINATION_ID to resolve segment values and validate accounting flexfield combinations.
• GL_BUDGET_ENTITIES — joined on BUDGET_ENTITY_ID to identify the budget entity targeted by the upload.
• GL_BUDGET_VERSIONS — joined on BUDGET_VERSION_ID to identify the specific budget version.
• GL_PERIOD_TYPES — joined on PERIOD_TYPE to validate the period type used for amount distribution.
• FND_CURRENCIES — joined on CURRENCY_CODE to validate the budget currency.
• FND_CONCURRENT_REQUESTS — joined on REQUEST_ID to trace which concurrent process inserted and validated the rows.
• GL_BUDGET_BALANCES — the target table populated by the Budget Upload program after interface validation.
• GL_BUDGET_ASSIGNMENTS — defines which accounts are enabled for budgeting, used to validate interface rows against budget assignment rules.

The Budget Upload concurrent program is the principal API-level entry point, reading from GL_BUDGET_INTERFACE and writing to the GL budget balances. Because the table is transient, DBAs should ensure purge processes run after successful uploads to prevent stale rows from accumulating.