You are on page 1of 6

1/23/2020 Document Display

Copyright (c) 2020, Oracle. All rights reserved. Oracle Confidential.

Fusion Assets Data Conversion Suggestions (Doc ID 2052502.1)

In this Document

Purpose
Scope
Details

Definitions
Preparation?
How to prepare the setup for legacy data conversion?
Which method should be used to convert legacy data?
How to convert with accumulated depreciation?
What about YTD_DEPRN column, how to fill it?
How do I convert legacy data into the Tax Book?
I have converted the Assets. What is next?

How to reconcile the data conversion?


Which reports can I use?
What about the balances in Oracle General Ledger?
References

APPLIES TO:

Oracle Fusion Assets - Version 11.1.11.1.0 and later


Oracle Fusion Assets Cloud Service - Version 11.1.11.1.0 and later
Information in this document applies to any platform.

PURPOSE

This document is a guide to support consultants and customers during data conversions.experience.

SCOPE

This outlines the preparation for and the methods to follow to to do data conversions into Fusion Assets.

DETAILS

Definitions

Interface FA_MASS_ADDITIONS

Between Fusion Payables and Fusion Assets there is the interface FA_MASS_ADDITIONS. This interface is not only used to
transfer invoice lines from Payables to Assets. One can also use this interface to load legacy assets into Oracle Assets. The
distributions for the rows in table FA_MASS_ADDITIONS are stored in table FA_MASSADD_DISTRIBUTIONS.

https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-state=15kn0ck6wj_4#aref_section311 1/6
1/23/2020 Document Display

OER FBDI Templates

In the Oracle Enterprise Repository (OER) one can find File Based Data Import (FBDI) templates which are intended for the
use for Cloud/SaaS, but can also be used for On Premise, for the data of the legacy assets to be imported and posted.To find
the Fixed Asset Mass Additions Import template one can enter Search String Asset, pick Type File Based Data Import, and pick
the relevant Release and then click the search button on the left-hand side. Under the Details tab displayed one can download
the XLSM Template: FixedAssetMassAdditionsTemplate.xlsm. There are also templated available for other mass transactions
for Fusion Assets in OER.

ADFdi Template

One can also use the Additions template for the (ADF Desktop Integrator) to enter and upload the legacy assets data. ADFdi
is a Desktop Tool using Microsoft Excel to load (mass) transaction data into the application.

SQL*Loader

Oracle offers several ways to load legacy data into the Assets interface FA_MASS_ADDITIONS. One of them is the
SQL*Loader. Examples and instructions can be found in the Oracle EBS Open Interfaces Manuals. Note: SQL*Loader cannot be
used by Cloud/Software-as-a-Service (SaaS) customers.

Additions API

The Applications Programming Interface (API) can be used for On Premise to create assets and do adjustments though
PL/SQL rather than though the normal Oracle Assets interfaces or through the pages. Note: APIs cannot be used by
Cloud/Software-as-a-Service (SaaS) customers.

Preparation?

How to prepare the setup for legacy data conversion?

Fusion Assets should be set up. Use the Check Setup Diagnostics to verify the setup as explained in Diagnostics: Validations
for Fixed Assets Setup (Doc ID 1338395.1). The Diagnostics will check your Assets setup and tell you in the output if there are
any issues to be found. Oracle Support can give you advice on how to rectify the issues if there are any found.

As Oracle Assets has it's own calendar, you are not forced to convert your assets legacy data at a certain point in time. As
most legacy systems will give you complete data after closing the last period of a fiscal year, the best period to start with in
Oracle Assets is therefore the first period of the next fiscal year. (Please see the section on tax books for tax book conversion).

When you add an asset, the system creates a record in tables FA_DEPRN_SUMMARY and FA_DEPRN_DETAIL with the
DEPRN_SOURCE_CODE B respective BOOKS with the period prior to the addition, which shows that the record was not created
by a depreciation run. So when you convert with accumulated depreciation, you load with the accumulated depreciation taken
in the legacy system, which Oracle Assets then saves in the B row with the period counter for the previous period.

Which method should be used to convert legacy data?

The assets can be either added through the FA_MASS_ADDITIONS interface or manually through the Additions pages.

The decision, which route to take, depends on the number of assets to be converted. A handful can easily be entered, but for
more assets one needs to look into the options listed above.

https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-state=15kn0ck6wj_4#aref_section311 2/6
1/23/2020 Document Display

There are 3 ways to load assets: you can use the ADFdi (ADF Desktop Integrator) Template/OER Templates and upload assets
via the spreadsheet into the interface, one can use the SQL*Loader and load the asset via a flat file into the interface, and one
can use the Additions API to create assets. The OER Templates were created for Cloud, but can also be used on premise. The
Fusion Assets OER Templates contain a sheet with the Instructions and CSV Generation.
The Additions API lets you create assets directly via PL/SQL rather than through the normal Oracle Assets interfaces.

Note: SQL*Loader and API cannot be used on Cloud.

With all methods you have the option to tell the system the accumulated depreciation or let the system calculate the
depreciation for you.

How to Add a Manual Asset in Fusion Assets? [Video] (Doc ID 1378167.1)


How to Add an Asset via Spreadsheet? [Video] (Doc ID 1378112.1)

How to convert with accumulated depreciation?

When loading assets into the interface with accumulated depreciation and ytd depreciation you have to be aware of the
following fields:
Amortize - Yes/No
Amortization Start Date -Date from the current open FA period

Unless you are using a depreciation method based on cost or table-based, it is very important that these columns are filled, as
the system will then know that you want the system to continue calculating depreciation based on net book value (NBV). If
you do not fill these columns, the system will calculate depreciation based on cost ignoring the accumulated depreciation
already taken in the legacy system.

Note: If you are using flat rate, table-based or formula depreciation based on cost, there is no need to load the assets as
amortized, but if STL is used, then the addition should be amortized.
In General, it does not make a difference if depreciation is calculated as cost / life or NBV / remaining life, but if transactions
were performed in the legacy system which altered the cost / life accumulated depreciation, then the system will calculate a
depreciation catchup either when an expensed adjustment is performed or, depending on the settings, in the last period of the
fiscal year. Usually the largest assets have this situation and thus the surprise can be rather unpleasant when the catchup is
created.

White Paper - Subledger Accounting Setup for Oracle Fusion Assets (Doc ID 1396942.1) - 12. Asset Depreciation Book -
Annual Depreciation Rounding

What about YTD_DEPRN column, how to fill it?

The column YTD depreciation cannot be left at 0.00 if the column deprn_reserve is filled or the values can be equal to the
depreciation reserve/accumulated depreciation.
When posting the Mass Additions, the system creates a record in tables FA_DEPRN_SUMMARY and FA_DEPRN_DETAIL with
the DEPRN_SOURCE_CODE B respective BOOKS with the period prior to the addition, which shows that the record was not
created by a depreciation run. This record and the corresponding record in table FA_BOOKS is the basis for the calculation of
the first depreciation.

Depreciation in Oracle Assets is always calculating the yearly depreciation and then spreads it over the periods in the year.
With the last period of the fiscal year the system checks the accumulated depreciation and also takes into consideration the
year-to-date depreciation. If the ytd_deprn, which the asset was converted, does not match with the accumulated
depreciation, this can lead to unpleasant surprises at the end of the first fiscal year.

To avoid this issue it is easiest to convert into the first period of a fiscal year with the balance of the previous fiscal year from
the legacy system. This means that YTD_DEPRN and DEPRN_RESERVE can have the same amount.
https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-state=15kn0ck6wj_4#aref_section311 3/6
1/23/2020 Document Display

A YTD DEPRN of zero or equal to accumulated depreciation should be fine if the open FA period when the asset is added is the
first period of the fiscal year.

How do I convert legacy data into the Tax Book?

Initial Mass Copy copies all the assets added to your corporate book before the end of the current tax fiscal year into the open
accounting period in your tax book.

With Periodic Mass Copy Fusion Assets copies new assets and transactions you made in your corporate book during one
accounting period in the current fiscal year into the open period of your tax

book. You can run periodic mass copy on a daily basis, allowing tax books to be synchronized daily with the corporate book
activity.

Once the 'Allow Reserve Adjustments' feature is available in Fusion Assets, when setting up a tax book you should set the
open period to the last period of the previous fiscal year (so 1 period prior to the start period of the corporate book) and
depreciate it 'empty'. Why? In the tax book one will have the possibility to adjust the depreciation for a previous fiscal year. To
be able to use this functionality, the first depreciation run must be in the previous fiscal year.

So after having depreciated the last period in the fiscal year empty and having loaded the assets into the corporate book into
the first period of the new fiscal year and closed the period you can Periodic Mass Copy the converted assets into the tax
book. The accumulated depreciation is NOT copied from the corporate book. So again you now have several options on how to
proceed:

1) Run the initial mass copy program, or later the Periodic Mass Copy.
2) Then use FDI or FBDI cloud sheet to update the information for these assets then run the Post Adjustments Process.

Please note that just like in the corporate book, a backdated expensed addition will generate a depreciation catchup. So you
may consider to make sure to leave the 'Copy amortized additions and adjustments as expensed' check box in the Manage
Asset Book page for the tax book unchecked if you add the assets in the corporate book amortized and you also do not want a
depreciation catchup in the tax book.

How to Migrate Data to a Tax Book ? (Doc ID 1949776.1)


What is the way to convert Tax Book Assets In Fusion that is comparable to the Tax Upload (FATAXUP) process in EBS? (Doc
ID 1947952.1)
How Do You Copy All Adjustments to the Tax Book (E.G. Life in Months Changes) for Changes and Adjustments That Are
Currently Not Transferred? (Doc ID 1944532.1)
Yearly Depreciation And Closing Balance Reports For Tax Books (Doc ID 1959242.1)
Not Able To Perform Initial Mass Copy As Well As Periodic Mass Copy - No book in the LoV (Doc ID 2031560.1)

I have converted the Assets. What is next?

How to reconcile the data conversion?

One can do the conversion, depreciate without closing the period, create the journals and then add the assets from Payables,
run depreciation to and close the period and then create the journal for the new assets from Payables. (Create Accounting)

How do you reconcile now:

Do the assets in Oracle Assets match the assets in the legacy system?
Do the balances match with those from the legacy system?
https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-state=15kn0ck6wj_4#aref_section311 4/6
1/23/2020 Document Display

Do the balances match with those converted into Oracle General Ledger?

Which reports can I use?

First it is good to check the data converted. These reports are useful for this task:

Asset Additions Report- This report can be used to reconcile the balance on the cost accounts in Oracle General Ledger
with the balance in Oracle Assets. The report does NOT reflect any adjustments in the period of addition, only the data of the
original addition. The report displays among others the following two columns:

Initial Cost: This column matches the Additions column of the Cost Detail report for
your capitalized assets, and the Additions column of the CIP Detail report for your CIP
assets if the report is run for the period prior to capitalization. This column reflects the
cost of the asset in the period it was added to the system.

Initial Depreciation Reserve: The amounts in this column match the Additions column
of the Reserve Detail Report for your capitalized assets. This column reflects the
depreciation reserve of the asset in the period it was added to the system, so the reserve loaded.

Asset Register Report- One page per asset with all data available. This is tedious for thousands of assets, so not really
recommended to reconcile the complete data conversion.

The following 3 (6 respectively) reports should be used also for regular monthly reconciliation:

Cost and CIP Detail and Summary Reports, Reserve Detail and Summary Reports - These reports can be used to
check data integrity and to reconcile account/cost center balances within Oracle Assets and also with Oracle General Ledger.
Should they show a * on the right side, please contact Oracle Support and upload the report output and the corresponding
asset trace to your service request. Create Accounting needs to have been run at least in draft mode for the period for which
the report has been run and for the Reserve Detail/Summary Report depreciation also needs to have been run at least without
closing the period to obtain correct output results.

What about the balances in Oracle General Ledger?

Should the reports reconcile, you can go ahead and run depreciation and create journal entries for GL. For audit purposes I
would advise to post the addition journal. You will then have to reverse the addition journal in order to avoid duplicated
balance amounts on your cost accounts.

If you let Oracle Assets calculate your accumulated depreciation, you will have to enter a manual adjustment journal in
General Ledger to correct the then too high balance on expense and reserve. You already have a converted balance on the
reserve account in General Ledger. If you added your legacy assets with reserve, then you can post and do not have to
reverse the depreciation journal, as it will only contain the current month depreciation.

So, congratulations, you have now successfully completed your legacy data conversion. Stop!This conversion was only done in
your test environment. As everything went well, you can now repeat the procedure in your production environment.

Fixed Asset Beginning Balances - Data Conversion (Doc ID 2011242.1)

REFERENCES

NOTE:2011242.1 - Fixed Asset Beginning Balances - Data Conversion


NOTE:263393.1 - Oracle Assets Data Conversion Release 11.5 (11i) and 12 Suggestions
NOTE:1378167.1 - How to Add a Manual Asset in Fusion Assets? [Video]
https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-state=15kn0ck6wj_4#aref_section311 5/6
1/23/2020 Document Display

NOTE:1378112.1 - How to Add an Asset via Spreadsheet? [Video]


NOTE:1396942.1 - White Paper: Subledger Accounting Setup for Oracle Fusion Assets
NOTE:1338395.1 - Diagnostics: Validations for Fixed Assets Setup
NOTE:1949776.1 - How to Migrate Data to a Tax Book ?
NOTE:1947952.1 - What is the way to convert Tax Book Assets In Fusion that is comparable to the Tax Upload (FATAXUP)
process in EBS?
NOTE:1959242.1 - Yearly Depreciation And Closing Balance Reports For Tax Books
NOTE:2031560.1 - Not Able To Perform Initial Mass Copy As Well As Periodic Mass Copy - No book in the LoV
Didn't find what you are looking for?

https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-state=15kn0ck6wj_4#aref_section311 6/6

You might also like