ASSERTION_FAILED dump in GRC system.

[Former Member]

Hi All,

I am troubleshooting an issue on GRC system and need forum's help/guidance. There are ASSERTION_FAILED dumps occurring GRC system daily with WF-BATCH user. There is no particular pattern for these dumps like happening at a particular period, but they do occur daily. I am posting more information below, please help me in fixing this issue,

Category	ABAP Programming Error
Runtime Errors	ASSERTION_FAILED
ABAP Program	CL_GRFN_MSMP_NOTIFICATION=====CP

Application Component  GRC

Short text

The ASSERT condition was violated.

What happened?

	In the running application program, the ASSERT statement recognized a
	situation that should not have occurred.
	The runtime error was triggered for one of these reasons:
	- For the checkpoint group specified with the ASSERT statement, the
	activation mode is set to "abort".
	- Via a system variant, the activation mode is globally set to "abort"
	for checkpoint groups in this system.
	- The activation mode is set to "abort" on program level.
	- The ASSERT statement is not assigned to any checkpoint group.

What can you do?

Note down which actions and inputs caused the error.

	To process the problem further, contact you SAP system
	administrator.
	Using Transaction ST22 for ABAP Dump Analysis, you can look
	at and manage termination messages, and you can also
	keep them for a long time.

Error analysis

    The following checkpoint group was used: "No checkpoint group specified"

    If in the ASSERT statement the addition FIELDS was used, you can find

    the content of the first 8 specified fields in the following overview:

    " (not used) "

    " (not used) "

    " (not used) "

    " (not used) "

    " (not used) "

    " (not used) "

    " (not used) "

    " (not used) "

User and Transaction

    Client.............. 100

    User................ "WF-BATCH"

    Language key........ "E"

    Transaction......... " "

    Transaction ID...... "DBA981E25DCFF10F88E200155D000C5E"

    EPP Whole Context ID.... "00155D000C5E1ED2A0B53B79EBA128E2"

    EPP Connection ID....... "E4A981E2755EF13988E200155D000C5E"

    EPP Caller Counter...... 1

    Program............. "CL_GRFN_MSMP_NOTIFICATION=====CP"

    Screen.............. "SAPMSSY1 3004"

    Screen Line......... 2

    Debugger Active..... "none"

Please let me know if I could provide more details.

[Colleen]

Hi

Since this is running under WF-BATCH and relates to SE24 CL_GRFN_MSMP_NOTIFICATION the error is due to workflow notifications based on your MSMP configuration

As a notification workflow item, it would explain why there is no pattern or consistency in time of day or number of items.

First, please check your WF-BATCH user has an email address and SAP_ALL/SAP_NEW assigned

You should consider if this is a recent issue or has always occurred. If recent, consider if you have imported SAP notes or support stack OR has someone made changes to MSMP

If not, you will need to review the workflow items and MSMP configuration to see if it is having issues determining the Agent to send the workflow notification to

In doing a quick search for ASSERT in the methods of this class, the only method "GET_NOT_VARS_AND_ATTACHMNTS" contains the value. Possibly consider debugging this in Non Prod environment to understand how it works.

If all else fails, raise a message with SAP as per ST22 instructions.

[Former Member]

Hi Colleen,

Thanks for the detailed steps. I have the email id and profiles are maintained correctly.

I am from Basis team and I am not sure of the configuration of the notifications.

I will contact the GRC team and will seek for help.

Thanks again,

Pradeep