Sap rsbasidoc update

It looks like it is missing something in the converting phase. How can I get the objects to be changed with the new logical system name? BLDS must change them or is there another way to do it? Also, we need to execute the same function module in old BI source system with the same inputs to delete the entries needed for the source system change.

In this context, we are executing the function module in ECC source system Client We are using the note as primary source, but to be honest it is not clear for me the scenario I need to use. What do you suggest? I performed for a test source system, however the source system is not available into RSA1 anymore.

How can I reverse that? I need to keep available the objects into RSA1. Read this SAP Note first:. We restarted the system to adapt some parameters into profile, and immediately later run the BDLS no test and it finished OK. No Account? Sign up. By signing in, you agree to our Terms of Use and Privacy Policy. Already have an account? Sign in. By signing up, you agree to our Terms of Use and Privacy Policy. Enter the email address associated with your account.

We'll send a magic link to your inbox. BDLS - Logical system name conversion. My strategy is after the copy is done and QAS now has overwritten and is now , 1 create a new client in QAS,. Although it will take time and save the BW team extra headache with residual issues from the wrong client configuration. Please let me know if you think this is a good option or offer other options if not?

Thank you for your timely response Janette for providing the note. Being that the system copy had already taken place and that QAS was overwritten in the process, which is now PRD , can you clarify what the note actually suggesting in relation to system copy cases like this? I understand that BW operates on a single client. If possible do not change the client and keep client of the productive system. A BW client copy will copy nearly nothing as most of the tables are client independent.

Thank you again Janette. We'll keep it as and follow the post copy steps and do the necessary to record the extra steps as needed. Does this scenario also work for ODP source systems? For ODP source systems ODP queue is relevant and therefore the old 'subscriptions have to be deleted' and new subscriptions have to be created by starting the DTP for example.

Child pages. Source Systems. Browse pages. A t tachments 0 Page History. Jira links. Created by Janette Koppensteiner , last modified on Feb 08, Scenario B1 replace productive BW system Be aware that a system refresh is a task, during which productive use of the target system of the copy is not possible.

Scenario C1 replace a productive source system of a BW system Be aware that a system refresh is a task, during which productive use of the target system of the copy is not possible.

Scenario A2 create or refresh a non-productive system group Scenario B2 create a new non-productive BW system Scenario C2 create a new non-productive source system Scenario B3 refresh an existing non-productive BW system Scenario C3 refresh an existing non-productive source system Scenario B4 create a non-BW client by copying a BW client Scenario C4 create a new non-productive source system client.

Mapping in transport Target BW System. Child pages. Source Systems. Source System connection tables. Browse pages. A t tachments 1 Page History.