Application Development and Automation 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: 
Read only

Runtime Error for Function Module

Former Member
0 Likes
906

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 .


1 ACCEPTED SOLUTION
Read only

former_member184455
Active Participant
0 Likes
696

Hi u k,

Maybe this is the problem described in SAP note 1717414.

There it says, to overcome the issue:

Using the explicit generation (SE38 -> Program -> Generate) for:

CL_SLIN=======================CP

CL_SLIN_CHECKER_I18N==========CP

CL_SLIN_CHECKER_SECURITY======CP

can solve this problem in advance.

In Release 731,

CL_SLIN_CHECKER_DYNPROS=======CP

CL_SLIN_CHECKER_MOD_ENH=======CP

must also be generated explicitly.

regards, Randolf

2 REPLIES 2
Read only

former_member184455
Active Participant
0 Likes
697

Hi u k,

Maybe this is the problem described in SAP note 1717414.

There it says, to overcome the issue:

Using the explicit generation (SE38 -> Program -> Generate) for:

CL_SLIN=======================CP

CL_SLIN_CHECKER_I18N==========CP

CL_SLIN_CHECKER_SECURITY======CP

can solve this problem in advance.

In Release 731,

CL_SLIN_CHECKER_DYNPROS=======CP

CL_SLIN_CHECKER_MOD_ENH=======CP

must also be generated explicitly.

regards, Randolf

Read only

0 Likes
696

Awesome!   Thank you. I spend a few hours trying to fix this on the  NW7.03 trial....