Solution : https://service.sap.com/sap/support/notes/325525 (SAP Service marketplace login required)
Key words :
/bw --> services & implementation --> system copy & migration, connected bws/bw source systems, entire system infrastructure connected, bw source system connections, bw source systems, bw source system, entire system group, single bw system, single source system, execute transaction bdls
Related Notes :
| 886102 | System Landscape Copy for SAP NetWeaver BW |
| 793717 | Client copy into the BW client in Netweaver/mySAP ERP |
| 760949 | Deallocating extraction due to upgrade or in copied system |
| 733623 | Oracle export/import for BW system copies |
| 606757 | Naming conventions for logical systems |
| 562356 | Message TR017 when creating the source system |
| 562350 | Message TK103 when saving source system-dependent objects |
| 542631 | Changes in the BW documentation for BW 3.0B |
| 524554 | Storing destinations in the BW environment |
| 458484 | Changes to the BW documentation for BW 3.0A |
| 423184 | ALE: Problems with logical system names |
| 369758 | BDLS: New functions and better performance |
| 325470 | Activities after client copy in BW source systems |
| 184971 | Notes on BW source system connections |
| 184754 | Procedure after BW database copy |
| 184447 | Building a BW-system landscape |
| 184322 | Procedure after DB copy of BW source systems |
| 121163 | BDLS: Converting logical system names |