According to options that are used on the Suggest Vendor Payments report and that dimension is used as default in the entry in Microsoft Dynamics NAV 2009, the report suggests incorrect dimensions in Microsoft Dynamics NAV 2009. This problem occurs in the following products:
-
Microsoft Dynamics NAV 2009 R2
-
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 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. However, 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 Dynamics NAV client users are logged off the system. This includes Microsoft Dynamics NAV Application Server (NAS) services. 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. Before applying the change, please import all SEPA updates.
To resolve this problem, follow these steps:
-
Change the code in the MakeGenJnlLines function in the Suggest Vendor Payments report (393) as follows:
Existing code...
JnlLineDim.SETRANGE("Journal Line No.","Line No.");
JnlLineDim.DELETEALL;
CreateDim(
DimMgt.TypeToTableID1("Account Type"),"Account No.",
DimMgt.TypeToTableID1("Bal. Account Type"),"Bal. Account No.",
DATABASE::Job,"Job No.",
DATABASE::"Salesperson/Purchaser","Salespers./Purch. Code",
DATABASE::Campaign,"Campaign No.");
IF SummarizePerVend THEN BEGIN
TempDimBuf.RESET;
TempDimBuf.DELETEALL;
...Replacement code
...
JnlLineDim.SETRANGE("Journal Line No.","Line No.");
JnlLineDim.DELETEALL;
IF SummarizePerVend THEN BEGIN
TempDimBuf.RESET;
TempDimBuf.DELETEALL;
... -
Change the code in the MakeGenJnlLines function in the Suggest Vendor Payments report (393) as follows:
Existing code 1...
TempDimBuf.RESET;
TempDimBuf.DELETEALL;
DimBufMgt.GetDimensions(TempPaymentBuffer."Dimension Entry No.",TempDimBuf);
IF TempDimBuf.FINDSET THEN
REPEAT
DimMgt.SaveJnlLineDim(
DATABASE::"Gen. Journal Line","Journal Template Name","Journal Batch Name","Line No.",0,
...Replacement code 1
...
TempDimBuf.RESET;
TempDimBuf.DELETEALL;
DimBufMgt.GetDimensions(TempPaymentBuffer."Dimension Entry No.",TempDimBuf);
IF TempDimBuf.FINDSET THEN BEGIN
CreateDim(
DimMgt.TypeToTableID1("Account Type"),"Account No.",
DimMgt.TypeToTableID1("Bal. Account Type"),"Bal. Account No.",
DATABASE::Job,"Job No.",
DATABASE::"Salesperson/Purchaser","Salespers./Purch. Code",
DATABASE::Campaign,"Campaign No.");
REPEAT
DimMgt.SaveJnlLineDim(
DATABASE::"Gen. Journal Line","Journal Template Name","Journal Batch Name","Line No.",0,
...Existing code 2
...
DATABASE::"Gen. Journal Line","Journal Template Name","Journal Batch Name","Line No.",0,
DimMgt.GlobalDimNo(TempDimBuf."Dimension Code"),TempDimBuf."Dimension Value Code");
UNTIL TempDimBuf.NEXT = 0;
END ELSE BEGIN
LedgEntryDim.SETRANGE("Table ID",DATABASE::"Vendor Ledger Entry");
LedgEntryDim.SETRANGE("Entry No.",TempPaymentBuffer."Vendor Ledg. Entry No.");
...Replacement code 2
...
DATABASE::"Gen. Journal Line","Journal Template Name","Journal Batch Name","Line No.",0,
DimMgt.GlobalDimNo(TempDimBuf."Dimension Code"),TempDimBuf."Dimension Value Code");
UNTIL TempDimBuf.NEXT = 0;
TempDimBuf.FINDFIRST;
DeleteDimNotInTempDimBuf(
DATABASE::"Gen. Journal Line","Journal Template Name","Journal Batch Name","Line No.",0,TempDimBuf);
END;
END ELSE BEGIN
LedgEntryDim.SETRANGE("Table ID",DATABASE::"Vendor Ledger Entry");
LedgEntryDim.SETRANGE("Entry No.",TempPaymentBuffer."Vendor Ledg. Entry No.");
...Existing code 3
...
REPEAT
JnlLineDim.SETRANGE("Allocation Line No.",0);
JnlLineDim.SETRANGE("Dimension Code",LedgEntryDim."Dimension Code");
IF NOT JnlLineDim.ISEMPTY THEN
JnlLineDim.DELETEALL;
UNTIL LedgEntryDim.NEXT = 0;
DimMgt.MoveLedgEntryDimToJnlLineDim(
...Replacement code 3
...
REPEAT
JnlLineDim.SETRANGE("Allocation Line No.",0);
JnlLineDim.SETRANGE("Dimension Code",LedgEntryDim."Dimension Code");
IF JnlLineDim.FINDFIRST THEN
JnlLineDim.DELETE(TRUE);
UNTIL LedgEntryDim.NEXT = 0;
DimMgt.MoveLedgEntryDimToJnlLineDim(
... -
Change the code in the DeleteDimNotInTempDimBuf function in the Suggest Vendor Payments report (393) as follows:
Existing code...
EXIT(NOT DimBuf.ISEMPTY);
END;
BEGIN
END.
}
...Replacement code
...
EXIT(NOT DimBuf.ISEMPTY);
END;
LOCAL PROCEDURE DeleteDimNotInTempDimBuf@17(TableID@1000 : Integer;JnlTemplateName@1001 : Code[10];JnlBatchName@1002 : Code[10];JnlLineNo@1003 : Integer;AllocationLineNo@1004 : Integer;DimBuf@1006 : Record 360);
VAR
DimFound@1007 : Boolean;
BEGIN
JnlLineDim.RESET;
JnlLineDim.SETRANGE("Table ID",DATABASE::"Gen. Journal Line");
JnlLineDim.SETRANGE("Journal Template Name",JnlTemplateName);
JnlLineDim.SETRANGE("Journal Batch Name",JnlBatchName);
JnlLineDim.SETRANGE("Journal Line No.",JnlLineNo);
JnlLineDim.SETRANGE("Allocation Line No.",0);
IF JnlLineDim.FINDSET THEN
REPEAT
DimFound := FALSE;
REPEAT
IF JnlLineDim."Dimension Code" = DimBuf."Dimension Code" THEN
DimFound := TRUE;
UNTIL DimBuf.NEXT = 0;
IF NOT DimFound THEN
JnlLineDim.DELETE(TRUE);
UNTIL JnlLineDim.NEXT = 0
END;
BEGIN
END.
}
...
Prerequisites
You must have one of the following products installed to apply this hotfix:
-
Microsoft Dynamics NAV 2009 R2
-
Microsoft Dynamics NAV 2009 SP1
In addition, you have to install KB2664507.
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 Usefor other considerations.
