RFC Destination Fails

[Former Member]

Hi,

We have created a RFC Destination of Type H to SRM System. We have used PIAPPLUSER of the target system in the logon properties. When we test for this RFC Destination we get the Status message as 500 Internal Server Error. In the Response Body tab we get the error as below

"Error when processing your request

The URL -target system URL- was not called due to an error.

Note

The following error text was processed in the system TargetSys : Log on with a dialog user

The error occurred on the application server TargetHost and in the work process 0 .

The termination type was: ERROR_MESSAGE_STATE

The ABAP call stack was:

Method: EXECUTE_REQUEST of program CL_HTTP_SERVER================CP

Function: HTTP_DISPATCH_REQUEST of program SAPLHTTP_RUNTIME

Module: %_HTTP_START of program SAPMHTTP

Error code: ICF-IE-http -c: Port# -u: PIAPPLUSER -l: E -s: TargetSysName -i: HostName -w: 0 -d: 20110920 -t: 150440 -v: ERROR_MESSAGE_STATE -e: Log on with a dialog user

The PIAPPLUSER is System user in the target SRM system. But we tried changing the User to Dialog user but that time we are getting the error as

Note

The following error text was processed in the system TargetSys : The browser is not supported

The error occurred on the application server TargetHost and in the work process 0 .

The termination type was: ERROR_MESSAGE_STATE

The ABAP call stack was:

Function: ICF_ATTACH_ITS_PLUGIN of program SAPLHTTP_RUNTIME

Method: EXECUTE_REQUEST_FROM_MEMORY of program CL_HTTP_SERVER================CP

Function: HTTP_DISPATCH_REQUEST of program SAPLHTTP_RUNTIME

Module: %_HTTP_START of program SAPMHTTP

Error code: ICF-IE-http -c: Port# -u: PIAPPLUSER -l: E -s: TargetSysName -i: HostName -w: 0 -d: 20110920 -t: 150440 -v: ABORT_MESSAGE_STATE -e: The browser is not supported.

Any help how to resolve this issue will be greatly appreciated.

Thanks & Regards

Prem Anandh P.

[prasanthi_chavala · Accepted solution]

Hi,

In your error logs it is showing that

"Error when processing your request

The URL -target system URL- was not called due to an error. "

So i would advice you to verify under technical settings, the url given in the path prefix is valid or not.

FYI:

/sap/xi/engine?type=entry

for SAP systems based on SAP BASIS 6.40 (XI 3.0 message protocol).

/sap/xi/engine?type=receiver

for SAP systems based on SAP BASIS 6.20 (XI 2.0 message protocol).

Also i suggest you to use system User id name (eg: PISRMLOGIN...etc) other than PI standard system user id's in your RFC destination to SRM system.

Thanks,

Prasanthi.

[Former Member]

Hi,

It seems issue with the User ID has not sufficient roles in SUS , ask your security team to provide the below roles to User ID PIAPPLUSER .

SAP_BC_FPADS_ICF 09.09.2011 31.12.9999 Form Processing: Role for ICF Service

SAP_BC_JSF_COMMUNICATION 09.09.2011 31.12.9999 Communications User for SAP Java Security Framework

SAP_BC_JSF_COMMUNICATION_RO 09.09.2011 31.12.9999 Communications User for SAP Java Security Framework (Display)

SAP_CA_BFA_DATATRANSFER 09.09.2011 31.12.9999 Data Transfer Specialist

SAP_EC_SUS_ADMIN_VENDOR 18.08.2011 31.12.9999 mySAP SRM SUS Administrator Supplier

SAP_EC_SUS_SERVICE_AGENT 09.09.2011 31.12.9999 SAP SRM SUS Service Agent

SAP_XI_IS_SERV_USER 09.09.2011 31.12.9999 Exchange Infrastructure: Integration Server Service User

[Former Member]

Kumar,

The RFC Destination is working perfectly fine in our Dev & QA environment. The username used for these 2 environments have exactly the same roles as that of PIAPPLUSER from our Dev environment. Anyways will suggest this option to our Security team & test with this role changes. Will keep posting the results here.

Thanks & Regards

Prem Anandh P.

[naveen_chichili]

Hi Prem Anandh,

Check if PIAPPLUSER is locked in your PI Server.If it is locked try to unlock it and the give PIAPPLUSER in your RFC destination and try to test .

Regards,

Naveen

[Former Member]

The PIAPPLUSER used in this RFC Destination is available in the SRM server & it is not locked. Just in case, PIAPPLUSER available within PI is also not locked.

Thanks

Prem Anandh P.

[naveen_chichili]

DID you try giving other Service user PISUPER ?

Regards,

Naveen

[Former Member]

The PIAPPLUSER already has the roles SAP_ALL & SAP_NEW assigned with it. Do we still need to try with other Service Users?

Thanks & Regards

Prem Anandh P.

[naveen_chichili]

try once

[Former Member]

Chichilin,

PISUPER user is not available in our SRM System as such...

Thanks & Regards

Prem Anandh P.