What is the Recommended Approach for Converting Assets Into Asset Management?
(Doc ID 2629946.1)
Last updated on JULY 21, 2020
Applies to:PeopleSoft Enterprise FIN Asset Management - Version 9.2 to 9.2 [Release 9]
Information in this document applies to any platform.
Q&A on converting Assets into Asset Management:
Qn1: What is the recommended approach for converting assets from another application with all transactions (ADD, ADJ, RET, etc) into Oracle/PeopleSoft?
1. In order to load Asset transaction details into PeopleSoft Asset Management, the following 3 interface tables need to be populated - INTFC_FIN, INTFC_PHY_A and INTFC_PHY_B.
2. Will INTFC_TYPE field in INTFC_FIN record differentiate between different types of transaction rows?
3. Is there any specific sequence that should be followed when loading all transactions rows together for an asset during conversion?
4. What other precautions do we need to take, if any?
Qn3: What precautions should be taken when assigning Interface IDs for the conversion rows? Should the new intfc_id assignments start with the last used intfc_id or 1?
Qn4: The plan it to load conversion assets to a pre-production environment and then move the rows into production via DMS scripts after validation. There are approximately 50k assets to convert.
1. Is there any challenge related to this approach?
2. Which tables should be loaded with the DMS scripts?
Qn5: Should each row in the INTFC_FIN table have a corresponding row in the INTFC_PHY_A table? When loading multiple transactions (ADJ, RET etc.) and inserting rows into INTFC_FIN, should a corresponding row be inserted into INTFC_PHY_A table?
Qn6: Can PSFT provide a list of all AM tables loaded by the AMIF1000 process?
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