Change Source system Tech.Name

Production : PRE -
> PRB
PRE-Production : PPE -
> PRE
We make a copy of our production BI to Preproduction BI (PPB) we follow note # 886102. We want to connect this system to our pre production ERP (PPE).We already run BDLS change the logical system name we created new RFC created which is pointed to new R3 system .Problem is when we are going to run Tcode RSA1 in source system it shows old Tech name PRE600. We are unable to activate the source system.
We can create new source system (PPE),but All our BI objects mapped with old source System (PRE600). I am afraid to change thousands of BI objects ( change source system from PRE600 to PPE600).
Is there any work around we can change the Logical Source system Tech.Name? or some batch job which change the source system name for all BI objects.
Appreciate your earliest reply.
Nawab

Hi
Can you please check the Tcode BDLS
Check the document it will be helpful
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/bff13df2-0c01-0010-6ba7-bc50346a6fd8
Regards

Similar Messages

Change source system name in variant in BWQ

Hi Gurus,
I created a process chain for global seetings for unit of measurement and fiscal year variants and transported to BWQ.
In BWQ, I found the source system name in variant is showing ERD source system name, but I need to change it to ERQ source system name. Any advice how to change source system name in variant in BWQ I would appreciate it.
Thanks
Liza

Hello Again Liza...
I had the same problem but I didn't need to include in process chain...
So to execute periodically you can change it in debug mode, not the best solution...
But since you need to use it in a process chain, you should copy that program to one of yours Z.
Do this:
Go to transaction se38 and insert the program name "RSIMPCUST".
Click on the button of "Copy" (Ctrl+F5).
Change the source program name to ZRSIMPCUST (or whatever you want)
Click Enter
Click the button to mark everything (F8)
Click Enter
On the next window of the name of the include click enter (leave it blank)
Click on the button Change of your Source Code
In line number 54 you'll find this in Selection Screen part:
PARAMETERS: logsys TYPE rsa_logsys MODIF ID p01.
PARAMETERS: logsysnm LIKE tbdlst-stext MODIF ID p02.
Delete those two lines and insert this ones:
PARAMETERS: logsys TYPE rsa_logsys.
PARAMETERS: logsysnm LIKE tbdlst-stext.
Now click on Activate button (Ctrl+F3)
Now you have a new program just like the old one but you can change the source system to whatever you want!
Please assign points,
Diogo.

Does not allow to change source system in Variant

Hi Gurus,
I am creating a variant for the program RSIMPCUST, but it does not allow me to change source system name. It is showing me gray color. Do you how to fix this issue ?.
Thanks
Liza

Hello Liza,
Did you try my solution?
[Re: Change source system name in variant in BWQ]
There are solutions to change variants properties, but that particular program has the logsys parameter not able to change, so you cannot change the value of that variant (only with debug).
It's best to go for that solution I already provided to you...
Diogo.

Tracking source system table name for a field in ODS

Hi Guys,
I know this is pretty simple for many of you, Being a newbie, pls clarify for me :
Consider field1 in ODS1. I want to know the database table which is updating that field. From transfer rules i can see which is the source system filed name but from which table that is coming???
Thanks in advance!!!

You can find the name of the data source if you right click on the ODS and click on Show Data Flow -- > You will be able to see the flow and get the data source name.
Once you have the data source name , go to transaction RSO2 and see if the data source is based on a table or view or FM ..once you have this info you can analyze the table or the FM to find the source table and field..
Hope it helps,
Ashish..

Source System Logical Name change

Hello,
We are refreshing our R3Qas system with a copy of our R3Prd system. As part of this task our R3Qas logical name is changing from QASC230 to QASC200.
I am at the point in the refresh where I am beginning tasks on the existing BWQas system.
I Right Click on the source system representing the R3Qas system "QAS client 230" technical name: QASC230. I choose 'Restore' I then provide the logon information but the system it jumps to is the Old R3Qas not the new R3Qas.
I know that it is jumping based on the RFC, So I assume I can change that RFC to jump to the new system, what do you think? Also what about the Source System name an technical name, will it always be QAS Client 230 and QASC230 or can that be changed to reflect the new name of QASC200?
Thanks for your advice and assistance!
Nick

Since the BWQ system was already an existing system that was attached to the previous R3Q system, this task was essentially busy work.
The change that occured was that the existing R3Q system (Physical Name: QAS01 Logical Name: R3QASC230) was being replaced with a new R3Q system (A copy of Production was used) (Physical Name: QAS02 Logical Name: R3QASC200).
The actions that I needed to take to connect BWQ to the new R3Q follow:
1. On QAS02 visit TX SE37. and run RSAP_BIW_DISCONNECT, Choose 'Single Test'. For I_BIW_LOGSYS: I provided BWP001 which corresponds to the logical name of our Production BW system. For I_OLTP_LOGSYS: I provided R3PRDC200 which corresponds to the logical name of the QAS02 system (this system). I then Click 'Execute' and 10 seconds later this step is done.
2. On QAS02 visit TX: BDLS. For the 'Old Logical System Name' provide BWP001. For the 'New Logical System Name' provide BWQ001. Ensure the 1st radio button is selected, and deselect all checkboxes. From the Program menu choose to 'Execute' in background (it took about 45 minutes). Confirm the 'Mapping System Name'.
3. Again on QAS02 visit TX: BDLS. For the 'Old Logical System Name' provide R3PRDC200. For the 'New Logical System Name' provide R3QASC200. Ensure the 1st radio button is selected, and deselect all checkboxes. From the Program menu choose to 'Execute' in background (BASIS already did this step so a message appeared to that effect)
4. On the BWQ box visit TX: BDLS. For the 'Old Logical System Name' provide R3QASC230. For the 'New Logical System Name' provide R3QASC200. Ensure the 1st radio button is selected, and deselect all checkboxes. From the Program menu choose to 'Execute' in background (it took about 45 minutes). Confirm the at the prompt and run.
5. On BWQ create new RFC's based on the old ones to point at the new QAS02 system. Modify the old ones with an X in the 'Target Host' so they do not function.
6. Open up the BWQ client in SCC4. (or perhaps try SM30 to modify the table in the next step)
7. On BWQ visit TX: SE16. Tablename: RSLOGSYSDEST. Change the 'Old' reference to the QAS box to the 'New' information. (ie: R3QASC230 became R3QASC200).
8. On BWQ visit TX: WE20. Expand 'Partner Type LS', Select 'R3QASC200', click the classification tabe, change the 'Partn.Status' from I to 'A' and save.
9. On BWQ right click on the R3 Source system and choose 'Restore' Provide the passwords that are required. When prompted to logon to the remote system use an ADMIN (BASIS) level Account. Click 'Continue' when you get the 'User exists...' prompt. Click 'Only Activate' when prompted. you will then get a termination message regarding the port description.
10. On BWQ Back at WE20: Expand 'Partner Type LS', Select R3QASC200, double click on RSRQST. Under 'Outbound Options' click the drop down for 'Reciever port' Select the 'new' correct system and 'Save'.
11. On BWQ right click on the R3 Source system and choose 'Restore' Provide the passwords that are required. When prompted to logon to the remote system use an ADMIN (BASIS) level Account. Click 'Continue' when you get the 'User exists...' prompt. You will get a prompt to Use or Check, choose 'Use'. When prompted about 'Connection cannot be used' click 'Delete'. Logon again as ADMIN account, Click 'Continue' when you get the 'User exists...' prompt. Click 'Replicate as well' when prompted. you will then get a termination message regarding the port description.
You should be all set now!
Nick

Change of DTP tech name in transport causes error in Process chain

Hello people,
This message was posted before and I do not think there was an answer. I hope I have better luck.
When we transport DTP and process chain, the DTP tech name is changed in the target system while the DTP specified in the transported process chain remains as the source system. This causes an error in the process chain in the target system because it cannot recognise the DTP specified in it. To rectify it, I modify the process chain in the target system to point to the DTP with the new tech name. Is there another way such that I do not need to modify the target system.
I am currently trying to find an answer and I will share if I find one. Thanks.
HWS

Hello again,
My problem is resolved. I am in SP17 and I applied a few SP18 notes:
0001002791
0001077030
0001139653
0001147587
0001147766
I then re-transport the request with the DTP and process chain. The expected result is the dtp in the process chain should be pointing to the new dtp. CHeers.
HWS
Edited by: Ho Wei Siong on Aug 14, 2008 3:35 PM

Change Source system ID

Hi Experts,
We did a system copy of BW system alone, and when we tried to restore the connection with the source system, i am getting the following message.
Source system cannot use any of the proposed connection names
Message no. RSAR362
Diagnosis
Every connection to a source system is named using a unique two-digit identifier. Source system DEVCLNT030 does not accept any of the proposed values.
The last proposed value was BA.
System Response
Source system has not been connected.
Procedure
If you want to recreate the source system from BI information, then you can only use a single value, namely BA, because the connection already has this name in BI.
Delete the existing connections in the source system or contact a BI consultant.
BDLS was successfull, and returned no errors.
I checked the source ID in the RSA1 and it exists, how do i change this value.
Thanks in advance
Praveen

Hi Praveen,
Login to ur SAP R/3 or ERP Source System and go to table RSBASIDOC.
Put the R/3 logical System Name and BI logical system name as parameters and see the table values, i am sure the 2 digit unique identifier value will be the one giving u the problem.
This error comes after system copy of source system as ur system still behaves as Production System (the one from which it is copied).
Execute function module RSAP_BIW_DISCONECT in SAp R/3 System with parameters as ur R/3 logical System Name and BI logical system name and option forced delete as X. to delete entry from RSBASIDOC table.
now go to BW system RSA1 > Source System> restore ur system.
Hope it helps
Thanks
CK

How to change source system in process chain

Hi All,
In our Bw quality system, process chain is pointing to the Production system ,
I want to keep the process variant name same as production but want to change the source system
For example.. let us say currently process chains(All DTPs) are pointing to the Production server (PD001) ip (200.12.23.22)
now i want to keep the Server name same but want to point it to the quality system..so after change Process chain will show same name but it should point out to quality system.(let us say bwq 200.12.23.232).
Can you please help me on this

Hi Pravender,
In our BW system , we have same process chain in all the system (Dev, Quality and production)..and naming convention is also same ..(all process chain points to Production system only)..
So when I want to load data from development i just need to change the source system ip adrress to the Development Server (So names in process chain will indicate production but it will point to the development server), .
I want to know how can i change the source system mapping.
Hope i am clear now

Changing source system reference

Hi,
When I transport from dev to Q, how can I change the source system assignments to Q system? I guess I have to change the assignments as they are referencing dev source system in development and should reference Q when they come to Q.
Thanks.

Consider you have BWD, BWQ and BWP and you want to have them loaded from R3D, R3Q and R3p respectively.
First you need to create R3 source systems in each of the BW systems (and not transport it).
For steps refer:
Creating Source System in BW
Before transporting your rest of the development make sure you have maintained source system mapping.
If it is not maintained then the same source system name will be used in the target system.
This can be done via rsa1->tools->mapping source system or transaction RSLGMP
Lets say your landscape in BWD, BWQ and BWP connected R3D, R3Q and R3P respectively.
In BWQ create a new entry with values, OrSrceSyste = R3D and TargSrceSy = R3Q
In BWP create a new entry with values, OrSrceSyste = R3D and TargSrceSy = R3P
If you are tranporting any datasource of BW sourcesystem (ex: technical content datasources), then
In BWQ create a new entry with values, OrSrceSyste = BWD and TargSrceSy = BWQ
In BWP create a new entry with values, OrSrceSyste = BWD and TargSrceSy = BWP

Change Source System RFC

Dear All,
we have 2 server ecc 6.
1. production
2. backup
right now my sap bw connect to ecc production.
we have plan to use backup instead of production
is it enough just simply changing the IP and host name at the current RFC connection.
from IP production to IP backup server ?
without creating new RFC connection ?
is there any procedure that we have to do before or after the changes ?
please advice

Hello Dady,
You have to take care of RFCs, Logical system names and RSA1 stuff in order to use backup ECC server instead of Production.
I suggest you to go through the following document for better understanding. It's strongly recommended to take offline backup before you attempt to modify source system configuration in BW system.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/70a7b233-8be5-2c10-4190-aed723af5373?QuickLink=index&overridelayout=true
Good Luck.
Thanks,
Siva Kumar

How to Change Source system type of ECC6.0 in BW system

Hi BW Experter,
   I connected ECC6.0 PRD system with BI7.0 PRD system , the connection is successful,
but the source system type of ECC6.0 PRD is not collect . The ECC6.0 PRD is as a
BW system type in the source system list of bw system .
   I found that Tcode RSA1 has ever been run in PRD ECC6.0 , So I did a connection testing of
ECC6.0 QA with BI7.0 PRD .
     Step 1. Connect ECC6.0 QA with BI7.0 PRD , ECC6.0 QA was as SAP system type in source system list of bw system .
     Step 2. Run tcode RSA1 in QA ECC6.0
     Step 3. Delete connection of ECC6.0 QA with BI7.0 PRD .
     Step 4. Connect ECC6.0 QA with BI7.0 PRD again , ECC6.0 QA was as SAP system type in source system list of bw system .
   I want to know how to change ECC6.0 PRD source system type to SAP .
If it can't been change to SAP ,Is there any impact when ECC6.0 PRD is as bw system type in source system .
Thank you for your help .

I got the soulution from note: 1087980 - ECC Source systems appearing in BI folder
Summary
Symptom
Source system connection for an ECC system appears in the BI folder, rather than in SAP folder, as expected.
Other terms
Wrong folder,RSA1, RSBASIDOC, RSAP_BIW_DISCONNECT
Reason and Prerequisites
Transaction RSA1 was inadvertently used on an ECC system , thereby creating a 'Myself' source system entry in RSBASIDOC table
Solution
This is just a display issue and does not cause any operational issues. Therefore, it need not be corrected, especially if the ECC system in question is used as a BI system as well.
If it is absolutely required that the ECC source system appear in the correct folder, perform the following steps.
1. Check that an entry with SRCTYPE 'M' exists in table RSBASIDOC table of ECC source system.
2. Note the values for SLOGSYS and RLOGSYS. It should be same.
3. Run the function module RSAP_BIW_DISCONNECT in the ECC system.
   NOTE: Never run that function module in a BI system!
4. Enter the following values :
I_BIW_LOGSYS   <RLOGSYS> as noted in step 2
I_OLTP_LOGSYS <SLOGSYS> as noted in step 2
I_FORCE_DELETE <X>
< DO NOT ENTER ANY VALUE IN THE FIELD - RFC target sys !!!!! >
5. Go to RSA1-> Source systems in the BI system connected to the ECC system.
6. Select the ECC source system and select RESTORE in the right click menu.
Now the ECC system should appear in the SAP folder.
If running RSAP_BIW_DISCONNECT results in an error like OTHER_ERROR, please check if a valid RFC connection exists in transaction sm59.
If the myself source system connection cannot be deleted in any case, log a service marketplace message with SAP Support.
Edited by: fang frank on Jul 15, 2009 8:31 AM

Change source system in Dev

Hi
I have a dev system that is mapped to 2 source systems, R/3 clients (clients 245 and 246) and datasources are mapped to either of these systems. One of these R/3 clients (245) has now been deleted and I want to convert all of the datasources that pointed to it to the new client (246). I want to convert only the datasources pointing to the old client (245), but not change those that are already pointing to the new client (246). Would BDLS help in this situation.
Thanks in advance
Simon

you can do these:
1 ) change in SM59, the source r/3 qlty to point to your dev server. That should do the trick without making a lot of changes. once you change the source system via this option, you have to perform a check/restore (so that the partner profile in dev system can be updated), replication and activation of the transfer structures.
2) You can also ask your BASIS guy to run program for BDLS that changes the system pointer.

Change source system in Infosource

Hi
I am working on BI7. I have one isse. For an infosource source system has been assigned to client 100. I would like to change it to 200. Pl let me know how to make this change.

Hi
I didn't get your question,how a infosource is assigned to source system,your data source will be assigned to source system and your infosource and data sourece will be assigned to each other..
delete the datasource from source system 100 and create a data source in 200 and assign it to your infosource(i am considering both 100 and 200 source systems are assigned linked to your BW system via RFC(SM59))..
Hope it helps
Thanks
Teja

Change Source System in Transfer Rules

Dear All,
I need to change the Source System assignment in Transfer Rule from System "A" to System "B", as the System "A" no longer exists.
I came across the T-Codes BDLS/BDLSS but aint sure if this can help me rectify the issue.
Request you to please provide some inputs.
Regards,
Nitin S.

Hi
if you change the source system you may face the problem.
first you can replicate the Dat sources on B, then you can map the info source with your respective data source.
else it will not allow you for thr mapping.
Regards,
chandra.

Change source system in BW 3.5

Hi,
My current situation is that. In BW I have a source system (RHD) with several infosources, transfer rules ... assigned. The basis people has made a copy of RHD in a new system (RHX).
Is there any way to modify the source system in BW to get the data from RHX without modify objects manually (infosources, trasfer rules..)?
Thanks.

Hello,
in the transport connection of the Administrator Workbench there is a special collection mode for system copies. Select your Source system and use this mode. All source system dependend objects are collected in a transport request. Export this request, connect your new source system and maintain the translation of logical system names in the Admin Workbench. Then reimport the transpor request and all datasources, transferrules etc. are then 'copied' to the new source system. Have a look in SAP note 886102.
Hope that helps
Regards
Christoph Vortkamp

Change Source system Tech.Name

Similar Messages

Maybe you are looking for