Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

How receipt layers posted on Microsoft Dynamics GP 9.0 or 10.0 can appear like layers from Microsoft Business Solutions - Great Plains 8.0


Symptoms

You review the receipt records in the Purchase Receipts (IV10200) table and notice that the following fields are not populated on some of your records that you have posted on Microsoft Dynamics GP 9.0 or Microsoft Dynamics GP 10.0:

VCTNMTHD

ADJUNITCOST

QTYONHND

Note The QTYONHND field will only be populated for items with an Average Perpetual valuation method.

↑ Back to the top


Cause

The VCTNMTHD (valuation method), ADJUNITCOST (adjusted unit cost) and QTYONHND (quantity on hand) fields were added to the Inventory Purchase Receipts (IV10200) table on Microsoft Dynamics GP 9.0.  All receipt layers posted on versions earlier than that version would not have these values populated with the exception of 1 layer.

When you convert your data from Release 8.0 to Release 9.0 or 10.0, we will populate these 3 fields on the most recent (by received date), unsold receipt layer.  This is done on a per item basis and we call this 'stamping the record' because the valuation method is now 'stamped' on that receipt. 

This record becomes our starting point so that if you post a transaction whose receipt date is prior to the date of the receipt that the conversion stamped, we will treat that new receipt layer like a receipt that was posted on Release 8.0.  The VCTNMTHD, ADJUNITCOST, and QTYONHND will not be populated.

For example say the conversion process stamped a receipt layer whose date was March 15, 2010.  A receipt transaction dated March 14, 2010 or earlier would be treated like a Release 8.0 layer and would not have the VCTNMTHD, ADJUNITCOST, and QTYONHND fields in the IV10200 populated.  However, a receipt dated March 15, 2010 or later would have those populated. 

↑ Back to the top


Resolution

Backdating receipt transactions is not a recommended business practice.  This is especially true if the date being used comes before the date of the receipt that the conversion stamped.  It is recommended to avoid dating inflows with a date before an existing date in the Inventory  Purchase Receipts (IV10200) table for that item.

↑ Back to the top


More Information

If the VCTNMTHD field is not populated on a receipt line, then when the receipt is sold those sold records (outflows) are not recorded in the Inventory Purchase Receipts Detail (IV10201) table.  Due to this, you will not see information populated in the Purchase Receipts Quantity Sold Details window.  To open the Purchase Receipts Quantity Sold Details window select Inquiry on the menu bar, point to Inventory, and then click Receipts. Once a receipt has been selected in the Purchase Receipts Inquiry window, click on the Quantity Sold field.

The transaction quantity of the new, backdated inflow will still be included in the item's QTYONHND on the appropriate stamped receipt layers.

The Unit Cost of the new, backdated inflow will still be included in the calculation for the item's average cost if this is an item with an Average Perpetual valuation method.

↑ Back to the top


Keywords: kbmbsmigrate, kbmbspartner, vkball, kb

↑ Back to the top

Article Info
Article ID : 2013772
Revision : 1
Created on : 1/8/2017
Published on : 8/21/2012
Exists online : False
Views : 109