CUA configuration question

[Former Member]

Hi guys,

I am in the process of "refreshing" our sandbox SRM 4.0 environment using R/3 as a backend. In order to allow for a realistic design where a SRM is added to an existing R/3 infrastructure, I decided to remove the previous (incorrectly installed) CUA schema (srm was central here), and to setup CUA again with R/3 backend acting as central system.

Everything is quite clear, I just have some understanding problems with the issue of naming the RFC destinations exactly as the logical systems.

In our environment, those rfc destinations already existed before using a login with SAP_ALL privileges for remote logon. The SAP documentation advises to use newly created users with limited privileges or to add the CUA roles/profiles to the existing users (SAP_BC_USR_CUA_***).

This obviously doesn't make sense if the respective logon already has SAP_ALL.

So to questions arise:

1. What to do for this concrete issue (e.g. not creating any additional users or roles, just stick with superuser as RFC remote logon) ?

2. What's the general preferred design for RFC destinations ? Does one create multiple RFC destinations to the same logical system, using different user depending on the distribution model ?

Thx in advance

Nick

[Former Member]

Hello Bapujee,

You are certainly right. Infact i was rethinking on it after I posted my answer.Probably my way of explanation was not correct. It is definitely not a rule to have logical system name same as that of RFC though it is highly advisable and resolves any confusion. My answer to your second question will further clarify it.

Regarding your second question where you have pointed out that you didnot understand my sentence the answer is simple. A large use of logical system is for data distribution between two SAP and ALE ditribution is an important mechanism in this. So let me explain this with the help of ALE model. Let us assume your host system is abc and also that we you have another SAP system XYZ. You can create any number of of RFC destinations XYZ,XYZ1,XYZ2 etc for system XYZ.

Now suppose the logical system for XYZ is XYZ. Now when we create an ALE model for data distribution between our system ABC and XYZ then we need to use logical systems ABC and XYZ. Lets also assume that the data is flowing from ABC to XYZ.

Now when you try to do generate the partner profile the model view SAP will look by default for RFC destination XYZ. If it finds it then it will generate the partner profiles successfully and also will allow you to distribute the ALE model view. If it doesnot find XYZ it won't allow you to generate the partner profiles and then you need to do it manually through WE20 and WE21 which is very tedious. You can try to do this by creating a dummy logical system in SALE and then a dummy ALE model view in BD64. It will really help you to understand the scenario. First just create a logical system TEST and don't create an RFC destination TEST for it. In second step create RFC destination TEST and then check for the results. In the third scenario create another RFC destination TEST1 which would be a copy of TEST and check again.

Also one more and very important aspect of this is that every client of an SAP system should have a logical system assigned to it naturally. Now lets us take a scenario where system XYZ has client 100 . Let us say we have a logical system XYZ100 assigned to client 100 of XYZ. Now you can again create any number of RFC destinations pointing to client 100 of XYZ but SAP by default will pick only that RFC destnation which is name as XYZ100 . If you don't have any such RFC destination created then you again need to do manual work as described above.

However when no logical system is involved the issue become pretty simple. For example you have an ABAP program which fetches data through RFC calls from other systems.Suppose you are executing the program in ABC to fetch data from XYZ. here you can use any RFC destination XYZ, XYZ1 or XYZ2 since you will be feeding the same information while creating the RFC destinations. Here there is no need for a unique RFC destination.

I hope this resolves your questions. Please let me know if you have any more questions on this topic. You are most welcome.

Ands if you are satisfied with the answers please award points accordinly if possible for you to do so.

Regards.

Ruchit.

[Former Member]

Hi Ruchit,

Thankyou verymuch for the detailed explanation.

Yes,when the system picksup the RFC destination automatically ,it should be same as the Logicalsystem name.This I have faced while creating source systems in BW using automatic generation.since we did'nt followed the standard nomenclature , I was forced to do it manually.

I will try to simulate the scenarios as specified by you in ALE.

Iam sorry as I can not award you points as this question is not posted by me.

Nick Laqua,

Please accept my apologies for diverting this topic from your original question.

Once again Thanks Alot Ruchit!

Regards,

Bapujee Naidu

[Former Member]

Hello Nick,

The answer to your first question is that you can retain the old super users without any issues. However it is important that they are not dialog users but communication or system users.What SAP says is a general advise and while it is always better to go by it in certain cases like these you can use your discretion. SO no need to create new roles/users.

The question to second answer is pretty simple. There is 1 to 1 relationship between a logical system and its corresponding RFC destination in terms of naming them. One logical system will support only one RFC destnation and only that one which has the same name as the logical system itself. So a logical system ABC will only interact with RFC destination ABC and not with something like XYZ. Only a logical system XYZ will identify a RFC destination XYZ. So create only 1 RFC destnation for a given logical system. You can have multiple RFC destinations for the same system but that will hold good only as long as their is no logical system involved. May be you can write a piece of ABAP code involving plain RFC call. This would not need any logical system so you can use any RFC destination corresponding to the target syste. But when you are talking about CUA you are talking about an ALE distribution model which involves a logical system. Here only the 1 to 1 relationship between RFC destination and logical system will hold good.

Please let me know if you need more clarifications on this topic and kindly award points if you found the answer satisfactory.

Regards.

Ruchit

[Former Member]

Hi Ruchit,

I have neither experience with CUA or SRM,but i have a query regrding the RFC destinations in general.

I feel you can have as many RFC destinations as you want(though one is enough) to a logical system and the name of the RFC connection can be anything.

If logical system name is XYZ,the naming convention proposed by SAP is to name the RFC connection also as XYZ,but this is not a rule.

Because we provide targethost,client,userid and password in the RFC connection ,the connection works fine irrespective of the name of the connection.

And also I dont understand the sentence"You can have multiple RFC destinations for the same system but that will hold good only as long as their is no logical system involved."

I like to be corrected with your expertise,if Iam wrong.

Thanks & Regards,

Bapujee Naidu