Change Source Client RFC in BW

Hi Basis Gurus!
We recently did a system copy of our BW Dev environment from production. The basis team has set up the RFC connection to point to the ECC Configuration client (200). We obviously need to be mapped to the data client (220). Basis team is informing us that the connection cannot be changed. I do not have a basis background so I'm having trouble understanding why this would be. Can anyone shed any light on this or give instruction on how we can change this source client mapping to be correct?
Thanx,
Cindy Palle

Just want to say thank you. I could fix a problem with your information.
I was searching to change the background user from ALEREMOTE to BWREMOTE as all our process chains were running on ALEREMOTE.

Similar Messages

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

Change of Source client in transport request

Hi Gurus,
I want to change source client of transport request
Since I want to transport request between clients of same server.
I did it using scc1
But when I want to make any changes to form which was included in that request it is saying
Request/task DEVK***** has invalid source client XXX
I am trying this in YYY client
Please provide solution
Thanks in advance for your efforts

Yogesh,
Does both the clients allow development in the server? Generally it should not be the case.
Does the client still exists in the server?
Here is a thread with replies for such an error message.
Re: regarding Client change for transport request
Check it,it may give you some lead.
K.Kiran.

Change Source System client for BI datasources

Friends,
We have created/migrated datasources in QA system using existing SAP Source System, for example, ECC Client 320. Now we want to change the SAP Source System to the different client, for example, ECC Client 330.
All datasources are already created when connected to old Source System (ECC Client 320). The new requirement is to extract the data from new client, from ECC Client 330. We like to change this seamlessly without impacting the data loads, full as well as delta.
Any ideas as to how to accomplish this please?
Regards,
Upender Kadire

Hi,
The client mentioned while creating source system in BW is to be changed.
Go to the RFC Destination created for R/3 system in BW and change the client.
Now regarding the delta, the delta has to work fine, as BW system is Client independent. It looks for the Source and bring data.The delta queue is maintained in R/3.if you change the client, the delta will be picked from the new client.
Happy Tony
Happy Tony

Services in JCo RFC not getting started after Changing the client from 001

Hi SAP Stars,
I have recently Installed Quality and Production servers with PI 7.1 on windows 2003, Sqlserver 2005, when I'm doing Post Activities(http://host:port/nwa) in which I try to change the client from 001 to 300(newly created) in JCo RFC(4 services) and start the service it is throwing error when I again change it to 001 client and start the service it is getting started, Could anyone help me in solving this issue same issue I facing in PI 7.1 Quality and Production
Thanks In Advance
Anil Kumar

Hi Anil,
All these JCo RFCs are client specific RFCs.
Please logon your PI NWA
Choose Configuration Management - Infrastructure- JCo RFC Provider
Then, Select the RFC
Under Details -> Choose Repository Configuraton
Change the client name to 300 (your new client)
Save
And repeat the same for all JCo RFC that you want to work for your newly created client.
Please ensure that you are using SAPJSF user & correct password for all these RFCs.
Ideally, these rfcs shuould work now if now please restart your PI (mostly Java alone also do)
I hope this helps you.
Regards
Sekhar
Edited by: sekhar on Dec 17, 2009 11:39 AM

Best Way to Change Source System Client

We initially had a ECC source client for BI as 35. But over time, we suffered with good test data because the ECC team use client 15 and not 35. We want to change BI 7 to use client 15. I have created a new source system in RSA1 for Client 15 but when I try to delete client 35 and /or change the source client on a datasource, all the data mappings are deleted!
I would really appreciate any advice or information on the best way to change the source R3 client for Bi without losing data mappings. Point awarded and much respect
Warm regards
Lee Lewis

Hi,
Yes. There is a way to change the source system without deleting the old system. Please use the T.code BDLS and for more information refer the below link
Re: Changing a Source System.
OSS note 886102 will also give more information about this.
Hope it helps.
Thanks.

Changing the source client of a transport request

Hi!
I transported few requests from client 300 to client 200 using transaction scc1.
Now, i want to transport them to another client from 200. But when i try to release those requests the systems prompts "Request <#> (300) belongs to a different client".
I tried changing the source by double clicking the request, but I'm unable to do so.
Can u please suggest any way of changing the source client of these requests ?
Thanks!!
Regards,
Muzammil.

Hi,
Goto SE01,
The type transport number
Display
Place cursor on the TR
Click Utilities=>Reorganize=>Change Project.
Best regards,
Prashant

Source system RFC fails after transport

Hi all
in our QA system any transport containing a process chain causes the RFC connection to the source ECC6 system to fail after too many logon attempts.
This doesn't happen when we send the same transport to production.
Any ideas?
Regards
Hayley

Hi
thanks, but I had already checked out this note. This refers to the post processing of the transport on BW of client 000 logging onto the BW client to carry out changes, not the RFC connection to the BW ECC source system.
The transport goes through ok, and the process chain can be activated, however at this point we always notice that the ECC source system connection fails with an RFC error, as soon as we get the password reset and changed in SM59 it works ok.

How to change the Client n user details for a model in Production

Hello Friends,
I have an application which is calling RFC function module from SAP R/3.
In development system while creating Model I have entered the Back end details like Client, User Name and Password.
If I transport the application into Production, The Client and user name will be different. In this case How would I change the client n user name details.
Do I have import again in Production. But does sounds a good idea.
ThanQ for Ur time.
Cheers.. Sam

When you create Model first time, to import Interface of RFC you would need to logon into R/3. But once you are done with the Interface, your connection to R/3 will be determined by the client and UID details in JCo connection.
Now when you transport your code from DEV to QA system, the JCo connection with the same name should be there. or else, you would need to create the same in the new server. I dont see a need to reimport the model. If that is the case, then developers would have to spend huge amount of time doing this job alone.
Hope this solves ur problem.
Regards
Murali.

Change Source system Tech.Name

Production : PRE -
> PRB
PRE-Production : PPE -
> PRE
We make a copy of our production BI to Preproduction BI (PPB) we follow note # 886102. We want to connect this system to our pre production ERP (PPE).We already run BDLS change the logical system name we created new RFC created which is pointed to new R3 system .Problem is when we are going to run Tcode RSA1 in source system it shows old Tech name PRE600. We are unable to activate the source system.
We can create new source system (PPE),but All our BI objects mapped with old source System (PRE600). I am afraid to change thousands of BI objects ( change source system from PRE600 to PPE600).
Is there any work around we can change the Logical Source system Tech.Name? or some batch job which change the source system name for all BI objects.
Appreciate your earliest reply.
Nawab

Hi
Can you please check the Tcode BDLS
Check the document it will be helpful
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/bff13df2-0c01-0010-6ba7-bc50346a6fd8
Regards

Client Copy - Which source client 000 or 001?

I have a new SAP Netweaver 2004s SR1 ABAP+JAVA system with the following usage types:
SRM App
SRMLac
AS Java
AS ABAP
DI
MI
All the post-installation steps have been completed (including the CTC template configurations for DI and MI). The Java, DI, and MI have been configured against client 001. Now I want to create a new production client. The J2EE_ADMIN and users associated with DI and MI exist in client 001.
I want to create a new production client 010. Should I copy the users (SAP_USER) from client 001 and the customizing data (SAP_CUST) from client 000? Or, can I copy everything from client 001? There is a lot of conflicting information in the SAP Notes in regard to which source client to use.

You should not use a transport of copies for table USR02. Use client copy profile SAP_USER or SAP_UONL (without authorization profiles and roles).
And you should never copy customizing from client 001 to build up a new client. 001 happens to be a ordinary customer client which does not get supplied with changes SAP delivers after the release date. New SAP Netweaver 2004s installations use client 001 to file the user masters needed for the JAVA part. But this does not change the fact that client 001 is a customer client and should not be used as a template.
For local client copies you could use copy profile SAP_UCUS with source client 000 and source client user master 001 in one step. This has the same result as a client copy with SAP_CUST from 000 and SAP_UONL from 001 (i.e. thet authorization profiles and roles come from 000, when you need them from 001 you can either copy the missing individually or use SAP_ PROF in a separate step).

Change the Client that J2EE connects to !

Hello Folks,
Our J2EE engine seems to be connected to Client 001(j2ee_admin user is actively occupying the sessions). But our active client is different.
How do we change the client that a j2ee engine connects to? We are in CRM5.0
Thanks

Hi Senthil,
If you want to just change the client then you have to go to the XCM of your application and follow the following link.
Components -> customer -> jco. here you will see the details of the client which you can change.
But if you want to keep the existing client and create another scenario which will connect to the diffrent client then you have to create a new jco, new Application configuration, new RFC connection. In CRM system you have to check the transaction SRMO.
<b>Allot points if my post helps!!</b>
Best regards,
Vikash.

"Master data attr. of" un change source of update rule.

hi,
What is the importance of following in "change source" (characteristics) in update rules.
1. master data attr. of
2.initial value
3. Source chars
4. constant
When and why these are used.
Thanks in advance.
Regards,
Avneet

Hi Avneet,
Lets say Material group is an attribute of 0MATERIAL. You cube contains Material and also Material Group as a separate characteristic (not as navigational attr) becasue you want to store the value of material group as it was during the time the transaction happened.
But here you transactional data coming from the source brings Material values, not values of Material Group. So in the update rule for Material Group, you can specify "Master data attribute of" 0MATERIAL. What the system will do is take the value of 0MATERIAL on this record and populate Material Group taking the value that is present in Material Master data.
So if Material = M100 and Material Group is MG01 in master data, it will supply MG01 to Material Group char in the cube.
Hope this helps...

Issue in OWB mapping - when changing source and target database

Hi,
I need help for resolution of the issue I am facing when moving mapping from development environment to QA.
Here is situation,
We develop ETL using one source, one staging and one target database.
In development we use one control_center for Source to staging and another control center staging to target.
All works fine in development.
Now I have created new runtime repository and imported all OWB projects (with full dependencies, exact replica of development). Now I need to change source and staging and target as different database.
I have created new database location connections and defined/attached DB connectors with stage and target location.
Now issues are
1.     Two Staging mapping are not able to bound with source table (giving different error
a.     One mapping show error for source synonym translation no longer valid when deploying this mapping , but validation comes without any issue)
b.     Other mapping show error for source table/object not bound to repository
2.     All the target mapping show validation successful, but when deploying says “table or view does not exist”. But tables are exists on source stage and target. (also permission are set correctly for target user to read from staging tables).
Not sure how to proceed from here.
I have recreated new repository and re-imported all project/mappings and defined all connection but still same issue.
Thanks in advance,
Vipin

1. Two Staging mapping are not able to bound with source table (giving different error
a. One mapping show error for source synonym translation no longer valid when deploying this mapping , but validation comes without any issue)
b. Other mapping show error for source table/object not bound to repository
The above error were resolved when re-synchronized the table (for few I have to reimport the table) and mapping.
2. All the target mapping show validation successful, but when deploying says “table or view does not exist”. But tables are exists on source stage and target. (also permission are set correctly for target user to read from staging tables).
The above error still pending. My target mapping are not able to deployed/compiled.
For the above I have defined one Staging location to one target target location and target location have connector to staging (not sure if I have to define connector name same as staging location, as I have created DB connector with different name but reference database is same as staging location).
Mapping are assoicated with desired data locatoin and meta data.
control center is also have that data location.
Mapping are configured for the desired location.

Does not allow to change source system in Variant

Hi Gurus,
I am creating a variant for the program RSIMPCUST, but it does not allow me to change source system name. It is showing me gray color. Do you how to fix this issue ?.
Thanks
Liza

Hello Liza,
Did you try my solution?
[Re: Change source system name in variant in BWQ]
There are solutions to change variants properties, but that particular program has the logsys parameter not able to change, so you cannot change the value of that variant (only with debug).
It's best to go for that solution I already provided to you...
Diogo.

Change Source Client RFC in BW

Similar Messages

Maybe you are looking for