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

Similar Messages

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!

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

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

Transport InfoSources to New Source System

Hi.
When implementing BW in our QA environment, all InfoSources, and their related InfoPackages, Transfer Rules, Update Rules, etc.) were created using a temporary R3 QAS source system mapping (ex.TMP). We are now removing this temporary client and I now need to change my InfoSources (along with customized Start Routines, InfoPackages, etc.) to point to a new QAS source system (ex. PRM).
Note that this new source system is already identified as a source system for BW and all DataSources created on TMP have been transported to PRM. Subsequently, all DataSources have been replicated from PRM to BW.
However, I'm having trouble on the BW end. I can't easily
transfer the InfoSources, etc. to the new source system. I've asked some BW / Basis folks and they suggest transporting the InfoPackages out-of and then back-into the BW QA client. Is this possible? Is there a better way to push my InfoSources, InfoPackages, etc. from the old source client (TMP) to the new one (PRM)? Thanks!

Dear Dave
Please do not attempt to change the logical system name your self, as I feel that you have not tried it before.
This is some thing that your basis people have to do. Depending on the size of database this change can take from 2-24 hours (not exact times, but just some thing to show the magnitude of the task).
Good luck
/FZA
Message was edited by: Fariborz Zangoui

How to transport FM retraction configuration if source-system changes?

Hi experts,
I have configured FM retraction in ERP through SPRO connecting it to my Dev source system in my Dev ERP. What do I need to do to transport this configuration to my production ERP and make sure the BI source-system changes from Dev to Prod as well? Is there some kind of souce-system mapping as there is in the BI side for the extraction?
For example, I have everything set-up for source-system BWD and I want it to change to BWP when I transport the configuration from ERP dev to ERP prod.
Thanks
Edited by: Pedro Fontes Pais on Dec 2, 2008 6:36 PM

Hi Christian,
Thanks for your reply, but I didn't get anywhere in OKE7 & OKE8 to include the credit records I made in KSAZ in a Transport.
Can you elaborate it more.
Thanks
Amit Goyal

Source system conversion doesn't work after transport

Just transported a query to BW Production and found that the source system is still the same as in DEV.
The conversion is there (QAS-->PRD). But the conversion doesn't seem working in the transport.
Can anyone tell me how to troubleshoot this issue?

Hi,
Please check the following:----
1. RSA1->Source Systems --> Select the source system -->Check. It should take you to the correct source system with a Remote logon.
2. Check the logical system mappings in RSLOGSYSMAP table.
3. http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/70a7b233-8be5-2c10-4190-aed723af5373
Regards,
Suman

Source system assignement in production

Hi all
Before importing any requests which are related to infosource , cubes and update rules into production, do we need to make any source system assignment in production system?
I have directly imported into production but there were no source system / data source assignments to these infosource.
can you please suggest what to do for these souce system assignments in production.
thanks in advance
AN

Hi,
you have to assign the production source system to your BW system. After replication of the DataSources, you can import your development from the BW development system.
Important is the conversion in the SPRO Transaction - Change source system name after transport. In this view you have to type in the source system name of the source system linked to your development system and the name of the source system linked to your production system. During import to production system, BW will automatically change the source system names.
regards
Juergen

Transport: Multiple Source Systems in QA

Hi gurus,
I have developed in BW Dev Transfer Rules starting from one R/3 Dev Source System.
Now I need to transport BW Dev settings into BW QA system, where I have 4 R/3 QA Source Systems.
In RSA1 --> Transport Connection --> Conversion (F8) I can introduce only one record to map Dev Source System with QA Source System.
How can I define that the single Dev Source System must be translated into several QA Source System ?
Is it possible ?
Thank you in advance.
Riccardo.

Hi,
Import 4 times by having Different conversion Each time.
And another thing:
Have you tried to create 4 Conversions at a time with same Source of source system and importing with these 4 conversions at a time. Even I too feel that it would not work. But you should try atleast once.
With rgds,
Anil Kumar Sharma .P

Virtual Transport Path to move BI source system dependant objects.

Currently, our BI Test system (which contains all Transported Objects from BI Dev) is connected to ECC client 100. We want to change BI connection to different Client i.e ECC 115 (this client contain better test Data). We have removed BI connection from Client 100 and connected to Client 115. But our entire Source System Dependent Objects in BI still point to ECC Client 100. To change these Objects to point to the correct Client 115, we are executing the following steps:
1 Remove Source System ECC Client 100 from BI2
2 Connect New Source System ECC Client 115 to BI2
3 Ensure that New Source System Connection to Client 115 have been set up
4 Create a virtual transport path within BI2 for re-import into BI2 queue for the ? Transport Package
5 Open BI2 to assign user authorization in order to be able to create a transport in BI2
6 Copy Source System dependent rules & create Transport
7 Change the Source System Assignments on the target client
8 In SE09 - check that only the required source system has been copied
9 Move the transport in through the import queue
We are stuck at step 4. Basis team says it is not possible to create a transport path from BI2 system to the Virtual System (in the same BI system) and move it. But I am pretty sure that this can be done as I did this earlier in my previous project. This is something related to Basis so I cant help them.
Do you have any idea, how this can be done?
Any help will be highly appreciated.

Hi
I do not understand few things :
- why did you remove the source system ?
- what do you mean by BI2 ? It is the same QA system as before....So why do you need to create a virtaul path for transport ?
The steps you should have followed is to use BDLS transaction to rename ECC100 to ECC115
The source dependant objects would have been renamed automatically.
By the way, you now can start over from your dev and collect the source system dependant objects
Transport the request in QA, paying attention to change the transcodification table to target ECC115 and not ECC100...
Hope it helps
PYG

BI Production as a source system on BI Development

We have a requirement to make the Production BI environment as a source system on the Development BI environment. This is required with a view to make greater live data available in a particular cube on the Development box to aid in future enhancements
The same Production BI environment is again reaquired as a source system on the Quality BI environment. This is required with a view to make greater live data available in a particular cube on the Quality box to help in testing/UAT activity
My question is that corresponding to the source system BI PROD on BI DEV and source system BI PROD on BI QA. What can I keep as a source on BI PROD itself. Can/should BI PROD itself be the corresponding source system on BI PROD ? Is it technically feasible. What are the pros and cos/risks of such a design design

Hello,
You can add the BW production system as a source system in the DEV and QA system without any problem. I don't believe there is any need to attache the production system as a source to itself, this connection alrady exists (the so called myself connection), if you goto RSA1 and under source system you will find a source system connection for production that points to it self, this is used for all internal datamart loads that might occur in the production system itself. Therefore there is no need to add the system again with a connection to itself.
Best Regards,
Des

Source System of Dev System is not active QAS System.

Hi
I am trying to transport my SAP-BI flow from Dev System to the Quality System.
but I am getting an error "Source System of Dev system is not active in QualIty System.
I have checked RFC Connection ,everything is fine.Please help.
Thanks and Regards,
Asim

Have you checked the mapping of the source systems in the conversion table (RSLOGSYSMAP)?
Usually, DEV source systems are not available in QA, so when you transport to DEV, the source system assignment has to be changed to a QA source system.
For example, source system CRDCLNT100 (CRM DEV system) is connected to BWDCLNT100 (BW Dev)
and CRTCLNT100 is connect to BWTCLNT100.
Objects in BWD which are assigned to CRD, have to be re-assigned to the CRT source system when transporting them from BWD to BWT.
The mapping table is maintained in RSA1, menu option tools > 'mapping of the source system names'.
Jan.

Transport managment, source system changed in import

Hi all,
i faced with the need to change the source system in transport management. I mean, dev source system to assign a different test system source. now is the following:
InfoPackage ZPAK_4MSK400H4M9FGMEKV9ZGDSN4M, source system LGDCLNT300 changed by source system LGTCLNT010 in import (tr STMS).
I'm looking for opportunities to change the target source systems LGPCLNT010.
Where can I find a setting to change the source system during the import?
Thnx.
PS LGPCLNT010 source system already exists in test. only need to assign LGDCLNT300 (DEV) -> LGPCLNT010 (TEST).

Hi,
The entries are maintained in table RSLOGSYSMAP. Goto SM30 put the table name and click on maintain.
Or simply goto transport connection from RSA1 and click on "Conversion button" on tool bar.
Regards,
Durgesh.

Source System mapping for BW configuration transport

I create a data model mapped to the testing source system i.e DEV201 but the configuration source system is DEV200.
Now i am about to transport the BW configuration to BW-QAS , I am wondering if I have to assign the data model to the config. source system(DEV200) or i can created a transport request attached to DEV201 ?
Is there any concern on this ?

Hi,
I'm not clear your system landscape. Do system landscape like that:
BWD (BW development) --> DEV201
Now you want transport all objects to BW_QAS with connected to DEV200.
If this is true, you do like this:
- On BW_QAS: create source system (DEV200). Maintain conversion of source system after transport (Original: DEV201; Target source system: DEV200).
- After that transport your modeling from BWD to BW_QAS.
Hope this helps
BR
TRUC

Conversion of Source System in BI 7.0

Hi Guys,
           We created a Generic Extractor and replicated the datasource (7.0) in BI Development. I have an ODS with Transformations for this datasource. Everything works fine in development. The extractor has been transported to R/3 quality and replicated (7.0) in BI Quality. The ODS and transformation has been transported to BI Quality.
But after the transport, when I look at BI Quality system, the transformations are not active. The strange thing is that the datasource linked to the transformation still shows the R/3 Dev source system. I can see the datasource itself connected to R/3 QA source system, but the datasource linked to the transformation shows the R/3 Dev source system. It seems to me that something has to happen to change the source system of the datasource linked to the transformation to the R/3 QA system. We have installed SP11.
Can anyone please help me out with this. We are literally running out of time.
Thanks a lot in advance.
Harsha.

It should read like these
You are mapping Dev ECC to QA ECC and BI Dev to BI QA to load Data
Once done you can check these entries in table - RSLOGSYSMAP
should look like these
Original source system                   Target system
ECC Dev                                  ECC QA
BI Dev                                        BI QA
Hope it Helps
Chetan
@CP..

Production transports referring to Dev Source system

Similar Messages

Maybe you are looking for