Read before and after sap bw client changes

========== The following is an article about the hackerHttp://space.itpub.net/554557/viewspace-670324

Basic copiedClient200. After logging on to the system and logging on to rsa1, the system prompts activation. If you don't have to worry about that much, all the way to OK, the result will be mined.

After two days of basic change, we recommend using the system's default client 001 for BW, So we re-created the account in 001.

It also takes several days to complete.

When rsa1 is clicked, no familiar interface is displayed. The error box is displayed.

After the query, the problem is that BW is not independent from the client (and BW tables do not have the mandt column), soInstallA single host can only have one BW system. Previously, 200 was used, and now 001 is not used. However, this is not difficult. You only need to switch the BW system client identified by the system,

Enter SE16, enter the table name rsadmina, enter the content display, change the column bwmant to the current client value, and 001.

Enter rsa1 again. There is no previous error box, but a new problem occurs.

It seems that client 001 didn't specify the logical system, so I clicked create and created a new logical system. I thought everything was okay, my God. An error occurs again.

There's a lot to do. Click "help" to prompt you to change the logical system to the logical system corresponding to client 200, delete the connection, and change it to the new logical as required.
System. As a result, I can go to rsa1, but I found that the system has a bi link and there is no place to delete it. Because this link is self-connected. For example, if you import a cube from DSO, this link will be used and cannot be deleted. There is no place to delete it. When will it be created? After thinking for a long time, I finally remembered that the first time I entered rsa1, I required to execute the activation action. It must have been automatically created at that time. How can I solve this problem? This information must exist in a table, so I use st05 to track New Source
Systems: rsbasidoc [Assignment of source systems to biw systems incl.]. Because what you want to change is a keyword, you need to write a simple ABAP.

Update rsbasidoc
Set
Rlogsys = 'newid'
Slogsys = 'newid'
Where
Rlogsys = 'old '.

Here, the new and old words are written according to your actual situation.

Once again, rsa1 is ready.

====================================== My post-reading experience

Rsadmina: The cliet corresponding to the BW system, which is global. If you modify this parameter, all users will be affected. (It seems a bit nonsense, it is impossible for a user to correspond to a client ).

Rsbasidoc: The distribution from the source system to the biw System, including the IDOC type. The first column of this table is slogsys, which is similar to what we see in the rsa1 Source System and defines BW (dwh system) which source system is connected. For example