2936334 - Best Practice activation - move to production

Important: Please note this KBA is meant for Greenfield implementations where the DEV, QAS and PRD systems start with a clean client created as a copy of client 000.

1. Before moving the Activation transports from DEV to QAS, should need to move transports related to Prerequisites notes, Activities performed related to Merged client and Activities related to the activated scope items?
   
   Yes.
   
   
2. How should be set the client currency in DEV and PROD system?
   

   The client currency in QAS and PRD should be set manually which is same as DEV client. (In DEV the currency is set by Best Practices activation, since no Best Practices activation in QAS and PRD, it should be done manually.)

3. Should take care of some parameters like rsdp/max_runtime and heap area, which was set while doing the DEV activation on QAS and PROD system?
   
   No, since there is no Best Practices activation in QAS and PRD.
   
   
4. What should be the sequence of transports (customizing and workbench) go in QAS and PRD?
   
   They should be released in the sequence they are created. Workbench transports can go first and then the customizing.
   
   
5. Should be moved the "Manual rework required" solution from DEV to QAS, that solution needs to be activated manually in QAS and PROD after moving the transports?
   
   Yes. During activation the manual rework required solution in QAS and PRD, the solution builder will create two dummy transports by default, but they will not have any configuration. The activation stops at each manual activity, after performing the activity, needs to be confirmed each of those steps.
   
   
6. Is it necessary to perform manual activity only for the building blocks mentioned in the manual rework guide??
   
   The Manual rework activities depend on the scope items selected in Z solution.
   
   
7. Is it allowed to transport BP activation to an already existing / running productive system?
   
   No. BP activation transport can overwrite existing business processes in some cases. Transport of BP activation to already existing / running client is not supported. 
   
   
8. How to avoid transport of unwanted company code to Quality and Production ?
   
   Delete the unwanted company code templates from Development and then release the transport to Quality and Production system. See KBA 3086744

KBA , SV-CLD-ACT , S4H Best Practices – Generic Content Activation , How To