RFC Destination Proxy type to be used for Web Services

[Former Member]

Hi Experts,

I had a basic question regarding the RFC Destination creation for Web Service Management. What is the Transfer Protocol type that we need to select for the RFC destination created in SM59 for Web Services. I see 3 options available

                              basXML

                              Classic with bgRFC

                              Classic with tRFC

Which option do we choose?

Every note or thread I see is talking about bgRFC queues....but once we select it as a bgRFC queue we cannot change it back to any other option is what I have heard. Please confirm...

Any inputs will be a great help.

Thanks.

Nagappan

[Former Member]

Hi All,

This issue is resolved. I just followed the note 1043195 and things are working now.

Thanks.

Nagappan

[Former Member]

Hello Nagappan,

Can you please specify the correct solution for this as currently i m facing the same issue in ecc system.

Regard-

Gaurav

[Former Member]

Hello Nagappan,

can you please clarify your scenario and your requirements?

If you're calling a web service from PI, for example, you don't need any SM59 connection. If you call a web service from ABAP front end, you don't need it, either. You just import the WSDL and the system configures the rest for you. If you come up with some more details, we can give you a clearer answer.

Regards,

Jörg

[Former Member]

Hi Jorg,

We are trying to set up SAP FSCM in ECC6 EHP6 using Web Services. SAP has mentioned that the below mentioned proxies should be set up.

CreditCommitmentNotification_In

CreditCommitmentNotification_Out

CreditPaymentBehaviourSummaryNotification_In

CreditPaymentBehaviourSummaryNotification_Out

We have done the same. Now to check if the Web Service is working correctly, I am running the report SRT_ADMIN_CHECK, the system throws the error mentioned below,

These 2 items have been configured in SOAMANAGER as mentioned. However, when I run SRT_ADMIN_CHECK report to confirm that the settings are done correctly, I am getting the below errors with respect to client 000.

000	Inbound destination	X		Inbound destination WS_BGRFC_INBOUND000 is NOT operational
000	Inbound destination	X		Error: No check of inbound destination:WS_BGRFC_INBOUND000 no usable service destination in client:000

Also when I check the actual error in the SXMB_MONI screen in the xml message the error says

<SAP:Code area="ABAP">INTERFACE_REGISTRATION_ERROR</SAP:Code>

<SAP:P1>ifmmessif</SAP:P1>

<SAP:P2>CreditCommitmentNotification_Out</SAP:P2>

<SAP:P3>http://sap.com/xi/PI/FIN/Operational/Global</SAP:P3>

<SAP:P4 />

<SAP:AdditionalText />

<SAP:Stack>No implementing class registered for the interface (ABAP interface, request message CreditCommitmentNotification_Out, request message, namespace http://sap.com/xi/PI/FIN/Operational/Global)</SAP:Stack>

This is where my Basis consultant asked this question for the type of RFC.

Hope I am clear.

Thanks,

Nagappan

[Former Member]

Hello Nagappan,

is there a special reason you check this in client 000? Your application client should be some other, right? In any case, I assume the report would yield the same result, since coding is client independent. It seems to me that implementation for the service interface is missing. Is this SXMB_MONI error on ECC side or on PI side? Are you calling a web service on ECC or from ECC?

Regards,

Jörg