EAM: Missing LO (Lease Obligation) if Lease Retired with Add Date
Last updated on SEPTEMBER 15, 2016
Applies to:PeopleSoft Enterprise FIN Asset Management - Version 9 to 9 [Release 9]
Information in this document applies to any platform.
In release 9.0, Bundle #37, Demo, after retiring a leased asset with the same date as the add, the resulting accounting entries were missing an offset to the LO (Lease obligation) account.
Unbalanced entries for LO.
Steps to replicate:
1. Add a leased asset to BU FRA01, profile LeasedCar, dates 04/24/2015. Lease term 36 periods, interest rate 3%, MRP 1000, Advance. Save.
2. Run am_depr_calc.
3. Retire the asset, changing the type to Retire As Scrapped. Leave the same dates as the Add. Save.
3. Run am_depr_calc.
4. Run am_amaedist.
Expected an offsetting entry to the LO account created for the Add.
Did not get an entry for LO.
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