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

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

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

Hi,
I have my BW dev cltn connect to source system 630 ..now the client 630 has been dropped and it has to be connected to 650...what sholud be my steps...i ahve seen BDLS transaction but can any 1 who has done it b4 guide me.
Thanks
Prashant

hi prashant,
check this out.
Note 886102 - System Landscape Copy for SAP BW 2.X, 3.X and NW2004s BI
Fresh source system clients in production BW system
Note 195610 - Logical system name conversion in T000
Note 121163 - BDLS: Converting logical system names
hope it helps,
regards,
Parth.

Source system changed to BI instead of R/3 after system copy

Hi All,
We have done system copy of R/3 and BW from production to test.
After doing the post process the R/3 test source system in BI become as business ware house system and showing under the tree of BI.
Due to that all data sources are not active. Could any one help me in this case.
Thanks & Regards
Srini

Dear Srinivas,
You have to restore the Source system connection in BI. There are few steps you have to do before that.
you have to make both R/3 and BI system as modifiable and do the procedures as mentioned in the SAP Notes 1087980.
Once these both steps were done, please right click on your source system connection in BI.
please validate all the passwords there and it will navigate to R/3 SM59 RFC connection. There you have to check all the credentials whether it is correct or not. once it done. plz save it and get back to BI source system connection.
Replicate the meta data and activate the data sources and transfer structures.
After all these steps, right click once again on your source system connection and click Check.
Here source system connection will be OK.
Hope this would give you clear pic on your issue.
Edited by: Mohan Kumar on Jun 25, 2009 10:52 AM

Change of the source system

Hi
all
Background installation from SAP r/3 was already done and the system is up and running.
Now i would like to replace the SAP R/3 with ECC version , where I must replicate the same extractor now with obviously a different version of ECC.
I wonder if the source system change will effect the similar infoobjects which were already installed and assigned to a different source system.
Please explain me the effect and defects, or if any changes on the master data already existing.
thanks

When you change the source system - all your transfer rules , data sources etc will be gone and you will have to do them again.
The master data and transacton data will not be affected only that you will have to init the same again and deltas subsequently...
You could instead - keep the old system connection alive and then create a new set of transfer rules , data sources etc for the new system - that way you can have the old Transfer rules , data sources active and then have the coding done the for same alive for reference as well..

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.

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

DS-BW:Data load called from BW failed after Source System program_id change

Hi,
In my BW 7.0 instance I have Data Services 3.2 as source system.
Some time ago I have changed instance of Data Services I am connecting to - I just changed PROGRAM_ID in RFC connection parameters for that source system.
Since that time when I am trying to execute infopackage to call a job I am getting following error:
OCI call <OCISessionBegin> for connection <xxxxxxx> failed: <ORA-01017: inv
where <xxxxxx> is Oracle database connection name for Data Services instance I connected originally.
What can be reason for that?
Regards,
ak

In Data Services Server Manager on DS box there were configurations for job server I connected originally and for the other job server. After removing original config it works fine.
ak

Changing the source system in QA

Hello All,
I just wanted a quick opinion from your experience on the following issue:
We have a ECC Dev client 20 connected to BI Dev client 20
Similarly we have ECC QA 120 connected to BI QA 120
But due to some reason we now want to connect a new ECC QA client 150 to BI QA 120 and take out ECC QA 120 totally(120 is wiped off).
I already have a lot of development transported to BI QA where the source system is ECC 120. Now if 120 dies and we pull the data from 150, what are the pitfalls to watch for?
Like all my Master data objects , DSO and Cubes still point to ECC QA client 120 but now the "actual" source system is going to be ECC QA 150.
Points,
Gaurav

You need to replicate all the data sources in BI from QA 150 and change the source system assignment to 150 instead of 120.
Also, you need to reinitilase delta for delta enabled extractors.
Two things to watch out:
1. If you dont have source system identifier, then if you happen to get records with same key, then it will overwrite. This applies to both master and transaction data.
2. For transaction data that is not delta enables, there may be a possibiltiy with which the records will get duplicated. So, better to delete the old requests before reload the data from QA150.
Ravi Thothadri

Source system change

Similar Messages

Maybe you are looking for