Results for “gl_budget_entities”

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

Overview

GL_BUDGET_ENTITIES is the General Ledger master table that stores budget organization definitions in Oracle E-Business Suite 12.1.1 and 12.2.2. A "budget organization" (also called a budget entity) is the named container under which a set of accounting flexfield ranges is held and against which budgets are entered, frozen, and reported. Each row in this table represents one such organization for a specific ledger, and the entity serves as the anchor point for the entire budgeting workflow — from range assignment through budget entry to funds checking.

The table resides in the GL schema and is owned by the General Ledger product. It is a foundational setup object: without a defined budget entity, no budget assignment ranges can exist and no budget journals can be created. The ETRM metadata documents it with 60 columns and classifies it heuristically as a Data Vault hub. In practice this means the table should be modeled as a durable, business-keyed entity whose satellite and link tables hold the time-variant details, range assignments, and transactional budget facts that surround it.

Key Information Stored

The surrogate primary key is BUDGET_ENTITY_ID (enforced through GL_BUDGET_ENTITIES_PK). Two unique indexes act as business-key candidates. The first, GL_BUDGET_ENTITIES_U1, is also defined on BUDGET_ENTITY_ID. The second, GL_BUDGET_ENTITIES_U2, is defined on the combination of NAME and LEDGER_ID, confirming that the organization name must be unique within a ledger.

• NAME — the user-visible budget organization name, unique within the ledger.
• LEDGER_ID — the ledger to which the budget organization belongs; a foreign key to the ledger definition.
• STATUS_CODE — controls whether the entity is active and available for budget entry.
• START_DATE / END_DATE — the effective period during which the organization may be used.
• DESCRIPTION — free-form descriptive text for the organization.
• BUDGET_PASSWORD_REQUIRED_FLAG and ENCRYPTED_BUDGET_PASSWORD — support optional password protection on budget maintenance.
• SECURITY_FLAG — indicates whether definition access security applies.
• SEGMENT1_TYPE through SEGMENT30_TYPE — precedence and range-type indicators for each accounting flexfield segment, defining how ranges are interpreted for the entity.
• REQUEST_ID, PROGRAM_ID, PROGRAM_APPLICATION_ID, PROGRAM_UPDATE_DATE — the standard concurrent program and audit columns, with REQUEST_ID referencing FND_CONCURRENT_REQUESTS.
• ATTRIBUTE1 through ATTRIBUTE10, CONTEXT — the standard descriptive flexfield columns for customer-defined attributes.

Standard WHO audit columns (CREATION_DATE, CREATED_BY, LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN) are also present.

Common Use Cases and Queries

The most frequent requirement is listing the budget organizations available for a given ledger, typically driven by a LOV or a report parameter. A representative query joining the entity to its concurrency context is:

• SELECT be.budget_entity_id, be.name, be.status_code, be.start_date, be.end_date FROM gl_budget_entities be WHERE be.ledger_id = :ledger_id AND be.status_code = 'A' ORDER BY be.name;
• Joining ranges to entities: SELECT ba.budget_entity_id, ba.account_range_id FROM gl_budget_assignments ba WHERE ba.budget_entity_id = :budget_entity_id;
• Listing budget balances held per entity: SELECT eb.budget_entity_id, eb.budget_name FROM gl_entity_budgets eb WHERE eb.budget_entity_id = :budget_entity_id;

Typical reporting scenarios include reconciling which organizations are protected by passwords, identifying entities whose END_DATE has passed, auditing definition changes using the WHO columns and PROGRAM_ID, and validating that every budget journal posted can be traced back to its owning entity. Extraction scripts for data warehouses commonly select the hub columns plus the LEDGER_ID business key to seed a budget-organization dimension.

Related Objects

GL_BUDGET_ENTITIES is heavily referenced; the following are the most significant dependencies and join paths.

• GL_BUDGET_ASSIGNMENTS — stores the accounting flexfield ranges assigned to the entity, joined on BUDGET_ENTITY_ID.
• GL_BUDGET_ASSIGNMENT_RANGES — the segment-level range definitions, joined on BUDGET_ENTITY_ID.
• GL_BUDGET_FROZEN_RANGES — ranges temporarily frozen for budget entry, joined on BUDGET_ENTITY_ID.
• GL_ENTITY_BUDGETS — the named budgets defined within each entity, joined on BUDGET_ENTITY_ID.
• GL_BUDGET_INTERFACE — the open interface table through which budget journals are loaded, joined on BUDGET_ENTITY_ID.
• GL_BUDGET_INTERIM and GL_BUDGET_RANGE_INTERIM — interim staging tables used by range maintenance, joined on BUDGET_ENTITY_ID.
• FND_CONCURRENT_REQUESTS — referenced by the REQUEST_ID foreign key for the concurrent program that created or updated the row.

In addition, multiple Public Sector and grants-related objects (for example, IGI_DOS_SOURCES, IGI_DOS_DESTINATIONS, IGI_BUD_JOURNAL_HEADERS, and IGC_CBC_BA_RANGES) carry a BUDGET_ENTITY_ID foreign key, confirming that the entity is a genuine hub reused across budgeting, funds checking, and grants sub-ledger functionality.