Asset books, tax books and dimension overrides

Translate Oracle Assets into the D365 fixed asset register book by book, keeping construction-in-progress flows distinct from straightforward additions and replacing flexfield segment overrides with asset-level default dimensions.

What you will be able to do

• Map asset categories and books onto D365 fixed asset groups and books
• Review depreciation conventions and tax books individually rather than in aggregate
• Keep construction-in-progress and capitalisation flows distinct in the posting design
• Replace segment-level dimension overrides with asset default dimensions
• Build the net book value and depreciation reserve reconciliation the load gate requires

Introduction

Fixed assets is the most comfortable module on this path, and comfort is its own risk.

Categories, groups and what a group is for

An EBS asset category carries default accounting and default depreciation behaviour for the assets assigned to it. A D365 fixed asset group does the same job, so the mapping is comfortable in principle.

The book-by-book review

This is the part the source guidance singles out, and it deserves the module's most careful attention.

Additions and capitalisation

The asset addition posting rule debits asset cost and credits either an asset clearing account or the payables liability, and the target expresses this through acquisition posting keyed on asset group and book. Its instruction is short and important: keep construction-in-progress-to-capitalisation scenarios distinct.

Depreciation and the dimension override

The depreciation posting rule debits depreciation expense and credits accumulated depreciation, keyed on asset group and book. Straightforward — except for its note, which is the sharpest instruction in this module: asset-level default dimensions must replace segment overrides where used.

Transfers, retirements and the variants worth testing

Asset transfer, disposal by sale and disposal by scrap all correspond conceptually. The variants worth individual testing are the ones whose accounting is easy to get subtly wrong:

Loading and reconciling

Assets load in the fifth wave alongside projects and open production, with a gate requiring asset net book values to agree asset by asset. The asset-by-asset requirement is deliberate: a register-level total can conceal offsetting errors between assets, and offsetting errors are exactly what a convention mismatch produces.

What this module cannot tell you

The source package says nothing about enterprise asset maintenance. Whether the estate manages maintenance in EBS, in a specialist system, or informally is a discovery item, and the target decision between native asset management and a third-party product depends entirely on the answer.

Knowledge check

Summary

Fixed assets translate well, and the source package's confidence reflects that. The risks are specific and named rather than structural.