Source system -SAP R3 Transportable

Gurus quick question,
I have a source which is connecting to SAP R3system.(BW devlopment).Do I need to create the similar source system in BW QA environment or can I transport from Dev to QA BW systems.
or Can I create RFC,Port definition,partner profile,Source system in the QA BW system also.
Please provide some tips.
Advance Thanks all.

hi smartone s,
happy new year.
you need to create source system in your bw qa,
create rfc both bw qa and r/3 connected to it.
hope this helps.

Similar Messages

Conversion of source system names after transport

Hi gurus,
Please someone can tell me how to configure the "conversion of source system names after transport" in the BI system as my transport is not working on a new BI System ?
Thx in advance

Hi Firmin,
You can do this in RSA1 in tools under conversion of logical source system names.
Here you maintain the development system or the system used for development as the source system.
You will have to mention the logical name of the development system.
In the target system column mention the system in which the transports would be imported. This could be the quality system or the production system.Again you would have to mention the logical system name
Check the folllowing link for more informationn on this.
[Conversion of logical names|http://help.sap.com/saphelp_nw70/helpdata/en/46/94b1fc87bd13eae10000000a155369/content.htm]
Hope it helps you ,
Best regards,
Sunmit.

Conversion of Source system name after transport

Dear All,
I need one clarification.
Say you have developed a fresh modelling in BW Dev server and your source system is R3 dev system. Now you need to transport all the request to BW Quality system but the source system will be R/3 quality system.
For this change of source system name we need to maintain some mappings.... From Tools menu there is an option to do this...
My doubt is in Production server how do we maintain the mapping...
Quality system ---> Production
or
Development system---->Production.
Hope i am clear....
Thanks & Regards,
Anup

Hello Anup,
The question you raised particularly is about the change of source system when your transports are alredy done. For this, i would like to say is that when you do any transports in the R/3 or BW front, the source system change is done only when :
1. It is done, when you have a single base system and different R/3 (source system)
2. If you have a single source (R/3) and a single destination (BW Quality), you do not need to map the source system.
Well, i case that is needed, you may do it via :
1. Go to RSA1
2. Go to Tools.
3. Tools -> Conversion of source system.
In the right most table column, provide the source system you need to connect with your BW system.
This will internally connect you with the specified R/3 system.
Hope it helps!
Neha.

Importance of "Source System Assignment While transporting the objects

Hi Friends,
What is the Importance of "Source System Assignment While transporting the objects. And when do we select this icon. what is the exatly significance for this.
Thanks in advance for all......
Regards,
Ramesh.

HI Rameshpennabadi ,
This option is only enable for object like transfer rule, data source and IP if you want them to assign source systems,other wise the dialog box Choose Source system by Default? appears.
Thanks,
Deepak

BW: Connect to new source system via special transport

Hello everyone!
I have a BW system connected to an R/3 source system. I have made a copy of the source system. Now I want all my models to be connected to both source systems. I heard that this can be achieved via special transport (i.e. place all source system dependant objects into a special transport request to be imported back into my BW system, but with the new source system assignment). Does anyone have any documentation on how to do this?
Best Regards and Merry Xmas!
Luís Andrade.

Hi Luis,
There are two parts,
1) If you want to transport all your objects from current R/3 system to newly created r/3 system then you can create a TR and use it in SCC4 transaction during client copy. In the same fashion you can use RSA1---> transport connection and use the TR for system copy. After that once you release this TR all the objects will move from one system to another.
2) But if you have already moved all the objects in source system but now you want them to replicate in BI then go to SAP BI system select your source system and then from the context menu choose replicate datsources option, it will fetch everything from respective source system in BI.
Regards,
Durgesh.

Source system mapping for transport

We just create a change request for an InfoSouce. Now we transport this change request from DEV system to TEST system. But when this change request was imported on TEST system, got the "Method Execution" red error which can be checked through STMS in log. The red error msg is "Source system A does not exist", where A is our R3 DEV server. Actually we need the source system B which is R3 TEST server in the InfoSouce transported into BW TEST system, but the problem is that the change request was created on BW DEV which uses A as Souce System in the InfoSouce, then how to make the InfoSouce has B on BW TEST after the transport?
Roberto gave an answer (see my another post: What should BASIS do for an InfoSource transport for Souce System change?) as below:
"you have to set the source system mapping in your target system in RSA1, Transport Connection -> F8 and then import your request again !"
But he said this setting would be done at the target or TEST system. I don't think it's right, this mapping setting should be done at the DEV system since our transports are created in DEV Transport Connection, am I right?
Please verify who is right?

hi Kevin,
let's refer to sap's doc
'bw and transport'
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/3010ba90-0201-0010-2896-e58547c6757e
p. 33
'.. make sure to set the source system mapping configuration in each <u>target system</u> to convert the transfer rules ..'

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

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

Mapping of Quality System (Source System) after the Transport

Hi,
We have two quality source systems like 300,400 in sync with the development ,to extract the data . I am transporting Transfer rule mapping from the development .After the transport to Quality , the changes are reflected in 300 . But I want to change it from 300 to 400 i.e.Transfer rule mapping should be reflected in 400. What is the transaction code used to change this mapping in BW System?
Thanks for your time.
Thanks & Regards,
Raja

Raja,
When you transport - you have a transport mapping in your dev system that tells BI which system connects to which system in the QA system for instance
FLAT_FILE in DEV could be Z_FLATFILE in QA - accordingly the datasources are mapped. Also the transfer rules are source system specific which means that you change the source system - the transfer rules will have to be recreated.
Instead what I am asking you is to maintain the mappings for client 400 in DEV and then maintain the mappings as 400 - 400 in the qa system and then transport the same. If your dev systems are linked to QA300 and your mapping says QA400 the same will hold good.. however if you have QA300 in dev to be sent to QA as QA300 and then change the source system .. it will not work since this will be seen as a source system change and you cannot change the same. You could try BDLS and try changing the logical client name ( I am not sure if it is BDLS ) or change the RFC connection parameters in SM59 but am not sure if it would work....

Source System mapping while transporting objects from Q to P

Hi All,
I have moved all my transports from BW DEV to Q twice with different source system mappings, say R3D to R3Q and again R3D to R3X, as I have to do testing from both the source systems.
Now, I have to move all those transports to PROD and I found out that they will be moved from Q to P and not from DEV to P. In such case, what source system mapping should I maintain in P? Is that R3Q to R3P or R3R to R3P?
Hope I am clear with my question. Please let me know if it is not clear.
Thanks,
RPK.

Hi Nasiroddin,
Itseems I am not clear with my question. Let me put it in another way.
My BWQ is connected to two R/3 source systems, say R3Q and R3X where as my BWP is only connected to R3P. While transporting the requests from BWQ to BWP, I know that I have to maintain the source system mappings(Tools->Mapping of the source system names). Now I am in doubt about what mapping do I need to maintain(either R3Q->R3P or R3X->R3P)? Which source systems transfer rules etc.(all source system dependant objetcs) will be transported, either R3Q or R3X?
Thanks,
RPK.

Cannot see Source system Assignment after Transporting to QA

Hi All
I need your help once again, I transported a ODS object from DEV to QA, In dev it has a source system assignment but, in QA I don't see the source system assignment.
I went into sm59 and did a test connection and authorization, everything looks fine. I did a restore connection and replicated data sources, and transported again, but still I don't see the source system.
On R/3 side the application componenet nodes did not get transported with the data source.
Please let me know if I am missing anything that needs to be transported.
Thanks
Latha

Hello Latha,
Please see the import log for that transport in se01 in the BW dev system.What is the exact error messages it gives?U may need to also look at the long text of the messages.
Another point abt what u have said..that in the corresponding R/3 QA system,the datasource is not showing up in rsa6,am I right?
then there was some problem with the transport from R/3 dev,that contained the datasource definition.check that transport too..
cheers,
Vishvesh

Transport of Source System assignment for a Virtual Cube

Built a transport with the datasources, transfer rules, cubes etc..
After transport to my Q system - in the Q system I am not seeing any source system assignment for my remote cube
OBviously it exists in Dev
Everythign else is fine - datasource, infosource trasnfer rules but nothing underneath the infocube where the source system normally is
transport before and after in the transport conenctor picks up nothing to be transported
Logical system mapping table in Q is fine (naturally - because the datasouces got there) - replicate all done
Any ideas?

hi Simon,
check sap help
http://help.sap.com/saphelp_nw04/helpdata/en/3b/63c620e18411d4b2d90050da4c74dc/frameset.htm
The source system assignments are local to the system and are not transported.
hope this helps.

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.

Unable to Create Source System under 'SAP'

Hi,
We are on BI 7.0 and I am trying to create an R/3 Logical System (RSA1 - Source Systems - SAP - Create...)
But everytime I try to do that logical system is getting created under 'BI' folder (instead of 'SAP' folder). Do you know why this could happen?
Thanks.

Hi SDNBI,
I have stumbled across the same phenomenon. Netweaver contains BI and ERP. When in the specific ERP system you want to create under the SAP folder you have in the past used the RSA1 transaction then the system thinks that this system should belong to BI folder. Hence it places that in BI folder. On the other hand when you have not executed RSA1 in the system you want to create then it should place it normally under the SAP folder because in that case it doesnt relate it to BI.
Hope that helps
Assign points if helpful.
Rgds
John

Prevent objects being transported for Sandpit source system

Hi there,
We have a 3-tier systems landscape for BI: DEV, QAS, PRD (we do not have a sandpit BI). In our R/3 development system we habe two clients which are both setup as source system for BI DEV. One of the clients in R/3 DEV serves as sandpit in that system and objects can't be transported from it. However, since this client is connected to BW, objects related to this source system can be transported from BI DEV. We want to prevent that, so only the objects in BW DEV for the real R/3 DEV development client are allowed.
Is there a way in BI to configure a source system in such a way (other than via security roles/profiles), that objects related to this source system can't be transported?
Cheers.

Sander, you should post this in BASIS also. By posting in both the forums, you have a better chance.
In case BASIS folks say that they cannot stop this, try this work-around.
In BWQ, in RSA1, there is a Source System Mapping in one of the tools menu. There, your DEV is mapped to QAS, etc.
There, you may have your R/3 DEV mapped to R/3 QAS.
See if there is an entry for your R/3 Sandpit/Sandbox. If there is one, leave the mapping for it as Blank.
See, the only Objects that are related to Source System in BW are InfoSource-DataSources. If there is no mapping for SOurce System in BWQ, then the transport will fail.
This is just a thought.
Uday-Ram Chamarthy

Source system -SAP R3 Transportable

Similar Messages

Maybe you are looking for