SNC & CUA

[Former Member]

We are having CUA set-up with 4.7 (Unicode) as master and CRM as child system. We have also enabled SNC on 4.7 (Unicode) system where as CRM system is non-Unicode and SNC not enabled. When i try to create user and assign profiles in Master, user gets created in child system but profiles are not assigned. In fact, IDOC posting gives error in child system.

I want to know whether SNC is required on both systems? Error message says 'target system requires SNC'.

Any ideas?

Thanks,

[christian_wippermann]

Hi, I am a little puzzled that the creation of the user succeeds but the profile assignment fails. However, the logon requirements are defined in two places: the RFC destination that you use in the source system and the logon requirements of the target system (defined by the profile parameters snc/accept_insecure_*). Your target seems to allow non-SNC logon. How about the destinations in the source system?

Cheers,

Christian

[Former Member]

Target system is Non-SNC so user gets created correctly. However, at a time of assigning profiles, call is made from Child to Master. Since, RFC destinations (defined in child system) are defined as Non-SNc, it gives error while making call and thus profiles does not get created.

So, one option is that both system should be SNC enabled.

Second option is that Child system (which is Non-SNC) should have RFC destination (for Master) as SNC Active.

Are these assumptions true?

Thanks,

[christian_wippermann]

Hi,

Your CUA requires SNC for incoming RFC connections. This actually leaves you with two options: configure the RFC destination in your satelite system to support SNC (as you already wrote), or allow username / password based user authentication for the RFC connection into your CUA.

The profile parameter to set in your CUA system is: snc/accept_insecure_rfc. I would recommend setting it to "U" and adjusting the user master of the communication user appropriately. The documentation on this can be found <a href="http://help.sap.com/saphelp_erp2005/helpdata/en/d9/9cfb741a644ea7b0d296209fee892f/frameset.htm">here</a>.

Cheers,

Christian

Message was edited by: Christian Wippermann

[Former Member]

I'll try out with profile parameters and see how it works.

Thanks for your replies,

Sanjay shah

[WolfgangJanzen]

Please perform a connection test (using transaction SM59) for the RFC destination used by the Central User Admininistration (actually: the ALE subsystem which transmits the IDOCs created by the CUA).

Yes, both communication partners need to be equipped with SNC (actually: the same SNC product). If the RFC client requests an SNC connection and the RFC server is not able to offer the requested service, then the RFC connection fails.

In your case, the RFC client seems not to use SNC but the RFC server demands the usage of SNC (=> profile parameter snc/accept_insecure_rfc). Maybe, <a href="http://service.sap.com/~form/handler?_APP=01100107900000000342&_EVENT=REDIR&_NNUM=713495">SAP Note 713495</a> can be helpful for you.

Regards, Wolfgang