Error QP 146 : Inspection Characteristics used several times in operations.

[rajesh_madham]

Question :Soft warning of consistency check turns into hard error when a BDC or lsmw or BAPI is used to upload the data into SAP during insp plan or routing ??

Error QP 146 : Inspection Characteristic used several times in operations.

Abap'ers who are facing similar problem many times can also note this.(many Q&A on this)

Obstruction is due to Task list contains error popup box.

Actual error in log :Inspection Characteristic MIC s used several times in Insp Plan.

Inspection points are not used and task list status must be 4 .(data come from Tibco interface)

How can we solve this ?

[rajesh_madham · Accepted solution]

To Resolve and the solution.

We need to remove the consistency check indicator for Status 4 of task list header of routing or Insp plan.

MIC's repetition is not allowed by default as SAP had willfully kept to avoid duplication.

But this becomes obstruction , if there is a mass upload of data.

we faced this while uploading the data from tibco software interface and this was their fixed requirement to upload 4 status directly and abaper couldnt code for this error.

Initially we thought it was a warning and can be ignored .But it becomes obstruction and hits many times.

We tried group counter 2 and assigning to diff operations but simply customer cant change TIBCO data .

Depends if customer can accept with status 1 also.

Only one check box needs to be removed for conscheck at Tcode op46 and save the TR ( status 4 of tasklist ) and let the other 2 checkbox indicators be present like for release ind and release for costing as the purpose of released status should still be present .

use this as step first "configuration for task list"

and then

run the BDC or run a BAPI which involves insp plan tasklist or routing tasklist with above setting.

Please follow this step to avoid additional coding of saving the data with status 1 and then come back to change the status 4 .

conclusion: Please do the coding part after consulting the functional consultant and do the setting at op46. This will solve the problems of Abapers at this level and need for additional coding at this point will be solved.

[rajesh_madham]

some answers from other questions on same topics.

answer 1

I initial create them with status 1(created) insteat of 4(Released) which allow me to save it.

answer 2

Then Manually I change the status to 4 which is very less manual effort compared to entering the whole data.

ou could use the workbench to change the status, (CWBQM). Might be faster. Changing the status could also probably be done very easily with an LSMW as well.

These are not working in this case