Quantcast
Channel: SCN: Message List - Governance, Risk and Compliance (SAP GRC)
Viewing all articles
Browse latest Browse all 8113

GRC Process Control 10.0 Automated Monitoring RFC Error

$
0
0

Hi,

 

I'm trying to implement Automated Monitoring with ABAP Reports in Process Control 10.0 . The data source has been set up, the business rule has been developed and assigned. But when I schedule a job for this data source, job get stuck in "Progressing" phase. When I check ST22 in ECC side, I saw that I get a dump with short text "Function module "GRFN_IE_CALLBACK_RFC" not found."

 

When I check this FM, I saw that this RFC was located in GRC side and ECC couldn't find this RFC, because the destination parameter

is not correct.

 

I create an RFC destination via SM59 in ECC side for GRC PC, but nothing changes. Do I have to define this destination in SPRO, and if it is correct, where do I have to define it?

 

Any suggestions would be greatly appreciated. Thanks,

 

Mustafa

 

|Error analysis                                                                                    |

|    The program "/GRCPI/GRIA_AM_REPORT_CALLBACK" contains the CALL FUNCTION                       |

|     statement.                                                                                   |

|    The name of the function module to be called is "GRFN_IE_CALLBACK_RFC".                       |

|                                                                                                  |

|    No function module exists with the name "GRFN_IE_CALLBACK_RFC".                               |

|    All function modules are listed in the Function Library (SE37).                               |

|    -                                                                                             |

|                                                                                                  |

|    Possible reasons:                                                                             |

|    a) Wrong name specified. Pay particular attention to                                          |

|       upper/lower case and underscores ("_").                                                    |

|       or                                                                                         |

|    b) Transport error                                                                            |

|    c) In the case of an enqueue/dequeue module,                                                  |

|       the lock object may not have been activated                                                |

|       (ABAP/4 Dictionary).


Viewing all articles
Browse latest Browse all 8113

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>