1. This issue is generally caused by a failed MO receipt. Follow the below script to correct the failed receipt:https://community.dynamics.com/gp/b/dynamicsgp/posts/how-to-troubleshoot-a-failed-mo-receipt
  2. If there is not a failed MO receipt, there may be hung records from an MO receipt that was entered but not posted. Run the below scripts.

    select * from MOP1020 where MANUFACTUREORDER_I='enter your MO'

    select * from WO010302 where MANUFACTUREORDER_I='enter your MO'

    select * from WO010515 where MANUFACTUREORDER_I='enter your MO'
  3. The MOP1020 is the MOP_Pending_Serial_Lot table. It will hold records for all serial and lot numbers that are being used on Manufacturing documents that are not posted. This includes unposted MO receipts and unposted pick document. If an MO receipt is being entered there will be records in this table. If you escape out of the MO Receipt window instead of posting the receipt, it can leave stranded records in this table. Check the DOCNUMBR column for the record.

    If the document is for an invalid MO Receipt, run the below script to delete the records.

    delete MOP1020 where DEX_ROW_ID='enter the dex_row_id of the line'

     If the document is an unposted pick document, post the pick document or delete the lines off the pick document within GP.

  4. The WO010302 is the MOP_Lot_Issue table. It will hold a record for each lot number that has been issued to an MO that is not closed. The lot numbers must be in the table to appear in the MO Entry window. The SERLTQTY column will contain the quantity issued for that lot number. There are 3 columns (QTYCONSUMED, QTYPENDING, ATYALLOC) that can impact how many of the SERLTQTY are available to be used on the MO Receipt. The QTYCONSUMED contains the number of items that have been previously used on other MO receipts, the QTYPENDING contains the number of items that are on receipts or reverse issue pick document, the ATYALLOC contains values that are being used by Mo Receipts that are currently in the MO Receipt Entry window but have not been posted.

    The quantity available in the MO Receipt Entry window to select will be:

    SERLTQTY- (QTYCONSUMED- QTYPENDING- ATYALLOC) = Quantity available

  5. The WO010515 is the MOP_Serial_Issue table. It will hold a record for each serial number that has been issued to an MO that is not closed. The serial numbers must be in the table to appear in the MO Entry window. The SERLTQTY column will contain the quantity issued for that serial number. There are 3 columns (QTYCONSUMED, QTYPENDING, ATYALLOC) that can impact how many of the SERLTQTY are available to be used on the MO Receipt. The QTYCONSUMED contains the number of items that have been previously used on other MO receipts, the QTYPENDING contains the number of items that are on receipts or reverse issue pick document, the ATYALLOC contains values that are being used by Mo Receipts that are currently in the MO Receipt Entry window but have not been posted.

    The quantity available in the MO Receipt Entry window to select will be:

    SERLTQTY- (QTYCONSUMED- QTYPENDING- ATYALLOC) = Quantity available

  6. To correct:

    Run the below script to remove any stranded records from the MOP1020.

    delete MOP1020 where MANUFACTUREORDER_I='enter your MO'

    Establish how many component quantities have already been consumed. If this script returns results, you will need to determine the quantity consumed of each item using the second script.

    select sum(QTYRECVD) from MOP1100 where MANUFACTUREORDER_I='Enter the MO' 

    select QTYSOLD, ITEMNMBR, * from MOP1000 where MANUFACTUREORDER_I='Enter the MO'  
  7. Run the below script to update the serial or lot lines so that they can be consumed on the MO receipt.

    If there were results in step 2, calculate what has been consumed and run the below scripts.

    update WO010302 set QTYCONSUMED='enter the quantity consumed', QTYPENDING=0, ATYALLOC=0 where DEX_ROW_ID='enter your dex_row_id'

    If you are using serialized item, replace the WO010302 table in the above script with the wo010515 table.

    If there were no quantities consumed, enter 0 in the qtyconsumed columns in the above scripts.
  8. If this does not correct the issue, contact the support desk.