Results for “gl_budget_types”

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

Overview

GL_BUDGET_TYPES is the General Ledger master table that holds the definitions of budget types in Oracle E-Business Suite Release 12.1.1 and 12.2.2. A budget type is the user-defined classification that determines how budget amounts behave within General Ledger — for example, whether a budget is a standard operating budget, a project budget, or an encumbrance control budget. Every budget entered, uploaded, or tracked in the application must reference exactly one budget type, making this table the governing lookup for all budgeting activity in the ledger.

The object resides in the GL schema with a status of VALID and is described in the ETRM documentation as "Budget type definitions." It carries a documented physical schema of 11 columns and is owned by the General Ledger product/module.

From a dimensional modeling perspective, the heuristic Data Vault classification mined from the foreign key structure is hub-leaning. GL_BUDGET_TYPES therefore functions as a natural hub candidate: its primary key is a single business code, and multiple dependent tables attach to it through that key. This classification is a modeling suggestion, not an enforced property, and reflects the fact that the table holds stable reference data rather than transactional events.

Key Information Stored

Because GL_BUDGET_TYPES is a definition table, the majority of its documented columns are descriptive or audit-related. The principal columns are:

• BUDGET_TYPE — the primary key of the table and the business-key candidate. It stores the unique identifier for each budget type and is enforced by both the primary key constraint GL_BUDGET_TYPES_PK and the unique index GL_BUDGET_TYPES_U1. Because the primary key and unique index cover the same single column, the surrogate key and business key are effectively identical here; no separate system-generated identifier is documented.
• DESCRIPTION — the user-facing name of the budget type, used on entry forms, reports, and listings.
• AUDIT_TRAIL_FLAG — controls whether changes to budget data associated with this type are tracked in the audit trail.
• LAST_UPDATE_DATE and LAST_UPDATED_BY — the standard EBS WHO columns recording the date of the most recent change and the application user who made it.
• ATTRIBUTE1 through ATTRIBUTE5 — five open-ended descriptive flexfield segments available for client-specific extensions.
• CONTEXT — the descriptive flexfield context value that determines which attribute segments are enabled and how they are interpreted.

The presence of the ATTRIBUTE and CONTEXT columns indicates that GL_BUDGET_TYPES participates in the Oracle descriptive flexfield framework, so implementations can add validation and reporting attributes without altering the base table structure.

Common Use Cases and Queries

The most frequent requirement is simply resolving a budget type code to its description when reporting on budget balances, budget journals, or budget organization assignments. A typical lookup pattern is:

• SELECT gbt.budget_type, gbt.description FROM gl_budget_types gbt WHERE gbt.budget_type = :budget_type;
• SELECT gbt.budget_type, gbt.description, gbt.audit_trail_flag FROM gl_budget_types gbt ORDER BY gbt.budget_type;

Because GL_BUDGETS and GL_BUDGET_VERSIONS both carry BUDGET_TYPE as a foreign key, the table is almost always joined outward rather than queried in isolation. A representative join for reporting budget versions with their type names is:

• SELECT gv.budget_name, gv.budget_version_name, gbt.description FROM gl_budget_versions gv, gl_budget_types gbt WHERE gv.budget_type = gbt.budget_type AND gv.budget_type = :budget_type;

Other practical scenarios include driving a validation value set from BUDGET_TYPE and DESCRIPTION, enumerating available budget types in a concurrent request or Discoverer report, and confirming whether the audit trail is enabled for a given type before relying on audit history. In most production instances the row count is small and static, so the table is a safe candidate for caching in custom reporting or integration layers.

Related Objects

The foreign key relationships documented for this table identify the dependent objects that reference it, and the general ledger schema supplies the adjacent objects used in reporting:

• GL_BUDGETS — references GL_BUDGET_TYPES through GL_BUDGETS.BUDGET_TYPE. This is the primary dependent table, holding budget header definitions.
• GL_BUDGET_VERSIONS — references GL_BUDGET_TYPES through GL_BUDGET_VERSIONS.BUDGET_TYPE. Budget versions (and, in turn, budget lines and balances) are scoped by budget type.
• GL_BUDGET_TYPES_PK — the primary key constraint on BUDGET_TYPE that governs uniqueness and enforces the parent side of both foreign keys.
• GL_BUDGET_TYPES_U1 — the unique index on BUDGET_TYPE, the documented business-key candidate.

In practice, budget journals, budget balances, and budget organizations are reached through GL_BUDGETS and GL_BUDGET_VERSIONS rather than through direct foreign keys to GL_BUDGET_TYPES. Implementations should treat GL_BUDGET_TYPES as read-mostly reference data and avoid direct DML; budget types are normally created and maintained through the General Ledger budgeting setup forms and the standard budgeting APIs.