cancel
Showing results for 
Search instead for 
Did you mean: 

Dump in WDA application .

Former Member
0 Kudos

Hi everyone

I am trying to test on of the standard application(in se80) of talent management but it is throwing an error :

"The Assert Condition was violated".

package : paoc_tmc

WDA application :hrtmc_long_profile

Package : EHP4

can anyone help me ?

regards

vaibhav

Accepted Solutions (0)

Answers (2)

Answers (2)

Abhinav_Sharma
Contributor
0 Kudos

Hi Vaibhav,

May be the following links can help you out:

  1. http://scn.sap.com/thread/1885781
  2. http://scn.sap.com/thread/1596288

Cheers!!

Abhinav

Former Member
0 Kudos

Hi Vaibhav,

Goto st22 and identify where you are getting this error. It might be because of cardinality.

When no data exits you will get this type of error. Please check.

Cheers,

Kris.

Former Member
0 Kudos

Hi Krishna

Thanx for your eply :

here is the explanation :

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.

It is standard application where in i cant change the cardinality

regards

vaibhav

Former Member
0 Kudos

Hi Krishna

Thanx for your eply :

here is the explanation :

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.

It is standard application where in i cant change the cardinality

regards

vaibhav