Transport complete source system?

We are duplicating one of our source systems (PRT). We already have a duplicate of our BI prod system (QBI). Can I transport the complete source system (PRT) from our prod (PBI) system to the duplicate (QBI)?
Note that the duplicates (Qxx) has the same logical system name as the prod systems (Pxx).
-AD

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.

Similar Messages

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

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

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

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.

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.

Do we transport 0LOGSYS (Source System) Info Object?

We are transporting the info objects first time to the quality. when we selected the necessarry objects for the required info objects in transport Organization it also picked 0LOGSYS info object.
My question is do we transport 0LOGSYS info Object?
And also it has created a Task number which is a type of repair (Yello color if you see in the main screen of SE09).
why it has created a repair task?
Can anybody please explain this?
Thanks
Sonu.

[Hello Sonu,|http://chandranonline.blogspot.com]
Yes, you can transport 0LOGSYS InfoObject.
If the current system is not the original system of the object, the object will be assigned to a task of the type repair.
Repair in Change & Transport System
The modifications of SAP standard objects.
Repository objects that are changed in a system other than their original system are entered in repairs. Objects can be transferred from their original system by transports.
For more info see this [Request Types and Task Types|http://help.sap.com/saphelp_nw04/helpdata/en/19/3f5bf8a4b011d285090000e8a57770/content.htm]
[Thanks|http://chandranonline.blogspot.com]
[Chandran|http://chandranonline.blogspot.com]

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

Reg Change of Source system in BI Producton

Dear All,
We had a R/3 source system 900 and data was getting loaded from this client to BI 600 client everyday.
Scenario:-
Nowin R/3 the client system is changed from 900 to 950 and 900 client is no longer available.
Problem:-
What are the steps we need to take care of in BI system since the source system (client) has changed
Kindly give your inputs for the same.
Thanks & Regards,
Khan

Hi Khan,
Please follow the below steps:
The requirement is that Clients 900 connection should no longer exists in BW and replaced by clients 950
Below steps would hold good if the datasources of CLNT950 & CLNT900 are identical.
1) Delete CLNT950 in BW (no Datasources of this system is used in BW)
2) run BDLS in BW change CLNT900 to CLNT950
3) Run RSAP_BIW_DISCONNECT in 950 clients ..
4) Restore connection CLNT950
Please remember to make a transport of source system dependent objects(for the original connection) on BW side, else you lose all the transfer rules and stuff. It has to be reimported later after mapping the old and new source system connections in table RSLOGSYSMAP.
Hope it helps,
Thanks,
Amit Kr.

Data Marts dont change source system id in QA

Hi friiends!
I have generated export datsource for characteritic in Dev.
When I transport this to QA, the datasource keep the Dev source system, this is wrong, In QA the datasource must be associated the QA source system.
How can I solve this?
Thank you in advance!!

Hello ,
Please check what you have collected in the Transport request. Select only Data source and transport without source system name.
Thanks.
Geeta

Duplicating the existing sourcesystem assignments to a new source-system

Hi all
We have another new sourcesystem (logical system) in our BI system.
This is a copy of the productive erp-sytsem, upgraded to EHP4.
Now we want to test the connectivities and data load procedures.
Is there a possibility to "copy" all the existing datasources/transformations of an existing system
to this new system without using transports?
We already tried using report 'RBDLSMAP' but it seems to overwrite the existing assignments.
Any idea??
Thanks
Thomas

Hello Thomas,
You have to use a transport , to transport the source system dependent objects normally the following procedure is used:
RSA1
Transport Connection
Button 'Collection mode' set to 'start manual collection'
Press 'Source system assignment' button (it's the one left of the
'Request BEx' button)
Select the source systems you want to save the transfer rules for
Continue
Button 'Grouping' set to 'Save for system copy'
At the left border click on 'Object Types'
Extend tree 'Source system' LSYS
Double click on 'Select objects'
Select the source systems you want to collect objects for
the source system is now displayed in the right box
Press collecting button ('gather dependent objects')
this may take a while
Right click on the root of the tree and select
Transport all below
Expand the whole tree and check if there isn't an object which is locked
by an other open transport request !!
(the column 'Transport request' has to be empty (BEFORE deleting the corresponding source system
connection!)
Kind Regards,
Des

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

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

Probelms while replicating Data Source and transport into test system

I find the following error messages whilre transporting into test system.
DataSource 0EC_PCA_1 does not exist in source system of version A.
Mapping between data source 0EC_PCA_1 and source system is inconsistent.
DataSource 0EC_PCA_1 does not exist in source system of version A.
Field AFABE will not be delivered from DataSource 0EC_PCA_1 in source system.
any ideas please..........
Enhanced the Extract structure and activated the data source in Source system
Replicate the Data source in BI and install the Infosource through BI Content activated and transport them to Test system.

Hi,
1.First transport the data source from R/3 dev to R/3 quality
2.Replicate the data source in BI Quality ( make sure you that in the data source tab, you are searching the data source below the appropriate source system ---otherwise you data source may not appear)
3.goto rsd1in BI development for activataing the info objects which you have added extra in the info source (z info objects )
activate these info objects and collect in another request
4.transport these info objects from BI dev to BI quality
5.transport entire data source to bw quality.
Thanks,
Tarun Brijwani.
Edited by: Tarun Brijwani on Apr 6, 2009 4:26 PM
Edited by: Tarun Brijwani on Apr 6, 2009 4:26 PM

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!

Transport complete source system?

Similar Messages

Maybe you are looking for