3

In `ST22, I found a short dump caused by a RFC in a infinite loop.

The problem is that I did not find any jobs that triggered the RFC, nor any errors in SM58.

How can I find out how that RFC was triggered? Which transaction should I check ?

In ST22, in the call stack is just subroutine pool SAPMSSY1

Sandra Rossi
  • 11,934
  • 5
  • 22
  • 48
Ovidiu Pocnet
  • 579
  • 12
  • 32
  • 3
    have you taken a look into transcation STAD? You can see which user triggered the rfc. Also you can double click the rfc to get some more info as to the partner IP the connections and the calls. – mrdeadsven May 09 '19 at 08:17

1 Answers1

4

You have a section "caller" in the short dump.

It provides only a very general information. There is the "call program".

enter image description here

Sandra Rossi
  • 11,934
  • 5
  • 22
  • 48
  • The call is being made by another SAP system(let's call is X) to which I also have access. The call program is SAPLCSER. In system X, I checked if there are any jobs with that program, no results. No matching entries in SM58. In STAD I could not find any helpful info. Is there anything else to check ? – Ovidiu Pocnet May 09 '19 at 10:06
  • 1
    It won't be easy to trace anyway. If it's a standard program, open a ticket at SAP support. Jobs only refer the very first program to be called. SAPLCSER (function group CSER) is about CIF (SCM/APO?). You should also ask the people responsible of the calling system to check the logs. – Sandra Rossi May 09 '19 at 11:49