Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Runtime Error for Function Module

former_member192971
Participant
0 Kudos
513

Hi Guys ,

  I am facing a runtime error when i am trying to Run extended program check , code inpsector for a Function Module.

Runtime Error looks like below...


  Category : ABAP Programming error

Runtime Errors : ASSERTION_FAILED

ABAP Program : CL_SLIN_CHECKER_SINGLE========CP

APPLICATION COMPONENT : BC-ABA-LA

  The Assert Condition was violated.


What happened?

    In the running application program, the ASSERT statement recognised 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,

      activation mode is set to "abort".

    - Via a system variant, the activation mode is globally set to

      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.

Could any one suggest the Reason and try to solve my error.

Thanks .

4 REPLIES 4

wol
Active Participant
0 Kudos
157

Even if you think "situation sthat should not have occured" it seems as if it has actually occured.

You should debug the code an check for the situation.

Regards

Stefan

kumud
Active Contributor
0 Kudos
157

Hi,

In ST22 dump it must be pointing to the code where the dump occurs and some additional information.

You could show us that part as well. Moreover, I just did a quick search on SCN for this kind of error and found an exact thread for this kind of issue. Link farming is  not allowed and hence I would not be able to post the thread. It's better you do a search on this issue. Thanks.

Regards,

Kumud

Former Member
0 Kudos
157

As has already been mentioned it is worth looking at the short dump in ST22 to see where the error occurs and debugging your code to see what values are held in the relevant variables. Check for notes. I vaguely remember having a similar problem some time ago when we moved to a unicode system and I think I found a note which solved the problem.

0 Kudos
157

Hi Kevin,

            Check in the Slin T-code this might help you where u have done the mistakes.in your Report