PO Express document "Update was terminated" received from author

[gevanj]

hi all,

i create a stock transfer po, when i save the po (me21) it successfully save & generate the number. but when i click back button

i got popup ( expression Information) & say Express document "Update was terminated" received from author XXX ,

when i go to inbox then double click the record i can see

this details

Update was terminated

System ID....   LED
Client.......   180
User.....   LBPUIT01
Transaction..   ME21N
Update key...   5......
Generated....   10.07.2014, 13:19:41
Completed....   10.07.2014, 13:19:41
Error Info...   PO is not relased!
                                                        

then i go to sm13

fill the my details and get the error

Function Module        RV_MESSAGE_UPDATE

Status                 Update was terminated

Report

Row

Error details   Class:     00         Number:    398

PO is not relased!

Please help me to solve this issue

[FredericGirod]

Hi,

first check in ST22 if you have a dump

and if not, you could try to check in SM13, you must have a line in red, if you double click you will have the detail of the function call. Sometimes you could reprocess the error and try to debug it

regards

Fred

[former_member184504]

These are background dumps. Got to SM13 and see where the update of record is getting failed.

[gevanj]

hey. please read my issue i already mention sm13

then i go to sm13

fill the my details and get the error

Function Module        RV_MESSAGE_UPDATE

Status                 Update was terminated

Report

Row

Error details   Class:     00         Number:    398

PO is not relased!

[FredericGirod]

Did you go in the detail ? in the log error ?

[gevanj]

Function Module       RV_MESSAGE_UPDATE

Status                 Update was terminated

Report

Row

Error details   Class:     00         Number:    398

PO is not relased!

[raymond_giuseppi]

Look thru SM13. Usually RV_MESSAGE_UPDATE is relative to message with customer developed print forms that raise an error in update task ...

Regards,

Raymond

PS: Read note 111062 - Printing problems in Materials Management "The problem is caused by an error in the R/3 System or by an error due to a customer modification."

[kiran_k8]

Gevan,

There are options to debug from SM13.Exploring that option will give you a lead.

K.Kiran.

[gevanj]

i already done. but couldn't trigger the error.

it has lot of codes to debug

[raymond_giuseppi]

Either

• From SM13 debug the FM,
• Or start debug in main transaction and activate update debug (Menu : Settings, Display/Change Debugger Settings, check Update debugging)

You could set a watchpoint on statements like MESSAGE or RAISE.

Regards,

Raymond

[krish469]

HI jeevan,

                Not a solution but a hunch from my end. Check whether Form ( script/Smartform/SFP) is attached to the automatic message type that triggered to PO yiu have created.

                       Else look for message via update debugging option as suggested by Kiran.

Regards,

Siva

[gevanj]

after the save complete i enable the debugger via "/h"

then also error was triggered

[krish469]

You need to activate Update debugger , as   RV_MESSAGE_UPDATE is an Update FM.

[gevanj]

hey can u please explain me the steps, plzzz

[krish469]

->When debugger is activated -> Go to Setting to change debugging settings

->Check the Update Debugging option and save the settings.

[naveenvishal]

Please check whether a workflow is attached on the execution of the t-code.

We have seen the cases where a failed workflow(erroneous workflow) has triggered the same message giving no clue for it.

You can do one thing, check for any workflow attachment (may be through it's Business Object to Workflow Assignment, tcode SWETYPV) and deactivate the same.

You can also confirm the same by stopping all workflows in the system for some time and execute the transaction to check.

[Former Member]

Hi

The message 398 of class 00 is very generic message, I suppose is triggered in a custom development.

RV_MESSAGE_UPDATE is the function module to update the message for the print, so probably the setting of your system is to print the PO while creating.

Check where that message is caleed in the print program (you can find it by nace transaction)

Max