Transfer Back-dated to DPIS (Date Placed In Service) is Not Moving Expense Nor YTD to New Distribution (Doc ID 1495290.1)

Last updated on DECEMBER 05, 2016

Applies to:

Oracle Assets - Version 12.1.3 and later
Information in this document applies to any platform.
YTD
Year-To-Date
Back-dated

Symptoms

Multiple transfers in the same period provide unexpected depreciation results. The asset expense catchup from addition (or Year To Date - YTD) is left on the original distribution.

Example:

For the asset life the asset has 4 distribution ids (1 each from Addition, Curr Pd Transfer, Curr Pd Transfer #2, Back-dated transfer)


Let us call them D1, D2, D3 and D4

Distribution Id : D1
Distribution Id : D2
Distribution Id : D3
Distribution Id : D4

And their life span is as follows.

D1 : 01-Sep-2010 to 01-Dec-2010
D2 : 01-Dec-2010 to 01-Dec-2010
D3 : 01-Dec-2010 to 01-Dec-2010 (Backdated to 01-Sep-2010)
D3 : 01-Sep-2010 to

When a transfer happened between D1 to D2, it was a current period transfer. So, only reserve is transferred. Expense and YTD remains with D1 only.

And again D2 to D3 transfer happened with current period. Here too only reserve is transferred.
Now D3 to D4 transfer is from DPIS. But D3 had only reserve part with it (YTD and Expense didn't move with initial current period transfer).
When D3 didn't have any expense part, there is no expense available to back out (same is true for YTD).
Due to this reason, no expense, nor YTD transferred to D4.  They remain on D1 where they booked.

System is working as expected.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms