SAP for Utilities Discussions
Connect with fellow SAP users to share best practices, troubleshoot challenges, and collaborate on building a sustainable energy future. Join the discussion.
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

Error is generated in Print workbench function ISU_INV_BILL_PREPARE

Former Member

‎03-08-2010 6:01 PM

0 Kudos

Runtime Errors MESSAGE_TYPE_X

Date and Time 08.03.2010 16:32:47

-

-

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:

Unexpected ELSE case: field sy-subrc with value 0 (/1PWB/200201002180926

57 )

Long text of error message:

Something has occurred in a CASE or IF construct which the

developer did not expect, or which is not permissible here.

System Response

Procedure

Note the field name and field value from the message as well as the

data pattern which lead to the error. Create a problem message.

Technical information about the message:

Message class....... "E9"

Number.............. 898

Variable 1.......... "sy-subrc"

Variable 2.......... 0

Variable 3.......... "/1PWB/20020100218092657"

Variable 4.......... " "

-

-

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:

"MESSAGE_TYPE_X" " "

"SAPLE21J" or "LE21JU09"

"ISU_INV_BILL_PREPARE"

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.

-

1 REPLY 1

Former Member

‎03-08-2010 8:50 PM

0 Kudos

You should try to read the dump instead of dumping it here. In your dump it gives you the values for SY-MSGID, SY-MSGNO, SY-MSGV1, SY-MSGV2, SY-MSGV3, SY-MSGV4. That points to a problem in one of the print workbench objects (a letter or an invoice or something). Take a look at that application form and see what the problem is.