Our project R/3 impl going on APO can impl or after R/3 than APO can impl.

[Former Member]

Hi All,

In Our project R/3 impl going on APO can impl or after R/3 than APO can impl.

can u explain when should comes in picture.

[Former Member]

Prasad,

Expert Amol's points supporting parallel implementation are all well taken. One additional point that he did not mention is that of 'project fatigue'. Once R/3 is implemented, there is less desire on the part of the business community to implement 'yet another' module of SAP (APO) later.

Here some points for using the other approach (first R/3, then APO).

1. Scratch R/3 implementation is a huge task by itself. Depending on what modules in APO are also to be implemented, simultaneous implementation of APO adds to the project complexity, and it becomes harder to control. Expert resources who understand the nuances of your business, and also understand the SAP software, are typically in very short supply. It is hard to keep their efforts from being diluted when they are asked to participate in so many decisions.

2. During implementation of R/3, the business community typically will re-think their business processes several times during the R/3 implementation. Each revision of the business process entails adjustments of the SAP solution design. If you can settle your business processes before implementing APO, then the APO design is less likely to need multiple revisions.

3. Intelligent implementation sequencing can reduce (but not eliminate) the duplicated effort. For instance, implementing PP in R/3, and then later implementing PP/DS in APO, is a fairly trouble-free implementation, since so much functionality is the same, and the R/3 work would have to be done in any case. Deferring/eliminating R/3 SOP or LTP implementation in lieu of a later DP and SNP implementation in APO means that much of the R/3 effort will not need to be done at all. Implementing ATP in R/3 first allows the user community to begin to understand how SAP ATP works, and gives them a basis for deciding if and how APO GATP is to be implemented.

Best Regards,

DB49

[Former Member]

Hi

I think ist good idea to do R3 and APO implementation parallel.

For APO , R3 is always source of master data. During the parallel implementation itself only you can do the respective master data migration which will avoid duplicate efforts.

If you are not implementation APO, you are require to implement some planning logic or process for your business case which can be scrap after you starting using APO. This will again add your efforts. These are the few benefits. In our case which is Pharma industry , we preferred to implement do R3 and APO parallel.

Please let us know if it helps you. Please also let us know if you require any more information.

Thanks

Amol