EAM: Mass Transaction Manager (MTMTOOL) for IntreUnit Transaction Validates the Bonus Depreciation Date Range Against the Wrong Dates.
(Doc ID 2879003.1)
Last updated on JUNE 24, 2022
Applies to:
PeopleSoft Enterprise FIN Asset Management - Version 9.2 to 9.2 [Release 9]Information in this document applies to any platform.
Symptoms
Mass Transaction Manager for InterUnit Transfer validates the Bonus Depreciation date range against the wrong dates.
Users were making few mass interunit transfers using the Mass Transaction Manager (MTMTOOL) and noticed for few assets, encountered error below in the transaction loader program
when the assets that were being transferred all had valid dates on one of their tax books and that where in range with the depreciation bonus setup.
This issue has been noted to be only happening specifically with using Mass Transaction Manager.
When the same asset was transferred individually, no issue was encountered.
It appears that the process validates the date against the PS_ASSET In-Service Date and Acquisition Date, instead of validating against the PS_BOOK table.
Error/s:
Steps to replicate:
- Set up Depreciation Bonus.
(Set Up Financials/Supply Chain > Product Related > Asset Management > Depreciation > Depreciation Bonus)
Depreciation Bonus = 14
Bonus Percent
Use same date for both - option selected
Acquisition & In-Service From = 09/27/2017
Acquisition & In-Service To = 12/31/2020
- For Business Unit = US001, Allow duplicate tag numbers.
(Set Up Financials/Supply Chain > Business Unit Related > Asset Management > Asset Management Definition)
1. Populate and upload ExcelToCI for Book CORP.
Interface ID = 99300022
Note:
For Book CORP:
In Service Date = 5/1/2021
Acquisition Date = 5/1/2021
(Note: Dates outside Depr Bonus date range, but this row does not have Depr Bonus/Percent populated)
2. Run Load into to AM process (Interface ID = 99300022). Run Status = Success.
(Asset Management > Send/Receive Information > Interface Transactions > Load into AM)
3. Access Review Interface Transactions to review the Interface ID = 99300022.
(Asset Management > Send/Receive Information > Interface Transactions > Review Interface Transactions)
Business Unit = US001
Asset ID = 000000000256
Load Status = Loaded
Note:
For the rest of the Books:
In Service Date = 12/29/2020
Acquisition Date = 12/29/2020
(Note: Dates within Depr Bonus date range)
For Books FEDERAL and AMT:
Depreciation Bonus = 14
Depreciation Bonus Percent = 100.0
4. Run Load into to AM process (Interface ID = 99300023, 99300024, 99300025). Run Status = Success.
5. Access Review Interface Transactions to review the Interface ID = 99300023, 99300024, 99300025.
Business Unit = US001
Asset ID = 000000000256
Load Status = Loaded
6. Now, Run Mass Transactions IUT (Inter Unit Transfer) for Asset 256 from BU US001 to US003. Run status = Success.
(Asset Management > Asset Transactions > Mass Transactions > Run Mass Transactions)
Interface ID 10000062
7. Load into AM. Run AMIF1000. Run Status = Success.
8. Review Interface Transactions:
Trans Load Type:
US001 (IUT Out)
US003 (IUT In)
Load Status = Errored
All four (4) books for US001 (IUT Out):
1 Correct the related transactions before running this interface transaction again.
2 Valid In-Service and Acquisition dates must be entered to be able to use this Bonus Percent.
Change the In Service and Acquisition Dates of the transaction or Update the Depreciation
Bonus Information in the profile of the asset accordingly.
All four (4) books for US003 (IUT In)
1 Correct the related transactions before running this interface transaction again.
2 Valid In-Service and Acquisition dates must be entered to be able to use this Bonus Percent.
Change the In Service and Acquisition Dates of the transaction or Update the Depreciation
Bonus Information in the profile of the asset accordingly.
Test using the individual/online interunit transfer feature.
1. Navigate to Cost Adjust/Transfer Asset and make an InterUnit Transfer action_
2. Make a transfer from BU US001 to US002.
Result: InterUnit transfer successful.
See replication screenshots here.
NOTE: In the <images or examples> <above or below> and/or the attached document, user details / customer name / address / email / telephone number represent a fictitious sample (based up made up data used in the Product name test environment). Any similarity to actual persons, living or dead, is purely coincidental and not intended in any manner.
Changes
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
Symptoms |
Changes |
Cause |
Solution |
References |