How Fusion's multi-book fixed assets — corporate and tax books, depreciation methods, CIP capitalisation, group assets, revaluation, and mass transactions — translate to D365 Fixed Assets, and how Oracle Maintenance Cloud compares to D365 Asset Management for functional locations, maintenance assets, and work orders.
Oracle Fusion Assets manages the full fixed-asset lifecycle: asset creation (manual, via Mass Additions from Payables, or capitalised from capital projects), parallel accounting through multiple asset books, periodic depreciation, revaluation, impairment, retirement, and reinstatement.
An Asset Book is the accounting and reporting container for fixed assets. Fusion supports multiple books per asset, each with its own chart of accounts, depreciation method, useful life, and GL posting configuration:
D365 Fixed Assets expresses the same structures through a parallel but differently named set of objects.
In Fusion, a capital project accumulates construction costs in CIP GL accounts as expenditure items are entered against the project. The SLA engine processes each expenditure item and posts a debit to the CIP account (Account Rule configured for the capital project's expenditure type) and a credit to the cost-clearing account.
Fusion Assets supports revaluation — adjusting an asset's gross cost (and accumulated depreciation) to reflect current market values, typically required under IFRS for property, plant, and equipment. A revaluation write-up increases the asset's gross cost and creates a credit to a revaluation reserve equity account;
Oracle Maintenance Cloud (OMC) manages the physical maintenance lifecycle of assets: Functional Locations (the physical position in the plant or facility where an asset is installed), Maintenance Assets (the individual physical items being maintained), Maintenance Plans (scheduled preventive maintenance programmes), Service Requests (ad…
Fusion Assets and Oracle Maintenance Cloud cover the same territory as D365 Fixed Assets and D365 Asset Management respectively. The mapping is close in most areas; the gaps require explicit design decisions before the asset-domain loads begin.