Announcement:
wanna exchange links? contact me at sapchatroom@gmail.com.
Posted by
Admin at
Reply from r3dd3vil on May 5 at 7:56 AM Thanks Elena,
That worked :)
BR,
Adi.
| | | ---------------Original Message---------------
From: r3dd3vil
Sent: Tuesday, April 29, 2014 4:40 AM
Subject: Short Dump in Configuring STMS
Dear SAP Friends,
I am configuring between 3 systems (DEV, QAS and PRD) with the DEV system as the domain controller. When I try to include the QAS or PRD system to the created domain I get the following short-dump:
Category ABAP Programming Error
Runtime Errors ASSERTION_FAILED
ABAP Program SAPLTMSM
Application Component BC-CTS-TMS
Date and Time 29.04.2014 10:37:46
Short text
The ASSERT condition was violated.
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.
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) "
Trigger Location of Runtime Error
Program SAPLTMSM
Include LTMSMU05
Row 312
Module type (FUNCTION)
Module Name TMS_MGR_CONFIGURE_CLIENT
Thank you in advance for support in this issue.
Best regards,
Adi. |
| Reply to this email to post your response. __.____._ | In the Spotlight Become a blogger at Toolbox.com and share your expertise with the community. Start today.   _.____.__ |
