Re : Dump in ME21N

[Former Member]

Hi

While i am creating purchase order i am getting 'Express document' and dump error.

System ID.... I04

Client....... 120

User..... ABAP1

Transaction.. ME21N

Update key... BA6F0C6C08604EB38FBF61AF3A7D53B2

Generated.... 08.09.2008, 11:37:04

Completed.... 08.09.2008, 11:37:05

Error info... 00 671: ABAP/4 processor: RAISE_EXCEPTION

How to solve this

Thanks

Mani

[former_member335885]

Hi Mani,

Check for the recommended solution given in the dump. If it is MM functional issue then you have to do it or please report this to the Basis person.

If you can find out the problem and post it we can give a solution.

I feel this is a MM issue as it says RAISE_EXCEPTION

Thanks & Regards,

Kiran

[Former Member]

Hi ,

I had posted the dump error in ST22 .

Runtime errors RAISE_EXCEPTION

Occurred on 08.09.2008 at 11:30:31

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.

Regards,

Mani

[Former Member]

Check if you have made any developments of your own to run the PO creation in background? This dump would occur only in the following circumstances:

The function you call, WS_QUERY, is not intended for use in batch jobs.

(WS stands for WORKSTATION). These functions cannot run in background,

as they require frontend.

I must therefore request that you not use this function module in batch

jobs and instead use READ DATASET and WRITE DATASET as proposed in note

7925. As additional info please review the note 131360.

please apply the corrections of attached OSS note 782934 and re-test

your scenario.

[deiva]

Hai,

1.Analyze this dump error in SM13 - update requests & double click on the error. This will show the details of error , which is marked in red colour.

2.You can analyse this by ST22 ABAP runtime error.

[Former Member]

Report this Dump error to basis Team

Regards

Saravanan