Source System Mapping

Hi,
My requirment is to extract data from 12 databases to BW using DB Connect.
The Tables/Views in all DB's are same (technical Name...etc)
I am developing 12 different streams (DSO-->CUBE) so that each DB data will be loaded to corresponding Data Targets and building a Multi cube on all 12 Info Cubes
BW Development:
In Development there is only one TEST DB avaliable
If i build 12 Different Streams...then how i map the transformations from PSA to DSO
Thanks

hi,
In 7.0 you can directly create datasources for the the DB connect tables.
Follow the below simple steps:
1)goto source system -> db connect -> doble click ur source system
2) create application component
3) right click on the application component -> create datasource
4) give name of the datasource -> check if the source system name is correct -> select proper datasource type.
5)Now in extraction tab for adapter see if you have database table and put the right vname for table/view.
http://help.sap.com/saphelp_nw04/helpdata/en/c6/0ffb40af87ee6fe10000000a1550b0/frameset.htm
Extract data from oracle DB to SAP BI 7.0
Ramesh
Edited by: ramesh kumar on Mar 25, 2008 1:11 PM

Similar Messages

Source system mapping between BW systems

Hi All
I have question regarding source system mapping between BW systems
We are in BW7 and we still have BW3.5 objects (Cubes,IO,ODS ets)
We have 1 source in BW Dev that need to split to 2 different sources in BW QA
e.d BW Dev map to ECC Dev 110 and when we transport ,it should map
to 2 sources ,one is ECCQA Clinet 200 and another map to ECCQA Client 210
in the conversion in BW QA we have mapped it to the 2 ECC QA sources but
the problem is that if we would only work with BW7 objects this will work but since we have
also BW3.5 objects the mapping in not complete for the 3.5 objects , we also checked the 7.0 button in the conversion and it still have missing objects

Hi... i dont understand your isse you have one source of transport and in the destination if points to two systems and this works for you....and your problem is in 3.5 objects? its a version problem?
Regards

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.

Source system mapping/conversion between BW systems

Hello BO/BW Forum
I have question regarding source system mapping between BW systems
We are in BW7 and we still have BW3.5 objects (Cubes,IO,ODS ets)
We have 1 source in BW Dev that need to split to 2 different sources in BW QA
e.d BW Dev map to ECC Dev 110 and when we transport ,it should map
to 2 sources ,one is ECCQA Clinet 200 and another map to ECCQA Client 210
in the conversion in BW QA we have mapped it to the 2 ECC QA sources but
the problem is that if we would only work with BW7 objects this will work but since we have
also BW3.5 objects the mapping in not complete , we also checked the 7.0 button in the conversion
any assistance is highly appreciated

Hi,
Hope you aware of Infosources interacts with Replicated Datasources.
As per your post, BW1 is a source system for BW2 and BW3.
So, you have to create Infosources in BW2 and BW3. So you have to replicate the datasources in BW2 and BW3.
Regards,
Suman

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 target system to convert the transfer rules ..'

Problem BW : DTP lost source system mapping and new one created?

I had a little question concerning the BI content activation, when you have to activate objects and there are two source systems, one of them already with a flow working. Do you have to check both source systems in your screen of source system selection, if there are shared objects? I was afraid if I only checked the one I wanted the existing one would dissappear? I donu2019t want to touch the existing one as it was a 3.5 flow which has been migrated to 7.0.
I have also another question, which is a worse scenario of what has happened recentlyu2026!! Imagine you have originally one source system in your BW DEV environment (towards QA) with a certain amount of Datasources connected to it as well as some DTPu2019s. A new source system was added to this BW DEV (towards PROD). Do you think adding this new source system could have an impact in the mapping of the DTP towards the Datasources? In fact, some of our DTP have been modified and they are pointing to the incorrect Datasource/Source system. These DTP were created manually as well as the Transformations as it was a former 3.5 flow. Do you know a way to bring it back to itu2019s previous connection. Maybe a table that points to the correct source system or a function module? RSBKDTP and RSBK* tables do not store this info (only descriptions) and RSRV doesnu2019t do it.
Please let me know if you have had a similar case! Points are waiting and the gratitude of my boss...lol

Any ideas?

Source System Mapping between BW Dev and Prod system

Hi,
I have a DB Connect Source System in BW Dev system called DBSRCDEV which points to one of our Oracle Dev DB.
In Production, the DB Connect Source System is called DBSRCPROD and it points to the corresponding Oracle Prod DB.
In Development, I created a data source on this Source System (DBSRCDEV) and I tried to transport it to Production. But it failed with error saying that DBSRCDEV does not exist.
Where and how can I maintain or configure the mapping between DBSRCDEV and DBSRCPROD Source System so that I can transport my data source to Production?
Please help.
Thanks,
CH

Hi,
usually you need to maintain the setting for the change of the logical system name (source system) in each target system of a transport. So in your prod system goto rsa1->tools->change logical system names...
After maintaining that table, try to import your request again.
regards
Siggi

Source System mapping for BW configuration transport

I create a data model mapped to the testing source system i.e DEV201 but the configuration source system is DEV200.
Now i am about to transport the BW configuration to BW-QAS , I am wondering if I have to assign the data model to the config. source system(DEV200) or i can created a transport request attached to DEV201 ?
Is there any concern on this ?

Hi,
I'm not clear your system landscape. Do system landscape like that:
BWD (BW development) --> DEV201
Now you want transport all objects to BW_QAS with connected to DEV200.
If this is true, you do like this:
- On BW_QAS: create source system (DEV200). Maintain conversion of source system after transport (Original: DEV201; Target source system: DEV200).
- After that transport your modeling from BWD to BW_QAS.
Hope this helps
BR
TRUC

Remote Process Chains Source Systems mapping issues

Hi,
We have a process chain in APO system, which upon success calls another process chain in BW.   We recently implemented SCM5/BI7, and taking the advantage of remote chains functionality to call the BW chain from APO.
However, when we transported the APO process chain from DEV to QA, the source systems in the remote chain are still pointing to DEV systems.   We were expecting to see both APO and BW source systems getting switched from DEV to QA.
We have already verified the logical mappings for Sources Systems are in place under RSA1 | Transport Connect | Conversion.   Also, the source systems seem to map correctly for other objects like data sources etc..   Only issue is with the remote chain.
Is there any other setting which need to be set to make it work.   Any help or guidance will be greatly appreciated.
Thanks in advance,
Ravi Chitluru.

Ravi,
I have a similar situation. Can you explain how to run process chains in APO which can gets data from BW cubes, which in turn gets data from R/3.
In this equation R/3->BW->APO, what are the options like 1)run process chains in BW system to pull data from R/3 into BW and run process chains to load BW data into APO 2)run remote process chains to pull data from R/3 into APO(of course via BW).

Source System Mapping in QC

Hi Experts,
Iam doing Transport from Dev to QC, Everything went well.Small Problem is PC Source system (DataSource is Inactive)for all PC Source system files. Pl Help.Urgent.

Hello Param SiVam,
How r u ?
Check the Technical name for the FLATFILE Source System in the DEV system & QC System. If this is different then u may have to change the Source System Assignment.
As we know the DataSource & InfoSource name is same.
If both are same, then Right click the FlatFile Source System and select Activate.
Best Regards....
Sankar Kumar
+91 98403 47141

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 replication in BI 7.0

Hello All,
I want to replicate my datasource(for function module Generic extraction) in BI 7.0 system
I have replicated datasource in BI 7.....
Now when I want to create transformation....I selected my datasource and Source system(R/3)......but its giving a msg
Source not active
kindly suggest ...
Thanks in advance,
Sonu

Hi,
Check
1. in rsa1>source system>select your source system-->right click ->check
2.Rsa1>Tools->Source system Mapping in Bw
3.In sm59 tcode you can check the source system status.
If you find ther is no connection b/w Source and BW
Just Right click your sourcesystem (as in point1) -->go to Restore.(you can take the help of Basis team for this settings)
Regards
Hari

Conversion of source system names

Hello Experts,
After having some transport problem (transporting infopackages), I notice that the source system mapping is not the same in DEV compared to PRD.
Other than change log which was not turned on, is there any other way I can find out who or when was the last change to this mapping table?
Am I right to say the mapping entries should exist in all systems? My DEV currently only has 1 entry compared to 6 entries in QAS and PRD.
The source system underwhich the infopackage resides is not shown in the DEV source system mapping table.
Is this the cause of my transport problem?
Regards,
Mirella Russo

Dear Experts,
Thanks for the useful information. Points awarded.
Am I right to say that mapping in target system cannot be transported and is set directly in target system QAS, PRD via RSA1 and no mapping is required even if there are other source systems, like flat file source systems, when the source system name is to be the same in all systems? In this case, my source system is a flatfile. Does this mean I need not maintain it? The 'no mapping' warning received in transport log shows that the flatfile source system concerned exists in the target system but no mapping. As I do not need source system name change, can I say I need not maintain in the mapping table? I still cannot understand why the error come about.
Many thank you in advance.
Regards,
Mirella Russo

Copy Transferrules from one source system to another

Hi everybody,
we're uploading data from nearly 25 sourcesystems (including separate systems and systems with more than one client to extract from) via flat-file. The source-system exports data to a shared file directory and the bw-system reads it from there. Though this results in only one transferrule for all source-systems, it keeps generating problems every time upload is due.
Somebody had the idea to switch to 'standard' R/3->BW method of data staging, using generic extractors and so on. But this will result in 25 transferrules which, I'm afraid, have to be set up and maintained seperately. As there's quite some coding in the rules (the transfertructure in fact has 241 fields), flaws are for sure!
We know the trick of exporting a transferrule, changing the source-system-mapping and re-importing the same transport-request. That can be used to copy to one or two other systems, but not for 25.
Does anybody know another way to copy a transferrule from one source system to multiple other source systems?
Looking forward to your answers
Thanks and Regards
Robert

Hi Ralph,
I don't like that methode. Importing the same transport 15 times, each time changing the source-system mapping and making sure, that source-system gets the changes seems to be a huge source of errors, which will be hard to find.
What do you think of the following idea to solve the issue a totally different way:
All transfer-rules directly connected to the source-systems are stripped of all Coding, so there is a plain 1 by 1 transformation including 0logsys.
The InfoSources attached all lead to one ODS-Object, which has the only purpose to collect the data from the source-system without any transformation. So some fields a filled by a system and other fields maybe not.
The coding specific for source-systems is moved to transfer- / update-rules from that ODS-Object to the original ODS-Objects / Cubes and the "collecting" ODS-Object is emptied after every loading process.
This will result in a single point of change. It will be quite a huge program (maybe in startroutine) but it's the one and only point, where changes and corrections have to be made.
Regards
Robert

Source System Dependent BI Objects

When working with Source System Dependent Objects like
1) DataSources (based on source system ABC)
2) InfoPackage (based on source system ABC)
3) DTP (source is datasource that is based on source system ABC)
Question 1)
Once we create the obove objects in DEV system.
If we update the IMG activty in QA (Source system conversion after transport).
and transport the above objects to QA system.
All the above objects should be available with new source system in QA? Is this the right way to do it?
Question 2)
Once we create the obove objects in DEV system.
If we DO NOT update the IMG activty in QA (Source system conversion after transport).
and transport the above objects to QA system.
Some of the above objects are not available with the new source system?
Workaround: Go to RSA1 (Top Menu -> tools --> they are couple of options where we can enter 1) source and target source system info AND 2) do a check, activate and replicate source systems.
After this some more objects are visible but not all? Is there any other way i can complete the conversion?
Question 3) I tried the below in an other landscape
Once we create the obove objects in DEV system.
we DID NOT update the IMG activty in QA (Source system conversion after transport).
and transported the above objects to QA system.
FYI: All objects with source system in QA are available. I am wondering how the source system conversion took place?
Question 4) When we enter source system for DEV and QA in QA system, Do we need to enter even PC file source systems?
Example:
1) ABC in DEV = BCD in QA
2) PC_FILE in DEV = PC_FILE in QA
Thanks for your help.

Below are the following ways to do the mapping in Target System for Sourse System Conversion:
1) rsa1->tools->source system mapping OR
2)rsa1->transport connection->'conversion of log.system'(yellow box with 'x' and 'conversion' icon) OR
3) spro->bus info warehouse->transport settings->change source system name after transport (transaction rslgmp) OR
4)maintain table RSLOGSYSMAP (sm30)
Que1.
Yup
Que2.
if no maintenance done, system will transport as the same source system name. You have to convert everything manually...cumbersome process.
Que4.
Normaly for flat file we use the same name, to avoid any warnings, we just maintain the 'conversion' with the same name

Source System Mapping

Similar Messages

Maybe you are looking for