Assertion Failed Error

[Former Member]

Hi All,

Some of the users using my appliation is getting the below error.

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.

The application is working fine for many other users. Only few are facing this issue. They are getting this dump when they are trying to submit the data. What could be the issue?

I checked with the Authorization roles assigned for them. Everything is fine. Is there any special authorization needed to update the table?

[Former Member]

The problem is that I am not able to reproduce the error from my side. Many employees are reporting that they are getting this dump. I tried several times and am not able to reproduce the error.

[Former Member]

This happens at times.

1. For the assert condition, you have to debug the code and use ST22 for further details.

2. I would suggest you to check or try to reproduce the same in user system and if possible try to use debugger in user system (If possible).

This will help you to solve the issue soon.

[Former Member]

Ya I checked the log in ST22. Its pointing me to some standard SAP code. Not the code from our application.

1 method decode.

2

3 data: encoded_chars type match_result_tab.

4 find all occurrences of regex '~(....)' in input results encoded_chars.

5

6 data: offset type i.

7

8 field-symbols: <encoded_char> like line of encoded_chars.

9 loop at encoded_chars assigning <encoded_char>.

10 data: char_off type i. char_off = <encoded_char>-offset + 1.

11 data: char_len type i. char_len = <encoded_char>-length - 1.

12

13 data: unicode type xstring.

14 unicode = input+char_off(char_len).

15

16 try.

17 data: char_sequence type string.

18 m_converter->convert( exporting input = unicode importing data = char_sequence ).

19

20 data: length type i. length = <encoded_char>-offset - offset.

21 concatenate result input+offset(length) char_sequence into result.

22

23 offset = <encoded_char>-offset + <encoded_char>-length.

24 catch cx_sy_conversion_codepage cx_sy_codepage_converter_init cx_parameter_invalid_typ

>>>>> assert fields unicode condition 0 eq 1.

26 endtry.

27 endloop.

28

29 concatenate result input+offset into result.

[Former Member]

Hi,

Before this statment for dump is encountered, are you doing any converisons for datatypes....

Are you moveing value from datatype to other..

Please chkci n deubuggin everyline where this is going for a dump.

Regards,

Lekha.

[thomas_jung]

This error tells you quite a bit. It is a code page conversion error. You should look at what languages the users are logging in with and what languages they are inputing data with. It appears they are inputting characters outside the code page for the language in which they are logging in. This is a problem if your system is non-unicode. For instance, they login with English but enter Polish characters. English is Latin-1 and Polish is Latin-2. That's just an example. You should study what languages are actually in use in your applications.

[Former Member]

The issue is solved by the SAP Note 1343806.

I tried to reproduce the error and found one such case. We had a textedit where the user enter the Reason. Some users have tried to enter the reson in a bulleting format which caused the Assertion failed error.

Applying this note, resolved that issue.

Thanks everyone for your responses.

[Former Member]

Hi,

I saw that note, but in that nothing mentioned related to this issue. can you help me from this.

Regards,

sampath.

[Former Member]

Hi Thomas,  

         Am also facing this issue. am using ALV Grid report there more than 50,000 entries available. its first time display working fine but whenever click some action, that time it will though an dump. Kindly find below screen short. 

Thanks,

Tamil C.

Category               ABAP Programming Error                                                      
Runtime Errors         ASSERTION_FAILED                                                            
ABAP Program           CL_DATAPTABLECACHE============CP                                            
Application Component  BC-FES-GUI                                                                  
Date and Time          07.08.2015 16:58:46                                                         
                                                                                                   

  

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.

[thomas_jung]

"The ASSERT condition was violated" is a fairly meaningless error my itself. It basically says something bad happened but doesn't provide any reason why. I would suggest that you check ST22 and look for a corresponding short dump. That will provide more details about the actual cause of the error. At least it should lead you to the offending source code that triggered the assertion and from there you should be able to see the condition check that leads to it. Without more details there isn't much advice that can be provided here. There are several common causes of assertion errors in WDA - like incorrect cardinality, incorrect dynamic binding, etc.