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.

Similar Messages

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

Standards around source system changes

Hello,
This is a general post around good practices to catch source system changes before they impact universes and reports
We have several universes built on source systems and generate user reports
The challenge we face is that there are many changes to these source systems that end up affecting the schema or flow of data. Source teams operate on a best endeavors policy to let us know if any of these impact universes/reports, but many times we discover the impact after the change.
Is there a way to design an automated check or process to proactively check or let us know whenever underlying source systems change from a BO universe stand-point? Are there any tools that can flag such concerns?
I am aware that this is a fairly open question, i am hoping to get advice from seasoned gurus who might have been in similar situations.
Regards

R S,
The only thing I can think of, is not using the same database as your source systems uses.
Instead, use data services to export the data to your own database, specific for reporting. And inside DS you can make it send out emails whenever something did not go as expected (table change, data type change, table renamed).
Your load process from the system database will stop when something like this, but at least it won't effect the reporting side (BO).
This idea on it's own is an entire project and a big one, so I don't know if would be what you are looking for.
Best
Leandro

What should BASIS do for an InfoSource transport for Souce System change?

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

hey Roberto,
I think this setting should be conducted on DEV system other than the target TEST system as you said, am I right. Since we conduct the transport on DEV through the Transport Connection and the settings of the mapping of the source system should be set on DEV, right?
Our BASIS know nothing about BW that we can't depend on them even if this is BASIS work.
Thanks

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

Source system change

Hi,
Just a quick overview of our situation,
After the installation of BI development system (BID: 100) it was connected to the ECC dev system (ECD: 120).
Few months later, functional guys requested to change the source system connection from ECD: 120 to the new client in ECD system (i.e. ECD: 130).
But instead of using BDLS for the conversion, our team has created one more source system in the BID system for ECD: 130 client.
Now we have two entries in RSA1.
ECDCLNT120
ECDCLNT130 ..(new entry created by our team)
Now, we want to correct this situation. So now we have decided to follow the below steps.
1. Delete the client 130 connection from RSA1 and confirm that all references to client 130 have been deleted.
2. Run BDLS in BIW system to convert client 120 to 130
3. Re-establish the connection from BID to client 130 (SM59, WE21, WE20, RSA1 etc)
4. Establish the connection using "Restore" and test it.
5. Replicate and reactivate all transfer structures and data sources.
Regarding the first step, what exactly happens when someone delete the source system using RSA1.
Will this process deletes all info packages, data sources etc. associated with the source system ECD: 130?
Will there be any impact on the infopackages, process chains etc. related to the old source system ECD: 120?
As per some of the SDN threads/past experience, it might be possible that we could lose our custom (Z) infopackages, datasources after the source system deletion.
Could you please confirm this? And also verify above approach and suggest the best way in our case.
Thanks,
Tushar

Hi Tushar,
Regarding the first step, what exactly happens when someone delete the source system using RSA1 ?
It deletes all entries in the table :RSBASIDOC
Following entries are deleted at table level
RSBASIDOC record BI + R/3 Deleted
Technical connection optional
Partner profiles BI + R/3 deleted
Port definitions BI + R/3 deleted
Basis Idoc type BI + R/3 deleted
Dependent objects BI + R/3 deleted
Hope this helps.
Regards,
Mani

New source system : selective source system change

Hello,
Here is the situation, in BW dev we had only one system for all R3 module, DEV. Now they have split DEV in two system for HR and the rest of the modules. We than have HRD and DEV. HRD is a new system which have to be connected in BW Dev. That's not the problem.
The problem is that all my HR extractions have now to take place in HRD, and not anymore in DEV (where the others modules extractions still have to continue).
I would like to change the source system assignement, but only for the HR infosources, and not manually one by one ...
I cannot use BDLS or something like that because it will change all the assignements, and not only HR ones.
Do you have any experience ?
Jarod

I don't think you can "programmatically" change source system assignments for selected infosources/infopackages. I think you will need to set up the extractions from HRD manually. However, there are some things to think about.
How many infosources will be shared between DEV and HRD (ie. extract the same data from both systems)?
Do you need to segregate the master data (ie. append 0sourcesystem to shared master data infoobjects)?
Will there be a separate HRQ and QAS quality system? production?
Hope this helps.

Source system changes in current Portal

Hi Friends!
We have SAP BI 7.0 for several countries. Now, the company is thinking about create a "new instance" (copy of the original) in the same server, separeted by region (because days ago, create a new instance in ECC too)
Then, I think that in the new BI we will work like we have a new source system...
a) What will happend with the queries and wad in portal? do I need publish them again?
b) is enough if I change the sourcesystem in portal? how/where I can do it?
c) is necessary or good idea create a new portal instance for this bi new instance?
Thanks a lot for your expert opinion!

Hi,
You can keep the same portal, no need to create separate portals. You just need to create new systems for each additional BI system you create, then give those systems a different alias (perhaps by region like SAP_BW_US, SAP_BW_UK etc...). Then the reports that you have defined in the portal just need to be changed to point to the new systems you created.
Hope that helps,
Simon

Source System changes from SAP System to BI Warehouse on ECC activation

We are in the process of building a new development environment from an existing development environment.
After copying from system backup in the new development environment we performed BDLS to map to new source systems. At this point of time the source system for ECC ("SAP System from Release 3.0E" was changed to type "SAP Business Information Warehouse".
Why does this happen?
How can we prevent this?
Thanks for your help.

Hello.
Please check the following note if ti can be helpful to fix this issue.
1087980-ECC Source systems appearing in BI folder
Thanks,
Walter Oliveira,

Source system changes impact on BI system

Hi All,
I would like to know is there any work around if source system connected with BI changes. In our environment BWQy 100 is connecte with ECCQ1 100, now bais team needs to copy ECCQ1 100 to ECC2 Q100 and free ECCQ1 for some reason. And asking BW team use ECCQ2 as source system in future.
In this case we need to create new transformations and lot of work involved. Is there any work around to avoid creating transformations for new ECCQ2 system (like SID renaming etc).
Please adivise here how to handle this situation with minimun damage to system, for sure we can't use any more ECCQ1.
All useful threads get awarded...
Best Regards
Edited by: VENKAT78 on Aug 25, 2010 2:36 PM

try this it might help.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/805eefcd-5428-2d10-c0ab-dc27a95b2c81?quicklink=index&overridelayout=true
Ravi

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.

Transport Management: Syntax Pre-Check before Importing

Hello experts,
Today we imported a new transport in the productive system; after import we got syntax errors in the system. The transported report includes a function call; this function module does not yet exist in the productive system; other transport including the function module was not yet imported in the productive system.
Using SE09 we can determine conflicts in different transports, however it is not possible to determine missing objects called from other objects (such as calling of function module).
Is there any possibility to do a syntax pre-check (or type of simulation) of objects in target system before importing the object?
Thank you very much in advance.
Best regards,
Kurt

Hello Vikas,
Thank you for your reply.
Before releasing the transport we do all checks, such as syntax-check, consistency and for inactive objects.
This is not the issue; what I need is a check against the target system (Productive system).
Development system --> Quality system --> Productive system.
Before importing the transport I will check, if there any object called in my report/program, that is not yet existing in the productive system.
Thank you & best regards,
Kurt

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.

Transport managment, source system changed in import

Similar Messages

Maybe you are looking for