Hi,
While posting the document in migo we are facing two dumps first MESSAGE_TYPE_X this comes and then DBIF_RSQL_SQL_ERROR.
For detailed view i am pasting the dump hereunder,
Runtime Errors MESSAGE_TYPE_X
Date and Time 11.04.2008 05:04:20
Short text
The current application triggered a termination with a short dump.
What happened?
The current application program detected a situation which really
should not occur. Therefore, a termination with a short dump was
triggered on purpose by the key word MESSAGE (type X).
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
Short text of error message:
Document number 1000 4900000000 2008 was already assigned
Long text of error message:
Diagnosis
Document number 4900000000 in company code 1000 and fiscal year
2008 has already been assigned.
System Response
Termination of processing.
Procedure
Check document number range 49 in company code 1000 and fiscal year
2008 and correct the number range status if necessary.
Technical information about the message:
Message class....... "F5"
Number.............. 152
Variable 1.......... 1000
Variable 2.......... 4900000000
Variable 3.......... 2008
Variable 4.......... 49
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:
"MESSAGE_TYPE_X" " "
"SAPLMBWL" or "LMBWLU21"
"MB_POST_GOODS_MOVEMENT"
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.
ystem environment
SAP-Release 700
Application server... "NELPRD"
Network address...... "200.200.200.114"
Operating system..... "AIX"
Release.............. "5.3"
Hardware type........ "0005CFF0D700"
Character length.... 16 Bits
Pointer length....... 64 Bits
Work process number.. 1
Shortdump setting.... "full"
Database server... "NELPRD"
Database type..... "ORACLE"
Database name..... "NPS"
Database user ID.. "SAPSR3"
Char.set.... "C"
SAP kernel....... 700
created (date)... "Apr 2 2006 20:44:50"
create on........ "AIX 2 5 005DD9CD4C00"
Database version. "OCI_101 "
Patch level. 52
Patch text.. " "
Database............. "ORACLE 9.2.0.., ORACLE 10.1.0.., ORACLE 10.2.0.."
SAP database version. 700
Operating system..... "AIX 1 5, AIX 2 5, AIX 3 5"
Memory consumption
Roll.... 16192
EM...... 20949240
Heap.... 0
Page.... 122880
MM Used. 15949904
MM Free. 806288.
The second one is hereunder,
untime Errors DBIF_RSQL_SQL_ERROR
xception CX_SY_OPEN_SQL_DB
ate and Time 11.04.2008 05:04:23
Short text
SQL error in the database when accessing a table.
What can you do?
Note which actions and input led to the error.
For further help in handling the problem, contact your SAP administrator
.
You can use the ABAP dump analysis transaction ST22 to view and manage
termination messages, in particular for long term reference.
How to correct the error
Database error text........: "ORA-08102: index key not found, obj# 172496, file
21, block 248899 (2)"
Internal call code.........: "[RSQL/DELE/SNAP ]"
Please check the entries in the system log (Transaction SM21).
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:
"DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
"SAPMS380" or "MS380F10"
"DELETE_OLD_SNAP_RECORDS"
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.
The exception must either be prevented, caught within proedure
"DELETE_OLD_SNAP_RECORDS" "(FORM)", or its possible occurrence must be declared
in the
RAISING clause of the procedure.
Your soon help and suggestions will be highly appreciated.
Thanks and regards,
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.