This article applies to Microsoft Dynamics NAV for the following countries and language locales.
-
English (Canada) (en-ca)
-
English (United States) (en-us)
-
Spanish (Mexico) (es-mx)
-
French (Canada) (fr-ca)
Symptoms
Assume that you create a job that uses the Completed Contract work-in-progress (WIP) method in the North American version of Microsoft Dynamics NAV 2009. You run the Post WIP function on the job without running the Calculated WIP function on the job first. In this situation, a duplicate of the WIP entries that are posted for the previous period is posted incorrectly. Therefore, when you run the Balance Sheet report for the previous period, the doubled WIP balance is displayed.
This problem occurs in the following products:-
The North American version of Microsoft Dynamics NAV 2009 R2
-
The North American version of Microsoft Dynamics NAV 2009 Service Pack 1 (SP1)
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 specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next Microsoft Dynamics NAV service pack or the next Microsoft Dynamics NAV version that contains this hotfix.
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 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 or fitness for a particular 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 support engineers can help 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 be the only client user who 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" role ID, you must verify that the user account has the following permissions:-
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.
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 resolve this problem, follow these steps:-
Add a new DeleteEntriesForJob function in the Job WIP Entry table (1004) as follows:
PROCEDURE DeleteEntriesForJob@1001(Job@1002 : Record 167);
SETCURRENTKEY("Job No."); SETRANGE("Job No.",Job."No."); IF NOT ISEMPTY THEN DELETEALL(TRUE); -
Change the code in the CalcGLWIP function in the Job Calculate WIP codeunit (1000) as follows:
Existing code...
GLEntry.FIND('+'); JobWIPGLEntry."G/L Entry No." := GLEntry."Entry No."; DimMgt.CopyLedgEntryDimToLedgEntryDim(DATABASE::"Job WIP Entry", JobWIPEntry."Entry No.", DATABASE::"Job WIP G/L Entry", JobWIPGLEntry."Entry No."); JobWIPGLEntry.INSERT; UNTIL JobWIPEntry.NEXT = 0; END;Replacement code
...
GLEntry.FIND('+'); JobWIPGLEntry."G/L Entry No." := GLEntry."Entry No."; DimMgt.CopyLedgEntryDimToLedgEntryDim(DATABASE::"Job WIP Entry", JobWIPEntry."Entry No.", DATABASE::"Job WIP G/L Entry", JobWIPGLEntry."Entry No."); JobWIPGLEntry.INSERT; UNTIL JobWIPEntry.NEXT = 0; END; // Add the following line. DeleteWIP(Job); -
Add a new DeleteWIP function in the Job Calculate WIP codeunit (1000). To do this, follow these steps:
-
Add a new local variable in the DeleteWIP function in the Job Calculate WIP codeunit (1000), and then specify the variable as follows:
-
Name: JobTask
-
DataType: Record
-
Subtype: Job Task (1001)
-
-
Add a new local variable in the DeleteWIP function in the Job Calculate WIP codeunit (1000), and then specify the variable as follows:
-
Name: JobWIPEntry
-
DataType: Record
-
Subtype: Job WIP Entry (1004)
-
-
Add a new local variable in the DeleteWIP function in the Job Calculate WIP codeunit (1000), and then specify the variable as follows:
-
Name: JobLedgerEntry
-
DataType: Record
-
Subtype: Job Ledger Entry (169)
-
-
Add the following code in the DeleteWIP function in the Job Calculate WIP codeunit (1000):
PROCEDURE DeleteWIP@1001(Job@1002 : Record 167);
VAR JobTask@1003 : Record 1001; JobWIPEntry@1004 : Record 1004; JobLedgerEntry@1005 : Record 169; JobTask.SETRANGE("Job No.",Job."No."); IF JobTask.FIND('-') THEN REPEAT JobTask.InitWIPFields; UNTIL JobTask.NEXT = 0; JobWIPEntry.DeleteEntriesForJob(Job); JobLedgerEntry.SETRANGE("Job No.",Job."No."); JobLedgerEntry.MODIFYALL("Amt. to Post to G/L",0);
-
Prerequisites
You must have one of the following products installed to apply this hotfix:
-
The North American version of Microsoft Dynamics NAV 2009 R2
-
The North American version of Microsoft Dynamics NAV 2009 Service Pack 1 (SP1)
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.
Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained herein is provided as-is in response to emerging issues. As a result of the speed in making it available, the materials may include typographical errors and may be revised at any time without notice. See Terms of Use for other considerations.