Results for “fa_capital_budget”

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

Overview

FA_CAPITAL_BUDGET is a transaction-level table in the Oracle Assets (OFA) module that stores budget asset records used to run depreciation projections, forecast reports, and capital planning exercises. In Oracle E-Business Suite 12.1.1 and 12.2.2, the table resides in the FA schema and is documented as VALID with an ETRM description of "Budget assets used to run depreciation projections and reports." Unlike the production asset tables that drive the fixed asset register, FA_CAPITAL_BUDGET holds simulated or forward-looking asset data that can be projected through depreciation engines without committing entries to the corporate books.

From a Data Vault modeling perspective, the mined foreign-key structure classifies this object heuristically as a link. The table does not represent an independent business entity but rather an associative relationship that binds a budget definition, a period sequence, a book, an asset, and optionally a transfer transaction or distribution record. This classification is a modeling suggestion derived from the FK topology, not a formal Oracle designation.

Key Information Stored

The physical schema documents 24 columns, of which a compact subset carries the substantive business content:

• BUDGET_ID — Identifier of the parent capital budget; also the leading column of the composite primary key and the FK to FA_BUDGET_DISTRIBUTION.
• PERIOD_NUMBER — The fiscal period within the budget horizon; forms the second component of the composite key.
• PERIOD_COST — The projected depreciation or cost amount attributable to the asset for that period, and the principal measure column.
• ASSET_ID — References FA_ADDITIONS_B, tying the budget row to a specific asset.
• BOOK_HEADER_ID — References FA_BOOKS, indicating the depreciation book against which the projection is evaluated.
• TRANSFER_HEADER_ID — References FA_TRANSACTION_HEADERS, allowing budget rows to model transfers in or out.
• DISTRIBUTION_ID — References FA_DISTRIBUTION_HISTORY, supporting multi-distribution cost allocation.
• QUARTER_NUMBER — Denormalized quarter indicator used for quarterly rollups.
• ATTRIBUTE_CATEGORY_CODE and ATTRIBUTE1–ATTRIBUTE15 — The standard Oracle EBS descriptive flexfield segments, available for client-specific budget extensions.

The surrogate primary key is FA_CAPITAL_BUDGET_PK, defined on (BUDGET_ID, PERIOD_NUMBER). A unique index, FA_CAPITAL_BUDGET_U1, mirrors the same (BUDGET_ID, PERIOD_NUMBER) combination, confirming the composite key as the documented business-key candidate.

Common Use Cases and Queries

Resource planning, capital expenditure forecasting, and what-if depreciation analysis are the primary scenarios. Analysts typically aggregate PERIOD_COST by budget, book, or period, and reconcile budgeted asset populations against the live asset register. A representative projection query joins the table to its parent budget and books:

SELECT cb.budget_id,
       cb.period_number,
       fb.book_type_code,
       SUM(cb.period_cost) projected_cost
FROM   fa_capital_budget cb,
       fa_books fb
WHERE  cb.book_header_id = fb.book_header_id
GROUP  BY cb.budget_id, cb.period_number, fb.book_type_code
ORDER  BY cb.budget_id, cb.period_number;

A second common pattern correlates budget rows to real assets to detect assets present in the budget but absent from the register:

SELECT cb.asset_id, cb.period_number, cb.period_cost
FROM   fa_capital_budget cb,
       fa_additions_b ab
WHERE  cb.asset_id = ab.asset_id
  AND  ab.asset_number IS NULL;

Quarterly rollups leverage QUARTER_NUMBER, and the ATTRIBUTE segments support client-specific reporting through the descriptive flexfield.

Related Objects

• FA_BUDGET_DISTRIBUTION — parent budget definition; joined on BUDGET_ID.
• FA_ADDITIONS_B — asset master; joined on ASSET_ID.
• FA_BOOKS — depreciation book; joined on BOOK_HEADER_ID.
• FA_TRANSACTION_HEADERS — source transactions; joined on TRANSFER_HEADER_ID.
• FA_DISTRIBUTION_HISTORY — cost distribution detail; joined on DISTRIBUTION_ID.

These five FK relationships constitute the table's documented dependency surface and should be the starting point for any integration, reporting, or reconciliation development.