2006 Nov 07 2:45 PM
Good morning,
This is kind of a basis issue and kind of an abap issue so I will post it here because all the abapers out here are on top of their game. Does anyone know of a role change in ERP ECC 6.0 regarding RFC connection? We recently upgraded our production environment to ECC 6.0 from 4.6C and can no longer execute RFCs. We have invoked SU53 after the failure of the RFC and there is nothing listed. We have also set up a system trace in production and no authoization failure is listed. Any help would be greatly appreciated.
Thanks,
Jereme
2006 Nov 07 4:22 PM
Update:
I am trying to execute one of the simple RFCs that SAP packages with the system. The RFC is Partner_Client_Get. This works from DEV to QAS but not DEV to PROD or QAS to PROD. Here is the error that I get when executing to PROD.
Test for function group BDCC
Function module PARTNER_CLIENT_GET
Uppercase/Lowercase
Runtime: 4,719,721 Microseconds
Exception SYSTEM_FAILURE
Message ID: 00 Message number: 719
Message:
No RFC authorization for user E009551 ( BDCC ).
RFC target sys: PRD
Export parameters Value
P_MANDT
Good morning,
This is kind of a basis issue and kind of an abap issue so I will post it here because all the abapers out here are on top of their game. Does anyone know of a role change in ERP ECC 6.0 regarding RFC connection? We recently upgraded our production environment to ECC 6.0 from 4.6C and can no longer execute RFCs. We have invoked SU53 after the failure of the RFC and there is nothing listed. We have also set up a system trace in production and no authoization failure is listed. Any help would be greatly appreciated.
Thanks,
Jereme
2006 Nov 07 2:48 PM
Did you check the connection in sm59? If the connection is o.k. you probably have an system_failure. Check then, if the called FM is remote enabled or if the interface of the remote FM did change. Use the debugger.
Best regards,
Thomas
2006 Nov 07 3:59 PM
Hello Thomas,
Yes the connection does work and we can execute between DEV and QAS. However we cannot go between QAS and PROD or DEV and PROD. The function module remained the same and works in DEV to QAS. I'm quite sure it is a authorization issue but my basis team and security administrator do not know what has changed to cause this. Is there a good way to get an authorization trace in production? I tried setting the RFC trace in both PROD and QAS and nothing useful is returned.
Thanks,
Jereme
2006 Nov 07 4:22 PM
Update:
I am trying to execute one of the simple RFCs that SAP packages with the system. The RFC is Partner_Client_Get. This works from DEV to QAS but not DEV to PROD or QAS to PROD. Here is the error that I get when executing to PROD.
Test for function group BDCC
Function module PARTNER_CLIENT_GET
Uppercase/Lowercase
Runtime: 4,719,721 Microseconds
Exception SYSTEM_FAILURE
Message ID: 00 Message number: 719
Message:
No RFC authorization for user E009551 ( BDCC ).
RFC target sys: PRD
Export parameters Value
P_MANDT
2006 Nov 07 5:03 PM
Make sure the user in target system is authorized to execute your function - object s_rfc: rfc_type = 'FUGR', rfc_name = function GROUP, actvt = 16. You can check it using one of reports that are available in transaction SUIM.
| User | Count |
|---|---|
| 3 | |
| 2 | |
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |