Source system in Production doesnt exists Error RC- 8

Hello experts!
We connected a second source system to our 7.0 BW. We transported from development to quality system and everything is fine. Now we want to transport to production and we got RC=8 and the message that our "source system does not exist"
First we checked our source system. It is ok. we can replicate datasources, load units and currencies. But when we want to transport something what is directly connected to the source system we got everytime a RC=8 because of source system. For sure, we checked our "Conversion of logical source systems names". We checked if the mapping from development to productive is correct many times but we can find no error.
Is there something I can not see?
I tried to transport Transformations, DataSource Migration, other things connected to 7.0 and 3.x DataSources. Nothing works. I transported a transformation got a little different error like no rules exist because missing infoobjects in source or target or they are not activated. But target seems to be ok and source also have the fields.
Also I have searched the previous threads I have got what I have done but for sure some thing I am missing !!
Any Ideas???
Best regards,
Yash

Thanks Murali for your prompt reply,
I have manged to do the conversion settings again and now the source system client problem subsides !!!
But when I import the requests again from QA to PRD it says that some DS cannot be activated due to inconsistency in CRM production system. Actual message is.
Start of the after-import method RS_ISMP_AFTER_IMPORT for object type(s) ISMP (Activation Mode)
Mapping between data source 0CRM_SRV_CONTRACT_H and source system PC4CLNT400 is inconsistent
Start of the after-import method RS_ISCS_AFTER_IMPORT for object type(s) ISCS (Activation Mode)
InfoObject Source System of Preceding Doc. ( 0PRELOGSYS ) is not active, total of 4 inactive InfoObjects
InfoObject Exchange Rate Date ( 0CRM_EXCDAT ) is not active
InfoObject Exchange Rate Type ( 0CRM_EXCTYP ) is not active
InfoObject Quotation GUID ( 0CRM_QUOGUI ) is not active
InfoObject Source System of Preceding Doc. ( 0PRELOGSYS ) is not active
InfoObject Text of CO Document Line Item ( 0CO_ITEM_TX ) is not active
InfoObject Text of CO Document Line Item ( 0CO_ITEM_TX ) is not active
InfoObject Text of CO Document Line Item ( 0CO_ITEM_TX ) is not active
InfoObject Text of CO Document Line Item ( 0CO_ITEM_TX ) is not active
is that due to the DS .. some are in BI 7 cannot be mapped with 3.X ?
I will be importing a new request all the way from DEV to QA and Then in PRD as of now to see the inconsistency once again.
Cheers
Yash

Similar Messages

Source system ECQCLNT320 does not exist in BI Production

Hi,
When i am transporting the BI objects along with the datasources it is giving the following error.
our system Landscape:
BI Dev. & BI Qty Same Box
ECC Dev.
ECC Qty
ECC Prd.
in our landscape BI dev and BI Quality are the same Box, i am transporting BI cube objects along with ECC quality system datasources from BI dev. system. But when we import the cube request the following error is occuring.
Please help me as i am in typical stage.
ERROR: Start of the after-import method RS_RSDS_AFTER_IMPORT for object type(s) RSDS (Activation Mode)
Source system ECQCLNT320 does not exist
Can we transport the ECQ datasources from BI dev system where i am using them.
Thanks,
Baswa

Hi,
RC on ECQCLNT320 check the source connection under sourcesystem tab in Rsa1,it might having issue else
Check in the RSA6 (Sourcesystem) wether DataSource is active mode or not ,
Go to Tcode RSDS for Replication of DataSource in BW system .
Regards,
Satya

Source system BW100 does not exist

Hi Guru's
I'm trying to transport the datamart infopack from dev to QA and it's failed due to "Source system BD1_100 does not exist; InfoPackage ZPAK_DVDXOWDKOMSF5YW6F4EDXMXL1 deleted".
I've tried to trnasport datamart as well but still failed what could be the problem?
Regards,
Ramana.

Hi Raman
It simple. If you want load data from QAS to QAS then you need take conversion when transport request importing to QAS. So you need record BWDEV ---> BWQAS in "Transport connection".
IF you want load data from BWDEV to BWQAS then you need BWDEV as source system in QAS and no record in "Transport connection".
http://help.sap.com/saphelp_nw04/helpdata/EN/80/1a616be07211d2acb80000e829fbfe/content.htm

Error message from the source system, Caller 09 contains an error message.

Hi,
Guru's, i got an error massage when my process chain is running(Daily) in BIW 7.0, the error got in Data Loading from source to PSA or data targets. The errors having the below details
Error message from the source system
Diagnosis
An error occurred in the source system.
System Response
Caller 09 contains an error message.
Further analysis:
The error occurred in Extractor .
Refer to the error message.
Procedure
How you remove the error depends on the error message.
Note
If the source system is a Client Workstation, then it is possible that the file that you wanted to load was being edited at the time of the data request. Make sure that the file is in the specified directory, that it is not being processed at the moment, and restart the request. "
Can any body help me out of this situation what to do and how to resolv ethe problem.
Thanks and Regards,.
Taps....

Caller 09 is a very common issue - please search the forums before posting....
Arun

Transfer Rules for two Source System in Production

Hi All,
I have a question.
I have source system ECDCLNT230 (ECC Devlopment) which is connected to BIDCLNT200(BID Devlopment) I have two production source system ECPCLNT410 (ECP Pre Production Client) & ECPCLNT400 (ECP Production Client) which i want to connect with BIPCLNT400. when i transport my content from ECDCLNT230 to ECPCLNT410 and ECPCLNT400 , it works fine. i created 2 source system in BIPCLNT400 and replicated data source in to BIPCLNT400 so all data source has replicated.
Now when i transport the request from BIDCLNT200 to BIPCLNT400, i need two transfer rules, two transformation one for each source system. for that what kind of settings are required.
Thanks is advance.
Regards,
Komik Shah

Hi,
If I understand correctly, in your BW Production system, you want to connect / load data from your ECC Pre Production and Production system.
In this case, to automate the transport needed for changes of transfer rules for both source system, you will need to have two tranfer rules in your BW Dev. You can either create two source system in Dev pointing to the same ECC Dev system, or one to ECC Dev and the second to ECC QA. Use different name for this two source system.
In BW Production, you then then maintain the source system conversion of both source system.
Thanks.

"Document doesnt exists error" in MM while changing purchase order

While creating purchase order document number gets created but when i view the created document in me22 it shows the error "Document doesnot exists".can anyone help me in this issue
Regards,
Ramesh

HI
After creaating order check it in VBAK.
Aditya

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

Transports while importing DS error "Source system QAS does not exit "

Hi Experts,
      For a specific reason we are importing a DS from quality to development.While importing DS in Development side we are getting an error " Source system QAS does not exist".Error message as below:
   Start of the after-import method RS_ISMP_AFTER_IMPORT for object type(s) ISMP (Activation Mode)
   Source system QAS does not exist
   Start of the after-import method RS_ISTS_AFTER_IMPORT for object type(s) ISTS (Activation Mode)
   There is no DataSource with these attributes
   Start of the after-import method RS_ISTS_AFTER_IMPORT for object type(s) ISTS (Delete Mode)
   Start of the after-import method RS_ISMP_AFTER_IMPORT for object type(s) ISMP (Delete Mode)
   Start of the after-import method RS_ISCS_AFTER_IMPORT for object type(s) ISCS (Delete Mode)
   Start of the after-import method RS_ISTD_AFTER_IMPORT for object type(s) ISTD (Delete Mode)
   Start of the after-import method RS_ROUT_AFTER_IMPORT for object type(s) ROUT (Delete Mode)
   Errors occurred during post-handling RS_AFTER_IMPORT for ISCS L
   The errors affect the following components:
      BW-WHM (Warehouse Management)
   Post-import methods of change/transport request CXCK900023 completed
        Start of subsequent processing ... 20090306024549
        End of subsequent processing... 20090306024550
   Execute reports for change/transport request: CXCK900023
   Reports for change/transport request CXCK900023 have been executed
        Start of................ 20090306024550
        End of.................. 20090306024550
   Execution of programs after import (XPRA)
   End date and time : 20090306024550
   Ended with return code: ===> 8 <===
Our system sap bi is not new system, we are using from long time.Transports are working while moving dev to quality and quality to prod.
Can any body suggest on this.
Regards
Vinod

Hi vinod kumar,
i hope you need to map source system From QAS to DEV system,
genereally from DEV to QAS configuration will be there, but here request is moving from QAS to DEV so i think this should be configured.
RSA1-> Tools -> conversion of logical system names -> maintain original system and target system name for both BI and ECC systems.
Regards
Daya Sagar

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

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

Source System Error While transporting

Hi SDN,
We are transporting requests to a deployment test box SN1 and we are getting this error message while we never got this error message transporting to QAS and in QAS we did not need to create DEV010 as a source system - setting up RFC connection was sufficient.
Any thoughts?
===========================================================
Source system DEV010 does not exist
Message no. RSAR409
Diagnosis
Source system DEV010 is not known.
System response
The imported data for data source 8ZM_C42 was deleted again as the referenced source system does not exist and no mapping is defined in table RSLOGSYSMAP to an available productive source system.
Procedure
Create the referenced source system in the Administrator Workbench or define a mapping to a known source system in table RSLOGSYSMAP.
You get to the maintenance using Tools -> Conversion of the logical system names.

Speak to your basis team and ask them to make entries in table:
RSLOGSYSMAP .
Are you trying to transport info source or any source system dependt object? If so, this error is understandable.
This has been discussed several times and pl search the forum.
Ravi Thothadri

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

Conversion of source system names --- error in transport

hi
i want to transport my object from Dev111 to Quality222
but the transport ended up in error 8
it gave the error...
Source system PRODUCTION333 does not exist
I am confused,
shouldnot it should give error related to Quality system ???
how should be the mapping in Source system names?
after research it seems it should be maintained in
RSA1-TOOLS-mapping of SOURCE SYSTEM NAMES.
i have following systems...
BW- DEV111 QUTY222 PDN333
R3 DEV121 QUTY242 PDN363
What should the entries look like in which system

Landscape is -Transport should be send from Deve-Quality---Production
BW....................................
DEV111 QUTY222 PDN333
R3.....................................
DEV121 QUTY242 PDN363
CAN you advise if the entries SHOULD look like below in Quality and Production System???
Quality system should have entries like:
bw DEV111.............. bw Quality 222
r3 DEV121................ bw Quality222
Production system should have entries like:
bw Quality222.............. bw Production333
r3 DEV242................ bw Production333
Q1 ......IS THIS HOW ENTRIES SHOULD BE IN Quality & Production system???

Production transports referring to Dev Source system

Hi All,
We have Dev -> QA -> Prod setup for both BW and R/3.
In BW corresponding source systems are created in each server.
Transport Connection Source sytem mapping :
In BW QA , I have mapped the source systems R3DEV to REQA.
In BW PRD ,I have mapped the source systems R3QA to R3PR.
When I move the TP from QA to Prod , it gives error source system "R3DEV" does not exists.
Why is this behaviour ? It should refer to R3QA.
Shall I maintain R3DEV to REPR in production ?
Pls let me know , it's a question of production !
Regs,

Hello Subir,
As far as I am aware,when transports are done,the transport first moves from Dev to QA.
Then QA testing is done.Once testing confirmed OK,next is step to transport to prod system.
Now,I believe transport is done not from QA to Prod but from Dev to Prod system.
So I think u have to change source system mapping so that dev changes to prod system once transported.
Request others to confirm my thoughts..
cheers,
Vishvesh

Transporting 0material_attr gives reference source system error...

Hi Experts,
I know its not recommended but for some reasons we were trying to move 0material_attr data source and transfer rules and transfer structure 0material_attr_ba from quality system (QAS) to Development system. And every time we are getting the error "Source system QAS does not exist" while importing the request in DEV.
The reason for this error is that it is still keeping the reference source system of quality as QAS which is not there as logical system in DEV. My question is isn't it should automatically refer to R/3 DEV when imported to development system.
Thanks
Vishal

Hi,
As pointed out by Joke in the previous post, you need to maintain the mapping of logical system name for transportation.
In Dev, go to RSA1> Tools--> Conversion of logical system names.
Here create new entries.
Your Original Source System would be the QAS Logical System Name & Target Source System would be DEV Logical System Name.
Once entry is saved, re-import the transport request and check.
Hope this helps!

Source system in Production doesnt exists Error RC- 8

Similar Messages

Maybe you are looking for