Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Reply from srikrishna.durbha on Mar 26 at 2:55 AM Hi
Cutover strategy should go on the following lines for PS module for example:
1) How many projects must be uploaded, from which year on?
2) Do you need historical data (Actual costs, planned costs, etc)
3) What is the legacy system and how to extract existing data
4) How do you map legacy data to the new system (New project numbers,
WBS structures, Company code, Plant, cost center, etc)
5) Where do you maintain the mapping files and how the business would
validate and approve the mapping file
6) What is the method to convert the new data (from the mapping file)
to the SAP system (LSMW, BAPI, BDCs etc)
7) How many data conversion mock exercises are required before finally
uploading the same into the Live client
8) Trial balance
Hope this helps.
Regards
Srikrishna
| | | ---------------Original Message---------------
From: HIMANSHU SHEKHAR
Sent: Tuesday, March 26, 2013 12:03 AM
Subject: Cutover Strategy and Sequencing
Hello,
If you can let us know the environment in which project has been
implemented then we can suggest cut-over strategy. Do you have just ECC or
other systems also running in tandem? Are there any constraints of
business that they can go live only on a specific day of the month? Did you
do any sanity check in understanding how many active vendors and customers
business deals with? How many POs will be open at any given point of time
etc.
Any process adopted for consolidating customers and vendors in new system
will impact open items respectively.
Regards,
Himanshu |
| Reply to this email to post your response. __.____._ | In the Spotlight Become a blogger at Toolbox.com and share your expertise with the community. Start today.   _.____.__ |
