At the same time, another project is starting to develop payroll and will be active in beginning 2008. They will...
develop payroll on the first available "upgrade copy" of the upgrade process and will continue their activities up to beginning 2008. Meanwhile, on the basic upgraded 4.6C landscape, we still run the old HR implementation (with external payroll).
We are afraid that the concurrent development in the two projects may quickly become a nightmare, and that sooner or later HR payroll developments will need to be injected as source development of the classic landscape.
What do you advise regarding this situation?
First of all, you will want to implement the new developments in the new release. But this raises two questions.
- How you can do this without proper testing and stabilizing the system after it has been upgraded?
- How will you integrate the new application after the production system has been upgraded?
Of course, in the real world, this might indeed be a nightmare -- especially if both development systems start to differ during the course of time.
Dig Deeper on SAP HR management
Related Q&A from Bert Vanstechelman
An SAP user wants to know the risks of changing time zones in ECC 6.0. Continue Reading
An SAP user wants to know how to access an SAP IDES 4.7 system via the Internet through SAP GUI. Continue Reading
A SearchSAP.com reader wants to know how an increase of indexes and tables after upgrade to SAP ECC 6.0 will affect the memory requirements of a DB2 ... Continue Reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.