Most customers are faced with this difficult choice and get conflicting advice. Our recommendation is that, like all good consultants tell you, is it depends on your situation, specifically where you are at in your SAP implementation or perhaps even if you are doing a SAP ECC implementation at all.
There are really three primary time zones you should know about:
Each of these three implementation time zones has advantages and disadvantages to consider. There are also variations on the time zones, i.e., you may be doing a multi-phase roll-out, so Go-Live is actually a series of events.
|
During |
Immediately After |
6 Months After |
|||
|
Advantage |
Disadvantage |
Advantage |
Disadvantage |
Advantage |
Disadvantage |
|
Can establish Netweaver Environment Earlier. Can actively work with SAP Implementation team to make sure everything is NOT saved for BW. |
ERP Implementation Not Stable. Business processes not actually yielding data to work with. |
Few. Easier to make the transition as some of the SAP ERP implementation may still be onsite doing post implementation support |
Business still very much in transition. Data quality not under control. |
Business Processes stable and Business Content much easier to leverage. SAP BW team can typically handle non BW task with a few SAP Consulting resources |
The SAP ERP implementation team will not be available to make process improvement changes |
Clearly, our recommendation would be to start your SAP BW implementation about 6 months after Go-Live for maximum effectiveness at minimum cost. Others might disagree.
However, you can start your implementation during any of these time zones and still have a successful implementation, but with varying degrees of difficulty.
We have developed an extensive set of SAP Project Management Tips and Hints to help you through both your BW implementation and your core SAP ECC (R/3) implementation.
Appreciate your comments and feedback!
People Who Read This Also Read:
Thanks