Skip to Content
author's profile photo Former Member
Former Member

PM order print problem - Update terminated Urgent

Hi,

I am trying to print PM work order with tcode IW32 but when i print it

says Order 5000012 saved with notification 30000012.

But as soon as i do any other function it gives msg "Express document

"Update was terminated" received from author...etc"

Thanks in advance,

Prabaharan.G

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

9 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Oct 03, 2007 at 07:32 PM

    Hi Rob,

    I checked in SM13 and the error corresponds to a standard function module PM_PRINT_ORDER_CONTROL. Double clicking on the error line shows a pop up with the below details,

    Report: LSPO1U06

    Line: 194

    Error Details: 00 671: ABAP/4 processor: POSTING_ILLEGAL_STATEMENT.

    What information is it actually revealing.

    Sampath,

    As said above it goes into a standard print function module and gives an error , no custom code has been written in it.

    Regards,

    Prabaharan.G

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Oct 03, 2007 at 09:58 PM

    Hi Rob,

    Please find the source code extract, as in the dump. I think we are almost close to the solution . Please advise. Thanks for your help till now.

    Line SourceCode

    164 CHANGING button_3.

    165 ENDIF.

    166

    167 IF icon_button_4 NE space.

    168 PERFORM append_icon_to_button

    169 USING icon_button_4

    170 space "*048i

    171 CHANGING button_4.

    172 ENDIF.

    173

    174

    175 * Aufbereitung des Fragetextes und Berechnung der Dynprogröße

    176 PERFORM format_text TABLES text_tab1

    177 USING fragetext.

    178

    179 PERFORM calculate_screen_size

    180 USING

    181 textlength

    182 start_spalte

    183 start_zeile

    184 CHANGING

    185 tab_len1

    186 tab_len2

    187 end_spalte

    188 end_zeile

    189 dynpro_nummer.

    190

    191

    192 * Aufruf der Dialog-Dynpros

    193

    >>>>> CALL SCREEN dynpro_nummer STARTING AT start_spalte start_zeile

    195 ENDING AT end_spalte end_zeile.

    Regards,

    Prabaharan.G

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Oct 03, 2007 at 07:14 PM

    check failed updates with transaction SM13. Also ST22.

    Rob

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Oct 03, 2007 at 07:26 PM

    Hi Prabaharan,

    After save, will it process any custom developed code(User exits or Badi). If so check the code, there should not be any messages. Because, wheneve u hit save on a standard transactions, it should should run the update process on Background workprocesser, not on fore ground.

    If there is any 'I' message or any popup dialog in Custom developed code would leads to this short dump.

    reward points.

    Thanks,

    Sampath.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Oct 03, 2007 at 08:17 PM

    Hi Rob,

    I checked the error logs in SM13 and found the below,

    Please advise on the below. Is it now mandatory to apply an OSS note for this.

    Error analysis

    There is probably an error in the program

    "SAPLSPO1".

    This program is triggered in the update task. There, the

    following ABAP/4 statements are not allowed:

    - CALL SCREEN

    - CALL DIALOG

    - CALL TRANSACTION

    - SUBMIT

    Information on where terminated

    The termination occurred in the ABAP program "SAPLSPO1" in "POPUP_TO_CONFIRM".

    The main program was "RSM13000 ".

    The termination occurred in line 194 of the source code of the (Include)

    program "LSPO1U06"

    of the source code of program "LSPO1U06" (when calling the editor 1940).

    The program "SAPLSPO1" was started in the update system.

    How to correct the error

    Probably the only way to eliminate the error is to correct the program.

    -

    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:

    -


    "POSTING_ILLEGAL_STATEMENT" C

    "SAPLSPO1" or "LSPO1U06"

    "POPUP_TO_CONFIRM"

    Regards,

    Prabaharan.G

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Oct 03, 2007 at 08:28 PM

    Yes you are right , but what is the configuration to be checked. Can you please let me know.

    Regards,

    Prabaharan.G

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Oct 03, 2007 at 09:30 PM

    Hi Rob,

    If the error description shows duplicate entries then we could change the number range and try again , but now seeing the dump it clearly says that the update terminated statement was because of a " call XXX " statement within a program called as an Update task. Is there any solution for this, because all the above are happening inside standard Program. Could you please clarify.

    Regards,

    Prabaharan.G

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      the dump will give a code extract that shows the statment that caused the error. Can you post that code extract?

      But it's going to turn out to be either:

      i) config

      ii) OSS note issue

      iii) OSS message

      Rob

  • author's profile photo Former Member
    Former Member
    Posted on Oct 03, 2007 at 09:49 PM

    Hi Rob,

    Please find below the code extract,

    The termination occurred in the ABAP program "SAPLSPO1" in "POPUP_TO_CONFIRM". Line number is 194 that is the below statement.

    *Aufruf der Dialog-Dynpros

    CALL SCREEN dynpro_nummer STARTING AT start_spalte start_zeile

    ENDING AT end_spalte end_zeile.

    The error description explains as below,

    This program is triggered in the update task. There, the

    following ABAP/4 statements are not allowed:

    - CALL SCREEN

    - CALL DIALOG

    - CALL TRANSACTION

    - SUBMIT

    Regards,

    Prabaharan.G

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Nov 02, 2007 at 04:12 PM

    Problem solved after removing customized POP UP call in the program

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      Hi Christine,

      In our case we had an user exit where we wrote custom code to call a pop up and when the order is saved in the update task we should not call any customized pop up and hence the error came.Please check the user exits, BADI's which are coded in relation to order save.

      Regards,

      Prabaharan.G

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.