Transporting SOURCE SYSTEM

Hi Experts,
I created a Flat File Source System in BW Development system based on that i created DSO,CUBE,MULTICUBE,PROCESS CHAIN and REPORTS.
Issue :
I need to transport them to Test and Production system.There is no Flat File source system avaliable in Test & Production....I know that we don't Transport Source Systems across BW Environments...how to deal with this...do i need to ask our basis team to create source systems in Test and Production before importing any transports.

Yes - you basis guy will help you to setup the source systems.
STEPS TO CREATE FLAT FILE SOURCE SYSTEM
step:1 select source systems under modeling in AWB.
step:2 select Source Systems root node.
|---> context menu
|--->create......
step:3 select your required source system Icon.
(in your case it is PC Icon).
there it askes for a logical.......and source system name...
here u can specify any name of ur wish
for example:-
logical sys name --- PC_FF
source system name --- flat file source system*
*press Continue * button.
Observe the activation icon to confirm the successfull creation(_glowing lamp icon_ symbol)
You also can have a look:
http://help.sap.com/saphelp_nw70/helpdata/en/ac/4a4e38493e4774e10000009b38f889/frameset.htm
Hope it helps..

Similar Messages

RSDS transport - source system not exist

Hello Guys
i have a problem during transport of DataSource from DEV to QUA.
The error is:
Start of the after-import method RS_RSDS_AFTER_IMPORT for object type(s) RSDS (Activation Mode)
Source system D18CLNT228 does not exist
I have check already the transport table RSLOGSYSMAP and insert item to map the DEV system with QUA system (this done in both system,develop and quality). I check also the source system ID and everything seems update correctly (in both system develp and quality).
Anyway during the transport i have this error and when check in QUA system i have the DataSource, seems map correctly with the right source system but is not active...
do you have any suggestion
please let me know
regards
B.

Hi
check in your QUA system if corresponding source system is linked to it. Also currpospong trasports in source systems are moved properly.
Regards
Sudeep

How to transport source system dependent objects

Hi everybody,
I've read several questions about how to transport source dependent objects between systems and I still don't get whole picture
say I have BWDEV attached to R3DEV and
BWQA attached to R3QA
and I want to transport transfer rules from BWDEV to BWQA
1) should I create, by hand, the source system R3QA in BWQA and replicate its datasources in the first place?
2) or it has to be transported from BWDEV and "some how" converted in BWQA
3) where does the source system name mapping has to be done: in BWDEV, BWQA or in both
4) in order to do the mapping of names in BWQA I need to create the corresponding R3QA, otherwise I don't have the entry under TargSrceSy when executing tc RSLGMP
I really apreciate an step by step process for the above scenario
thanks a lot

Hi Juan,
Let me try to shed some light. Before you can transport dependent objects in the BW side, you have to make sure that the necessary dependencies in the R/3 side have already been transported. For example, if you have a datasource in R/3, you have to transport that from dev to QA first (before you transport anything in BW). Then, in the BW QA box you have to replicate the datasource before you can transport any BW objects in the BW QA. Then before transporting anything to BW QA and after replicating the datasource in the BW QA you have to go to RSA1->Tools Menu->Assignment of Source System to Source System ID menu item and make sure that R3DEV is mapped to R3QA. It is only after all the said checks have been done that you can transport objects in the BWQA.
Here are my answers to your questions:
Q1: This depends on your datasource. Some datasources can be transported. Some can be created in the QA box itself. But in both cases, you have to make sure that DataSource exists in R3QA and then replicate it in the BWQA.
Q2: The conversion follows the setup in "Assignment of Source System to Source System ID" in RSA1.
Q3: The "Assignment of Source System to Source System ID" in RSA1 has to be done in the BWQA.
Q4: Yes, you have to setup the R3QA Source System in the BWQA.
Hope this helps.

Transporting with diferent source systems.

Hi experts,
I am quite new in BW.
I have been developing some thing in sap BW.
I have Development, integration and Production in both BW and R3 source system. Each one should be connected with each other. So, development with development, integration with integration and production with production.
Here comes my doubt. All i have done is in the development systems. Now I want to transport and i don't know how to do this c'ause I want all the same things but connected to a different source system, and I think that when i am transporting I will have the Integration Business Warehouse connected with the development R3 system.
What should I do to avoid this and transport all but with a connection with a different system? Can anyone give me a clue please?
Thank you all!
Artur.

Hi,
BASIS team will comfigure the connection betwen BW systema nd R/3 system for all three environments.
R/3    DEV     -
>            QTY   -
>             PRD
              I                              I                        I
BW    DEV    -
>            QTY -
>               PRD
for transports, source systems Transports (R/3 datasource and tables) will be transported to QTYand PRD systems
and
for transports, BW Transports (BW infoobjects, DSO, Cube, Transformations....) will be transported to QTYand PRD systems.
[CTS and BW Transports]
[https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3010ba90-0201-0010-2896-e58547c6757e]
Regards
Daya Sagar

Assigning Source System to an InfoSource

For some InfoSources I sometimes have problems when I try and transport Source System assignment and datasource assignment.
In the past I have just done this assignment on the respective systems.
Is there potential consequences of doing the assignment outside of a transport? Thanks

Hi Niten,
If the assignmnet is "in sync" with the other systems where it was orginally assigned then there should be any issues.
However the correct method (also recommended by SAP) is to transport the assignments.
Bye
Dinesh

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 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

Transport Error - DS does not exist in Source system

Dear All,
I am getting below Error while transporting the DSO from DEV to Quality.
DataSource 8ZM_ALT does not exist in source system DCQCLI041 of version A.
I have checked the dataosource is active and available in Development system. But Its giving error while importing.
As per the dataflow the data of this DSO is updated to Cube.
Has anyone solved this issue, because i have checked in SDN but there are no suitable answers.
Regards
Sankar

Hi,
Your right I am transporting ZM_ALT Dso . The following log of the error we are getting.
DataSource 8ZM_ALT does not exist in source system DCQCLI041 of version A
Mapping between data source 8ZM_ALT and source system DCQCLI041 is inconsistent
DataSource 8ZM_ALT does not exist in source system DCQCLI041 of version A
Field /BIC/ZM_AA will not be delivered from DataSource 8ZM_ALT in source system DCQCLI041
Field /BIC/ZM_APPL will not be delivered from DataSource 8ZM_ALT in source system DCQCLI041
Field /BIC/ZM_BEM will not be delivered from DataSource 8ZM_ALT in source system DCQCLI041
Field /BIC/ZM_MOD will not be delivered from DataSource 8ZM_ALT in source system DCQCLI041
Field /BIC/ZM_NCDS will not be delivered from DataSource 8ZM_ALT in source system DCQCLI041
Field /BIC/ZM_NDESC will not be delivered from DataSource 8ZM_ALT in source system DCQCLI041
Field /BIC/ZM_NES1 will not be delivered from DataSource 8ZM_ALT in source system DCQCLI041
Field /BIC/ZM_NES2 will not be delivered from DataSource 8ZM_ALT in source system DCQCLI041
Field /BIC/ZM_NIN will not be delivered from DataSource 8ZM_ALT in source system DCQCLI041
Field /BIC/ZM_NPCS will not be delivered from DataSource 8ZM_ALT in source system DCQCLI041
Field /BIC/ZM_NPN will not be delivered from DataSource 8ZM_ALT in source system DCQCLI041
Regards
Sankar

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

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

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.

Error while source system creation/Source system transport

Hi,
     In our BW implementation, the system landscape is only 2 servers. One is BW Dev, another is BW Prd. All configurations are done in BW Dev and I extracted the data from QAS for this BW Dev system.
     Since we cant create the source systems in the BW Production system, I tried to create the source system for the SAP R3 Production system in BW Dev and trying to transport this to BW Production Instance.
     I have two queries.
1. Is this way is correct for creating the Source System for BW Production system?
2. When I tried to activate the source system I am getting the following error messages. (I tested the RFC Destinations. There is no problem, I also done the configurations for logical system creation and client assignment in both the systems).
Error in source system GWPCLNT900
     Message no. RSAR502
Diagnosis
     With Remote Function Call to system GWPCLNT900 error connection closed
     (no data) ccurred.
Procedure
     Remove the cause of the error.
When tried again I got the following error message
Basic type ZSBB030 doesnt exist. EA 447
Result of the destination check: Timeout RSAR 375.
Could anyone throw some light on these errors?
Thanks in advance.
Krishna

Hi,
you need to maintain the logical systems on both R/3 and BW. You also need to set up the RFC connection with users that can log in to the other system. The R/3 system must be open for customizing in scc4.
In transaction se03 the system change options for 'Business Information Warehouse: SAP Namespace' and 'Business Information Warehouse: Customer Namespace' may need to be modifiable. I am not completely sure about this.
The last thing I will mention is that I have seen source system creation fail when the RFC-users are system users, and the source system creation worked if the RFC-users was display user while creating the source system. The RFC-users must be changed back to system user later...
Please look at best practice documents on a more step-by-step guide...
Best regards,
Christian Frier

Assignment of Source System in quality after transport

Hi Experts,
We have implemented the Inventory management standard flow in Development,
Now to tell you, we have multiple landscape over here,
Depending on the project, and the fesiblility for the client, the tranport layer is been decided,
But for sure we have multiple source system,
By multiple source system, i mean not the other components like R/3, SRM or APO,
but for R/3 itself we have multiple boxes at each layer,
Now when transported to quality,
the standard objects are reflecting after few errors corrected and re transports,
But the source system which it has picked for the BF BX and UM datasource is not that i require according to the transports landing for the R/3 developments,
AT DEVELOPMENT LAYER,
BW development is GDA, which is having the source system connection to development R/3 (GD0),
AT QUALITY
We have BW as EQ3,
For R/3 we have EQ0 and NR0,
All the transports have reached in the respective target quality system,
But the data sources are having source system connection to NR0 and not EQ0,
I want it to be EQ0 as the data lies over there.
How do i resolve this ?
Thanks and should be appricated for your efforts in helping.

Hi Daljeet,
You should set the Source system Conversion option in Transport Connection before Transporting the objects to QA and PRD.
You can do this using the button 'Conversion' next to the button 'Source System Assignment'. Here you can specify the Target source system name after the Transport.
If you want to change all the assignments from NR0 to EQ0, this article will be helpful for you.
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/805eefcd-5428-2d10-c0ab-dc27a95b2c81
Get the help of your BASIS team also.
Refer this thread.
Re: source system in RSA1 is diiferent to the datasource in infoprovider

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

Transporting SOURCE SYSTEM

Similar Messages

Maybe you are looking for