Symptoms
When Manufacturing is loaded in Microsoft Dynamics GP 10.0 Service Pack 2 or in Microsoft Dynamics GP 10.0 Service Pack 3, you may notice that purchase receipts are processed incorrectly. You may experience the following problems.
Problem 1
You enabled the auto-receive setting. When the POP Shipment Receipt form automatically receives a shipment receipt line, the line cannot be added.
This problem occurs if the shipment receipt line has an item that is bin-tracked, lot-tracked, and QA-tracked.
Problem 2
Consider the following scenario.
-
A material cost is posted to a POP Shipment Receipt.
-
A standard cost item uses cost buckets.
In this scenario, multiple inventory accounts are not affected as expected.
Problem 3
When a POP Shipment Receipt is posted from a batch job, outsourcing cost does not appear in the MO Activity or Order Variance window. To avoid these problems, you can log on to the Fabrikam company, and then move to the live company in Microsoft Dynamics GP.
Resolution
Service pack information
To resolve this problem, obtain the latest service pack for Microsoft Dynamics GP 10.0. For more information, visit one of the following Microsoft Web sites, depending on whether you are a partner or a customer.
Partners
https://mbs.microsoft.com/partnersource/products/GreatPlains/downloads/servicepackCustomers
https://mbs.microsoft.com/customersource/support/downloads/servicepacks
Hotfix information
A supported hotfix is now available from Microsoft. The hotfix corrects the problem that is described in this article. Apply the hotfix only to systems that are experiencing this specific problem.
To resolve this problem immediately, contact Technical Support for Microsoft Dynamics and related products to obtain the hotfix. You can log on to the Microsoft Dynamics site and create a new support request. To do this, visit the following Microsoft Web site:
https://mbs.microsoft.com/support/newstart.aspx You can also contact Technical Support for Microsoft Dynamics and related products by telephone at (888) 477-7877.
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Technical Support Professional for Microsoft Dynamics and related products determines that a specific update will resolve your problem. The usual support costs will apply to any additional support questions and issues that do not qualify for the specific update in question.
Notes
-
If you visit the Microsoft Dynamics site, select Purchase Order Processing as the subcategory.
-
If you contact Technical Support for Microsoft Dynamics by telephone, use an appropriate Quick Access code.
Prerequisites
You must have Microsoft Dynamics GP 10.0 SP3 installed to apply this hotfix. The Microsoft Dynamics GP build must be 10.00.1193, and the Manufacturing build must be 10.0.1170.
Removal information
You cannot remove this hotfix.
Restart requirement
You must restart Microsoft Dynamics GP 10.0 after you apply this hotfix.
File information
The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Iconmfg.cnk |
Not applicable |
21,968,802 |
10-Dec-2008 |
03:14 |
Not applicable |
Installation information
To install this hotfix, follow these steps:
-
Extract the hotfix to a temporary directory.
-
Copy the chunk (.cnk) file to the Microsoft Dynamics GP 10.0 application folder.
Note By default, the Microsoft Dynamics GP 10.0 application folder is the following folder:C:/Program Files/Microsoft Dynamics/GP
-
Start Microsoft Dynamics GP 10.0.
-
Click Yes when you are prompted to include new code.
-
Repeat steps 2 through 4 for each additional computer where Microsoft Dynamics GP is installed.
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
