on 07-31-2014 9:29 AM
Hi Victor
Check & follow this note under section Solution 1.C, this should resolve this.
2000585 - CUA: Assigning minimal authorizations for communications users (version 2)
regards
Swami
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hi,
you are having authorization error, this is nothing to do with patch
you not required to edit the read rfc authorisation manually, it all done automatically.
For your case, i could suggest to delete the RFC destinations via managed system configuration the same screen you pasted above in first and recreate again.
this should work
Thanks
Jansi
Hi Victor,
What is the status ?
Did you try with what Jansi has suggested ?
That should work..!!
However, if not working then share ST22 dump.
Also have a look at 1627901 - Trusted RFC troubleshooting
Divyansnhu
Can you see this RFC existing in system ?
Then try this.
1. Call transaction SDCCN.
2. Choose Goto -> Settings -> Task-specific.
A hierarchy of task-specific settings is displayed.
3. Choose Task-specific settings -> Session Data Collection -> RFC Destinations -> Settings.
4. Click the Settings icon.
A dialog box is displayed.
5. Choose the Destinations tab.
6. Choose Display <-> Change.
- a) Choose Add RFC destination and specify your 'BACK' destination
Also, I would say to use a admin user like a copy of DDIC for the purpose as Jansi wrote before.
Divyanshu
Hi
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.