Development - Quality : Source system configuration

Dear All,
We have 3 System landscape to our Customer : Dev -> Qual -> Prod
Our Source systems are Oracle database, so we are using DB Connect in the project.
Oracle database dev - BI Development system ( pointing )
When we transport the objects ( info objects, infosource, infocube, update rules etc., ) i am getting a error source system does not exist.
The reason is for BI Quality system it is getting transport with Oracle database dev as a Source system and the same source system is not available in BI Quality system.
Oracle database Quality -
BI Quality system ( pointing )
So manually i am doing changes to the transfer rules---assigning data source etc and activating the things.
Please let me know where we can do the configurations for this...
Regards,
Vara Prasad

Hi Stefan/Seb,
Already i am maintaining the entries in conversion of log. System name like this..
LOGSYSORG LOGSYSNEW
BW100      BSDCLNT100      BWLOGICALSYSTEM
MBPCU1T    MBPCU1PP        Billing PreProd server1
WPSDB      WPSDB_PREP      Portal Pre Production System
MBPCU1T is My Oracle database dev and MBPCU1PP is oracle database quality system.
Still i have the issue, when i transport the request to quality it is showing the MBPCU1T in the transfer rules, So manually i am changing the source system and assining the data source to that.
Please let me know if i need to do any more configurations.
Regards,
vara Prasad

Similar Messages

Transfer rules are not exist for ECC Quality source system in BI Dev

Hi,
I Connected BI Dev system To ECC Dev and installed the sales, purchasing,... data flow, but here i am not getting the quality data to show the reports, to get Quality data I established the connection between BI Dev and ECC QA, while installing the transfer rules for the ECC QA data sources there no transfer rules are exist(only some of them exist) in the business content, but all the update rules,... are exist, when i right on the data source say create transfer rules it is proposing App praposal.
When i select source system as ECC dev while installing the transfer rules i can see all the transfer rules, but when i select source system as ECC QA i can see only some transfer rules.
only problem with transfer rules(some of them exist), for remaining all objects are properly existing in business content for ECC QA source system.
Regards,
chandra

Hi Fayzrakhmanov
Thanks for the quick reply. We are not moving the stuff to QA. We are only connecting QA ECC system to BI Dev. We already have datasources moved to ECC QA and created source system for ECC QA in BI Dev.
The problem is I am not able to get Business Content transful rule for new source system. We I can find some but not all unlike development.
Help on this would be appreciated.
Thanks

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

Change of source system

Hi all,
At present we have in our data source the quality source system of (R/3) mapped to the data source in the development of BI. Now i want to change the source system for the data sources in BI to R/3 Qualtiy.
This mapping is not done for all the application - it is done only for some of the applications like FI etc, and all other applications like the PP,QM etc have the respective R/3 clients mapped to the Data sources.
Can you kindly tell me the steps that has to be adopted to do this activity.
Regards,
M.M

- In R/3 QA , SE37, run function module RSAP_BIW_DISCONNECT to disconnect you R3 QA connection with BI Dev. ( you can find Log sys names of this connection in RSBASIDOC table in R/3 QA)
- BDLS has to be run in BI for changing R/3 QA to R/3 dev. Also ensure the changes have been done to SM59 destinations like ip/host, login/password, RFC dest descriptions etc. in both BI dev and R/3 dev.
- Then RESTORE R/3 dev Source System in BI dev - RSA1 (While performing RESTORE , R3 dev client needs to be opened. After Restore you can close that)
- Then you will have Replicate all datasources from Context menu of Source sys R/3 dev in RSA1.
- Then Run program (SE38) - "RS_TRANSTRU_ACTIVATE_ALL" in BI Dev to activate all transfer structures for R/3 dev source sys
Hope abovementioned steps help you.
Rgds,
Vikram.

Source system in RSA1 is diiferent to the datasource in infoprovider

Dear Guru's
I have created a quality source system in RSA1 tcode for client 210 but in my infoprovider it shows me of diiferent datasource ie for client 200 and i need this client to be 210 so kindly help me to resolve this issue
Regards
Mohammed

HI,
Do you want to change all the assignments from client 200 to 210. Or is it for this particular Infoprovider (you have mentioned) and the relevant transformations.
Does
1) both clients exists as your source systems or
2) client 200 is to be replaced by client 210.
In the second scenario, you can refer this article. Contact your BASIS team for guidance.
http://www.sdn.sap.com/irj/scn/index?rid=/library/uuid/805eefcd-5428-2d10-c0ab-dc27a95b2c81
For scenario 1, if you want to load data from 210 client to this particular Infoprovider , replicate the datasource for client 210 in BI side and create new transformation, Infopackage and DTP from the datasource to the target.
Hope this helps.
Regards,
hari.

Change Source System RFC

Dear All,
we have 2 server ecc 6.
1. production
2. backup
right now my sap bw connect to ecc production.
we have plan to use backup instead of production
is it enough just simply changing the IP and host name at the current RFC connection.
from IP production to IP backup server ?
without creating new RFC connection ?
is there any procedure that we have to do before or after the changes ?
please advice

Hello Dady,
You have to take care of RFCs, Logical system names and RSA1 stuff in order to use backup ECC server instead of Production.
I suggest you to go through the following document for better understanding. It's strongly recommended to take offline backup before you attempt to modify source system configuration in BW system.
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/70a7b233-8be5-2c10-4190-aed723af5373?QuickLink=index&overridelayout=true
Good Luck.
Thanks,
Siva Kumar

Source system in Development & Quality & Production

Dear Experts,
Normally we do developments in Development server,so we create source system connection to R3 Development server (say 120) and create DataSources, DTP and process chains based on the Source system 120.
Now my Doubt is when we transport the developments to QAS, how will i get the data from R3 Quality Server 500 (because my developments -DataSources, DTP,Infopackages and process chains are connected to R3 dev 120).
how should i do this?
Please give me your valuable inputs.
Regards
BI Learner

Hi Friend,
In general this connections done by Basis people.
So in your case automatically mapped quality r/3 to bw quality, but first replicate changes from r/3 quality to bw quality before moving changes from bw dev to bw quality.
this scenerio is normal wherever you go either in production perspective also.
SAP BW(Dev)---->SAP BW(Quality) and simaltaneously mapped SAP R/3(120)--->SAP BW(Dev),SAP R/3(500)---->SAP BW(Quality)
llly mapped production also, this is general landscape.
I try to give scenerio and hope it should helps out.
Thanks-RK

Can we have two R/3 Source Systems(Dev & Test) in BW Development....?

Hi All,
Till now we have only BW Development box..
Our Landscape for R/3 side is R/3 Development, Testing and Production.....
Already we have connected R/3 Development with BW Development... It is working fine as now... We have finished our task at Development...
My doubt is Can we Configure R/3 Testing to BW Development....eventhough R/3 Development is already configured with BW Dev....
Can we have two R/3 Source Systems(Dev & Test) in BW Development....?
Please help me out in this issue....
Your help will be appriciated...
Regards,
Kiran Telkar

Hi Kiran,
You can create second source system which will point to SAP R/3 Quality .
If you have transported all datasource activation requests to QA environment then all datasources are available in R3QA as well.
After creating source system , replicate datasources.
Only thing you need to do is to replicate efforts of assigning source system (R3QA)-> creating transfer rule -> Create info package and load data.
Hope that helps.
Regards
Mr Kapadia
Assigning points is the way to say thanks in SDN.

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

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

Source System inactive in Quality

Hi Experts,
I need to load the data from flat file to ods but my source system is inactive in Quality server when i double click on source system it is not showing any active button in quality server, but the same source system is active in development server.
Please can any one solve my problem.
Many Thanks in advance
David

Hi Srinivas,
Thanks for your answer, and one of my source system is still inactive for this i follow the below steps,
1) Run the program in se 38 RS_TRANSTRU_ACTIVATE_ALL
2) RSA1- source system_ right click on source system - activate..
but still my source system is inactive so how can i solve my problem... please give me solution.
Daivd

Configuring of a new source system in BW

Hi Experts
We have to set up a BW system, which will have 2 source systems( ECC) clients 550 and 590 of the same ECC ( ECC QUALITY). One client is already there and we have to configure another client of source system with the sane BW Client 350. I understand that the dataflow is partly different (e.g transfer rules and datasources are source system dependent). My question are
1.     How we can configure a Source System on BW.
2.     What changes if any I have to make in the existing system (BW)
3.     What will happens to the Existing Data-sources ( Do I have to replicate each and every data-source of the existing ECC clients to New ECC client.)
4.     Do I have to create New transfer and update rule for the new client
Any other point Pl. advice.
Thanks in advance.
Dinesh Sharma

You can more than one source system to onw BW client.
You have to use source system compounding to differentiate between characterstics values if you are loading to the same object. Otherwise you need to use separate characterstics for ex : Yxxxx object for one source system and Zxxxx object for another.
Also the dataload timing should be setup properly. Otherwise it may leads to object locks.

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

BI Production as a source system on BI Development

We have a requirement to make the Production BI environment as a source system on the Development BI environment. This is required with a view to make greater live data available in a particular cube on the Development box to aid in future enhancements
The same Production BI environment is again reaquired as a source system on the Quality BI environment. This is required with a view to make greater live data available in a particular cube on the Quality box to help in testing/UAT activity
My question is that corresponding to the source system BI PROD on BI DEV and source system BI PROD on BI QA. What can I keep as a source on BI PROD itself. Can/should BI PROD itself be the corresponding source system on BI PROD ? Is it technically feasible. What are the pros and cos/risks of such a design design

Hello,
You can add the BW production system as a source system in the DEV and QA system without any problem. I don't believe there is any need to attache the production system as a source to itself, this connection alrady exists (the so called myself connection), if you goto RSA1 and under source system you will find a source system connection for production that points to it self, this is used for all internal datamart loads that might occur in the production system itself. Therefore there is no need to add the system again with a connection to itself.
Best Regards,
Des

Transport ALE Configuration from Development to Production System

Hello All,
We have created ALE-IDOC scenario in the development system and its working fine. Now we want to transport it to the Production / Quality system. How can we transport the settings like logical systems, port definition, partner profiles, distribution model , RFC destinations from one system to another system??
Because the client numbers are different for development , quality and production systems.. Do we need to transport the logical system and client assignment using STMS or create directly in the target system??
Thanx in advance...

The issue with transporting the ALE distribution model is that the source and target logical system names change between the dev, test and prod environments.
Assume an ECC6 and PI landscape with dev/test/prod called E6D/E6T/E6P and PID/PIT/PIP with all systems using client 100. By default (SAP recommendation) the logical system name for E6D client 100 is E6DCLNT100 and its PI partner in the dev landscape will be PID client 100 with logical system name PIDCLNT100. In test the logical system names will be E6TCLNT100 and PITCLNT100 and in prod E6PCLNT100/PIPCLNT100.
So, when a distribution model is set up in dev with a source system of E6DCLNT100 sending messages to a target system PIDCLNT100 everything works nicely. This assumes that the PIDCLNT100 logical system partner in WE20/WE21 is mapped to a port which maps to an RFC destination pointing to client 100 of PID.
When this model is transported to the test system it won't work because the logical system names are wrong.
It is possible to create a logical system name called PISERVER in SALE and then map that, via WE20/WE21 to point to the corresponding PI instance. Thus in E6D, WE21 would map logical system PISERVER to the RFC destination for PIDCLNT100 but in E6T the mapping would link to RFC destination PITCLNT100 and in E6P to PIPCLNT100. In this way any ABAP programming trying to use the ALE distribution model would send messages to PISERVER and would be transportable.
However, setting up the source system in the same way appears to be impossible. When attempting to generate partner profiles, transaction BD82 stubbornly insists that the source system for which it will build profiles MUST be the logical system name defined for the execution client in SCC4. Theoretically, mapping similar to that for PISERVER could be performed for ECC6SERVER and the ALE distribution model could be built to send messages from ECC6SERVER to PISERVER but BD82 won't honour this source system.
This appears to make it impossible to transport an ALE Distribution Model. Can anybody provide a process to overcome this apparent architectural limitation?

Development - Quality : Source system configuration

Similar Messages

Maybe you are looking for