EAM: Mass Transaction Manager - IUT-Inter-Unit Transfer Results to Error -- '1 Combo Edit errors found'
(Doc ID 3062627.1)
Last updated on DECEMBER 10, 2024
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 (MTM) Inter-Unit Transfer results to a chartfield combination edit error.
This was after running Load into AM (AMIF1000) process. In Review Interface Transactions page for Transfer OUT (i.e. BU1 = Pending), for Transfer IN (i.e. BU2 = Errorred).
Error:
Combo Edit error/s found. Your setup requires that you need to correct them before saving
Steps to replicate:
1. Set Up Combo Edit in Ledgers for a Unit for BUs BU1 and BU2.
(Set Up Financials/Supply Chain > Business Unit Related > General Ledger > L/edger for a Unit | Journal Edit Options)
2. Make sure ChartField Edit Option should be Reject w/ edit error for BU1 and BU2 business Units.
(Set Up Financials/Supply Chain > Business Unit Related > Asset Management > Asset Management Definition | Business Unit/Book Definition)
3. Create an asset online following below steps:
(Asset Management > Asset Transactions > Owned Assets > Basic Add)
- Select a Profile ID
- On the Asset Acquisition Tab, enter amount and quantity and click on ‘Capitalize’ Button to Capitalize the asset.
Once clicked on Capitalize button, Capitalization Status is updated to “To be Capitalized”.
- Enter Department value in ChartFields section.
- Enter valid combination for Fund Code, Budget Reference and Product values in ChartFields section.
- Enter valid combination for Budget Reference and ChartField2 values in ChartFields section.
- After providing all the details, save the page. Asset ID gets generated.
4. Run Depreciation Calculation
(Asset Management > Depreciation > Processing > Calculate Depreciation)
Enter below parameters on the run control page and run the process:
• Business Unit
• Asset ID
There are two delivered process for asset depreciation:
• AM_DEPR_CALC (Application Engine)
• AMDPCALC (SQR)
5. Once the process is completed, navigate to below page to verify the depreciation amounts calculated for the asset.
(Asset Management > Depreciation > Review Depreciation Info > Asset Depreciation)
Below Asset ID is referred for IUT (InterUnit Transfer).
• From Agency: BU1
• From Department: xxxxxx
• To Agency: BU2
6. Check the Details for Business Unit – BU1 and Asset ID – 00000000xxxx
(Asset Management > Asset Transactions > History > Review Cost)
7. On the Mass Transaction Manager Run Control Page, selected the Transaction Type as ‘IUT – Inter-Unit Transfer’ and provided all the details for the Asset
(Asset Management > Asset Transactions > Mass Transactions > Run Mass Transactions)
- ID (00000000xxxx).
- Ran the ‘MTMTOOL’ process.
- Once the process went to Success, Interface ID is generated and asset submitted for approval.
- Login with required approver users and approve the asset.
- Asset approved successfully as Approval Pending checkbox is disabled.
8. In Review Interface Transactions, in search criteria enter below details for Inter-Unit Transfer Out Side transaction type:
(Asset Management > Send/Receive Information > Interface Transactions > Review Interface Transactions)
• Interface ID: 1000xxxx
• Business Unit: BU1
- Inter-Unit Transfer Out Side transaction details from Review Interface Transactions page.
In search criteria enter below details for Inter-Unit Transfer In Side transaction type:
• Interface ID: 1000xxx
• Business Unit: BU2
- Inter-Unit Transfer In Side transaction details from Review Interface Transactions page.
- ‘From Business Unit’ (BU1) ChartFields are transferred to ‘To Business Unit’ (BU2).
- Ran Transaction Loader Edit process.
- Process went to Success and Posted.
- Log File: Error generated for Invalid Department.
- Inter-Unit Transfer Out Side transaction status is pending and page saved successfully.
- Inter-Unit Transfer In Side transaction (BU2) load status went into Errored.
- Click on save button, Combo Edit error is triggered for Fund Code, Budget Reference and Product.Activity Guide
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 |