Rapidly Published 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 the Italian (it) language locale.
Symptoms
Assume that you have an invoice that uses multiple rates and the payment method of the invoice uses a balance account number in the Italian version of Microsoft Dynamics NAV. When you post the invoice by using an automatic payment, Microsoft Dynamics NAV creates multiple lines for the invoice and one line for the payment. However, only the first invoice is applied and closed. The other invoices are still open.
This problem occurs in the following products:
-
The Italian version of Microsoft Dynamics NAV 2009 Service Pack 1
-
The Italian version of Microsoft Dynamics NAV 2009
-
The Italian version of Microsoft Dynamics NAV 5.0 Service Pack 1
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 apply this hotfix, follow these steps:
-
Change the key in the Cust. Ledger Entry table (21) as follows:
Existing one-
Enabled:Yes
-
Key: Document Type,Document No.,Document Occurrence
-
SumIndexFields:
Replacement one
-
Enabled:Yes
-
Key: Document Type,Document No.,Document Occurrence
-
SumIndexFields: Remaining Pmt. Disc. Possible
-
-
Change the key in the Vendor Ledger Entry table (25) as follows:
Existing one-
Enabled:Yes
-
Key: Document Type,Document No.,Document Occurrence,Vendor No.
-
SumIndexFields:
Replacement one
-
Enabled:Yes
-
Key: Document Type,Document No.,Document Occurrence,Vendor No.
-
SumIndexFields: Remaining Pmt. Disc. Possible
-
-
Add a local variable in the ApplyCustLedgEntry function in the Gen. Jnl.-Post Line codeunit (12), and then specify the variable as follows:
-
Name: PaymentTerms
-
DataType: Record
-
Subtype: Payment Terms
-
-
Change the code in the ApplyCustLedgEntry function in the Gen. Jnl.-Post Line codeunit (12) as follows:
Existing code 1...
END ELSE
ApplnRoundingPrecision := GLSetup."Appln. Rounding Precision";
ApplyingDate := GenJnlLine."Posting Date";
IF GenJnlLine."Applies-to Doc. No." <> '' THEN BEGIN
// Find the entry to be applied to
...Replacement code 1
...
END ELSE
ApplnRoundingPrecision := GLSetup."Appln. Rounding Precision";
ApplyingDate := GenJnlLine."Posting Date";
// Add the following lines.
Cust.GET(GenJnlLine."Account No.");
IF Cust."Payment Terms Code" <> '' THEN BEGIN
PaymentTerms.GET(Cust."Payment Terms Code");
PaymentTerms.CALCFIELDS("Payment Nos.");
END;
// End of the added lines.
IF GenJnlLine."Applies-to Doc. No." <> '' THEN BEGIN
// Find the entry to be applied to
...Existing code 2
...
(OldCustLedgEntry.COUNT=1)
THEN
GenJnlLine."Applies-to Occurrence No." := 1;
// Delete the following line.
OldCustLedgEntry.SETRANGE("Document Occurrence",GenJnlLine."Applies-to Occurrence No.");
OldCustLedgEntry.SETRANGE(Open,TRUE);
// Delete the following lines.
OldCustLedgEntry.FINDFIRST;
OldCustLedgEntry.TESTFIELD("Bank Receipt Issued", FALSE);
OldCustLedgEntry.TESTFIELD(Positive,NOT NewCVLedgEntryBuf.Positive);
IF OldCustLedgEntry."Posting Date" > ApplyingDate THEN
ApplyingDate := OldCustLedgEntry."Posting Date";
GenJnlApply.CheckAgainstApplnCurrency(
NewCVLedgEntryBuf."Currency Code",
OldCustLedgEntry."Currency Code",
GenJnlLine."Account Type"::Customer,
TRUE);
TempOldCustLedgEntry := OldCustLedgEntry;
TempOldCustLedgEntry.INSERT;
// End of the deleted lines.
END ELSE BEGIN
// Find the first old entry (Invoice) which the new entry (Payment) should apply to
...Replacement code 2
...
(OldCustLedgEntry.COUNT=1)
THEN
GenJnlLine."Applies-to Occurrence No." := 1;
OldCustLedgEntry.SETRANGE(Open,TRUE);
// Add the following lines.
IF OldCustLedgEntry.FINDSET THEN
REPEAT
OldCustLedgEntry.TESTFIELD("Bank Receipt Issued", FALSE);
OldCustLedgEntry.TESTFIELD(Positive,NOT NewCVLedgEntryBuf.Positive);
IF OldCustLedgEntry."Posting Date" > ApplyingDate THEN
ApplyingDate := OldCustLedgEntry."Posting Date";
GenJnlApply.CheckAgainstApplnCurrency(
NewCVLedgEntryBuf."Currency Code",
OldCustLedgEntry."Currency Code",
GenJnlLine."Account Type"::Customer,
TRUE);
TempOldCustLedgEntry := OldCustLedgEntry;
TempOldCustLedgEntry.INSERT;
UNTIL OldCustLedgEntry.NEXT = 0;
IF NOT TempOldCustLedgEntry.FINDSET THEN
EXIT;
// End of the added lines.
END ELSE BEGIN
// Find the first old entry (Invoice) which the new entry (Payment) should apply to
...Existing code 3
...
TempOldCustLedgEntry.DELETE;
// Find the next old entry for application of the new entry
// Delete the following line.
IF GenJnlLine."Applies-to Doc. No." <> '' THEN
Completed := TRUE
...Replacement code 3
...
TempOldCustLedgEntry.DELETE;
// Find the next old entry for application of the new entry
// Add the following line.
IF (GenJnlLine."Applies-to Doc. No." <> '') AND (PaymentTerms."Payment Nos." <= 1) THEN
Completed := TRUE
... -
Add a local variable in the ApplyVendLedgEntry function in the Gen. Jnl.-Post Line codeunit (12), and then specify the variable as follows:
-
Name: PaymentTerms
-
DataType: Record
-
Subtype: Payment Terms
-
-
Change the code in the ApplyVendLedgEntry function in the Gen. Jnl.-Post Line codeunit (12) as follows:
Existing code 1...
ApplyingDate := GenJnlLine."Posting Date";
IF GenJnlLine."Applies-to Doc. No." <> '' THEN BEGIN
// Find the entry to be applied to
...Replacement code 1
...
ApplyingDate := GenJnlLine."Posting Date";
// Add the following lines.
Vend.GET(GenJnlLine."Account No.");
IF Vend."Payment Terms Code" <> '' THEN BEGIN
PaymentTerms.GET(Vend."Payment Terms Code");
PaymentTerms.CALCFIELDS("Payment Nos.");
END;
// End of the added lines.
IF GenJnlLine."Applies-to Doc. No." <> '' THEN BEGIN
// Find the entry to be applied to
...Existing code 2
...
GenJnlLine."Applies-to Occurrence No." := 1;
// Delete the following line.
OldVendLedgEntry.SETRANGE("Document Occurrence",GenJnlLine."Applies-to Occurrence No.");
OldVendLedgEntry.SETRANGE(Open,TRUE);
OldVendLedgEntry.SETRANGE("On Hold",'');
// Delete the following lines.
OldVendLedgEntry.FINDFIRST;
OldVendLedgEntry.TESTFIELD(Positive,NOT NewCVLedgEntryBuf.Positive);
IF OldVendLedgEntry."Posting Date" > ApplyingDate THEN
ApplyingDate := OldVendLedgEntry."Posting Date";
GenJnlApply.CheckAgainstApplnCurrency(
NewCVLedgEntryBuf."Currency Code",
OldVendLedgEntry."Currency Code",
GenJnlLine."Account Type"::Vendor,
TRUE);
TempOldVendLedgEntry := OldVendLedgEntry;
TempOldVendLedgEntry.INSERT;
// End of the deleted lines.
END ELSE BEGIN
// Find the first old entry (Invoice) which the new entry (Payment) should apply to
...Replacement code 2
...
GenJnlLine."Applies-to Occurrence No." := 1;
OldVendLedgEntry.SETRANGE(Open,TRUE);
OldVendLedgEntry.SETRANGE("On Hold",'');
// Add the following lines.
IF OldVendLedgEntry.FINDSET THEN
REPEAT
OldVendLedgEntry.TESTFIELD(Positive,NOT NewCVLedgEntryBuf.Positive);
IF OldVendLedgEntry."Posting Date" > ApplyingDate THEN
ApplyingDate := OldVendLedgEntry."Posting Date";
GenJnlApply.CheckAgainstApplnCurrency(
NewCVLedgEntryBuf."Currency Code",
OldVendLedgEntry."Currency Code",
GenJnlLine."Account Type"::Vendor,
TRUE);
TempOldVendLedgEntry := OldVendLedgEntry;
TempOldVendLedgEntry.INSERT;
UNTIL OldVendLedgEntry.NEXT = 0;
IF NOT TempOldVendLedgEntry.FINDSET THEN
EXIT;
// End of the added lines.
END ELSE BEGIN
// Find the first old entry (Invoice) which the new entry (Payment) should apply to
...Existing code 3
...
TempOldVendLedgEntry.DELETE;
// Find the next old entry to apply to the new entry
// Delete the following line.
IF GenJnlLine."Applies-to Doc. No." <> '' THEN
Completed := TRUE
...Replacement code 3
...
TempOldVendLedgEntry.DELETE;
// Find the next old entry to apply to the new entry
// Add the following line.
IF (GenJnlLine."Applies-to Doc. No." <> '') AND (PaymentTerms."Payment Nos." <= 1) THEN
Completed := TRUE
... -
Add a local variable in the OnRun trigger in the Sales-Post codeunit (80), and then specify the variable as follows:
-
Name: TotalRemainPmtDiscPossible
-
DataType: Decimal
-
-
Change the code in the OnRun trigger in the Sales-Post codeunit (80) as follows:
Existing code 1...
// Balancing account
IF "Bal. Account No." <> '' THEN BEGIN
Window.UPDATE(5,1);
CustLedgEntry.FINDLAST;
GenJnlLine.INIT;
...Replacement code 1
...
// Balancing account
IF "Bal. Account No." <> '' THEN BEGIN
Window.UPDATE(5,1);
// Add the following lines.
CustLedgEntry.RESET;
CustLedgEntry.SETCURRENTKEY("Document Type","Document No.");
CustLedgEntry.SETRANGE("Document Type","Document Type");
CustLedgEntry.SETRANGE("Document No.",GenJnlLineDocNo);
CustLedgEntry.CALCSUMS("Remaining Pmt. Disc. Possible");
TotalRemainPmtDiscPossible := CustLedgEntry."Remaining Pmt. Disc. Possible";
// End of the added lines.
CustLedgEntry.FINDLAST;
GenJnlLine.INIT;
...Existing code 2
...
GenJnlLine."Currency Code" := "Currency Code";
GenJnlLine.Amount :=
// Delete the following line.
TotalSalesLine."Amount Including VAT" + CustLedgEntry."Remaining Pmt. Disc. Possible";
GenJnlLine."Source Currency Code" := "Currency Code";
GenJnlLine."Source Currency Amount" := GenJnlLine.Amount;
...Replacement code 2
...
GenJnlLine."Currency Code" := "Currency Code";
GenJnlLine.Amount :=
// Add the following line.
TotalSalesLine."Amount Including VAT" + TotalRemainPmtDiscPossible;
GenJnlLine."Source Currency Code" := "Currency Code";
GenJnlLine."Source Currency Amount" := GenJnlLine.Amount;
... -
Add a local variable in the OnRun trigger in the Purch.-Post codeunti (90), and then specify the variable as follows:
-
Name: TotalRemainPmtDiscPossible
-
DataType: Decimal
-
-
Change the code in the OnRun trigger in thePurch.-Post codeunti (90) as follows:
Existing code 1...
GenJnlPostLine.RunWithCheck(GenJnlLine,TempJnlLineDim);
// Balancing account
IF "Bal. Account No." <> '' THEN BEGIN
IF GUIALLOWED THEN
Window.UPDATE(5,1);
VendLedgEntry.FINDLAST;
GenJnlLine.INIT;
GenJnlLine."Posting Date" := "Posting Date";
...Replacement code 1
...
GenJnlPostLine.RunWithCheck(GenJnlLine,TempJnlLineDim);
// Balancing account
IF "Bal. Account No." <> '' THEN BEGIN
IF GUIALLOWED THEN
Window.UPDATE(5,1);
// Add the following lines.
VendLedgEntry.RESET;
VendLedgEntry.SETCURRENTKEY("Document Type","Document No.");
VendLedgEntry.SETRANGE("Document Type","Document Type");
VendLedgEntry.SETRANGE("Document No.",GenJnlLineDocNo);
VendLedgEntry.CALCSUMS("Remaining Pmt. Disc. Possible");
TotalRemainPmtDiscPossible := VendLedgEntry."Remaining Pmt. Disc. Possible";
// End of the added lines.
VendLedgEntry.FINDLAST;
GenJnlLine.INIT;
GenJnlLine."Posting Date" := "Posting Date";
...Existing code 2
...
GenJnlLine."Currency Code" := "Currency Code";
GenJnlLine.Amount := TotalPurchLine."Amount Including VAT" +
// Delete the following line.
VendLedgEntry."Remaining Pmt. Disc. Possible";
GenJnlLine.Correction := Correction;
GenJnlLine."Source Currency Code" := "Currency Code";
...Replacement code 2
...
GenJnlLine."Currency Code" := "Currency Code";
GenJnlLine.Amount := TotalPurchLine."Amount Including VAT" +
// Add the following line.
TotalRemainPmtDiscPossible;
GenJnlLine.Correction := Correction;
GenJnlLine."Source Currency Code" := "Currency Code";
...
Prerequisites
You must have one of the following products installed to apply this hotfix:
-
The Italian version of Microsoft Dynamics NAV 2009 Service Pack 1
-
The Italian version of Microsoft Dynamics NAV 2009
-
The Italian version of Microsoft Dynamics NAV 5.0 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.
MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, THE RELIABILITY OR THE ACCURACY OF THE INFORMATION THAT IS CONTAINED IN THE DOCUMENTS AND THE RELATED GRAPHICS PUBLISHED ON THIS WEB SITE (THE “MATERIALS”) FOR ANY PURPOSE.
THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON-INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.
