cancel
Showing results for 
Search instead for 
Did you mean: 

Error in RFC to FTP asynchronous scenario

Former Member
0 Kudos

Hi Experts,

I have created RFC to File(FTP) scenario in SAP PI 7.31 AEX(java only) server.

When I execute RFC in sender SAP server, it gives run-time error(dump) as "call to messaging system failed".

But it successfully creates text file in target FTP server.

In message monitoring I found 2 messages for this.

First has status 'Canceled' with below message log,

Second message has status as 'Log Version' with no message log and with below message details.

Please suggest/guide me how to rectify this run-time error.

Thanks,

Amit Patil

Accepted Solutions (1)

Accepted Solutions (1)

JaySchwendemann
Active Contributor
0 Kudos

I could think of the following reasons:

  1. Make sure this is not a caching problem by executing /CPACache/refresh?mode=full
  2. Check ESR if mapping (you do have a mapping for this, right?) is executing correctly. Use "test" tab for this
  3. Make a dummy change to the mapping. Activate and re-execute
  4. Use XPI Inspector (Template 50 and give communication channel) to track down further

Cheers

Jens

Former Member
0 Kudos

Hi Jens,

I tried your suggestion, but couldn't work.

But I found 1 doubtful thing which is Quality of Service. It is found as

Quality of ServiceBE

in message details of 1st message.

Also in message content of 1st message it is as

9/18/2014 1:36:51.053 PMInformationFile adapter receiver: processing started; QoS required: BestEffort

I don't know from where is getting set as 'BE'. It should be 'EO' since my scenario is asysnchronous.

Please suggest.

Thanks,

Amit Patil

JaySchwendemann
Active Contributor
0 Kudos

Check FPT sender channel "quality of serivce" setting. Could very well be "best effort". Of course this doesn't make much sense here.

Cheers

Former Member
0 Kudos

Hi Jens,

In my case, RFC is on sender-side and File/FTP is on receiver-side.

And I guess, in File receiver adapter, there is no place to maintain QoS.

So this is quite strange that QoS is occurring as 'BE' in message monitoring.

It is showing 2 messages. 1st has status as 'Canceled' and 2nd has status as 'Log Version'.

Thanks,

Amit Patil

JaySchwendemann
Active Contributor
0 Kudos

Ok, sorry, I got wrong that you have RFC sender. My bad.


Some point I can think of now is...

1. How are you calling the sender RFC in your SAP system? Our call looks like this


CALL FUNCTION 'ZYOUR_FM' IN BACKGROUND TASK

2. How did you set up the receiver (inbound) interface? Is it asynchronous?

Cheers

Jens

Former Member
0 Kudos

Hi Jens,

I have kept inbound interface as asynchronous only.

And I'm executing my Function Module/RFC directly from SE37 by providing RFC destination.

Thanks,

Amit Patil

former_member183908
Active Contributor
0 Kudos

Do you have both import and export parameters in your RFC?If so please try to remove export parameters and try to run the interface again by importing RFC into ESR.

Thanks

Former Member
0 Kudos

Hello AMit ,

What is the mode of your service interface which you are using? Is it also Asynchronous?

Thanks

Gaurav

JaySchwendemann
Active Contributor
0 Kudos

Function Builder (SE37) probably uses sync call. I would suggest writing a test report and properly calling in background task.

Former Member
0 Kudos

Hi Jens,

I'll try & test this scenario by calling this FM/RFC in background task in a test program.

Then I'll let you know about the outcome.

Thanks,

Amit Patil

Former Member
0 Kudos

Hi Jens,

I have tried & tested the scenario by calling this FM/RFC in background task and with RFC destination in a test program. I got success. The message got processed successfully with QoS as EO. There was no run-time error/dump in sender SAP system. That means SAP-RFC execution in SE37 probably behaves synchronously although its an asynchronous interface.

Many Thanks,

Amit Patil

JaySchwendemann
Active Contributor
0 Kudos

Glad to hear you got your issue resolved.

Cheers

Jens

Answers (1)

Answers (1)

former_member183908
Active Contributor
0 Kudos

For RFC/IDOC interfaces generally you no need to create service interface.In case if you have created then check the mode of interface as suggested

Thanks

Former Member
0 Kudos

Hi Pavan,

Obviously I have not created any outbound interface. I used RFC as outbound interface.

Any other probable mistake?

Thanks,

Amit Patil