on 2010 May 28 4:19 AM
hi,all
I run t-code:TPM2,it is throwing an error,
error information as follows:
===========================================================================================
Runtime Errors ASSERTION_FAILED
Date and Time 2010.05.27 15:11:11
-
-
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. |
-
-
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) " |
-
Edited by: Jamesypeng2009 on May 28, 2010 11:20 AM
Related error information,please visit:
http://stephen.pen.blog.163.com/blog/static/1287592672010428114440104/
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
to be continued:
============
-
How to correct the error |
Probably the only way to eliminate the error is to correct the program. |
- |
If the error occures in a non-modified SAP program, you may be able to |
find an interim solution in an SAP Note. |
If you have access to SAP Notes, carry out a search with the following |
keywords: |
"ASSERTION_FAILED" " " |
"SAPLGLIN" or "LGLINU36" |
"G_RWIN_REVERSE" |
If you cannot solve the problem yourself and want to send an error |
notification to SAP, include the following information: |
1. The description of the current problem (short dump) |
To save the description, choose "System->List->Save->Local File |
(Unconverted)". |
2. Corresponding system log |
Display the system log by calling transaction SM21. |
Restrict the time interval to 10 minutes before and five minutes |
after the short dump. Then choose "System->List->Save->Local File |
(Unconverted)". |
3. If the problem occurs in a problem of your own or a modified SAP |
program: The source code of the program |
In the editor, choose "Utilities->More |
Utilities->Upload/Download->Download". |
4. Details about the conditions under which the error occurred or which |
actions and input led to the error. |
-
-
System environment |
SAP-Release 701 |
Application server... "SAPPRD" |
Network address...... "10.206.1.27" |
Operating system..... "AIX" |
Release.............. "6.1" |
Hardware type........ "00CCBCA24C00" |
Character length.... 16 Bits |
Pointer length....... 64 Bits |
Work process number.. 2 |
Shortdump setting.... "full" |
Database server... "SAPPRD" |
Database type..... "ORACLE" |
Database name..... "YDP" |
Database user ID.. "SAPSR3" |
Terminal.......... "acct0212" |
Char.set.... "C" |
SAP kernel....... 701 |
created (date)... "Jan 28 2010 19:50:15" |
create on........ "AIX 2 5 00CB5A5B4C00" |
Database version. "OCI_102 (10.2.0.4.0) " |
Patch level. 69 |
Patch text.. " " |
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.." |
SAP database version. 701 |
Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5, AIX 1 6" |
Memory consumption |
Roll.... 16192 |
EM...... 25139088 |
Heap.... 0 |
Page.... 655360 |
MM Used. 7130128 |
MM Free. 1246768 |
-
-
User and Transaction |
Client.............. 100 |
User................ "F200001" |
Language key........ "E" |
Transaction......... "TPM2 " |
Transactions ID..... "4BFD890DFA840154E10080000ACE011B" |
Program............. "SAPLGLIN" |
Screen.............. "SAPMSSY0 1000" |
Screen line......... 6 |
-
-
Information on where terminated |
Termination occurred in the ABAP program "SAPLGLIN" - in "G_RWIN_REVERSE". |
The main program was "RTPM_TRL_VALUATION_REVERSAL ". |
In the source code you have the termination point in line 246 |
of the (Include) program "LGLINU36". |
-
Edited by: Jamesypeng2009 on May 28, 2010 11:47 AM
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
112 | |
9 | |
8 | |
6 | |
5 | |
5 | |
4 | |
3 | |
3 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.