Featured Post

Dynamics GP 2019 is now Released

It is now released, Microsoft Dynamics GP 2019 which moves the system to the modern product life cycle   " Beginning with the October...

Monday, September 14, 2015

The first pair of Dynamics GP Exams has been completed, and more is yet to come


Dynamics GP exams and certification process is seeing the light again with the efforts of the association of Dynamics Professionals, the first pair of exams have been completed by now and further considerable achievement are yet to come with the efforts of such intellectual, valuable and hard-working professionals who are going the extra mile and burning the candle at both ends for the sake of GP Community.


Initially, two exams will be available which are "Core Certificate in Dynamics GP 2015 Installation and Configuration” and “Core Certificate in Dynamics GP 2015 Financials Setup and Functionality". The first offering will be at reIMAGINE 2015 for which details are comprehensively illustrated on Pre Conference Training for reIMAGINE Attendees

  • DYNAMICS GP 2015 CORE FINANCIALS EXAM
    Sunday, September 20 | 3:00 PM - 5:00 PM
    Hilton Garden Inn - Fargo, ND
    Cost: $149*
  • DYNAMICS GP 2015 CORE INSTALLATION & CONFIGURATION EXAM
    Sunday, September 20 | 3:00 PM - 5:00 PM
    Hilton Garden Inn - Fargo, ND
    Cost: $149*
     
There are essential details and further information which can be found on The Exams are Ready article by Briware Solutions Inc. 

Keep in mind that more is yet to come for the GP Exam, stay tuned.

Best Regards,
Mahmoud M. AlSaadi

Sunday, September 13, 2015

Rule of Thumb | Negative Quantity Sold on Item Maintenance


Another common question is brought up by users is related to the item maintenance window, which may displays a negative quantity under the field "Quantity Sold", is this a normal behavior or not ? If so, what's the comprehensive explanation for that. 

Negative Quantity Sold on Item Maintenance Window
Initially, it is quite essential to shed a light on two important definition according to the "language" of Dynamics GP, which is the Quantity Sold in the Purchase Receipt (IV10200) and the Quantity Sold in quantity master or item quantity inquiry (IV00102)

  • Item Quantity Master or Item Quantity Inquiry retrieves data from IV00102, which stores quantities in base unit of measurement, it recalculated associated quantities after every single inventory-related transactions (IV, SOP, POP ...etc). The quantity sold in IV00102 is calculated based on the following equations

    IV00102.Quantity Sold = SOP30300.Quantity Sold - SOP30300.Quantity Returned
  • As for the purchase receipt (IV10200) quantity sold field, it could basically be any "out"  transaction withdrawing from a specific cost layer, such as an adjustment out, POP return, SOP invoice ...etc
In this essence, it is quite logical that it is normal to have a negative quantity sold on the item inquiry window only when Returned Quantities exceeds the Sold Quantities, which results with negative result. 


Example:

Item : 128 SDRam
Transactions:
  • Receiving: 100 piece 
  • Sales Invoice:12
  • Adjustment out: 10 
  • Sales Return: 20
Quantity on hand = 100-22 = 78 (excluding sales returns)
Quantity Sold =  12 - 20 = -8 (negative amount)

Item Quantity Calculations

In this essence, having a negative quantity sold on the item maintenance window is a normal behavior due to a expected calculations. But the question remains, how would you have more returned quantities than sold quantities int he sales module ! That's absolutely represents a logical error.


Note: 
The rule of thumb series is a collection of frequently asked questions either by the community members or clients, the answers to such inquiries have been analyzed and verified by the concerned party. This case is a community thread from 2013 which can be found on this link

Best Regards,
Mahmoud M. AlSaadi

Rule of Thumb | Corrupted Enter/Match Invoice

This would be considered as one of the FAQ's since it is raised up often either by some of the community members or by clients. A glitch in the system occurs rarely and result with having the shipment lost on the enter/match invoice form. 

This case applies to clients using the shipment - enter/match cycle in which two separate documents are entered in order to initially receive goods then invoice, as shown below:

Receiving Transaction Entry - Shipment Type

Now the process shall be proceeded by entering the invoice form the enter/match invoice window (Transactions > Purchasing > Enter/Match Invoice). 
 
Enter/Match Invoice


In very rare cases, while a user is entering the invoice, a glitch occurs for whatever reason, resulting with corrupted records, and eventually you may receive an error (No available QTY to match for this shipment). If you are faced with such a case, here are the rule of thumb to be considered as part of troubleshooting the root causes:

  • First of all, check the PO status. When you open to the Enter/Match invoice window and choose the vendor, the system will accordingly bring all "Active" Purchase Order for this specific vendors. This means, the system will check POP10100 for all active purchase order. To do so, there is a key field "STATGRP" which values are:
    • Voided - 0
    • Active - 1
    • Closed - 2
  • Second of all, there are key fields in POP10500 (receipt line quantity). Once you pick a receipt on the Enter/match invoice, this table get populated with data before posting, which is the reason why any glitch would result with corrupted data in the POP10500 and eventually with the ability to match the invoice to the original shipment. The key fields to check are:
    • QTYSHPPD | Quantity Shipped
    • QTYINVCD | Quantity Invoiced
    • QTYREJ | Quantity Rejected
    • QTYMATCH | Quantity Match
    • QTYRESERVED | Quantity Reserved
    • QTYINVRESERVE | Quantity in Reserve 
    • QTYINVAJ | Quantity Invoice Adjustment 
  • The records in POP10500 are flagged either as posted or saved. Check the "Status" field for this piece of information. So the table is designed to hold both types of data (saved and posted) and always gets populated on the run time while filling on data on the application level.
Best Regards,
Mahmoud M. AlSaadi