Solution : https://service.sap.com/sap/support/notes/184322 (SAP Service marketplace login required)
Summary :
This SAP Note addresses the restoration of source system connections to a Business Information Warehouse (BW) system following a system copy (either via a database copy or client copy). It specifically targets scenarios wherein an OLTP system has been refreshed using a copy of another OLTP system. The recommended procedures begin with confirming the presence or absence of related entries in the RSBASIDOC table in the source system. Subsequent steps include ensuring the client maintains its logical name post-copy and adjusting logical system names via Transaction BDLS if necessary. Detailed instructions for restoring connections for different BW releases are provided, including executing specific transactions such as SM30, SM59, and SE37 to maintain system consistency and integrity. It is essential that these steps are performed accurately to re-establish connections and ensure that data flows correctly between the OLTP source system and BW.
Key words :
transaction se37 - function module rsap_biw_disconnect - single test, transaction se37 - function module rsap_biw_connect - single test, bw> i_slogsys <oltp source system, transaction sm30 - table t000, transaction se16 - table rsbasidoc, bw> i_restore i_tsprefix <tsprefix, transaction sm59 - destination <logical, administrator workbench - infosource tree, oltp system> i_basic_idoc <bidoctyp, function module
Related Notes :
| 937323 | Changing Production Client in an ABAP+Java System |
| 886102 | System Landscape Copy for SAP NetWeaver BW |
| 558563 | How does a client copy work with Demand Planning? |
| 524554 | Storing destinations in the BW environment |
| 369758 | BDLS: New functions and better performance |
| 325525 | Copying and renaming systems in a BW environment |
| 121163 | BDLS: Converting logical system names |