cancel
Showing results for 
Search instead for 
Did you mean: 

RFC Sender Error

Former Member
0 Kudos
52

Hi,

I'm creating a asynch RFC-XI-JDBC scenario. For the RFC sender i have created a RFC destination in sm59 and i have used the same program ID in my comm. channel. I have tested the RFc destination and its working fine.

I have also created the Sender, receiever agreement, Interface and receiver determinations.

When i execute the RFC from se37 i get a short dump when i enter the RFC Destination. It gives the followong error: "alternativeServiceIdentifier: party/servicefrom channel configuration are not"

Also the sender agreement that i have created is not reflected in SXI_CACHE.

Regards,

Sekar.

Accepted Solutions (0)

Answers (3)

Answers (3)

Shabarish_Nair
Active Contributor
0 Kudos

A similar case was observed in a scenario of mine but this dump was visible only if i made multiple calls to the RFC.

Try the sap note : 730870, it might help you.

Q 15: Whats wrong when the error message "lookup of alternativeServiceIdentifier via CPA-cache failed" shows up while sending a RFC call to the RfcAdapter?

A: A RFC sender channel is located beneath a service within the Integration Directory. Within this service choose "Service" -> "Adapter-Specific Identifiers". The values in the fields "R/3 System ID" and "Client" has to be maintained with the correct values of the system, that sends the RFC call to the RfcAdapter. It normaly only makes sense to have these values filled for services of type "Business System". If maintained in SLD, this fields will be filled automaticaly for services of type "Business System" and can be updated with the button "Compare with System Landscape Directory".

Former Member
0 Kudos

Hi,

This error comes in all these cases:

1. The RFC is running in sync mode and not receiving a reply from SAP XI.

2. The RFC adapter configuration are not done correctly.

3. The PROGRAM ID is not registered.

So you will have to check all this. It's a very common error. You must have missed out on some config.

Regards

vijaya

former_member181955
Contributor
0 Kudos

Hi Sadasivan,

As you told It seems you have done well.Instead of executing RFC in SE37.Call RFC from a SE38 program then your problem will be solved.

follow this below syntax.

CALL FUNCTION 'ZGET_STOCKQUOTE' IN BACKGROUND TASK DESTINATION

'R3TOSOAP'

any concern pleae call me .

thanks

N.P.Babu

iGATE Global Solutions Hyderabad 91-98490 65377

Former Member
0 Kudos

Hi prasad,

I tried calling the RFC from a report in SE38. But after that i can't see any message in SXMB_MONI.

Also i still can't see my sender agreement in SXI_CACHE.

I tried a delta cache refersh and a compete cache refresh. Still no luck.

Regards,

Sekar.

Shabarish_Nair
Active Contributor
0 Kudos

In the sender agreement case, you can try to delete the existing one and create a new agreement.

Also have a look at the SAP note i mentioned in the earlier post.

Former Member
0 Kudos

I deleted and created a new sender agreement. But i can't see it. I had a look at the SAP note that u mentioned.

Regards,

Sekar.

Shabarish_Nair
Active Contributor
0 Kudos

Can you try a cache refresh with the report SAI_CACHE_REFRESH, see if it helps !!! But you need to have that sender agreement very much in your cache ...

Former Member
0 Kudos

That also didn't work. so i just created a proxy and used that, now it's working properly.

Thanks for the help.

former_member184154
Active Contributor
0 Kudos

Looks like an error coming from the J2EE stack.

Open the last useful DefaultTrace.trc file (or use a log viewer) and serach for <i>alternativeServiceIdentifier</i>

Paste the exception full stack trace here.

Another hint: I guess SE37 in single test is going for synch mode, that is it's expecting an RFC response... So you'd better test from a report calling your fm in asynch mode.

Finally, the sender agr should really be in SXI_CACHE trx, so if you don't see it you could have a cache refresh problem. Crawl SDN for that: it's full of literature on this matter.

Alex