cancel
Showing results for 
Search instead for 
Did you mean: 

GR is not getting saved in database

Former Member
0 Kudos

Hi Experts,

User is doing GR for PO. GR is posted and document no is genrated. But Later that document is not present in database.

Checked in SM13- Update is terminated ( RV_MESSAGE_UPDATE ). Set up a live meeting with user gave her control of our system and then she was able to post with out any problem. Also user is able to post GR againest a few normal POs and all Asset POs in her system.

Please help me with this

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

thanks for the reply.

This is not a one time issue as there are more then 10 update termination for 4-5 pos. and also in between she successfully posted GR for 1 normal po and 2 asset pos in a duration of 15 days.

Also we got the error class as

Error details Class: FPRUNX  number: 102 no job started

Report: SAPLMIGO

also this is all standard code no enhancement is implemented for this posting so abaper saying that its very difficult to find out the problem through debugging.

JL23
Active Contributor
0 Kudos

This error is mostlikely caused by print program and form

do you use a customized form or print program? Or a country specific solution?

the FPRUNX 102 error is issued from program LFPCOMPCHK

Further see what SAP writes in Note 111062 - Printing problems in Materials Management

Former Member
0 Kudos

maybe it's the ADSUSER issue, check this:

http://scn.sap.com/message/8210637

Former Member
0 Kudos

Yes we do use a customized print program but its not country specific. I also suspect that this may be a print setting related problem but i dont know how to proceed and what to suggest user.

Former Member
0 Kudos

yes this might be an ADS related issue and sap suggested note 944221. but the problem is that user would not be able to perform the ADS check on her system and we cant physicaly reach user.

Also this may not be only limited to only ADSUser setting but also complete ADS.

JL23
Active Contributor
0 Kudos

it is certainly nothing what the enduser can solve or do differently to get around this issue, it is an IT issue.

if it is ralated to the form or print program, then your programmer should be able to debug the case.

if it is related to password used for ADS user, then contact your basis team

Former Member
0 Kudos

Well, at least there should be a BASIS team supporting enduser's SAP no? They should help in this case to check ADS first and rule out the cause or, fix it. Good luck!

Former Member
0 Kudos

Maybe there is duplicated document or number range issue, get ABAP help to dig deeper.

There are a few reasons why an update is terminated, go to transaction SM13, enter the date and user ID and find user's transaction that was terminated. Drill-down until you find which function (line) caused the termination and double click. That should help you determine why the update is failed.

Former Member
0 Kudos

Set up a live meeting with user gave her control of our system and then she was able to post with out any problem

On looking this sentence, it seems that problem is with user's system. But later as you said that she is able to post the GR for other POs.

So it seems as one time system issue. Some times system behaves abnormally.

To confirm it, try to post the GR for a PO(with same entries) in her system. (Better try in quality/test system)