ME22N error

[Former Member]

Hi,

I am trying to delete a line item from a PO and save the document.

Then i am getting the below Dump

The ASSERT condition was violated.

    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.

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) "

[JL23]

unchanged program or own development?

A dump usually has much more useful information than the part you posted here, see this blog

did you already talk to your local developers?

[Former Member]

yes i have talked to the developer also and he figured the original message which is causing this dump but not sure what this message is related to

text c* id * language * not found

[JL23]

This probably means that an expected text could not be found anymore. Still you have not yet answered if this dump is in your own created routines (BADIs/Userexits/requirments/modifications) or in the SAP standard code.

And this ABAPer should actually be able to tell you the content of those variables, which could then make a functional consultant remember about a certain action done in the past (e.g. a customizing change without changing existing POs )

[Former Member]

no this dump is from the standard code nothing from custom code

this is the system fields of the dump and the program flow

Name     Val.

SY-SUBRC 4

SY-INDEX 0

SY-TABIX 1

SY-DBCNT 0

SY-FDPOS 0

SY-LSIND 0

SY-PAGNO 1

SY-LINNO 1

SY-COLNO 1

SY-PFKEY NORMAL

SY-UCOMM MESAVE

SY-TITLE Held Stock DTNA 4502429478 Created by Traci Olszewski

SY-MSGTY E

SY-MSGID TD

SY-MSGNO 600

SY-MSGV1 C*

SY-MSGV2 *

SY-MSGV3 *

SY-MSGV4

SY-MODNO 0

SY-DATUM 20160817

SY-UZEIT 135534

SY-XPROG SAPCNVE

SY-XFORM CONVERSION_EXIT

No.   Ty.          Program                             Include                             Line

      Name

   19 FUNCTION     SAPLSBAL_DB                         LSBAL_DBU06                           295

      BAL_DB_SAVE

   18 FUNCTION     SAPLMELOG                           LMELOGU07                              12

      ME_LOG_SAVE

   17 FORM         SAPLMEPO                            LMEPOF0M                               37

      MEPO_SAVE_APLG_MESSAGES

   16 FORM         SAPLMEPO                            MM06EF0B_BUCHEN                      1024

      BUCHEN

   15 FUNCTION     SAPLMECOM1                          LMECOM1U04                             44

      MEPO_DOC_POST

   14 METHOD       CL_PO_HEADER_HANDLE_MM========CP    CL_PO_HEADER_HANDLE_MM========CM00H    34

      CL_PO_HEADER_HANDLE_MM=>PO_POST

   13 METHOD       SAPLMEGUI                           LMEGUICJI                             548

      LCL_TRANSACTION_PO=>SAVE

   12 METHOD       SAPLMEGUI                           LMEGUICJF                            1032

      LCL_APPLICATION=>POST_DOCUMENT

   11 METHOD       SAPLMEGUI                           LMEGUICJL                              63

      LCL_DOCUMENT_CMD=>IF_COMMAND_MM~EXECUTE

   10 METHOD       CL_COMMAND_PROCESSORS_MM======CP    CL_COMMAND_PROCESSORS_MM======CM002     7

      CL_COMMAND_PROCESSORS_MM=>IF_COMMAND_MM~EXECUTE

    9 METHOD       CL_CONTROLLER_MM==============CP    CL_CONTROLLER_MM==============CM002     5

      CL_CONTROLLER_MM=>EXECUTE

    8 METHOD       CL_COMPOSITE_SCREEN_VIEW_MM===CP    CL_COMPOSITE_SCREEN_VIEW_MM===CM008     8

      CL_COMPOSITE_SCREEN_VIEW_MM=>EXECUTE

    7 METHOD       CL_COMPOSITE_SCREEN_VIEW_MM===CP    CL_COMPOSITE_SCREEN_VIEW_MM===CM008    10

      CL_COMPOSITE_SCREEN_VIEW_MM=>EXECUTE

    6 METHOD       CL_WINDOW_MM==================CP    CL_WINDOW_MM==================CM005    21

      CL_WINDOW_MM=>HANDLE_EVENT

    5 MODULE (PAI) SAPLMEGUI                           LMEVIEWSF01                           277

      FCODE_EXIT

    4 FORM         SAPLMEGUI                           LMEVIEWSF01                            20

      CALL_SCREEN

    3 METHOD       CL_WINDOW_MM==================CP    CL_WINDOW_MM==================CM004    17

      CL_WINDOW_MM=>SEND

    2 FUNCTION     SAPLMEGUI                           LMEGUIU04                             259

      MEGUI_MAINTAIN

    1 EVENT        RM_MEPO_GUI                         RM_MEPO_GUI                            24

      START-OF-SELECTION

please let me know if you need any further information.

[JL23]

It is about text and message TD600, which is just the standard message when a text can't be found.

It has 3 variables

TD600 Text &1 ID &2 language &3 not found

Your text name in the dump is C* 

the text ID is *

the language is *

Does not make much sense to me. Let your ABAPer further debug and search the statement where these stars are moved to those fields.

[Former Member]

Hi, Just search 'The ASSERT condition was violated' and you will found many threads.

The ASSERT condition was violated. (termination: RABAX_STATE) -  2014 Solved.

The ASSERT condition was violated error in web dynpro abap - 2012

Getting "The ASSERT condition was violated" dump - 2014

Thanks,