This article applies to Microsoft Dynamics NAV for the Eastern Europe (EE) language locale.

Symptoms

Consider the following scenario in the Eastern European version of Microsoft Dynamics NAV 2009 R2:

  • You apply hotfix 2546451.

  • You set the Adv. Invoice Correction Type value to Absolute or to Fully Invoiced.

  • You generate a prepayment for a sales order or for a purchase order.

  • Half of the prepayment amount is paid and invoiced.

  • You post part of the sales order or the purchase order. Another half of the prepayment is paid and invoiced.

  • You try to post the remaining quantity of the sales order or the purchase order.

In this scenario, you receive the following error message:

Cust. Ledger Entry Entry No. 'Entry_Number' already exists.

For more information about hotfix 2546451, click the following article number to view the article in the Microsoft Knowledge Base:

2546451 "There is no Cust. Ledger Entry within the filter" error message when you try to post the remaining quantity of a sales order in the Eastern European 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:

  1. Change the code in the Sales-Post Advances codeunit (26585). To do this, follow these steps:

    1. Change the code in the PostPaymentCorrection function as follows:
      Existing code

      ...
      LedgEntryDim.SETRANGE("Entry No.",LinkedAdvanceEntry."Entry No.");
      DimMgt.CopyLedgEntryDimToJnlLineDim(LedgEntryDim,TempJnlLineDim);
      GenJnlPostLine.RunWithCheck(GenJnlLine,TempJnlLineDim);

      // Delete the following line.
      UNTIL LinkedAdvanceEntry.NEXT = 0;

      // Post Payment
      GenJnlLine.INIT
      ...

      Replacement code

      ...
      LedgEntryDim.SETRANGE("Entry No.",LinkedAdvanceEntry."Entry No.");
      DimMgt.CopyLedgEntryDimToJnlLineDim(LedgEntryDim,TempJnlLineDim);
      GenJnlPostLine.RunWithCheck(GenJnlLine,TempJnlLineDim);

      // Add the following line.
      UNTIL (LinkedAdvanceEntry.NEXT = 0) OR (InvoiceAmount = 0);

      // Post Payment
      GenJnlLine.INIT;
      ...
    2. Change the code in the CalcLinkedPmtAmountToApply function as follows:
      Existing code

      ...
      AmountToApply := ROUND(TotAmt,Currency."Amount Rounding Precision") - TotAmtRnded;
      TotAmtRnded := TotAmtRnded + AmountToApply;

      // Delete the following lines.
      IF LinkedAdvanceEntry.GET(CustLedgEntry."Entry No.") THEN BEGIN
      LinkedAdvanceEntry."Amount to Apply" := LinkedAdvanceEntry."Amount to Apply" + AmountToApply;
      LinkedAdvanceEntry.MODIFY;
      END ELSE BEGIN
      LinkedAdvanceEntry := CustLedgEntry;
      LinkedAdvanceEntry."Amount to Apply" := AmountToApply;
      LinkedAdvanceEntry."Currency Code" := Link."Currency Code";
      LinkedAdvanceEntry.INSERT;
      // End of the deleted lines.

      END;
      END;
      UNTIL Link.NEXT = 0;
      ...

      Replacement code

      ...
      AmountToApply := ROUND(TotAmt,Currency."Amount Rounding Precision") - TotAmtRnded;
      TotAmtRnded := TotAmtRnded + AmountToApply;

      // Add the following lines.
      IF AmountToApply <> 0 THEN
      IF LinkedAdvanceEntry.GET(CustLedgEntry."Entry No.") THEN BEGIN
      LinkedAdvanceEntry."Amount to Apply" := LinkedAdvanceEntry."Amount to Apply" + AmountToApply;
      LinkedAdvanceEntry.MODIFY;
      END ELSE BEGIN
      LinkedAdvanceEntry := CustLedgEntry;
      LinkedAdvanceEntry."Amount to Apply" := AmountToApply;
      LinkedAdvanceEntry."Currency Code" := Link."Currency Code";
      LinkedAdvanceEntry.INSERT;
      // End of the added lines.

      END;
      END;
      UNTIL Link.NEXT = 0;
      ...
  2. Change the code in the Purchase-Post Advances codeunit (26586). To do this, follow these steps:

    1. Change the code in the PostPaymentCorrection function as follows:
      Existing code

      ...
      LedgEntryDim.SETRANGE("Entry No.",LinkedAdvanceEntry."Entry No.");
      DimMgt.CopyLedgEntryDimToJnlLineDim(LedgEntryDim,TempJnlLineDim);
      GenJnlPostLine.RunWithCheck(GenJnlLine,TempJnlLineDim);

      // Delete the following line.
      UNTIL LinkedAdvanceEntry.NEXT = 0;

      // Post Payment
      GenJnlLine.INIT;
      ...

      Replacement code

      LedgEntryDim.SETRANGE("Entry No.",LinkedAdvanceEntry."Entry No.");
      DimMgt.CopyLedgEntryDimToJnlLineDim(LedgEntryDim,TempJnlLineDim);
      GenJnlPostLine.RunWithCheck(GenJnlLine,TempJnlLineDim);

      // Add the following line.
      UNTIL (LinkedAdvanceEntry.NEXT = 0) OR (InvoiceAmount = 0);

      // Post Payment
      GenJnlLine.INIT;
      ...
    2. Change the code in the CalcLinkedPmtAmountToApply function as follows:
      Existing code

      ...
      AmountToApply := ROUND(TotAmt,Currency."Amount Rounding Precision") - TotAmtRnded;
      TotAmtRnded := TotAmtRnded + AmountToApply;

      // Delete the following lines.
      IF LinkedAdvanceEntry.GET(VendLedgEntry."Entry No.") THEN BEGIN
      LinkedAdvanceEntry."Amount to Apply" := LinkedAdvanceEntry."Amount to Apply" + AmountToApply;
      LinkedAdvanceEntry.MODIFY;
      END ELSE BEGIN
      LinkedAdvanceEntry := VendLedgEntry;
      LinkedAdvanceEntry."Amount to Apply" := AmountToApply;
      LinkedAdvanceEntry."Currency Code" := Link."Currency Code";
      LinkedAdvanceEntry.INSERT;
      // End of the deleted lines.

      END;
      END;
      UNTIL Link.NEXT = 0;
      ...

      Replacement code

      ...
      AmountToApply := ROUND(TotAmt,Currency."Amount Rounding Precision") - TotAmtRnded;
      TotAmtRnded := TotAmtRnded + AmountToApply;

      // Add the following lines.
      IF AmountToApply <> 0 THEN
      IF LinkedAdvanceEntry.GET(VendLedgEntry."Entry No.") THEN BEGIN
      LinkedAdvanceEntry."Amount to Apply" := LinkedAdvanceEntry."Amount to Apply" + AmountToApply;
      LinkedAdvanceEntry.MODIFY;
      END ELSE BEGIN
      LinkedAdvanceEntry := VendLedgEntry;
      LinkedAdvanceEntry."Amount to Apply" := AmountToApply;
      LinkedAdvanceEntry."Currency Code" := Link."Currency Code";
      LinkedAdvanceEntry.INSERT;
      // End of the added lines.

      END;
      END;
      UNTIL Link.NEXT = 0;
      ...

Prerequisites

You must have the Eastern European version of Microsoft Dynamics NAV 2009 R2 installed 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.

For more information about partial shipment, click the following article number to view the article in the Microsoft Knowledge Base:

2672643 "There are non posted Prepayment Amounts on Order [number]" error message when you post partial shipment for a sales order in the East European version of Microsoft Dynamics NAV 2009 R2 For more information about final invoice, click the following article number to view the article in the Microsoft Knowledge Base:

2546442 "There are non-posted Prepayment Amounts on Order [Order Number]" error message when you post a final invoice in the prepayment scenario in the Eastern European version of Microsoft Dynamics NAV 2009

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.

Need more help?

Expand your skills
Explore Training
Get new features first
Join Microsoft Insiders

Was this information helpful?

What affected your experience?

Thank you for your feedback!

×