Source system moved to differnt folder in RSA1

Hi,
We did system refresh from R/3 production to R/3 Quality system.
After this, as a part of post refresh activities, we did restore source system connection in RSA1 of BI Quality system by
right click on R/3 Quality system and choosing the option Restore.
It asked us user id and passwords for aleremote and extremote users ( background users for BW and R/3 quality ).We provided those.
Then it asked us to provide the userid and password for administrator for R/3 quality system.
We provided user id and password of DDIC user in R/3 Quality system.
Then it gave the following message:
User already exists in source syst. Only continue if profile and password are correct.
Continue? or Cancel?
We selected "Continue".
Then it gave us the screen with following message:
RFC destination already exists in source system .Do you want to use this destination, check, or cancel source system connection?
Use ? Check? Cancel?
We selected "Use"
Then it gave us the following message :
Connection BB is used in the R3QCLNT100 source system as a connection BQ1CLNT100 to BW.
Do you want to delete this connection in the source system? Connection Is Restored After It Has Been Deleted Successfully.
Delete ? or Do not Delete?
We selected Delete.
After this, restore took place successfully but there is one problem.
After restore, in RSA1, Source system R3QCLNT100 ( source system name for our R/3 quality system ) is shifted from the folder SAP ( source system type for SAP source system ) to Folder BI ( source system type for BI system )
Please suggest how to shift the source system from BI to SAP Folder.
Thanks,
Tarun Brijwani.

Hi Tarun,
have you checked RFC connection before you did Restore?
Might be that you need to adjust RFC settings (TA SM59) for that particular source system.
Seems to me that IP of your R/3 QAS system is pointing into some BW system. That's why your source system was shifted under BI source systems in TA RSA1.
BR
m./

Similar Messages

Source system appearing in BI folder : Not able to delete entry RSBASIDOC

Hi all,
Iam creating source system connection from ECC to BI system.
But the source system appearing in BI folder all the time, i found one note 1087980 and tried deleting an entry with SRCTYPE = M from RSBASIDOC table with FM RSAP_BIW_DISCONNECT , but the system shows error message OTHER_ERROR and the entry does not get deleted.
For this SAP recommended to check a valid RFC connection between ECC and BI system , i have checked it and the RFCs are working fine for it also.
Please help.
Regards,
Akash.

follow this steps:
In the source sytem
SE37 e launch the FM RSAP_BIW_DISCONNECT
you will find the BIW and OLTP log on the RSBASIDOC
So run the FM.
IF you find the OTHER_ERROR, may you have to check the RFC connection. (If the source system was been refreshed, you have to create a RFC to PROD).
You should encounter this error ( Not able to delete entry RSBASIDOC), when you try to restore the DS: in this case infact, is the IDENTIFIER (TSPREFIX) that creates problem (so you have to delete the relevant entry from the table).
CIao,
Cristian

ERP source system appearing in BI folder

Hello All,
We have done a refresh of our ERP system from PROD to QA.
When I restored the connection of the source system in BI it is appearing under the Source System folder BI, instead of the SAP folder.
Also the symbol is different of that of an ERP source system.
Does this matter? Why does it think it is a BI system when it is an ERP system? Has anybody experienced this or no how to resolve it?
Many Thanks,
Nick.

Hello All,
Has anybody experienced this?
Any help appreciated.
Thanks,
Nick

SAP BI Quality system appearing in SAP folder and not in BI folder in RSA1

Dear SAP experts,
We recently did a system refresh of our BI 3.5 Quality system QED from the BI 7.0 Production system PED .We ran the BDLS for all the connected source system that were to QED.
But after this i find that in RSA1 under "source system" , myself source system QED is appearing in the SAP folder and not in BI folder. Because of this we are not able to do data loads with in the system.
I am not able to create the QED source system under the BI folder as it already exists. For all the other system in the landscape the BI system are appearing in the BI folder in RSA1.
Kuldeep Prasad.

Hi ,
Thanks for your response.
I had run the BDLS for PED > QED and have checked the spools where all the table till Z* was converted.
However i find that in table RSBASIDOC there are 2 entries which may be the problem.
Source system DWH System   Object Status      Basic type         Source system type
QEDCLNT010    PEDCLNT010   ACT                ZSOA001         M
QEDCLNT010    QEDCLNT010   ACT                ZSQN040          3
Please can ypou suggest whether can be the problem and what can be done to correct this.
Thansk a lot for your suggestion.
KUldeep.

Issue in source system creation under sap node

hi,
i am facing a strage issue here while creating a sap source system.
i have two development systems - bd1 for bi development, rd1 for r/3 development. rfc is propely maintained between both of the systems. now im creating the source sytsem under transaction rsa1 - source sytem - sap, i put in all the details and it prompts me to log in to the source system as well. it creates the system properly but the problem is that im creating it under the node sap and it goes under the node bi.
i have deleted it from there and repeated the same process again but still everytime it comes only under the node bi irrespectiv e of the thing that im creating it under sap.
this is the first time im facing this strange issue i have done the same process many time but never seen nething like this, does anyone have any idea for the same.
kindly give ur inputs.
thanks
dipika

Hi Dipika,
It is not an operational issue. Its just a display and should not have any problems.
Please go through the below SAP Note to fix the issue.
[Note 1087980 - ECC Source systems appearing in BI folder|https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/sapnotes/index2.htm?numm=1087980]
Regards,
Gaurav
Edited by: Gaurav Kothari on Aug 31, 2009 4:20 PM

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

Create Source System BW

Hi, I have problem try create source system (ERP) in the BW.
In the TX RSA1 > Modeling > Source System > SAP > Create connection succesfully but show new system in the Folder BI.
This new soruce system is displayed in the SAP folder but the folder is shown in BI.
Anyone have any suggestions?
Best Regards,
EDRS

Hello,
Looks like the SYSTEM shows right by displaying ECC under SAP rather than BI.
Refer to the note :- Note 1087980 - ECC Source systems appearing in BI folder
Thanks,
Arjun

Source system server migration (new ip address)

Hi Experts
We are moving our servers (source systems) to new boxes. The source systems will be copied to the new ones and the only thing changing will be the IP addresses. BW server will not be touched.
Do I need to create new source systems? I am hoping not to do this and, Are the deltas will be ok? Or do I need to reinitialize all the delta loads?
Thanks!
Daniel

Hi Daniel
No need to create new source system...In fact without deleting the existing one, you wont be able to create same source again.
And do not delete , because that means you will lose all the DataSource.
Need to adjust RFC to point to different hostname /IP address.
In case any inconsistency happens , need to restore the source system connection from BW side.
RSA1-->Source System--->Resotre ...this will automatically adjust RFC connection. Search Forum to know the process of restore in detail if needed.
Delta might need to be re-initialized. Are you planning to clear all the queue before ( LBWQ) server migration? Else you might end in some problems during migration if you are doing it by database restore method.
Regards
Anindya
Edited by: Anindya Bose on Feb 10, 2012 6:38 AM

Source system assignment while transporting to quality

Hi Guys,
I have the following landscape.
I have created 2 source system ECCDEV and CRMDEV for my BIDEV.
Now I wish to do transport to Quality box and i want to know what should be the source system assignment , I should maintain in rsa1->transport connection -> conversion of logical system name.
When I maintain ECCDEV -
> ECCQUA
I get the error : ECCQUA entry does not exist in TBDLS.
Do I have to maintain source system ECCQUA(Quality) in BIDEV(Development) itself?
-Amit

Hi Rakesh,
Let me know if my understanding is correct.
In DEV BI, I create a connection to DEV ECC.
Also, I create source system ID's for source system.
In the QUA BI, I create a connection with QUA ECC.
and assign source system connection (source and target) i.e. DEVECC and QUAECC.
Then I transport requests(activated datasources) from DEVECC to QUAECC and replicate the datasource in QUABI.
Please Confirm.
-Amit

Reconnect R/3 source system after BW systemcopy ?

We want to copy our BW 3.0b development system as a BW sandbox system in order to try out the BW 3.5 migration.
Therefore, we performed a system copy of our BW DEV system to a new machine. On the BW-side we ran BDLS to get a new logical name for the system and defined a RFC connection to our R/3 Dev Source System (incl. appropriate RFC users).
On the R/3 side we also defined an additional RFC connection to the "new - just copied" BW-system.
While trying to reconnect our R/3 Devopment source system within the new BW we encountered the problem that the R/3 system recognized that there already exists a connection to a BW (the old BW dev). If we take this option, the old connection is deleted and a new one is defined. However, from the R/3 perspective we want two BWs connected. It seems the problem has to do with the IDOCs and TRFC port definitions, because the IDOC type ZRSBW010 seems to point to the wrong system.
Unfortunately, we are stuck at the moment.
Any kind of help or hints to relevant SAP documents would be much appreciated.
In the OSS we found some notes on this topic (325525 etc.) but we still not sure how to proceed.
However, in general, we think it shouldn't be a problem to have one R/3 connected to several BW's or is it?
Frank Schülke, E.ON Ruhrgas IT, Germany

Frank,
It is possible to connect a copy of your BW dev. system to the same R/3 system. The problem you are experiencing is related to the connection ID from table RSABASIDOC. This is a unique ID in your system (normally the first two characters of your source system name). Tis ID is in RSBASIDOC in yuor BW and R/3 system. When you copy your BW and try to connect it to your R/3 system again, you will get the conflict you already noticed.
The solution is to run SE37 --> RSAP_BIW_DISCONNECT in your new BW system (make a screen shot first of the RSBASIDOC entry!). This will be cleared by the function module. You will notice that the source system is not visible anymore is RSA1. However all the transfer rules etc. are still there (invisible). This would not be the case when you are doing a remove source system in RSA1 as suggested. Now you can create the source system again via the normal way. Use exactly the same name for the source system mas you made it via the BDLS. During this process the BW and R/3 systems are "negociating" a new unique connection ID for this BW-R/3 connection. This creation of the source system will also make all the related info visible again (like transfer rules).
Note in general: If you get a screen saying the connection ID is already used, ALWAYS choose DO NOT DELETE. After chosing DELETE there is no way of solving the issue other then restoring the system from backup! In this case you would delete everything in your R/3 system regarding the original BW system! When you get the message, check RSBASIDOC in both systems as there will be a conflict.
Regards,
Sander.

New source system

We've just copied the BW Production system onto a new server (Test BW).
The BW Production is pointing to Production ECC6.
We're have created a new RFC in the Test BW, which point to Test ECC system.
We have also perform the source system conversion via BDLS.
In RSA1 ->Source System, I can see name of the source system has been changed to Test ECC6.
However, when I right click on Source System ->Connection Parameter, I can see that
the Source System is still linked to the old RFC which is pointing to the Production ECC6.
How can I change this RFC so that it is pointing to the new RFC that we just created?
Please help, thank you.

in the monitor screen, check the complete error message in status tab.you will find a button below the message, click on that to get the detailed message.
then goto details and see in which step you are getting the error(extraction/processing etc).
Or...
in the menu , Environment ->job overview->Source System and then also it will take u to R/3 side .
Check the job status...finished/cancelled etc.
If cancelled, then reload .
In any case, read the log what is getting displayed.
1.Please replicate and activate the data source in bw side under the appropriate source system
and then try loading.
or
2.In the processmonitor of the info package, (in details tab) when you right click on the red ststements and select displaying messages, there will be a question mark appearing at the right hand side.
or
3.check whether all the objects all active or not.
4.check if data source is active on R/3 side or not...if no...activate the same.and reload.
Is it happening for the first time...if yes...were there any transports on R/3 or BW containing these objects
5.Also, goto BD87, in both R/3 and BW side...check if there are any idocs stuck...if yes...manually process them...
6.Check in sm58 in R/3 or BW....if there are any entries there for this...if yes...select them and press F6...
Edited by: Ananda Theerthan on Mar 3, 2010 1:23 AM
Edited by: Ananda Theerthan on Mar 3, 2010 1:27 AM

Source System changes from SAP System to BI Warehouse on ECC activation

We are in the process of building a new development environment from an existing development environment.
After copying from system backup in the new development environment we performed BDLS to map to new source systems. At this point of time the source system for ECC ("SAP System from Release 3.0E" was changed to type "SAP Business Information Warehouse".
Why does this happen?
How can we prevent this?
Thanks for your help.

Hello.
Please check the following note if ti can be helpful to fix this issue.
1087980-ECC Source systems appearing in BI folder
Thanks,
Walter Oliveira,

Delete source system fails

I've got a flat file source system definition which I deleted via rsa1 --> source system --> right-click --> delete. it deleted all the dependant objects (transfer rules, psa, EDI config, etc), but the system still shows up in RSA1. There's an entry in table RSBASIDOC referencing this source system (field SLOGSYS), because we manually tried creating a basic idoc type for it (which we now can't delete with tcode WE20 since it's been generated).
Does anyone know off hand how to get rid of the source system in the RSA1 list?
Thanks!
Rich

Hi Rich -
I guess the SAP Note (967999) applies in your case. I've pasted it below for your reference.
Symptom
In the source system tree of the Administrator Workbench (AWB), you use the 'Delete' function in the context menu (right mouse button) for a connected source system.
Even though the system displays success message RSAR 262:
Source system & deleted
at the end in the status line, the source system connection is visible again after the AWB has been updated and the source system connection has not been deleted.
Other terms
Context menu, source system tree, right mouse button, delete source system, RSAR, 262, 620, SLG1, RSAR262, RSAR620, AdminWorkbench
Reason and Prerequisites
This problem is caused by a program error.
An error occurs during the deletion, however the system does not inform you correctly of this at the end, after the deletion process has terminated.
Solution
BW 3.0B
Import Support Package 33 for 3.0B (BW 3.0B Patch 33 or SAPKW30B33) into your BW system. The Support Package is available onceNote 914950 "SAPBWNews BW 3.0B Support Package 33", which describes this Support Package in more detail, has been released for customers.
BW 3.10 Content
Import Support Package 27 for 3.10 (BW 3.10 Patch 27 or SAPKW31027) into your BW system. The Support Package is available onceNote 935963 "SAPBWNews BW 3.1 Content Support Package 27", which describes this Support Package in more detail, has been released for customers.
BW 3.50
Import Support Package 19 for 3.5 (BW3.50 Patch 19 or SAPKW35019) into your BW system. The Support Package is available once Note 928662 "SAPBWNews BW Support Package19 NetWeaver'04 Stack 19", which describes this Support Package in more detail, has been released for customers.
BW 7.0
Import Support Package 10 for 7.0 (BW7.0 Patch10 or SAPKW70010) into your BW system. The Support Package is available once Note 914304 "SAPBWNews BW 7.0 Support Package 10", which describes this Support Package in more detail, has been released for customers.
To provide information in advance, the note(s) mentioned above may already be available before the Support Package(s) is/are released. In this case, the short text of the note still contains the words "Preliminary version".
Pls assign points if helpful.

Extraction failure and then picked up due to IDOC setting on source system

hi All,
Just give one master data Company Code load as an example. We run the data load every night around 12 though Process Chain. When we checked the monitor, find that it ran twice, 1st time, it ran at 12 which was supposed to run, but it failed with red error and the red error msg is:
"IDocs were found in the ALE inbox for Source System that are not updated. Processing is overdue."
then it ran again at 07:45:55 which was successful with green light. We guess this problem is caused by IDOC setting on the source system. Run WE02 on the source system, expend Inbound IDocs folder and then expend RSRQST folder, find status 64 which indicates the yellow status.
Can anyone explain here why the extraction failed 1st time around 12am due to IDOC setting on the source system, and then the run was picked up around 7am successfully?
Thanks in advance!

Hi Kevin,
this is really a strange behaviour. What I could imagine: it could be temporary network issue or performance issue or system unavailability on the r/3 source system side. maybe you could check if other processes/jobs on R/3 were canceled, or if there is any system log available at the time concerned.
Lilly

SAP Source System showing up as BI Source System in RSA1

I have 2 BW systems and 2 CRM Systems. In one BW system, when I create a SAP Source system in RSA1, It gets listed as a SAP Sources system along with ECC and all the rest.
The Logicial Systems and RFC Connections all appear to be the same between each pair.
In the other system, using identical procedure, it the source system gets listed as a BI Source System. The 2 CRM systems have identical components and version levels as do the 2 BW systems.
Any idea why and if this would make any difference and how to correct.

Hi,
To fix this, you need to do a restore (& not a delete) of the source system in BW, having deleted the RSBASIDOC entry in the source OLTP system.
This will force the BW system to interrogate the RSBASIDOC table entry in the source system again and it should then realise that it is an R/3 system (not a BW system) and move the entry to the SAP folder.
Rgds,
Colum

Source system moved to differnt folder in RSA1

Similar Messages

Maybe you are looking for