Results for “fa_budget_distribution”

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

Overview

FA_BUDGET_DISTRIBUTION is a core Oracle Assets (OFA) table that stores capital budget distribution information entered manually through the Assets application or uploaded in bulk from the FA_BUDGET_INTERFACE staging table. It resides in the FA schema and holds the detailed allocation of a capital budget across accounting flexfield combinations, asset categories, and depreciation books. The table is therefore central to tracking how budgeted capital amounts are distributed for planning and reporting purposes within Oracle E-Business Suite 12.1.1 and 12.2.2.

The table carries 23 documented columns and is protected by a composite unique index, FA_BUDGET_DISTRIBUTION_U2, defined on (BOOK_TYPE_CODE, CODE_COMBINATION_ID, CATEGORY_ID). A second unique index, FA_BUDGET_DISTRIBUTION_U1, enforces uniqueness on BUDGET_ID itself, which also serves as the primary key via FA_BUDGET_DISTRIBUTION_PK.

From a Data Vault modeling perspective, the foreign key and unique index structure suggests a satellite-leaning classification: FA_BUDGET_DISTRIBUTION hangs off FA_CAPITAL_BUDGET and enriches it with descriptive distribution attributes (book, category, and accounting combination), rather than acting as an independent hub or a pure transactional link.

Key Information Stored

The most significant columns and their roles are:

• BUDGET_ID — the surrogate primary key (FA_BUDGET_DISTRIBUTION_PK) and unique business identifier.
• BOOK_TYPE_CODE — identifies the depreciation book; a foreign key to FA_BOOK_CONTROLS and part of the composite unique index U2.
• CODE_COMBINATION_ID — the accounting flexfield combination for the budget line; foreign key to GL_CODE_COMBINATIONS and part of U2.
• CATEGORY_ID — the asset category; foreign key to FA_CATEGORIES_B and part of U2.
• LAST_UPDATE_DATE, LAST_UPDATED_BY, LAST_UPDATE_LOGIN — the standard audit who/when columns used for change tracking and interface reconciliation.
• ATTRIBUTE_CATEGORY_CODE — the descriptive flexfield context segment.
• ATTRIBUTE1 through ATTRIBUTE15 — the fifteen descriptive flexfield segments used to capture client-defined budget attributes.

In short, BUDGET_ID is the surrogate key, while the (BOOK_TYPE_CODE, CODE_COMBINATION_ID, CATEGORY_ID) triplet forms the natural business key.

Common Use Cases and Queries

Typical applications include capital budget reporting by book, category, or accounting combination; reconciliation of uploaded budgets against FA_BUDGET_INTERFACE; and validation of budget distributions before posting to General Ledger. A representative join query follows:

• Retrieve all distributions for a budget, joined to budgets, categories, and books:
  SELECT fbd.budget_id, fbd.book_type_code, fbd.category_id, fbd.code_combination_id FROM fa_budget_distribution fbd JOIN fa_capital_budget fcb ON fcb.budget_id = fbd.budget_id JOIN fa_categories_b fc ON fc.category_id = fbd.category_id JOIN fa_book_controls fbc ON fbc.book_type_code = fbd.book_type_code WHERE fcb.budget_id = :p_budget_id;
• Summarize budgeted amounts by accounting combination for GL reconciliation:
  SELECT code_combination_id, COUNT(*) dist_count FROM fa_budget_distribution GROUP BY code_combination_id;
• Audit recent changes using LAST_UPDATE_DATE and LAST_UPDATED_BY.
• Detect distributions that lack a valid GL_CODE_COMBINATIONS reference after upload.

Related Objects

The following objects are the most closely linked to FA_BUDGET_DISTRIBUTION through documented relationships:

• FA_CAPITAL_BUDGET — parent budget table; joined on FA_CAPITAL_BUDGET.BUDGET_ID = FA_BUDGET_DISTRIBUTION.BUDGET_ID.
• FA_BOOK_CONTROLS — referenced via BOOK_TYPE_CODE.
• FA_CATEGORIES_B — referenced via CATEGORY_ID.
• GL_CODE_COMBINATIONS — referenced via CODE_COMBINATION_ID.
• FA_BUDGET_INTERFACE — the staging table from which budget distributions are uploaded.

Together these objects support the complete capital budgeting cycle within Oracle Assets.