SAP for Utilities Discussions
Connect with fellow SAP users to share best practices, troubleshoot challenges, and collaborate on building a sustainable energy future. Join the discussion.
Showing results for 
Search instead for 
Did you mean: 

ASSERTION_FAILED dump during EMMA case generation for implausible reads

0 Kudos

Hi All,

When I am trying to create the emma clarification case using EMMA Tcode. Its giving me dump with below message:


The ASSERT condition was violated.

what happened?

  The current application program has detected a situation with the

  ASSERT statement that should not occur.

  The reason for this runtime error was one of the following:

  - For the checkpoint group specified with the ASSERT statement, the

  activation mode is "abort".

  - A system variant has been used to set the activation mode to "abort"

  globally for all checkpoint groups in this system.

  - The activation mode is set to "abort" at program level.

  - The ASSERT statement is not assigned to any checkpoint groups.

Program name where it is giving me dump is RSC1_ON_COMMIT_BUFFER: This program is being called when system try to create the delta.During debugging, I found that, When I remove following flags, KPI_REL flag from table EMMA_BPA and KPI_MSG flag and changed the value of field XBPAACT to 1 from EMMAC_BPA  table for BPAREA "EMR" its not giving any dump.

Below is the piece of code:

*   Threshold in number of lines to flush current buffer

    READ TABLE it_data ASSIGNING <ls_data> INDEX 1.

    ASSERT sy-subrc  EQ 0        AND

           <ls_data> IS ASSIGNED.

Here in internal table it_data in first iteration system creates two records but in second iteration it brings nothing and then dump comes. Not sure why it is coming here in second iteration when there was no data in table.

I don't want to change these config as it will result data not being updated in BI.

So please help how I can fix this error without changing the above config.



0 Kudos

Look at note 1638519 for the solution.  applying the changes should fix the error.



0 Kudos

Hi William,

Thank you for your reply.

This note is already implemented in our system. Any other suggestion would be highly appreciated.