01-13-2014 12:24 PM
Hello All,
When we are using Tcode: ME28 to Releases Purchasing Documents we got Error Message " Express document "Update was terminated" received from author "xxxxx"." for ONE Purchasing Document.
Remaining Purchasing Documents got Released successfully.
And we tried to re-execute the Purchasing Document(Error One) using Tcode: ME28, But still we are getting same Error Message.
I have checked Tcodes : SM13, SM21, ST22 . But I didn't find any Proper Reason why This Error is Triggering.
In Tcode: SM13 ..
It showing Error at Function Module 'RV_MESSAGE_UPDATE'.
When I go to DETAILS it is showing as:
=============================================
Function Module: RV_MESSAGE_UPDATE
Status: Update was terminated
Report:
Row:
Error details Class: ME Number: 000
*** General system messages ****
=============================================
In Tcode:SM21..
===================================================================================
Update terminated
Details:
Recording at local and central time........................
Task...... Process User...... Terminal Session TCode Program Cl Problem cl Package
26178 Dialog work process No. 026 1 K SAP Web AS Problem STSK
Further details for this message type
Module nam Line Error text Caller.... Reason/cal
thxxhead 6835 9 ThRecei vb erro
Documentation for system log message R6 5 :
An update request was terminated. You can use transaction SM13 to find
the reason.
Technical details
File Offset RecFm System log type Grp N variable message data
2392 180160 m Error (Function,Module,Row) R6 5 9 xxxxxxxxxxxxxxxxxxxxx
=====================================================================================
And I did Debugging to find the Route Cause for this ISSUE.
I found This Error Message is Triggering After COMMIT WORK Statement.
I WANT TO TELL THAT THIS KIND OF ERROR MESSAGE ARE TRIGGERING OCCUPATIONALLY IN LAST 3 to 4 MONTHS THIS IS FIFTH TIME.
Can anyone Please tell me what is the reason and how to resolve this issue.
Thanks and Regards,
Venkat
01-13-2014 12:56 PM
Hi Ram
can you please give screen shot of the update error details from SM13 ?
Also can you confirm that it is happening only for certain PO and not for all. Then it might be related to some Functional issue pertaining to the specific PO.
Thanks
Rishi
01-13-2014 2:52 PM
Hi Rishi,
Thanks for your update.
In Tcode: SM13 there is nothing much..
It showing Error at Function Module 'RV_MESSAGE_UPDATE'.
When I go to DETAILS it is showing as:
=============================================
Function Module: RV_MESSAGE_UPDATE
Status: Update was terminated
Report:
Row:
Error details Class: ME Number: 000
*** General system messages ****
=============================================
When we execute Tcode: ME28 there three levels(01,02,03) to release a PO for Approval.
First 2 working fine(01,02), but when they executed with Release-03 this Error message is triggering.
Changes for PO is updating properly in table EKKO i checked in debugging.
But when Commit Work is triggered this Error is coming.
Regards,
VenkatRam
01-13-2014 12:57 PM
Hi,
have you checked all SAP notes for RV_MESSAGE_UPDATE like
http://service.sap.com/sap/support/notes/1961083
Regards,
Klaus
01-15-2014 6:59 AM
Hi Klaus,
Thanks for your response.
I have check the SAP note which you have given
http://service.sap.com/sap/support/notes/1961083
But it is related to ME22 or ME22N.
Here we are able to save changes for PO through ME22N, but when we are Releasing the PO for approval thorough Tcode: ME28 . we are getting this error.
So, kindly let me know if you have any idea to resolve this..
thanks and regards,
VenkatRam
01-15-2014 8:56 AM
Hi,
SAP note 1961083 is related to ME22 and ME22N, but those are PO update transactions, and your error occurs in another PO update transaction. Maybe It's not related to ME28, because nobody contacted SAP with an issue for that transaction yet. I wouldn't exclude this note from solving a ME28 issue, too. And SAP describes this issue to be caused by many different reasons with remark etc. . Either they don't know all possible actions or they are too much to tell.
You should read that note to find out, if you can give it a try.
But I also recommend to search and check all SAP notes concerning RV_MESSAGE_UPDATE to you. Maybe there might be a better one for you.
Good luck!
Klaus
01-15-2014 9:59 AM
Hi,
Thanks Klaus..
There was some upgrade was happened on 08/2013 for this system.
When i was debugging ME28 transaction , I found that in Include Program 'FM06LFFR_FRG_UPDATE_FB' there was some code change.
Under :
PERFORM BELEG_BUCHEN USING *EKKO EKKO.
New code is added as below..
*{ INSERT
commit work and wait.
*} INSERT
I think because of this its not working consistently this is my guess.
Its working fine for all the Pos but for few POs this kind of error is Triggering.
From last 4 months this is 5th time this error is coming
So, kindly check it and confirm on this.
Thanks and Regards,
VenkatRam.
01-15-2014 10:09 AM
Hi Venkat
In my system we have commit at below mentioned place not inside loop you have it inside loop? Where do you have commit inside or outside loop? Was this statement entered using access key...?
*- Änderungerungsbelege verbuchen -------------------------------------*
EKKO = XEKKO.
PERFORM BELEG_BUCHEN USING *EKKO EKKO.
ENDIF.
ENDLOOP.
*- Änderungen sichern -------------------------------------------------*
READ TABLE XEKKO INDEX 1.
IF SY-SUBRC EQ 0.
*- Bestellköpfe verbuchen ---------------------------------------------*
COMMIT WORK.
ENDIF.
MESSAGE S177.
Thanks
Nabheet
01-15-2014 10:20 AM
Hi Nabheet,
Commit Work statement is not commented.
there was new statement is added..
EKKO = XEKKO.
PERFORM BELEG_BUCHEN USING *EKKO EKKO.
*{ INSERT
commit work and wait.
*} INSERT
ENDIF.
ENDLOOP.
*- Änderungen sichern -------------------------------------------------*
READ TABLE XEKKO INDEX 1.
IF SY-SUBRC EQ 0.
*- Bestellköpfe verbuchen ---------------------------------------------*
COMMIT WORK.
ENDIF.
MESSAGE S177.
Thanks and Regards,
VenkatRam
01-15-2014 10:23 AM
Can you please comare the version of this include under utilities to see who changed it?
Nabheet
01-15-2014 11:45 AM
Yes i have check this same code is been using from long Time..
After Upgrade(08/2013) this issues are coming.
I'm not sure were it is going Wrong..
Regards,
VenkatRam.