Skip to Content

SAP P1B: How to avoid entering inspection results twice

Good day

I have following question regarding transaction QA32. When I book a MIGO I have to enter inspection results like AI content etc. for a batch received from a 3rd party supplier (I copy the data from the COA received from the 3rd party supplier). Without entering the results the batch will not be released. The problem is if I we receive the exact same batch again from the supplier and I do another MIGO, I have to enter the results again. Somehow the inspection results are not saved even though its the exact same lot number. How can I make sure I dont have to enter inspection results over and over again for the exact same batch? How can I make sure I only have to enter the results once and its done?



Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Feb 06, 2017 at 07:13 PM

    Hi Mitch,

    You need to explore user Exits or BAPI at GR (MIGO) or Batch Creation, as you need to update some mandatory values. You may explore the BAPI's - BAPI_MATERIAL_GETBATCHES or BAPI_BATCH_GET_DETAIL. Also please check if the User Exit: MBCFC003 is helping to fix your purpose.



    Add comment
    10|10000 characters needed characters exceeded

  • Feb 07, 2017 at 02:22 PM

    A couple of issues: Do you receive the batch in under the vendor's batch number? i.e use external batch number and allow the user to type in the batch number? This is not common. So I'm guessing no. If you do, then the batch should already be there and you control this with the setting for the 01 inspection type and set that to only create inspection lots once, i.e. control inspection lot is Material/Batch/storage location. Then no lot is created and you don't need to record any results again.

    If you have SAP lots assigned, then your receivers need to search for an exisitng batch number using the vendor batch number. In the batch number field you should be able to use the "Batches for Vendor" match code and search by vendor batch number. If the batch is found, you receive it under that batch. (settings discusssed above could then apply). If no batch is found, you create a new SAP batch and record the vendor batch into the vendor batch number field.

    You could use a MIGO user exit possibly to propose a batch. I.e. once the vendor batch number field is populated, you click on "CHECK" in MIGO and an exit searches for a batch in your system with the same vendor batch number. Again, if none found, they would record the vendor batch number in the vendor batch field and get a new SAP batch number assigned.

    Another option is that when the lot is created you check the vendor batch number and search for any previously received batches with the same vendor batch number. If one is found, put a comment in the inspection text of the lot. Then when someone goes in to record results they can see this and use the "Copy results" functionality to copy the resutls from a previous inspection lot. The analyst can compare the copied resutls to the newer COA to make sure they match. Save the results and make the UD.

    Add comment
    10|10000 characters needed characters exceeded

    • Yes, when you have Control insLot set up to material document is means each purchase order receipt generates an inspection lot. With "material, batch and storage location" you only get and inspection lot for the first GR of that batch. (unless it fails, then you keep getting them until one passes).

      The key is that this is based on SAP batch number, NOT the vendor batch number field. It would only work if you type in the vendor batch as the SAP batch number. This often doesn't work as many vendors have batch numbers that exceed the 8(10?) characters allowed by SAP. So it then that you have to be able to search by vendor batch number and log in the reciept using the SAP batch number used previously.

      And yes, if you do this, the results don't have to be put in again.


      PS> please respond to answers as a comment and not another "Answer".