Purchase Order going to Dump if Output Message has Dispatch Time 4

[Former Member]

Hi All,

We are getting a Runtime Error while saving or changing any Purhase Order, if the Output Message has Dispatch Time maintained as 4 i.e. Send Immediately.

For all other dispatch time there is no issue. We have maintained condition record for the Message Type with Print Medium as 1 and Dispatch Time as 4. Also, the printer is maintained in the communication tab.

No printer is maintained as default in the User Profile. No Printer is assigned to purchasing group. Our requirement is to print on the printer specified in the Condition Records itself.

We are using Smartform, not standard SAP script for printing.

Please suggest how we can rectify this issue.

Regards,

Ankit

[Former Member]

Hi Ankit,

Whenever you use the output dispatch timing to "4", the processing is done in update task.

Check with Abaper if he is updating any table in driver program before printing the output or he has used any COMMIT statement. Since in udpate task no explicit COMMIT is allowed.

Thanks,

Sumit

[former_member222204]

Pls change output dispatch timing to 3 - with own transaction and use ME9F to process the output in debug. From here (and with the help of your short dump details) you will be able to see the root cause.

[Former Member]

Hi Brock,

When we change the disptach time to 3 and use ME9F to prcoess it, no dump is coming and the output is generated.

I have asked the develoepr to do the same as suggested by you, but of no help.Thanks!

Regards,

Ankit

Message was edited by: Ankit Patodi

[Former Member]

Hi,

You need to debug the smart forum program with help you your  ABAP consultant and check the situation why it is going for DUMP.

There is some statement which is wrong in the program which is causing the issue.

[JL23]

Without telling what information the dump has you can only hope that someone had the same issue. Providing enough info could allow others to step and give you solutions.

If you dont know how to read a dump then read this document first:

[Former Member]

Hi Jurgen,

Sorry for missing out the Dump details earlier.Please find below an extract from the dump:

Category               ABAP Programming Error
Runtime Errors         POSTING_ILLEGAL_STATEMENT
ABAP Program           FRMSCM0012
Application Component  Not assigned
Date and Time          10.06.2014 08:30:46

Error analysis
     There is probably an error in the program
     "FRMSCM0012".
     This program is triggered in the update process. The following ABAP
     statements are illegal here:

     - CALL SCREEN
     - CALL DIALOG
     - CALL TRANSACTION
     - SET SCREEN
     - LEAVE TO LIST-PROCESSING
     - SUBMIT
     - LEAVE SCREEN
     - LEAVE LIST-PROCESSING
     - LEAVE PROGRAM
     - LEAVE TO TRANSACTION
     - MESSAGE I/W/E (if not handeld using EXCEPTIONS ERROR_MESSAGE)
     - MESSAGE A

How to correct the error
     Probably the only way to eliminate the error is to correct the program.
     -
If the error occurs in a non-modfied SAP program, you might be able to
find a solution in the SAP Notes system. If you have access to the SAP
Notes system, check there first using the following keywords:

"POSTING_ILLEGAL_STATEMENT"
"FRMSCM0012" bzw. FRMSCM0012_SF
"SFORM_PRINT_OUTPUT"

Information on where terminated

    The termination occurred in ABAP program "FRMSCM0012", in

     "SFORM_PRINT_OUTPUT". The main program

    was "RSM13000 ".