Solution : https://service.sap.com/sap/support/notes/325470 (SAP Service marketplace login required)
Summary :
This SAP Note addresses the complications that arise post-client copy in a BW source system, particularly concerning the non-existence or inaccuracies of partner profiles and incorrect logical system names. Solutions provided involve transactions such as BDLS for renaming the target client, and specific actions detailed for different BW versions to restore ALE partners and adjust logical system names. Procedures span using transactions like WE21, SE16, WE30, SM30, WE57, and WE20 to establish the necessary configurations and ensure consistent integration across systems. Ensure to reference additional notes for comprehensive guidance on executing these transactions correctly.
Key words :
converting logical system names reason, convert client- independent tables, deleted ale partners manually, enter message type rsrqst, enter message class rssend, function module rsar_data_received, client-specific tables, incorrect logical system, sap basis area, pass idocs immediately
Related Notes :
| 937323 | Changing Production Client in an ABAP+Java System |
| 886102 | System Landscape Copy for SAP NetWeaver BW |
| 524554 | Storing destinations in the BW environment |
| 446294 | CC INFO: Logical system name and client copy |
| 369758 | BDLS: New functions and better performance |
| 325525 | Copying and renaming systems in a BW environment |
| 121163 | BDLS: Converting logical system names |