Picture1.jpg

System copy configuration of SAP Business Warehouse (SAP BW) system landscape is highly complex due to the many connections between the involved application systems. Typically such a system landscape contains SAP BW systems, BI Java systems and SAP BW source systems such as SAP ERP, SAP CRM and SAP SCM etc..  The two main copy use cases are Initial Copy (creating a new system from a copy) or System Refresh (refreshing the data of an existing system from a copy). In either copy use case, one must pay special attention to both the various system connection details (ie: connections between SAP BW system and its source system such as SAP ERP, SAP CRM etc.) and system configuration settings (ABAP and Java basic configurations). Additionally, with each system copy, a series of post copy configuration activities are required to ensure success. These activities are a part of every system copy including a migration to SAP HANA as well as regular system copies of your SAP BW landscape.

To manage such challenges, all these post copy activities have been automated for SAP BW system landscape (Post-Copy Automation or short: BW PCA). This automated solution makes the required post-copy activities much easier, more efficient and more robust. The manual guide for SAP BW system copy configuration described in SAP Note 886102 (SMP logon required) becomes obsolete. BW PCA is offered as part of the SAP Landscape Virtualization Management product. It can be executed in ABAP systems locally by using the ABAP task manager for lifecycle management automation or triggered by SAP Landscape Virtualization Management as part of an integrated solution.

Related topics:

To report this post you need to login first.