Source System no longer exists

Hello,
I am trying to remove an object from my InfoSource communication structure and I am getting the following error:
The InfoObject 0REQ_DATE is still used in the following places:
In the transfer rules for DataSource 2LIS_11_VASCL Source System PCPRDC200
The source system that is mentioned is our production system and that source system does not exist on our BW Development box. (Its possible that in the past it got deleted as a source system from the BW Development box)
I'd be greatful if someone can help me with this problem?
Thanks,
Nick

Hello,
After searching the forums I found that running the report:
RSAR_TRANSTRUCTURE_CHECK
With the following parameters
InfoSource: 2LIS_11_VASCL
SourceSystem: PCPRDC200
in SA38 fixed the issue
I found this report in the following thread:
Deleting transfer rules
Thanks!
Nick
Message was edited by:
Nick Bertz

Similar Messages

Transporting Process Chain - error Source system does not exist

Hi,
I tried to transport a local PC by itself (not including its main meta chain) since I have only done modifications in the local PC only. In the PC, there are PSA Processing, ODS Processing, ODS Activation, ABAP Program w/ variants and Infocube Rollup.
However, I got the following transport error: Source system does not exist
=======
Diagnosis
Source system is not known.
System Response
The imported data for DataSource was deleted again because the referenced source system does not exist and no mapping is defined in table RSLOGSYSMAP on an existing productive source system.
Procedure
Create the referenced source system in the Data Warehousing Workbench or define mapping to a known source system in table RSLOGSYSMAP.
You get to maintenance using Tools -> Conversion of the logical system names.
============
I have checked at the table RSLOGSYSMAP and all source system mappings are in order.
And the weird thing is, upon checking the PC itself in the transport-to box, I can activate it without any error.
FYI, we are currently upgrading to BI Accelerator. Am not sure if this could be one of the reasons.
Any inputs and tips are highly appreciated and will be rewarded with points accordingly.
Thanks

Hi,
This error is due to the fact that the
mapping table for the after import (RSLOGSYSMAP) is not correct maintained in PB7 system.
You need to maintain table RSLOGSYSMAP in each system
You can find the steps to do it in the attached note 127326:
o Maintain table 'RSLOGSYSMAP' in the target BW with view
   'V_RSLOGSYSMAP' and enter as 'original source system' the logical name of the source system in the source BW and as 'target source system' the logical name of the source system in the target BW.
   This maintenance is required since it allows the correct source system reference of the InfoSources to be transported.
This source system reference in turn is absolutely necessary to activate the transfer structure.
   Example:
   Source BW with source system AAA.
   Target BW with source system BBB where the source system AAA
   corresponds to the source system BBB.
   Entry in RSLOGSYSMAP in the target BW:
   Original source system: AAA, target source system: BBB.
   Give the DDIC user in the source BW in client 000 the
   authorization profile S_RS_ALL to create BW objects.
Cheers
Rajesh

Source system restore - Source system does not exist

Hello friends,
We have a problem. Now we have a new test system QA2. From BW system source system connection was configured for older test source system QA1.
We needed to route this source system to new system. I tried with changing RFC of QA1 to QA2 details.
Now, when i check RSA1 source system Check for QA1, i get this error :
Port 'A000000103 ' of type 'ALE ' does not exist
No destination exists to source system QA1
I can see this source system in RSA1 in BW. However, in WE21 port is not available now.
Please suggest.
I do not have to lose transfer rules/PSA tables..etc.
thanks
ashish

I get this when i try to restor connection :
Source system does not exist
Message no. RSAR175
Diagnosis
You have specified that you want to restore source system QA2. This source system is not known in BI.
System Response
The source system is not restored.
Procedure
Recreate the source system.
If the source system should be known to BI, the name of source system QA2 may be incorrect. Rename the source system and try the function again.

Transport Request got failed due to Source system does not Exist

Dear All,
I Have collected All data soruces which are related to R3 data sources and Flat File data sources...
After import the transport request it got failed due to Flata file source system does not exist in BI quality system.
But all data sources related to R3 and R3 Source system has been moved which are available in BI Quality sytem also.
why Flat File source and data source are moving.. why i am not sure it was throuing error message called Source System does not exist..
Thanks,
Ven

Dear Venkat ,
Go to Quality system .
Use RSA1 Transaction --> go to Tools --> Manage Source System :
Here you can map the entry of system ..
Second : go to Development system under RSA1> Transport Connection and click on Source system button first --> select your source system ---you can select multiple entry also ..collect your data source ( with before and after option ) and deselect which object you do not need ..And select collection mode to automatically ...
use the transport button to create transport request and release from development system .
I hope you will not get error in Q system .
If still facing error , Please let me know.
Regards
Vikas Sharma
Robert Bosch
Edited by: Vikas Sharma-Bosch on May 5, 2011 5:34 PM

Source system is already exist

Hi,
We are facing an issue with source system creation.
we have already created the RFC connetions between BW & ECC and there is no issue in RFC.
while creating the source system in RSA1 it giving the error Source system is already exist.
But there is no entry for the source system in tables RSLOGSYSDEST & TBDLS.
Both sides systems are opened inSCC4 & SE06.
Please help me out on this issue.
Thanks
Aravinda

Are you sure it's saying the sourcesystem exist? Isn't it saying the connection 'XY' already exists? ('XY' may be formed by other letters).
You should check in the table RSBASIDOC in both BW and source system if you can see any entry already referring to the the logical name you are trying to create or the connection/TSPREFIX being used (the 'XY').

Transport Error: Source system does not exist. Message no. RSAR203

Hi,
after transporting from BI_DEVELOP to BI_TEST I get an error whil importing Datasources:
Source system ERP_DEVELOP_SOURCESYSTEM does not exist - Message no. RSAR203
Which is upon the first sight correct, because I got the followings systems, RFC's and BI Sourcesystem:
ERP_DEVELOP -> BI_DEVELOP with RFC & Sourcesystem ERP_DEVELOP_SOURCESYSTEM pointing to ERP_DEVELOP
ERP_TEST -> BI_TEST with RFC & Sourcesystem ERP_TEST_SOURCESYSETM pointing to ERP_TEST
Can I map in the transport ( and how) in a way that the transports do not fail ?
ERP_DEVELOP_SOURCESYSTEM to ERP_TEST_SOURCESYSETM
or
Do I need to setup in BI_TEST a Sourcesystem ERP_DEVELOP_SOURCESYSTEM pointing to ERP_TEST ?
Thank You
Martin
Edited by: Martin Sautter on Jul 25, 2011 12:59 PM

Hi Martin,
You have to maintain the transport connection between your ERP_DEVELOP and ERP_TEST
your transport path should be as below
BI_DEVELOP -
> BI_TEST
ERP_DEVELOP -
> ERP_TEST
1)Make sure you have FRC connection between BI_DEVELOP and ERP_DEVELOP, BI_TEST and ERP_TEST
2)check you have transport connection between BI_DEVELOP and BI_TEST,ERP_DEVELOP and ERP_TEST
Now you transports should not fail
Hope this helps
Regards,
Venkatesh

Source System Does Not Exist - Transport Problem

Hi
We have the next Landscape in BW 7.0 (Netweaver 2004's)
LRDCLNT300     is R3 DEV
LRQCLNT700     is R3 QA
LBDCLNT100     is BW DEV
LBQCLNT700     is BW QA
The connections are
LBDCLNT100 (BW Dev) use as source system        LRDCLNT300 (R3 Dev)
LBQCLNT700 (BW QA) use as source system        LRQCLNT700 (R3 QA)
In RSA1->TOOLS -> Conversion of Logical System Names
In Conversion of source system after the transport we have these entries
Source System                    Target System
LBDCLNT100 (BW Dev)         LBQCLNT700 (BW QA)
LRDCLNT300 (R3   Dev)         LRQCLNT700 (BW QA)
But when we transport an order from BW DEV to BW QA show the error "source system LRDCLNT300 does not exist"
Never made the conversion of source system after the transport.
Can you help us please.

Thanks Edwin
     I create a RFC for LRDCLNT300 (R3 Dev) in my BW QA system (Target System).
I try an order again but it didn't work, also I try to check 7.0 checkbox but I got the message "No entry exists for original source system LBDCLNT100 for 3.x object"
and I have to uncheck again.
I still have the same problem the objects are associated to R3 Dev, never make the conversion to R3 QA.

Source system does not exist (RSAR203)

Hi to all
I have a error in phase XPRA_EXECUTION in BI_CONT 704 add-on upgrade by SAINT transaction.
Start of the after-import method RS_DTPD_AFTER_IMPORT for object type(s) DTPD (Modo de entrega)
Source system CLNT100CED does not exist
Source system CLNT100CED does not exist
Source system CLNT100CED does not exist
Source system CLNT100CED does not exist
Errors occurred during post-handling RS_AFTER_IMPORT_D for DSFO L
The errors affect the following components:
BW-WHM (Warehouse Management)
I read the thread
XPRA_EXECUTION error in BI_CONT 703 patching
but don't work for me.
The sap Note 1271454 does not work for me becouse I already aply the SP.
SAP_ABA     701     0007     SAPKA70107     Cross-Application Component
SAP_BASIS     701     0007     SAPKB70107     SAP Basis Component
PI_BASIS     701     0007     SAPK-70107INPIBASIS     Basis Plug-In
SAP_BW     701     0007     SAPKW70107     SAP Business Warehouse
BI_CONT     703     0003     SAPKIBIIP3     Business Intelligence Content
I upgrede add-on BI_CONT to 704 SP 08, for this the SAINT aply patch SAPKIBIIO4 TO SAPKIBIIO9 (prerrequisite)
The error appear in SAPKIBIIP6
Any suggestions?
Many thanks and best regards
William Neira

Hi,
Had you checked the SAP Note " Note 955647 - BI_CONT 703:Information on Add-On Support Packages".
Seems like SAP has released two support pack
SAPKIBIIP6..........AOP      24.07.2007
SAPKIBIIP6 updated..AOP      07.08.2007........955647
and recommends to apply the Support pack released on 07.08.2007. Kindly check and update.
Regards
Valavan.SM

After transporting I get error "source system does not exist"

Hello all,
I have transported my objetcs to BW quality system and transported the data sources to r/3 quality and everything went fine. But now when I am trying to go through everything my update rules are inactive and when I get to infosource it gives me this error
"Source system ERJ100 does not exist."
Is there any importamnt step that I am missing why are the objects not recognizing the source system?
Thanks,

hi,
check the system mapping in rsal tools system mapping tab as lilly mention. check if the mapping is defined correct. see the link below
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/e883de94-0501-0010-7d95-de5ffa503a86
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/3010ba90-0201-0010-2896-e58547c6757e
Might help
Thank you
Qandeel

Cannot make changes t oDTP - Source system does not exist

Hi,
I cannot open my DTP to make changes. when I tried to double click I got this error
Source system X01CLNT001 does not exist
Message no. RSAR203
I have tried connection test from SM59 and there seems to be no problem.
How do I resolve this?
thanks

Goto RSA1 --> Source System --> right click --> Check.
Is it giving any error?
You can click on restore also and check if anything improves.
Also check whether datasource and transformation is active.
Edited by: Pravender on May 28, 2010 12:11 PM

Transport issue - Source system does not exist

Hi at all!
I've got a problem after transport from BW QA-system (EBW) to BW PRD-system (PBW). All transports got the same error message, that the Source System DEV500 doesn't exist. But DEV500 is the development R/3 system. How could it be? Because we didn't connect the DEV500 to PBW. We connected PRDCLNT100 (Productive R/3) to PBW. Where is the failure?
Thanks in advance for your help.
Christof

Hi,
DEV R/3 -
> QA R/3 -
> PROD R/3
DEV BIW -
> QA BIW -
> PROD BIW
Is the above one is your landscape? If so , you must had created the Transport requests in DEV BIW and imported them into QA BIW. And for that you had maintained the source system conversions in QA ABIW .
Now you want to import into PROD BIW. And remember that the orgin(source) of the trnasport requests is DEV BIW. So you need to maintain the Conversions in PROD BIW for conversion from DEV R/3 to PROD R/3.
With rgds,
Anilk Kumar Sharma. P

Source system does not exist

Hi all,
When i run an infopackage its getting failed throwing out an error
"An error occurred in the source system.
System Response
Caller 09 contains an error message."
I have replicated the Data source and when i try activating it i am getting the following errors
"Inconsistent user object XXXXXXX "
"Error saving DataSource "
"DataSource XXXXX could not be activated"
Help me out
Regards,
MADhu

Hi,
Might be some issue in Data Source when you replicating it in BW system.
Check RFC connections between the Source and Target.
Could you mention the error message clearly.
Reg
Pra

Data loading from source system takes long time.

Hi,
I am loading data from R/3 to BW. I am getting following message in the monitor.
Request still running
Diagnosis
No errors could be found. The current process has probably not finished yet.
System response
The ALE inbox of the SAP BW is identical to the ALE outbox of the source system
and/or
the maximum wait time for this request has not yet run out
and/or
the batch job in the source system has not yet ended.
Current status
in the source system
Is there anything wrong with partner profile maintanance in the source system.
Cheers
Senthil

Hi,
I will suggest you to check a few places where you can see the status
1) SM37 job log (In source system if load is from R/3 or in BW if its a datamart load) (give request name) and it should give you the details about the request. If its active make sure that the job log is getting updated at frequent intervals.
Also see if there is any 'sysfail' for any datapacket in SM37.
2) SM66 get the job details (server name PID etc from SM37) and see in SM66 if the job is running or not. (In source system if load is from R/3 or in BW if its a datamart load). See if its accessing/updating some tables or is not doing anything at all.
3) RSMO see what is available in details tab. It may be in update rules.
4) ST22 check if any short dump has occured.(In source system if load is from R/3 or in BW if its a datamart load)
5) SM58 and BD87 for pending tRFCs and IDOCS.
Once you identify you can rectify the error.
If all the records are in PSA you can pull it from the PSA to target. Else you may have to pull it again from source infoprovider.
If its running and if you are able to see it active in SM66 you can wait for some time to let it finish. You can also try SM50 / SM51 to see what is happening in the system level like reading/inserting tables etc.
If you feel its active and running you can verify by checking if the number of records has increased in the data tables.
SM21 - System log can also be helpful.
Thanks,
JituK

Systems no longer exist on Report A Product Error page

When I go to SAP Support Portal and click "Report a Product Error" I am prompted to choose the system I am submitting a request ticket for.
When I use either search feature, my system (SBOP formerly known as EPM-PLA in the SAP universe) is not available. Previously I had two systems available - development and production - and now there are none and I can't even proceed.
What happened and what am I supposed to do now? Also, when I go to my message Inbox there are no messages even though I have submitted many tickets and communicated with the support several times before.

I didn't expect any support personnel to read it and respond or provide assistance but I did expect somebody might have an answer. Why would our installed systems suddenly change without authorization?
Thanks

How to delete source system in BI system

Dear Experts ,
recently we finished client copy in BI production system to quality system,
now we are facing problem with source system connections in bI system
in RSA1 APO production system's source system is comes to BI quality system now i need to delete that APO source system in BI quality system ..please let me the process how can i delete source in BI quality
can i delete it as below
log in into BI quality system --> RSA1 --> select source system which i need to deletse --> right click & delete
or we have any other process to delete it.
Regards

Hi Swathimatta,
Apart from the two ways to delete the source system:
1.- log in into BI quality system --> RSA1 --> select source system which i need to deletse --> right click & delete
2.- Execcuting the FM 'RSAP_BIW_DISCONNECT.
If you cannot delete the source system:
Use fuction module RSAR_LOGICAL_SYSTEM_DELETE to delete
the source system:
1 - Go to SE37.
2 - Run fuction module RSAR_LOGICAL_SYSTEM_DELETE.
3 - Fill with the parameters as mentioned below:
      I_LOGSYS          = FUENTE
      I_FORCE_DELETE    = X
      I_NO_TRANSPORT    =
      I_NO_AUTHORITY    =
Or follow the recommendations from note 140276, Solution 2:
"You cannot delete the source system. Two cases have to be distinguished:
    o The source system still exists.
       Switch to Transaction SM59. Find the destination which has the
       same name as the logical system of the source system from field
       SLOGSYS in table RSBASIDOC (see above).
       - Such a destination does not exist in Transaction SM59. In this
          case, you have to create the destination to the source system.
          Name the destination equal the entry in SLOGSYS from above.
          Then return to the Administrator Workbench and repeat the
          deletion.
       - The entry exists but a remote login is not possible. Correct
          the communication parameters.
       - Everything works. Change to Transaction SE37, function module
          RSAR_LOGICAL_SYSTEM_DELETE, Sngl. test. Parameter I_LOGSYS =
          <log. name of the source system>, I_FORCE_DELETE = 'X'.
    o The source system no longer exists or was replaced with another
       source system with the same IP address.
       Proceed as described in the first case but make sure, that the
       field 'Target host' contains a not existing server in the
       maintenance screen of the destination (Transaction SM59). If
       necessary, change an existing entry. Later when you delete, the
       system asks you whether you want to delete, although the source
       system is not available. Select 'Ignore'. "
I hope it can help you.
Regards,
Fran.

Source System no longer exists

Similar Messages

Maybe you are looking for