web
You’re offline. This is a read only version of the page.
close
Skip to main content
Community site session details

Community site session details

Session Id :
Dynamics 365 Community / Blogs / Dynamics GP Support and Services Blog / Microsoft Dynamics GP Alloc...

Microsoft Dynamics GP Allocations discrepancies

Views (77)
AE-02051958-0 Profile Picture AE-02051958-0
Hi Everyone,
 
We receive a fair amount of questions regarding allocation discrepancies, so I wanted to share my process on how to identify and potentially solve allocation differences. 
 
Allocations are just a way for GP to “hold” quantities to be used for specific documents.  Think of it as an item in stock being saved and set aside to be given to a specific customer sale or used in building a specific product. 
Some ways to allocate: (Think of it as quantities/items that will remove from inventory when posted)
  1. Inventory Decrease adjustments.
  2. SOP/Invoicing invoices
  3. Bill of materials/MFG
    1. Components that will be used to build the good
    2. Finished goods that are used in other finished goods (aka subassemblies)
  4. Purchase order returns
  5. Field service parts to be used.
  6. Project transfers
  7. Intransit transfers to via Site

GP updates the IV00102 summary table with items allocation amount from all unposted documents.  This matches what you see in Item Quantity Maintenance window (or Item Inquiry). When you zoom back on allocation to see the details, that looks at the work records saved throughout GP tables.
 
 


The calls we receive are when there is a discrepancy between the Allocated value in Item Quantities Maintenance window and the Item Allocation Inquiry window.
 
 

The calls we receive typically report that the allocation window shows one value, but when they zoom in to look at the transactions that allocate, the totals doesn’t match.   The other scenario we hear about is that the allocation is negative in the Item Quantity Maintenance.   Note we have had 2 bugs in the past that cause this scenario.  
 
  • MFG quality assurance (QA)– Has to do with returning items. Currently outstanding quality issue, but it takes very specific steps to create this issue so it should be rare that this occurs. 
  • SOP ship to address rolldown – very specific steps to recreate it - This is fixed in GP 2018 R2 released 10/1/2018.
 
If the two windows above match, but the Bin quantity inquiry window does not match from an allocation standpoint, it could be that you are using Separate fulfillment process in Sales Order Processing, and you just haven't selected the bin yet.  That is by design. So don't be concerned if the bin windows show a different number for allocations if you use Separate fulfillment method. 

ACTIONS FOR THESE CASES:
  1. The first line of defense is running IV reconcile.  That process typically resolved the majority of the allocation issues.   Inventory >> Utilities >> Reconcile.
 
  1. If reconcile does not fix the issue, the second step is to run the ALL-allocation script.  This will look at all worktables that could potentially have an allocation.  You use these results to compare the transactions shown in the Item Allocation Inquiry window to the script results.  
 

All allocation script
** Allocated Quantities with FS-PA-MFG-PO Returns (2) table information, including:
**                                                            
**        SOP10200 - Sales Transaction Amounts Work                                                
**        POP10500 - Purchasing Receipt Line Quantities                                                
**        POP10310 - Purchasing Receipt Line                
**        IV10001 - Inventory Transaction Amounts Work                
**        IVC10101 - Invoicing Transaction Amounts Work
**        BM10300 - Assembly Component
**        SVC00203 - Service Call Line Detail                                                
**        SVC30702 - Service Transfer Line Detail
**        SVC05601 - SVC_RTV_Line
**        SVC06101 - Depot Master Line
**        PA10901 - PA Inventory Transfer Work Detail
**        MOP1400 - MOP_Picklist_Site_QTYS
 
Typically, those documents found in BOTH the script results and in Item Allocation Inquiry are fine.  Ignore those for now.   It’s the documents that you find in the ALL-Allocation script and NOT listed in the Item Allocation Inquiry that you want to investigate. For those discrepancy documents use the other scripts we have to review the data to see what the issue might be with the data. (aka ALL SO or ALL PO for example) More than likely there is damage to the record, and it needs to be cleaned up.  For example, I've seen cases where the line information for the item is in the SOP10200, but the SOP header is missing in the SOP10100 which is why GP is allocating the quantity, but because the header is missing it's why you are unable to see it in the Item Allocation Inquiry window when you zoom. These discrepancies are typically caused by some type of posting interruption.  To investigate you would reach out to your Microsoft Partner or Microsoft to investigate.    After cleaning up data with SQL always reconcile and then check to see if the windows match.
 
Note: Not all fields say “ATYALLOC” in the backend.  We have fields called Pending, ATYALLOC, Committed, Reserved.  It just depends on the type of transaction that is unposted.  
Note:  Some fields on the window show in base quantities while the All-allocation script results currently show in the U of M used on the transaction.  So, there may be a quantity difference, but it is correct, just displays differently in the script results.  So just be aware that the quantities may not be exactly what you see between the script results and the inquiry.  That threw me off a few times.
 
I hope this article helps you understand a little more about allocations and some steps to identify where the issue might be coming from and how to go about resolving it.  
 
Warmest Regards,
Angela Ebensteiner | Sr. Technical Advisor | Microsoft Dynamics GP

Comments