cancel
Showing results for 
Search instead for 
Did you mean: 

QM - Characteristic with confirmation number xxxxxxxx is already blocked??

Former Member
0 Kudos

Hello QM experts,

I have a working interface between our LIMS solution and SAP via QM-IDI.

This week, one of our customer did a MB1B transaction (which triggered a new inspection lot) on a batch that had already another inspection lot (generated by the CORK transaction I believe).

Anyway, we ended up with 2 inspection lots on the same batch; which in principle is fine.

The 1st one went through the LIMS life cycle, and we sent the results back to SAP, and it worked fine.

The 2nd one went through the LIMS life cycle, and we sent the results back to SAP, and we received the "Characteristic with confirmation number xxxxxxxx is already blocked". We looked into SAP, and it was NOT the case; we were able to enter results manually.

Is there anyway to "override" a locked characteristic, or to somehow address this issue?

Thanks,

Michel

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Hello Michel,

May the following can help:

The code for this particular error message is: QI104.

This kind of error can happen when you mass process the data by the BAPI. In more detail, the next records tries to update the same object though the previous one have not finished, so the lock error can happen.

Here is some suggestions.

You may call the function ENQUEUE_EQQAMV1 to check if the lock is released, then only execute the transfer when the lock is released. Or insert the ABAP statement WAIT UP TO n SECONDS before transfering the next records, this will wait n seconds (e.g. 5 seconds) before executing the following statements.

Please contact your ABAP colleague, they should be aware of them.

Thank you.