Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. "The latest transaction no. must be an application in cust. ledger entry no [number]" error message when you unapply a customer ledger entry in Microsoft Dynamics NAV 2009

"The latest transaction no. must be an application in cust. ledger entry no [number]" error message when you unapply a customer ledger entry in Microsoft Dynamics NAV 2009

View products that this article applies to.

This article applies to Microsoft Dynamics NAV for all countries and all language locales.

↑ Back to the top

Symptoms

Consider the following scenario in Microsoft Dynamics NAV 2009:
  • You have a customer ledger entry that uses foreign currency.
  • You partly apply the entry to another entry.
  • You run the Adjust Exchange Rates function on the foreign currency that the entry uses.
  • You unapply the customer ledger entry.
In this scenario, you receive the following error message:  
The latest transaction no. must be an application in cust. ledger entry no number.

This problem occurs in the following products:
  • Microsoft Dynamics NAV 2009 R2
  • Microsoft Dynamics NAV 2009 Service Pack 1 (SP1)

↑ Back to the top

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.

↑ Back to the top



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 AdjustCustomerLedgerEntry function in the Adjust Exchange Rates report (595) as follows:
    Existing code 1
    ...
    AdjAmount := AdjAmount + OldAdjAmount;
    TempDtldCustLedgEntry."Amount (LCY)" := -OldAdjAmount;
    TempDtldCustLedgEntry."Entry Type" := TempDtldCustLedgEntry."Entry Type"::"Unrealized Gain";
    HandleCustDebitCredit(
    Amount,"Amount (LCY)",Correction,TempDtldCustLedgEntry."Amount (LCY)");
    TempDtldCustLedgEntry.INSERT;
    NewEntryNo := NewEntryNo + 1;
    AdjExchRateBufferUpdate(
    "Currency Code",Customer."Customer Posting Group",

    // Delete the following line. 
    0,0,-OldAdjAmount,0,-OldAdjAmount,DimEntryNo,PostingDate2,Customer."IC Partner Code");

    Adjust := FALSE;
    END;
    END;
    END;
    END;
    IF OldAdjAmount < 0 THEN BEGIN
    ...
    Replacement code 1
    ...
    AdjAmount := AdjAmount + OldAdjAmount;
    TempDtldCustLedgEntry."Amount (LCY)" := -OldAdjAmount;
    TempDtldCustLedgEntry."Entry Type" := TempDtldCustLedgEntry."Entry Type"::"Unrealized Gain";
    HandleCustDebitCredit(
    Amount,"Amount (LCY)",Correction,TempDtldCustLedgEntry."Amount (LCY)");
    TempDtldCustLedgEntry.INSERT;
    NewEntryNo := NewEntryNo + 1;
    AdjExchRateBufferUpdate(
    "Currency Code",Customer."Customer Posting Group",

    // Add the following line. 
    0,0,-OldAdjAmount,-OldAdjAmount,0,DimEntryNo,PostingDate2,Customer."IC Partner Code");

    Adjust := FALSE;
    END;
    END;
    END;
    END;
    IF OldAdjAmount < 0 THEN BEGIN
    ...
    Existing code 2
    ...
    AdjAmount := OldAdjAmount + AdjAmount;
    TempDtldCustLedgEntry."Amount (LCY)" := -OldAdjAmount;
    TempDtldCustLedgEntry."Entry Type" := TempDtldCustLedgEntry."Entry Type"::"Unrealized Loss";
    HandleCustDebitCredit(
    Amount,"Amount (LCY)",Correction,TempDtldCustLedgEntry."Amount (LCY)");
    TempDtldCustLedgEntry.INSERT;
    NewEntryNo := NewEntryNo + 1;
    AdjExchRateBufferUpdate(
    "Currency Code",Customer."Customer Posting Group",

    // Delete the following line. 
    0,0,-OldAdjAmount,-OldAdjAmount,0,DimEntryNo,PostingDate2,Customer."IC Partner Code");
     
    Adjust := FALSE;
    END;
    END;
    END;
    END;
    IF NOT Adjust THEN BEGIN 
    ...
    Replacement code 2
    ...
    AdjAmount := OldAdjAmount + AdjAmount;
    TempDtldCustLedgEntry."Amount (LCY)" := -OldAdjAmount;
    TempDtldCustLedgEntry."Entry Type" := TempDtldCustLedgEntry."Entry Type"::"Unrealized Loss";
    HandleCustDebitCredit(
    Amount,"Amount (LCY)",Correction,TempDtldCustLedgEntry."Amount (LCY)");
    TempDtldCustLedgEntry.INSERT;
    NewEntryNo := NewEntryNo + 1;
    AdjExchRateBufferUpdate(
    "Currency Code",Customer."Customer Posting Group",

    // Add the following line. 
    0,0,-OldAdjAmount,0,-OldAdjAmount,DimEntryNo,PostingDate2,Customer."IC Partner Code");
     
    Adjust := FALSE;
    END;
    END;
    END;
    END;
    IF NOT Adjust THEN BEGIN
    ...
  2. Change the code in the FindLastTransactionNo function in the CustEntry-Apply Posted Entries codeunit (226) as follows:
    Existing code
    ...
    // Delete the following lines.
    DtldCustLedgEntry.SETCURRENTKEY("Cust. Ledger Entry No.","Entry Type");
    DtldCustLedgEntry.SETRANGE("Cust. Ledger Entry No.",CustLedgEntryNo);
    LastTransactionNo := 0;
    IF DtldCustLedgEntry.FIND('-') THEN
    REPEAT
    IF (DtldCustLedgEntry."Transaction No." > LastTransactionNo) AND NOT DtldCustLedgEntry.Unapplied THEN
    LastTransactionNo := DtldCustLedgEntry."Transaction No.";
    UNTIL DtldCustLedgEntry.NEXT = 0;
    EXIT(LastTransactionNo);
    // End of the lines. 
    ...
    Replacement code
    ...
    // Add the following lines. 
    WITH DtldCustLedgEntry DO BEGIN
    SETCURRENTKEY("Cust. Ledger Entry No.","Entry Type");
    SETRANGE("Cust. Ledger Entry No.",CustLedgEntryNo);
    SETRANGE(Unapplied,FALSE);
    SETFILTER("Entry Type",'<>%1&<>%2',"Entry Type"::"Unrealized Loss","Entry Type"::"Unrealized Gain");
    LastTransactionNo := 0;
    IF FINDSET THEN
    REPEAT
    IF LastTransactionNo < "Transaction No." THEN
    LastTransactionNo := "Transaction No.";
    UNTIL NEXT = 0;
    END;
    EXIT(LastTransactionNo);
    //End of the lines. 
    ...
  3. Change the code in the FindLastTransactionNo function in the VendEntry-Apply Posted Entries codeunit (227) as follows:
    Existing code
    ...
    // Delete the following lines.
    DtldVendLedgEntry.SETCURRENTKEY("Vendor Ledger Entry No.","Entry Type");
    DtldVendLedgEntry.SETRANGE("Vendor Ledger Entry No.",VendLedgEntryNo);
    LastTransactionNo := 0;
    IF DtldVendLedgEntry.FIND('-') THEN
    REPEAT
    IF (DtldVendLedgEntry."Transaction No." > LastTransactionNo) AND NOT DtldVendLedgEntry.Unapplied THEN
    LastTransactionNo := DtldVendLedgEntry."Transaction No.";
    UNTIL DtldVendLedgEntry.NEXT = 0;
    EXIT(LastTransactionNo);
    // End of the lines. 
    ...
    Replacement code
    ...
    // Add the following lines. 
    WITH DtldVendLedgEntry DO BEGIN
    SETCURRENTKEY("Vendor Ledger Entry No.","Entry Type");
    SETRANGE("Vendor Ledger Entry No.",VendLedgEntryNo);
    SETRANGE(Unapplied,FALSE);
    SETFILTER("Entry Type",'<>%1&<>%2',"Entry Type"::"Unrealized Loss","Entry Type"::"Unrealized Gain");
    LastTransactionNo := 0;
    IF FINDSET THEN
    REPEAT
    IF LastTransactionNo < "Transaction No." THEN
    LastTransactionNo := "Transaction No.";
    UNTIL NEXT = 0;
    END;
    EXIT(LastTransactionNo);
    //End of the lines. 
    ...

Prerequisites

You must have one of the following products installed to apply this hotfix:
  • Microsoft Dynamics NAV 2009 R2
  • Microsoft Dynamics NAV 2009 Service Pack 1

Removal information

You cannot remove this hotfix.

↑ Back to the top

Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top

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.

↑ Back to the top

Keywords: kberrmsg, kbmbscodefix, kbnoloc, kbsurveynew, kbqfe, kbmbspartner, kbmbsquickpub, kb, kbmbsmigrate

↑ Back to the top

Article Info
Article ID : 2525776
Revision : 4
Created on : 9/21/2018
Published on : 9/21/2018
Exists online : False
Views : 352