topic Re: Update problem in BAPI_INSPOPER_RECORDRESULTS in Application Development and Automation Discussions

Update problem in BAPI_INSPOPER_RECORDRESULTS

Former Member — Mon, 21 Jan 2008 13:05:13 GMT

I am using the BAPI_INSPOPER_RECORDRESULTS for recording results for data coming from IDOCs. I am using this BAPI two times for two different materials in a program.

The problem is that while after COMMIT WORK during the second time, it is giving an express message that " Update terminated ".

Please Help

Regards Anuraag

Re: Update problem in BAPI_INSPOPER_RECORDRESULTS

piyush_mathur — Mon, 21 Jan 2008 13:22:05 GMT

Hi Anurag,

Use COMMIT work and WAIT every time.

Thanks

Piyush

Rewards point, if point helpfull

Re: Update problem in BAPI_INSPOPER_RECORDRESULTS

Former Member — Mon, 21 Jan 2008 13:26:04 GMT

I am using the same.

I have tried increasing the WAIT time also but this does not helps.

Re: Update problem in BAPI_INSPOPER_RECORDRESULTS

piyush_mathur — Mon, 21 Jan 2008 13:33:29 GMT

Check the Function Module Documentation:

Sequence for the confirmations

This method can be called up several times for an operation instance. If you switch to another operation instance, the confirmation is considered complete for the previous instance, and no more confirmations can be made for this instance before a COMMIT WORK (BapiService.TransactionCommit).

If an external program wants to make confirmations for several inspection lots and operations, we recommend that these confirmations are sorted according to the inspection lot and operation.

Regards,

Piyush

Re: Update problem in BAPI_INSPOPER_RECORDRESULTS

Former Member — Mon, 21 Jan 2008 13:42:04 GMT

Yes I am doing the same. After recording the results for one time, i COMMIT and WAIT.

My inspection operation number(INSPOPER) is same but the inspection lot number(INSPLOT) and the table CHAR_RESULTS changes.

Re: Update problem in BAPI_INSPOPER_RECORDRESULTS

Former Member — Wed, 23 Jan 2008 15:10:57 GMT

Hi Piyush, Any updates on this issue ?