RFC FM

[Former Member]

Hello,

I am currently facing a weird problem. When I call a RFC FM it returned with a short dump CALL_FUNCTION_REMOTE_ERROR.

So I implemented the exceptions as pointed out in note 1371131. This way I figured it returns with a SYSTEM_FAILURE.

Now the weird part is I call several RFC FMs calling the same system which work just fine. There is just this one which is giving me problems.

And in the end to make it even weirder when I tried debugging the problem the FM works just fine and doesn't return with this SYSTEM_FAILURE.

Has anyone ever faced such a problem? Please provide me with intel.

Best regards,

John

[Former Member]

Hi , Are you calling this RFC FM in a LOOP statement... If So there is a possibilities of RFC breakdown..

Is this FM again calling the Source system for any details? (For eg System A call the RFC FM in System B, in side this Fm, there will be another RFC call to System A).. This will some time end with error.

In debugging it is working means, try use WAIT statement before RFC call and check....

And Check the other system also for any dump.....

[Former Member]

Hi Senthil,

Thanks for your quick reply.

1. The FM is not called from within a LOOP

2. The FM goes from A to B and then sends data to PI. But not from A-B-A it just returns after executing in B.

3. I shall try it. ***> This doesn't work either.

But still I am curious about the cause of this problem.

Best regards,

John

Edited by: jvanpelt on Jul 16, 2010 9:14 AM

Edited by: jvanpelt on Jul 16, 2010 9:40 AM

[Former Member]

HI,

your SAP setting is Front-End Editor(New) ? or is Front-End Editor(old)?

[Former Member]

Hi Leo,

I work with the new Front end editor.

Best regards,

John

[Former Member]

Hi John,

One major cause for problems disappearing in debug mode are often [race conditions|http://en.wikipedia.org/wiki/Race_condition] (though of course there might be others). I.e. by invoking the debugger you most likely slow down the program execution and thus might miss issues that only show up if the program is executed at "full speed"...

But still I am curious about the cause of this problem.

Ok, you lost me in your explanation what you actually do. However, let's assume for now that you're calling an RFC in an ABAP system. In that case a SYSTEM_FAILURE exception should correspond to a short dump in the target system (i.e. where the RFC is executed) and you should be able to see the cause in ST22. So if you're really curious I'd recommend to check short dumps or exceptions in your target system, which should give you further information. Heck, even the exception message returned by SYSTEM_FAILURE might already tell you enough...

Unless you post further details I doubt that anybody will be able to provide you any explanation (it's more an invitation to a guessing game that usually attracts silly answers).

Cheers, harald

[Former Member]

Hi Harald,

Thanks for your reply!

The message of the exception is "Error in Control framework". I have never encountered such a problem so it is not clear to me what this means. Therefore I don't know what extra info to provide.

So I try to explain the process:

I have WD4A in system A. This calls a FM in system B where data will be collected and send to PI.

When I look in the target system there is no short dump in st22 but there is one in the calling system.

But the info in this short dump is minimal.

Foutenanalyse
    An error occurred when executing a REMOTE FUNCTION CALL.
    It was logged under the name " "
    on the called page.

Best regards,

John

[Former Member]

The message of the exception is "Error in Control framework".

OK, sounds like we both are guessing, so let me take an unqualified stab at it: Control framework sounds like it might be related to an RFC module that can only be executed when attached to a SAPgui. So you could try looking at the RFC in system B and see if there's anything that makes it "non-batchable". A quick (?) test might be to create a test program in system B that executes the problematic function module and run it once in dialog mode and then in background. If it dumps when run via a job, you found the cause...

Apart from that I don't have any good idea, if your short dump doesn't contain any useful information (sounds unusual, I'd expect some stack trace and code reference). If you're calling a standard RFC you probably should take a look at OSS...

[Former Member]

Harald,

Thank you very much for your time and effort. I think I might have found something.

I will investigate it further and close this thread.

Best regards,

John