Test and apply hotfix

Scott_Meja

How to apply and test hotfix KB 960894 in NAV 5.01. Attached is the KB 960894 Document. Have to prepare testing document for this hotfix in our NAVISION 5.0 database. I would like to know the steps to prepare the Testing document. Please Advice.




HOTFIX INFORMATION:
The Calculate Plan function suggests additional quantities for items that use the Lot-for-lot reordering policy in Dynamics NAV 5.0
CONFIDENTIAL ARTICLE
(The information in this article is provided to you in accordance with your Confidentiality Agreement)
RAPID 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.
This article applies to Microsoft Dynamics NAV for all countries and all language locales.
SYMPTOMS
When you run the Calculate Plan function on a requisition worksheet for an item or items that use the Lot-for-lot reordering policy in Microsoft Dynamics NAV 5.0, the Calculate Plan function quantity for the item or items.
CAUSE
This problem occurs because Microsoft Dynamics NAV incorrectly calls the MaintainProjectedInv function.
RESOLUTION
Hotfix information
A supported hotfix is now available from Microsoft. However, it is only intended to correct the problem that is described in this article. Apply it only to systems that are experiencing this receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Dynamics NAV 5.0 service pack or the next version 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 your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
Installation information
Microsoft provides programming examples for illustration only, without warranty either expressed or implied. This includes, but is not limited to, the implied warranties of merchantability purpose. This article assumes that you are familiar with the programming language that is being demonstrated and with the tools that are used to create and to debug procedures. Microsoft explain the functionality of a particular procedure, but they will not modify these examples to provide added functionality or construct procedures to meet your specific requirements.
Note Before you install this hotfix, verify that all Microsoft Navision client users are logged off the system. This includes Microsoft Navision Application Services (NAS) client users. You should is logged on when you implement this hotfix.

To implement this hotfix, you must have a developer license.
We recommend that the user account in the Windows Logins window or in the Database Logins window be assigned the "SUPER" role ID. If the user account cannot be assigned the "SUPER" the user account has the following permissions:
Note You do not have to have rights to the data stores unless you have to perform data repair.
Code changes
Note Always test code fixes in a controlled environment before you apply the fixes to your production computers.
To install this hotfix, change the code in the PlanItem function of the codeunit (99000854) as follows.
Existing code 1
…
MatchDates section
IF WeAreSureThatDatesMatch THEN BEGIN
MaintainProjectedInv(
…
Replacement code 1
…
MatchDates section
IF WeAreSureThatDatesMatch AND IsReorderPointPlanning THEN BEGIN
MaintainProjectedInv(
…
Existing code 2
…
CreateSupply section
IF Demand."Order Relation" <> Demand."Order Relation"::"Safety Stock" THEN
MaintainProjectedInv(
InvChangeReminder,NewSupplyDate,LastProjectedInventory,LatestBucketStartDate,ROPHasBeenCrossed);
…
Replacement code 2
…
CreateSupply section
IF (Demand."Order Relation" <> Demand."Order Relation"::"Safety Stock") AND IsReorderPointPlanning THEN
MaintainProjectedInv(
• The Modify permission for the object that you will be changing.
• The Execute permission for the System Object ID 5210 object and for the System Object ID 9015 object.

InvChangeReminder,NewSupplyDate,LastProjectedInventory,LatestBucketStartDate,ROPHasBeenCrossed);
…
Existing code 3
…
ReduceSupply section
BEGIN
MaintainProjectedInv(
InvChangeReminder,Supply."Due Date",LastProjectedInventory,LatestBucketStartDate,ROPHasBeenCrossed);
NewSupplyHasTakenOver := FALSE;
…
Replacement code 3
…
ReduceSupply section
BEGIN
IF IsReorderPointPlanning THEN
MaintainProjectedInv(
InvChangeReminder,Supply."Due Date",LastProjectedInventory,LatestBucketStartDate,ROPHasBeenCrossed);
NewSupplyHasTakenOver := FALSE;
…
Existing code 4
…
CloseDemand section
END ELSE BEGIN
InvChangeReminder := Demand;
InvChangeReminder.INSERT;
…
Replacement code 4
…
CloseDemand section
END ELSE BEGIN
IF IsReorderPointPlanning THEN BEGIN
InvChangeReminder := Demand;
InvChangeReminder.INSERT;
END;
…
Existing code 5
…
CloseSupply section
IF Supply."Due Date" >= PlanningStartDate THEN BEGIN

InvChangeReminder := Supply;
InvChangeReminder.INSERT;
END;
…
Replacement code 5
…
CloseSupply section
IF IsReorderPointPlanning AND (Supply."Due Date" >= PlanningStartDate) THEN BEGIN
InvChangeReminder := Supply;
InvChangeReminder.INSERT;
END;
…
Existing code 6
…
CloseLoop section
BEGIN
MaintainProjectedInv(
InvChangeReminder,ToDate,LastProjectedInventory,LatestBucketStartDate,ROPHasBeenCrossed);
IF ROPHasBeenCrossed AND IsReorderPointPlanning THEN BEGIN
…
Replacement code 6
…
CloseLoop section
BEGIN
IF IsReorderPointPlanning THEN
MaintainProjectedInv(
InvChangeReminder,ToDate,LastProjectedInventory,LatestBucketStartDate,ROPHasBeenCrossed);
IF ROPHasBeenCrossed AND IsReorderPointPlanning THEN BEGIN
…
Prerequisites
No prerequisites are required to apply this hotfix.
Removal information
You cannot remove this hotfix.
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, THE RELIABILITY OR THE ACCURACY OF THE INFORMATION THAT IS CONTAINED AND THE RELATED GRAPHICS PUBLISHED ON THIS WEB SITE (THE “MATERIALS”) FOR ANY PURPOSE.