This article applies to Microsoft Dynamics NAV for the Swedish (se) language locale.
Symptoms
Consider the following scenario in the Swedish version of Microsoft Dynamics NAV 2009:
-
You apply hotfix 2801885.
-
You post an inward registration entry for a purchase invoice for a vendor.
-
You close the inward registration entry by posting the purchase invoice.
-
You run the "Vendor - Balance to Date" report (321) for the vendor by filtering to a date that includes both posting dates for the inward registration entry and the purchase invoice.
In this scenario, the inward registration entry is unexpectedly printed. This problem occurs in the following products:
-
The Swedish version of Microsoft Dynamics NAV 2009 R2
-
The Swedish version of Microsoft Dynamics NAV 2009 Service Pack 1
For more information about hotfix 2801885, click the following article number to view the article in the Microsoft Knowledge Base:
2801885 Inward registration entries do not appear in the "Vendor - Balance to Date" report if you closed the inward registration entries on a date that is after the report filtering date in the Swedish version of Microsoft Dynamics NAV 2009
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 2009 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:
-
Change the code in the Data Item Number 4 section in the "Vendor - Balance to Date" report (321) as follows:
Existing code...
IF FINDSET THEN
REPEAT
IF Open THEN
MARK(TRUE);
// Delete the following lines.
IF AppliedInwardRegEntry.GET("Applies-to Entry") THEN
MARK(AppliedInwardRegEntry."Posting Date" <= MaxDate);
// End of the lines.
UNTIL NEXT = 0;
SETCURRENTKEY("Entry No.");
SETRANGE(Open);
...Replacement code
...
IF FINDSET THEN
REPEAT
IF Open THEN
MARK(TRUE);
// Add the following lines.
IF AppliedInwardRegEntry.GET("Applies-to Entry") THEN
MARK(AppliedInwardRegEntry."Posting Date" > MaxDate);
// End of the lines.
UNTIL NEXT = 0;
SETCURRENTKEY("Entry No.");
SETRANGE(Open);
... -
Change the code in the Properties section in the "Purch.-Post" codeunit (90) as follows:
Existing code...
PurchSetup.GET;
InwRegHeader.SETRANGE("Document Type",PurchHeader."Document Type");
InwRegHeader.SETRANGE("Document No.",PurchHeader."No.");
InwRegHeader.SETRANGE(Status, InwRegHeader.Status::Posted);
// Delete the following lines.
IF InwRegHeader.FIND('-') THEN
InwRegReverse.RUN(InwRegHeader);
// End of the lines.
PurchInvHeader.INIT;
PurchInvHeader.TRANSFERFIELDS(PurchHeader);
IF "Document Type" = "Document Type"::Order THEN BEGIN
PurchInvHeader."Pre-Assigned No. Series" := '';
...Replacement code
...
PurchSetup.GET;
InwRegHeader.SETRANGE("Document Type",PurchHeader."Document Type");
InwRegHeader.SETRANGE("Document No.",PurchHeader."No.");
InwRegHeader.SETRANGE(Status, InwRegHeader.Status::Posted);
// Add the following lines.
IF InwRegHeader.FINDFIRST THEN BEGIN
InwRegReverse.SetPostingDate("Posting Date");
InwRegReverse.RUN(InwRegHeader);
END;
// End of the lines.
PurchInvHeader.INIT;
PurchInvHeader.TRANSFERFIELDS(PurchHeader);
IF "Document Type" = "Document Type"::Order THEN BEGIN
PurchInvHeader."Pre-Assigned No. Series" := '';
... -
Change the code in the Global Variables section in the "Inward Reg.-Reverse" codeunit (11203) as follows:
Existing code...
PreviousDim1Code@1070021 : Code[20];
PreviousDim2Code@1070022 : Code[20];
DimensionsOnTotalTrans@1070023 : Boolean;
GenJnlCheckLine@1070024 : Codeunit 11;
Text005@1070025 : TextConst 'ENU=is not within your range of allowed posting dates;SVE=„r inte i ditt till†tna intervall f”r bokf”ringsdatum';
PROCEDURE MakeInwRegEntriesReverse@1070000();
BEGIN
IF InwRegEntry.FIND('+') THEN
...Replacement code
...
PreviousDim1Code@1070021 : Code[20];
PreviousDim2Code@1070022 : Code[20];
DimensionsOnTotalTrans@1070023 : Boolean;
GenJnlCheckLine@1070024 : Codeunit 11;
Text005@1070025 : TextConst 'ENU=is not within your range of allowed posting dates;SVE=„r inte i ditt till†tna intervall f”r bokf”ringsdatum';
// Add the following line.
PostingDate@1070030 : Date;
PROCEDURE MakeInwRegEntriesReverse@1070000();
BEGIN
IF InwRegEntry.FIND('+') THEN
... -
Change the code in the MakeInwRegEntryReverse function in the "Inward Reg.-Reverse" codeunit (11203) as follows:
Existing code...
InwRegEntry."Entry No." := NextEntryNo;
InwRegEntry."Applies-to Entry" := "Entry No.";
InwRegEntry.Open := FALSE;
InwRegEntry."Source Type" := "Source Type";
InwRegEntry."Source No." := "Source No.";
// Delete the following line.
InwRegEntry."Posting Date" := InwHeader."Posting Date";
InwRegEntry."Vendor Posting Group" := "Vendor Posting Group";
InwRegEntry."Gen. Bus. Posting Group" := "Gen. Bus. Posting Group";
InwRegEntry."Vendor No." := "Vendor No.";
InwRegEntry."Document No." := "Document No.";
InwRegEntry."Line No." := "Line No.";
...Replacement code
...
InwRegEntry."Entry No." := NextEntryNo;
InwRegEntry."Applies-to Entry" := "Entry No.";
InwRegEntry.Open := FALSE;
InwRegEntry."Source Type" := "Source Type";
InwRegEntry."Source No." := "Source No.";
// Add the following line.
InwRegEntry."Posting Date" := PostingDate;
InwRegEntry."Vendor Posting Group" := "Vendor Posting Group";
InwRegEntry."Gen. Bus. Posting Group" := "Gen. Bus. Posting Group";
InwRegEntry."Vendor No." := "Vendor No.";
InwRegEntry."Document No." := "Document No.";
InwRegEntry."Line No." := "Line No.";
...
Prerequisites
You must have one of the following products installed to apply this hotfix:
-
The Swedish version of Microsoft Dynamics NAV 2009 R2
-
The Swedish version of Microsoft Dynamics NAV 2009 Service Pack 1
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.
