SAP BPC: Implementation Lesson Learnt Part 4.
Continuing from we left off last time –
Point #4: System Landscaping:
I recommend using a 3 tier landscape to manage your SAP BPC environment.
BPC 5.1 doesn’t support the classical SAP transport process. You need to use Backup/Restore option at the server management level and then use file transfer process to support the implementation and post-production support. So when you backup the development server and restore the it to the new box to create QA server, you do need to do some manual work like setting up the initial security to the newly built system & etc. Because all these work (including the file movement analogues to the transport) are manual in nature, always keep a detailed work list with proper validation to have higher accuracy & low cutover time.
In case you are using a standalone BPC system only, in that scenario, 2 tiers architecture also will work.
Now, consider a scenario, where, you have already implemented BPC – Planning. And now you want to implement BPC – Consolidation. In this case you have 2 development pipe-lines. Consider the below diagram to manage the system landscape that time.
In the diagram below, you will be noticing the 2 lines. The top line was the first development roll out and the line below shows the current one. For example, your firm has already implemented Planning and now an initiative is happening to rollout consolidation.
The green arrow signifies ‘One time Copy’ to build the initial AppSet. The blue line shows the number in sequence for the object migration originated from Development AppSet-1. The black line signifies the object migration originated from the Development AppSet-2. The Red Cross signifies when the Development AppSet-2 is ready, Development AppSet -1 will be deleted and so on.
Lastly as I have mentioned, BPC 5.1 doesn’t support the classical SAP transport process, you need to be creative to establish your transport management. I plan to discuss on this in my next series.