Issues that are fixed in this hotfix rollup
This hotfix rollup fixes the following issues that were not previously documented in the Microsoft Knowledge Base:
Issue 1
Assume that you post an item arrival journal. However, you cannot post a packing slip if multiple batch numbers are received for the same purchase order line.
Objects that are affected
- Data Dictionary\Tables\InventBatch
Issue 2
Assume that you create a purchase order for an item. You enter a vendor batch number on the
Line details tab when you post a packing slip. In this situation, the vendor batch number is not updated on the created batch number.
Objects that are affected
- \Data Dictionary\Tables\InventBatch\initFromInventMovement
Issue 3
Assume that a new material that was issued resides on the same bill of material (BOM) level as the finished co-product item. When you perform an inventory closing, you receive the following error message if there was an adjustment to the cost price of the material:
You can't have unallocated cost on a planning item.
This problem occurs because the closing incorrectly ignores some co-product items and by- product items that are closed during the current closing.
Objects that are affected
- \Classes\InventCostItemDim
Issue 4
If the report as finished (RAF) for the item and for the co-product or by-product have different dates, the status of a batch order does not update unexpectedly.
Objects that are affected
- \Classes\ProdJournalCheckPostProd
Issue 5
Assume that you have a catch-weight enabled item in a batch order. The item is picked partly. When you run the Materials Requirement Planning (MRP) process for the item, the process enters an endless loop because the process tries to create a planned order for the catch-weight item.
Objects that are affected
- \Classes\PdsCatchWeight
- \Classes\ReqCalc
Issue 6
If you change the explosion principle to
Up in the
Explosion dialog box for a planned order (the ReqTransExplosion form), the higher level consumption is not displayed.
Objects that are affected
Issue 7
Consider the following scenario:
- You create a rework order for an ended batch order.
- You run the RAF process for the rework order.
- You create a sales order for the formula item and reserve the batch that is created from the rework order.
- You change the rework order.
In this scenario, you receive an error message that resembles the following:
Quantity entered is more than available on-hand inventory
Therefore, you cannot end a rework batch order if changes are made after you reserve the batch on a sales order.
Objects that are affected
- \Data Dictionary\Tables\ProdTable\validateWrite
Issue 8
If you have default order settings and site specific order settings specified on a bulk/pack order, the system uses the default order setting information for the standard order quantity, the minimum order quantity, the maximum order quantity on the consolidated order for packed items. However, the site specific information should be used.
Objects that are affected
- \Classes\PmfBulkPlanMarkValidate\createConsOrders
Issue 9
Assume that you run the master planning. When the master planning computes the expiry for shelf-life items, you receive the following error message:
Error executing code: Wrong argument types for comparison.
Additionally, the master planning stops.
Objects that are affected
- \Classes\PdsCircularArrayList
Hotfix information
A supported hotfix is available from Microsoft. There is a "Hotfix download available" section at the top of this Knowledge Base article. If you are encountering an issue downloading, installing this hotfix, or have other technical support questions, contact your partner or, if enrolled in a support plan directly with Microsoft, you can contact technical support for Microsoft Dynamics and create a new support request. To do this, visit the following Microsoft website: You can also contact technical support for Microsoft Dynamics by phone using these links for country specific phone numbers. To do this, visit the following Microsoft websites:
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.