on 09-19-2014 7:10 AM
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
I could think of the following reasons:
Cheers
Jens
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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 Service | BE |
in message details of 1st message.
Also in message content of 1st message it is as
9/18/2014 1:36:51.053 PM | Information | File 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
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
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
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
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
91 | |
10 | |
10 | |
9 | |
9 | |
7 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.