EAM: AM_AMAEDIST creates incorrect RET and LPY Leased Asset Accounting Entries (Doc ID 1368248.1)

Last updated on SEPTEMBER 15, 2016

Applies to:

PeopleSoft Enterprise FIN Asset Management - Version 8.9 and later
Information in this document applies to any platform.
***Checked for relevance on 18-Dec-2013***

Symptoms

In release 8.9, a leased asset was added with one date, but with a later transaction date. Later the asset was retired and accounting entries generated, but not as expected.

Steps to replicate:
1. Add an leased asset with trans date 9/2010, accounting date 10/2010, HY convention.
2. Run AM_DEPR_CALC.
3. Run AM_AMAEDIST.
4. Run AM_DPCLOSE for the accounting period
5. Retire the asset.
6. Run AM_AMAEDIST
7 Run AM_DPCLOSE for the period retired.

Expected results:
Retirement entries should bring the asset cost to 0.

Actual Results:
During a retirement the obligation account 20995 is supposed to be brought to zero.
In this case, AM calculated $32,379.00 to bring the 20995 account to a balance of (1,137.73).
This difference is comprised of three separate items.
1. The missing LPY from 9-2010 ----- 562.83
2. The missing LPY from 4-2011 ----- 574.72
3. A known rounding issue during retirement ----- .18

Account 71921 Lease Payable
During the initial addition, the 9-30-2010 LPY entries were not created.
AM breaks out the interest and obligation for each payable.
This difference is comprised of two items.
1. The missing LPY from 9-2010 ----- (562.83)
2. The missing LPY from 4-2011 ----- (110.45)

Account 72513 Interest Expense
During the initial addition, the 9-30-2010 LPY entries were not created.
This difference is comprised of one item.
1. The missing LPY from 9-2010 ----- 110.45


The problems:
1. The missing LPY from the initial entry.
2. The use of a not allowed lease payment in the retirement calculation
3. The rounding issue where AM rounds up to the nearest whole dollar leaving the accounting entries out of balance. This out of balance flows all the way to the GL and causes the JE to err out.

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