28/5/2018 Document Display

Copyright (c) 2018, Oracle. All rights reserved.

FAQ: Oracle Assets 'Upload Tax Book Interface' (FATAXUP) (Doc ID 579666.1)

In this Document

Purpose
Questions and Answers
What is the purpose of the Upload Tax Interface functionality?
What are the steps?
Can the Tax Upload Interface process (FATAXUP) be used to adjust an asset in periods after the period of addition?
Can the Tax Upload Interface Process be run also for Corporate Book?
How Can Current Cost, Accumulated Depreciation, Life and DPIS Be Adjusted in the Corporate Book?
Can an Asset's Depreciate Flag be modified via Tax Upload Interface?
How to perform the Tax Upload Interface transaction as Amortized?
Which columns should be populated in FA_TAX_INTERFACE for updating depreciation method?
Which transaction is created when FATAXUP is run?
Known Bugs in Release 11i
Known Bugs in Release 12
Still Have Questions?
References

APPLIES TO:

Oracle Assets - Version 11.5.10.0 and later

Information in this document applies to any platform.
FAXTAXUP

PURPOSE

This FAQ document identifies the most frequently reported how-to questions related to Oracle Assets 'Upload Tax Book
Interface' functionality.

QUESTIONS AND ANSWERS

What is the purpose of the Upload Tax Interface functionality?

The Tax Book Upload interface table allows you to enter information via SQL.
Once the assets have been added into your tax book, you can change basic financial information such as year-to-date
depreciation, accumulated depreciation reserve, cost and salvage value, for an unlimited number of assets in the tax book.

What are the steps?

1) Populate the FA_TAX_INTERFACE Table.

The required fields are ASSET_NUMBER and BOOK_TYPE_CODE in addition to the columns you want to modify. Set
POSTING_STATUS to POST.
You can find all columns in the Oracle Assets User's Guide.
Note: Only the values you are changing need to be populated, with the exception of the required fields.

https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-state=5d732tvtf_9 1/4
28/5/2018 Document Display

2) Navigate to Other > Requests > Run

Submit the 'Upload Tax Book Interface' concurrent request for your Book.

After this program completes successfully, the posting_status will be POSTED for related records.

The following example shows how you can use the Tax Book Upload feature.
1. You add an asset in the corporate book with an original cost of $100.
2. After running mass copy, the asset now appears in your tax book with an original cost of $100.
3. You want to change the original cost amount in the tax book to $80, so you execute the following SQL script:
insert into fa_tax_interface (asset_number, book_type_code, cost, posting_status)
values (’12345’,’ABCTAX’,80, ’POST’);
4. You run the Upload Tax Book Interface program so that the asset in the tax book now has an original cost of $80.

Can the Tax Upload Interface process (FATAXUP) be used to adjust an asset in periods after the period of
addition?

When the Tax Upload Interface process was initially released, it did have the restriction to only adjust assets in their period of
addition.

However, from patchset level 11i.FA.K and above, it is possible to use the Tax Upload Interface to adjust assets in any period
except that adjusting Original Cost, YTD Depreciation and Depreciation Reserve can only be performed in the period of
addition.

Refer to Note 284586.1 and Note 313400.1.

Can the Tax Upload Interface Process be run also for Corporate Book?

Yes, this is possible after modifying the value set for the FATAXUP program’s Book parameter.

See Note 264408.1 How to Configure the Upload Tax Book Interface Program to Work with Corporate Book.

How Can Current Cost, Accumulated Depreciation, Life and DPIS Be Adjusted in the Corporate Book?

Development has approved the use of the Tax Upload Interface (FATAXUP) introduced
in 11.5.4 for corporate books. The Tax Upload Interface program was originally only available for tax books, but has been
modified so that it can be used for corporate books.
Change the value set name from FA_TAX_BOOK to FA_BOOK_TYPE, to be able to see the Corp book in the LOV.
See Note 264408.1 How to Configure the Upload Tax Book Interface Program to Work with Corporate Book.

Can an Asset's Depreciate Flag be modified via Tax Upload Interface?

If you need to make changes to the Tax Book Upload Interface table that include changes to the DEPRECIATE_FLAG column,
you must upload the changes to the DEPRECIATE_FLAG column separately from other changes.

For example, you cannot upload changes to the COST column and the DEPRECIATE_FLAG column at the same time. You
should make all changes to the asset (excluding changes to the DEPRECIATE_FLAG column) and post them. You can then
delete the original rows in the table, and for those assets requiring a change to the DEPRECIATE_FLAG column, insert new
rows with only the ASSET_NUMBER, BOOK_TYPE_CODE, and DEPRECIATE_FLAG specified. You can also submit the changes
to the DEPRECIATE_FLAG column first before submitting the other changes.

This is not a limitation of tax upload interface but of the adjustment engine.

Refer to Note 221688.1.

How to perform the Tax Upload Interface transaction as Amortized?

https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-state=5d732tvtf_9 2/4
28/5/2018 Document Display

If you want the adjustment to be amortized, you should populate the following columns in addition to the required ones in the
FA_TAX_INTERFACE table:

AMORTIZE_NBV_FLAG=YES
AMORTIZATION_START_DATE= a date in the current open period

Which columns should be populated in FA_TAX_INTERFACE for updating depreciation method?

If you specify a depreciation method in the table, other fields may be required.
For Calculated and Table-based methods, LIFE_IN_MONTHS is required.
For Units of Production methods, PRODUCTION_CAPACITY is required.
For Flat Rate methods, ADJUSTED_RATE and BASIC_RATE are required.

Also note that if you enter values for any of these fields, you must enter the depreciation method name in the
DEPRN_METHOD_CODE column.

Which transaction is created when FATAXUP is run?

In Release 11i, when FATAXUP is run in the period of addition for an asset, the prior ADDITION transaction is voided
(ADDITION/VOID) and a new ADDITION transaction is created.
In Release 12, there are no more Addition/Void transactions. Therefore, the change done via the Tax Upload Interface is
recorded as an ADJUSTMENT transaction.

Refer to Note 473544.1.

Known Bugs in Release 11i

1) Unable to change the salvage value through Tax Upload Interface for assets which have a percentage salvage value
defined.
The Upload Tax Book Interface program completes normally but the percentage salvage value in FA_BOOKS is not overwritten
by the amount specified in FA_TAX_INTERFACE table.

This is Bug 4322967 Tax Upload Interface - Unable to Upload Salvage Value for Salvage Type Percent.

This is fixed in fataxupb.pls version 115.41 and higher.

Refer to Note 309057.1.

2) The FATAXUP process runs in an endless loop when it hits two consecutive records which do not actually update any
financial information.

This is Bug 4690642 Fataxup: Upload Tax Book Interface Is In Endless Looping.

This issue is fixed in fataxupb.pls version 115.42 and higher.

Refer to Note 340555.1.

3) When running Tax Book Interface to enter an adjustment on an asset in Tax Book and modify following values:
YTD_DEPRN
DEPRN_RESERVE
DEPRN_METHOD_CODE
LIFE_IN_MONTHS
AMORTIZE_NBV_FLAG=YES
AMORTIZATION_START_DATE
REVAL_AMORTIZATION_BASIS
REVAL_RESERVE
The transaction is not correctly handled as REVAL_AMORTIZATION_BASIS is not updated with the expected value in both the
FA_BOOKS and FA_DEPRN_SUMMARY tables.

This is Bug 6795070 Upload Tax Book Interface Does Not Update REVAL_AMORTIZATION_BASIS For Tax Book.

https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-state=5d732tvtf_9 3/4
28/5/2018 Document Display

This issue has been fixed in the files fataxupb.pls version 115.44 and FAVCALB.pls version 115.192 available via Patch
6817467.
This patch must be applied over patchset 11iFA.P + Patch 5964970 and Patch 6391392
OR 11iFA.P + Patch 6317575.

Refer to Note 554268.1.

4) Performance issue with Upload Tax Interface.

This is internal unpublished Bug 5705085: Upload Tax Book Interface Running For A Very Long Time.

This is fixed in fadprreg.ldt 115.24

fadpr.odf 115.69
fataxupb.pls 115.43
fataxups.pls 115.6
fataxup.opc 115.22

Please apply Patch 6391392 for 11.5.10 instance with 11i.FA.P.

Known Bugs in Release 12

1) Upload Tax Book Interface runs successfully but does not update YTD depreciation or reserve in period of addition.

This is Bug 6243777.

The adjustment API does not take into account the year-to-date depreciation or depreciation reserve when you adjust the
asset in the period of addition. This impacts the Asset Workbench, Tax Upload and other interfaces that use the Adjustment
API.
This is fixed in FAVADJB.pls version 120.42.12000000.3.
One off Patch 6243777 including this fixed file is now obsoleted and replaced by Patch 6935688.

2) Depreciation is incorrect for assets after running Upload Tax Interface to change reserve of the asset by amortized
adjustment in the period of addition.

This is Bug 6803812.

Refer to Note 560991.1 Upload Tax Interface Fails To Update Deprn_Reserve In Tax Book.

This Bug is fixed in Release 12.0.5.

For Releases 12.0 to 12.0.4, please apply one off Patch 6848159 including fixed file fataxupb.pls version 120.18.12000000.2.

Still Have Questions?

To discuss this information further with Oracle experts and industry peers, we encourage you to review, join or start a
discussion in the My Oracle Support Fixed Assets Community.

To provide feedback on this note, click on the Rate this document link.

Didn't find what you are looking for?

https://support.oracle.com/epmos/faces/SearchDocDisplay?_adf.ctrl-state=5d732tvtf_9 4/4