Hi ,
While creating purchase order we are getting an ABAP dump error , I had pasted the Dump error here :
Runtime Errors RAISE_EXCEPTION
Occurred on 28.07.2008 at 15:29:53
Exception condition "NO_BATCH" raised.
What happened?
The current ABAP/4 program encountered an unexpected
situation.
What can you do?
Print out the error message (using the "Print" function)
and make a note of the actions and input that caused the
error.
To resolve the problem, contact your SAP system administrator.
You can use transaction ST22 (ABAP Dump Analysis) to view and administer
termination messages, especially those beyond their normal deletion
date.
Error analysis
A RAISE statement in the program "SAPLGRAP" raised the exception
condition "NO_BATCH".
Since the exception was not intercepted by a superior program
in the hierarchy, processing was terminated.
Short description of exception condition:
Front-End Function Cannot Be Executed in Backgrnd
For detailed documentation of the exception condition, use
Transaction SE37 (Function Library). You can take the called
function module from the display of active calls.
-
How to correct the error
You may able to find an interim solution to the problem
in the SAP note system. If you have access to the note system yourself,
use the following search criteria:
"RAISE_EXCEPTION" C
"SAPLGRAP" or "LGRAPU32"
"WS_QUERY"
or
"SAPLGRAP" "NO_BATCH"
or
"RSM13000 " "NO_BATCH"
If you cannot solve the problem yourself, please send the
following documents to SAP:
1. A hard copy print describing the problem.
To obtain this, select the "Print" function on the current screen.
-
2. A suitable hardcopy prinout of the system log.
To obtain this, call the system log with Transaction SM21
and select the "Print" function to print out the relevant
part.
3. If the programs are your own programs or modified SAP programs,
supply the source code.
To do this, you can either use the "PRINT" command in the editor or
print the programs using the report RSINCL00.
4. Details regarding the conditions under which the error occurred
or which actions and input led to the error.
System environment
SAP Release.............. "620"
Application server....... "ides"
Network address.......... "172.16.0.175"
Operating system......... "Windows NT"
Release.................. "5.2"
Hardware type............ "2x Intel 801586"
Character length......... 8 Bits
Pointer length........... 32 Bits
Work process number...... 4
Short dump setting....... "full"
Database server.......... "IDES"
Database type............ "MSSQL"
Database name............ "I04"
Database owner........... "i04"
Character set............ "English_United State"
SAP kernel............... "640"
Created on............... "Aug 17 2007 00:20:23"
Created in............... "NT 5.0 2195 Service Pack 4 x86 MS VC++ 13.10"
Database version......... "SQL_Server_8.00 "
Patch level.............. "196"
Patch text............... " "
Supported environment....
Database................. "MSSQL 7.00.699 or higher, MSSQL 8.00.194"
SAP database version..... "640"
Operating system......... "Windows NT 5.0, Windows NT 5.1, Windows NT 5.2,
Windows NT 6.0"
User, transaction...
Client.............. 120
User................ "MM01"
Language key........ "E"
Transaction......... "ME21N "
Program............. "SAPLGRAP"
Screen.............. "RSM13000 3000"
Screen line......... 2
Information on where termination occurred
The termination occurred in the ABAP program "SAPLGRAP" in "WS_QUERY".
The main program was "RSM13000 ".
The termination occurred in line 29 of the source code of the (Include)
program "LGRAPU32"
of the source code of program "LGRAPU32" (when calling the editor 290).
The program "SAPLGRAP" was started in the update system.
What is the patch i need to apply for tis error .
Kindly guide me ,
Regards,
Rakesh
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.