RAPID PUBLISHINGRAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION THAT IS CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED TO SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.
If you enter an amount in the Counted Qty field that differs from the captured quantity for an item-site combination, the Inventory module calculates the default variance amount as the absolute difference between the two values, as long as the resulting default variance transaction is a valid transaction. The default variance transaction might vary if it would otherwise cause an invalid transaction. That is, if posting the transaction would cause the on hand quantity to be less than the allocated quantity.
When a stock count is processed, the Inventory module creates default inventory variance transactions to adjust inventory for the variance amounts. This is helpful if the variance is a legitimate finding of differences between the captured and counted amounts. However, if a variance exists because of transactions that have not been posted yet, or because transactions were posted after the stock count was started, then the default inventory variance transactions can cause additional discrepancies. We do not recommend posting additional transactions unless the stock count entry has already been posted.
The ability to restrict users from allocating and posting transactions for the stock count items by tracing the items in the stock count and by restricting the users from allocating or posting to this Item/Site combination is not a feature that is available in Microsoft Dynamics GP. Therefore, every time that a variance amount is identified, you should check the unposted transactions and the transaction history for the item-site combination. If it is necessary, you can adjust the variance amount accordingly before processing the stock count.
If transactions are posted after the stock count is started, the On Hand Quantity field in the Stock Count Entry window will no longer equal the captured quantity. You may have to adjust the variance amount accordingly based on this field. In this case, use the Item Transaction Inquiry by Date window to view transaction history. You could find that another user has posted a transaction since the stock count was started, for example. Additionally, you can use the Unposted Item Transactions window to view unposted inventory transactions.
To verify variance amounts in the Inventory module, follow these steps:
- Open the Stock Count Entry window. To do this, click Transactions, point to Inventory and then click Stock Count Entry.
- Type a stock count ID. The stock count must have a status of Entered.
- Select an item-site combination that has a variance amount.
- Click Unposted Trx and Trx History to determine the reason for the inventory variance. To view information about the quantities for specific transactions, select a document and then click Document Number.
- If you find an unposted transaction or a transaction in inventory history that accounts for all or a part of the variance, select the variance amount for the item-site combination and change it as needed.
- Click Save, and then close the window
DISCLAIMERMICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, THE RELIABILITY OR THE ACCURACY OF THE INFORMATION THAT IS CONTAINED IN THE DOCUMENTS AND THE RELATED GRAPHICS PUBLISHED ON THIS WEB SITE (THE “MATERIALS”) FOR ANY PURPOSE.
THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON-INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.
Article ID: 950020 - Last Review: Mar 29, 2017 - Revision: 3