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 value in the "Remaining Amount" field in the ledger entry that is created for an invoice is incorrect even though you apply hotfix 975264 in Microsoft Dynamics NAV 2009

The value in the "Remaining Amount" field in the ledger entry that is created for an invoice is incorrect even though you apply hotfix 975264 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 apply hotfix 975264.
    For more information about hotfix 975264, click the following article number to view the article in the Microsoft Knowledge Base:
    975264 The value in the "Remaining Amount" field in the ledger entry that is created for a payment is incorrect in Microsoft Dynamics NAV
  • You enter a value in the Appln. Rounding Precision field on the Application tab in the General Ledger Setup dialog box.
  • You post a sales invoice.
  • You post a cash receipt journal for the sales invoice.
In this scenario, the value in the Remaining Amount field in the corresponding ledger entry is incorrect. No value should be displayed in the Remaining Amount field.
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 PostCust trigger in the Gen. Jnl. -Post Line codeunit (12) as follows:
    Existing code
    ...
    // Post the application
    ApplyCustLedgEntry(

    // Delete the following line.
    CVLedgEntryBuf,DtldCVLedgEntryBuf,GenJnlLine,GLSetup."Appln. Rounding Precision");

    // Post customer entry
    ...
    Replacement code
    ...
    // Post the application
    ApplyCustLedgEntry(

    // Add the following line.
    CVLedgEntryBuf,DtldCVLedgEntryBuf,GenJnlLine);

    // Post customer entry
    ...
  2. Change the code in the PostVend trigger in the Gen. Jnl. -Post Line codeunit (12) as follows:
    Existing code
    ...
    // Post the application
    ApplyVendLedgEntry(

    // Delete the following lines.
    CVLedgEntryBuf,DtldCVLedgEntryBuf,GenJnlLine, 
    GLSetup."Appln. Rounding Precision");
    // End of the lines.

    // Post Vendor entry
    ...
    Replacement code
    ...
    // Post the application
    ApplyVendLedgEntry(

    // Add the following line.
    CVLedgEntryBuf,DtldCVLedgEntryBuf,GenJnlLine); 

    // Post Vendor entry
    ...
  3. Add a new local parameter in the ApplyCustLedgEntry function in the Gen. Jnl. -Post Line codeunit (12), and then specify the parameter as follows:
    • Var: No
    • Name: ApplnRoundingPrecision
    • DataType: Decimal
  4. Add a new local variable in the ApplyCustLedgEntry function in the Gen. Jnl. -Post Line codeunit (12), and then specify the variable as follows:
    • Name: ApplnRoundingPrecision
    • DataType: Decimal
  5. Change the code in the ApplyCustLedgEntry function in the Gen. Jnl. -Post Line codeunit (12) as follows:
    Existing code 1
    ...
    NewCVLedgEntryBuf2 := NewCVLedgEntryBuf;

    // Delete the following lines.
    IF NewCVLedgEntryBuf."Currency Code" <> '' THEN BEGIN 
    Management of application of already posted entries 
    IF NewCVLedgEntryBuf."Currency Code" <> ApplnCurrency.Code THEN 
    ApplnCurrency.GET(NewCVLedgEntryBuf."Currency Code"); 
    ApplnRoundingPrecision := ApplnCurrency."Appln. Rounding Precision"; 
    END ELSE 
    ApplnRoundingPrecision := GLSetup."Appln. Rounding Precision"; 
    // End of the lines.

    ApplyingDate := GenJnlLine."Posting Date";

    IF GenJnlLine."Applies-to Doc. No." <> '' THEN BEGIN
    ...
    Replacement code 1
    ...
    NewCVLedgEntryBuf2 := NewCVLedgEntryBuf;

    ApplyingDate := GenJnlLine."Posting Date";

    IF GenJnlLine."Applies-to Doc. No." <> '' THEN BEGIN
    ...
    Existing code 2
    ...
    // Management of posting in multiple currencies
    OldCVLedgEntryBuf2 := OldCVLedgEntryBuf;
    OldCVLedgEntryBuf.COPYFILTER(Positive,OldCVLedgEntryBuf2.Positive);

    IF NewCVLedgEntryBuf."Currency Code" <> OldCVLedgEntryBuf2."Currency Code" THEN BEGIN

    ...
    Replacement code 2
    ...
    // Management of posting in multiple currencies
    OldCVLedgEntryBuf2 := OldCVLedgEntryBuf;
    OldCVLedgEntryBuf.COPYFILTER(Positive,OldCVLedgEntryBuf2.Positive);

    // Add the following line.
    GetApplnRoundPrecision(ApplnRoundingPrecision,NewCVLedgEntryBuf,OldCVLedgEntryBuf); 

    IF NewCVLedgEntryBuf."Currency Code" <> OldCVLedgEntryBuf2."Currency Code" THEN BEGIN
    ...
  6. Change the code in the CustPostApplyCustLedgEntry function in the Gen. Jnl. -Post Line codeunit (12) as follows:
    Existing code
    ...
    // Post the application
    CustLedgEntry.CALCFIELDS(
    Amount,"Amount (LCY)","Remaining Amount","Remaining Amt. (LCY)",
    "Original Amount","Original Amt. (LCY)");
    TransferCustLedgEntry(CVLedgEntryBuf,CustLedgEntry,TRUE);
    ApplyCustLedgEntry(

    // Delete the following line.
    CVLedgEntryBuf,DtldCVLedgEntryBuf,GenJnlLine,GLSetup."Appln. Rounding Precision");

    TransferCustLedgEntry(CVLedgEntryBuf,CustLedgEntry,FALSE);
    CustLedgEntry.MODIFY;
    ...
    Replacement code
    ...
    // Post the application
    CustLedgEntry.CALCFIELDS(
    Amount,"Amount (LCY)","Remaining Amount","Remaining Amt. (LCY)",
    "Original Amount","Original Amt. (LCY)");
    TransferCustLedgEntry(CVLedgEntryBuf,CustLedgEntry,TRUE);
    ApplyCustLedgEntry(

    // Add the following line.
    CVLedgEntryBuf,DtldCVLedgEntryBuf,GenJnlLine);

    TransferCustLedgEntry(CVLedgEntryBuf,CustLedgEntry,FALSE);
    CustLedgEntry.MODIFY;
    ...
  7. Add a new local parameter in the ApplyVendLedgEntry function in the Gen. Jnl. -Post Line codeunit (12), and then specify the parameter as follows:
    • Var: No
    • Name: ApplnRoundingPrecision
    • DataType: Decimal
  8. Add a new local variable in the ApplyVendLedgEntry function in the Gen. Jnl. -Post Line codeunit (12), and then specify the variable as follows:
    • Name: ApplnRoundingPrecision
    • DataType: Decimal
  9. Change the code in the ApplyVendLedgEntry function in the Gen. Jnl. -Post Line codeunit (12) as follows:
    Existing code 1
    ...
    NewCVLedgEntryBuf2 := NewCVLedgEntryBuf;

    // Delete the following lines.
    IF NewCVLedgEntryBuf."Currency Code" <> '' THEN BEGIN
    // Management of application of already posted entries
    IF NewCVLedgEntryBuf."Currency Code" <> ApplnCurrency.Code THEN 
    ApplnCurrency.GET(NewCVLedgEntryBuf."Currency Code");
    ApplnRoundingPrecision := ApplnCurrency."Appln. Rounding Precision";
    END ELSE 
    ApplnRoundingPrecision := GLSetup."Appln. Rounding Precision"; 
    // End of the lines.

    ApplyingDate := GenJnlLine."Posting Date";

    IF GenJnlLine."Applies-to Doc. No." <> '' THEN BEGIN
    ...
    Replacement code 1
    ...
    NewCVLedgEntryBuf2 := NewCVLedgEntryBuf;

    ApplyingDate := GenJnlLine."Posting Date";

    IF GenJnlLine."Applies-to Doc. No." <> '' THEN BEGIN
    ...
    Existing code 2
    ...
    // Management of posting in multiple currencies
    OldCVLedgEntryBuf2 := OldCVLedgEntryBuf;
    OldCVLedgEntryBuf.COPYFILTER(Positive,OldCVLedgEntryBuf2.Positive);

    IF NewCVLedgEntryBuf."Currency Code" <> OldCVLedgEntryBuf2."Currency Code" THEN BEGIN
    ...
    Replacement code 2
    ...
    // Management of posting in multiple currencies
    OldCVLedgEntryBuf2 := OldCVLedgEntryBuf;
    OldCVLedgEntryBuf.COPYFILTER(Positive,OldCVLedgEntryBuf2.Positive);

    // Add the following line.
    GetApplnRoundPrecision(ApplnRoundingPrecision,NewCVLedgEntryBuf,OldCVLedgEntryBuf);

    IF NewCVLedgEntryBuf."Currency Code" <> OldCVLedgEntryBuf2."Currency Code" THEN BEGIN
    ...
  10. Change the code in the VendPostApplyVendLedgEntry function in the Gen. Jnl. -Post Line codeunit (12) as follows:
    Existing code
    ...
    // Post the application
    VendLedgEntry.CALCFIELDS(
    Amount,"Amount (LCY)","Remaining Amount","Remaining Amt. (LCY)",
    "Original Amount","Original Amt. (LCY)");
    TransferVendLedgEntry(CVLedgEntryBuf,VendLedgEntry,TRUE);
    ApplyVendLedgEntry(

    // Delete the following line.
    CVLedgEntryBuf,DtldCVLedgEntryBuf,GenJnlLine,GLSetup."Appln. Rounding Precision");

    TransferVendLedgEntry(CVLedgEntryBuf,VendLedgEntry,FALSE);
    ...
    Replacement code
    ...
    // Post the application
    VendLedgEntry.CALCFIELDS(
    Amount,"Amount (LCY)","Remaining Amount","Remaining Amt. (LCY)",
    "Original Amount","Original Amt. (LCY)");
    TransferVendLedgEntry(CVLedgEntryBuf,VendLedgEntry,TRUE);
    ApplyVendLedgEntry(

    // Add the following line.
    CVLedgEntryBuf,DtldCVLedgEntryBuf,GenJnlLine);

    TransferVendLedgEntry(CVLedgEntryBuf,VendLedgEntry,FALSE);
    ...
  11. Create a new GetApplnRoundPrecision funtion in the Gen. Jnl. -Post Line codeunit (12). To create the function, follow these steps:
    1. Add a new local parameter in the GetApplnRoundPrecision funtion in the Gen. Jnl. -Post Line codeunit (12), and then specify the parameter as follows:
      • Var: Yes
      • Name: ApplnRoundingPrecision
      • DataType: Decimal
    2. Add a new local parameter in the GetApplnRoundPrecision funtion in the Gen. Jnl. -Post Line codeunit (12), and then specify the parameter as follows:
      • Var: No
      • Name: NewCVLedgEntryBuf
      • DataType: Record
      • Subtype: CV Ledger Entry Buffer
    3. Add a new local parameter in the GetApplnRoundPrecision funtion in the Gen. Jnl. -Post Line codeunit (12), and then specify the parameter as follows:
      • Var: No
      • Name: OldCVLedgEntryBuf
      • DataType: Record
      • Subtype: CV Ledger Entry Buffer
    4. Add a new local variable in the GetApplnRoundPrecision funtion in the Gen. Jnl. -Post Line codeunit (12), and then specify the variable as follows:
      • Name: CurrencyExistInledger
      • DataType: Boolean
    5. Add a new local variable in the GetApplnRoundPrecision funtion in the Gen. Jnl. -Post Line codeunit (12), and then specify the variable as follows:
      • Name: CurrencyCode
      • DataType: Code
      • Length: 20
    6. Add the following code in the GetApplnRoundPrecision funtion in the Gen. Jnl. -Post Line codeunit (12): 
      IF NewCVLedgEntryBuf."Currency Code" <> '' THEN
      CurrencyCode := NewCVLedgEntryBuf."Currency Code"
      ELSE
      CurrencyCode := OldCVLedgEntryBuf."Currency Code";
      IF CurrencyCode <> ApplnCurrency.Code THEN
      CurrencyExistInledger := ApplnCurrency.GET(CurrencyCode);

      IF CurrencyExistInledger THEN BEGIN
      IF ApplnCurrency."Appln. Rounding Precision" <> 0 THEN
      ApplnRoundingPrecision := ApplnCurrency."Appln. Rounding Precision"
      ELSE
      ApplnRoundingPrecision := GLSetup."Appln. Rounding Precision";
      END;

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 (SP1)

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: kbmbscodefix, kbnoloc, kbsurveynew, kbqfe, kbmbspartner, kbmbsquickpub, kb, kbmbsmigrate

↑ Back to the top

Article Info
Article ID : 2564237
Revision : 4
Created on : 9/20/2018
Published on : 9/20/2018
Exists online : False
Views : 240