on 09-12-2012 5:00 AM
Category | ABAP Programming Error |
Runtime Errors | ASSERTION_FAILED |
ABAP Program | CL_SALV_BS_FILTER=============CP |
Application Component BC-WD-CMP-ALV
Date and Time | 11.09.2012 12:47:37 |
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. |
Short text
The ASSERT condition was violated. |
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) " |
How to correct the error
Probably the only way to eliminate the error is to correct the program. | |
- |
If the error occures in a non-modified SAP program, you may be able to | |
find an interim solution in an SAP Note. | |
If you have access to SAP Notes, carry out a search with the following | |
keywords: |
"ASSERTION_FAILED" " " | |
"CL_SALV_BS_FILTER=============CP" or "CL_SALV_BS_FILTER=============CM00C" | |
"DO_STRATEGY_DYNAMIC_WHERE" |
If you cannot solve the problem yourself and want to send an error | |
notification to SAP, include the following information: |
1. The description of the current problem (short dump) |
To save the description, choose "System->List->Save->Local File | |
(Unconverted)". |
2. Corresponding system log |
Display the system log by calling transaction SM21. | |
Restrict the time interval to 10 minutes before and five minutes | |
after the short dump. Then choose "System->List->Save->Local File | |
(Unconverted)". |
3. If the problem occurs in a problem of your own or a modified SAP |
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
Information on where terminated
Termination occurred in the ABAP program "CL_SALV_BS_FILTER=============CP" - | |
in "DO_STRATEGY_DYNAMIC_WHERE". | |
The main program was "SAPMV75F ". |
In the source code you have the termination point in line 86 | |
of the (Include) program "CL_SALV_BS_FILTER=============CM00C". |
Kindly help us to resolve the issue.
Regards
Raghu
Hi Raghu
Im facing the same issue. Please did you ever fix it?
Regards,
Franklin Cedillo
Basis Consultant
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
85 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.