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.

The system incorrectly clears the Applied-to ID field when another user closes the Apply Vendor Entries dialog box 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 R2 and in Microsoft Dynamics NAV 2009 Service Pack 1 (SP1):
  • User 1 suggests a payment to a vendor by enabling the Summarize per Vendor setting in the Payment Journal dialog box. When User 1 does this, the system applies the payment to appropriate vendor leger entries.
  • User 2 opens the corresponding Vendor Ledger Entries dialog box and runs the Apply Vendor Entries function on one of the vendor entry lines that were applied to the payment before.
  • User 2 does not post the application and closes the Apply Vendor Entries dialog box.
In this scenario, the system incorrectly clears the Applied-to ID field of the vendor ledger entry in the Apply Vendor Entries dialog box.

↑ 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 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.

↑ 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. 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 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 Apply Vendor Entriesform (233). To do this, follow these steps:
    1. Change the code in the Form - OnQueryCloseForm trigger as follows:
      Existing code
      ...
      END;
      END;

      // Delete the following line.
      IF (CalcType = CalcType::Direct) AND NOT OK AND NOT PostingDone THEN BEGIN

      Rec := ApplyingVendLedgEntry;
      "Applying Entry" := FALSE;
      "Applies-to ID" := '';
      "Amount to Apply" := 0;
      CODEUNIT.RUN(CODEUNIT::"Vend. Entry-Edit",Rec);
      ...
      Replacement code
      ...
      END;
      END;

      // Add the following line.
      IF CheckActionPerformed THEN BEGIN

      Rec := ApplyingVendLedgEntry;
      "Applying Entry" := FALSE;

      // Add the following line.
      IF AppliesToID = '' THEN BEGIN

      "Applies-to ID" := '';
      "Amount to Apply" := 0;

      // Add the following line.
      END;

      CODEUNIT.RUN(CODEUNIT::"Vend. Entry-Edit",Rec);
      ...
    2. Add a global variable, and then specify the variable as follows:
      • Name: AppliesToID
      • DataType: Code[20]
    3. Add a global variable, and then specify the variable as follows:
      • Name: ActionPerformed
      • DataType: Boolean
    4. Change the code in the SetVendApplId function as follows:
      Existing code
      ...
      VendEntrySetApplID.SetApplId(VendLedgEntry,ApplyingVendLedgEntry,AppliedAmount,PmtDiscAmount,GenJnlLine."Applies-to ID")
      ELSE
      VendEntrySetApplID.SetApplId(VendLedgEntry,ApplyingVendLedgEntry,AppliedAmount,PmtDiscAmount,PurchHeader."Applies-to ID");
      CalcApplnAmount;
      ...
      Replacement code
      ...
      VendEntrySetApplID.SetApplId(VendLedgEntry,ApplyingVendLedgEntry,AppliedAmount,PmtDiscAmount,GenJnlLine."Applies-to ID")
      ELSE
      VendEntrySetApplID.SetApplId(VendLedgEntry,ApplyingVendLedgEntry,AppliedAmount,PmtDiscAmount,PurchHeader."Applies-to ID");

      // Add the following line.
      ActionPerformed := TRUE;

      CalcApplnAmount;
      ...
    5. Change the code in the CalcApplnAmount function as follows:
      Existing code
      ...
      AppliedVendLedgEntry.SETRANGE(Open,TRUE);

      // Delete the following line.
      AppliedVendLedgEntry.SETRANGE("Applies-to ID",VendEntryApplID);

      IF ApplyingVendLedgEntry."Entry No." <> 0 THEN BEGIN
      VendLedgEntry.CALCFIELDS("Remaining Amount");
      ...
      Replacement code
      ...
      AppliedVendLedgEntry.SETRANGE(Open,TRUE);

      // Add the following lines.
      IF AppliesToID = '' THEN
      AppliedVendLedgEntry.SETRANGE("Applies-to ID",VendEntryApplID)
      ELSE
      AppliedVendLedgEntry.SETRANGE("Applies-to ID",AppliesToID);
      // End of the added lines.

      IF ApplyingVendLedgEntry."Entry No." <> 0 THEN BEGIN
      VendLedgEntry.CALCFIELDS("Remaining Amount");
      ...
    6. Change the code in the FindApplyingEntry function as follows:
      Existing code
      ...
      VendLedgEntry.SETRANGE("Vendor No.","Vendor No.");

      // Delete the following line.
      VendLedgEntry.SETRANGE("Applies-to ID",VendEntryApplID);

      VendLedgEntry.SETRANGE(Open,TRUE);
      VendLedgEntry.SETRANGE("Applying Entry",TRUE);
      ...
      Replacement code
      ...
      VendLedgEntry.SETRANGE("Vendor No.","Vendor No.");

      // Add the following lines.
      IF AppliesToID = '' THEN
      VendLedgEntry.SETRANGE("Applies-to ID",VendEntryApplID)
      ELSE
      VendLedgEntry.SETRANGE("Applies-to ID",AppliesToID);
      // End of the added lines.

      VendLedgEntry.SETRANGE(Open,TRUE);
      VendLedgEntry.SETRANGE("Applying Entry",TRUE);
      ...
    7. Create a new function as follows:
      PROCEDURE CheckActionPerformed@1011() : Boolean;
      BEGIN
      IF ActionPerformed THEN
      EXIT(FALSE);
      IF NOT (CalcType = CalcType::Direct) AND NOT OK AND NOT PostingDone THEN
      EXIT(FALSE);
      EXIT(TRUE);
      END;
    8. Create a new function as follows:
      PROCEDURE SetAppliesToID@1031(AppliesToID2@1043 : Code[20]);
      BEGIN
      AppliesToID := AppliesToID2;
      END;
  2. Change the code in the ApplyVendEntryformEntry function in the VendEntry-Apply Posted Entries codeunit (227) as follows:
    Existing code
    ...
    ApplyingVendLedgEntry."Applying Entry" := TRUE;
    ApplyingVendLedgEntry."Applies-to ID" := VendEntryApplID;
    ApplyingVendLedgEntry."Amount to Apply" := ApplyingVendLedgEntry."Remaining Amount";
    CODEUNIT.RUN(CODEUNIT::"Vend. Entry-Edit",ApplyingVendLedgEntry);
    COMMIT;
    VendLedgEntry.SETCURRENTKEY("Vendor No.",Open,Positive);
    VendLedgEntry.SETRANGE("Vendor No.",ApplyingVendLedgEntry."Vendor No.");
    VendLedgEntry.SETRANGE(Open,TRUE);
    IF VendLedgEntry.FINDSET THEN BEGIN
    ApplyVendEntries.SetVendLedgEntry(ApplyingVendLedgEntry);
    ApplyVendEntries.SETRECORD(VendLedgEntry);
    ApplyVendEntries.SETTABLEVIEW(VendLedgEntry);
    OK := ApplyVendEntries.RUNMODAL = ACTION::LookupOK;
    ...
    Replacement code
    ...
    ApplyingVendLedgEntry."Applying Entry" := TRUE;

    // Add the following line.
    IF ApplyingVendLedgEntry."Applies-to ID" = '' THEN

    ApplyingVendLedgEntry."Applies-to ID" := VendEntryApplID;
    ApplyingVendLedgEntry."Amount to Apply" := ApplyingVendLedgEntry."Remaining Amount";
    CODEUNIT.RUN(CODEUNIT::"Vend. Entry-Edit",ApplyingVendLedgEntry);
    COMMIT;
    VendLedgEntry.SETCURRENTKEY("Vendor No.",Open,Positive);
    VendLedgEntry.SETRANGE("Vendor No.",ApplyingVendLedgEntry."Vendor No.");
    VendLedgEntry.SETRANGE(Open,TRUE);
    IF VendLedgEntry.FINDSET THEN BEGIN
    ApplyVendEntries.SetVendLedgEntry(ApplyingVendLedgEntry);
    ApplyVendEntries.SETRECORD(VendLedgEntry);
    ApplyVendEntries.SETTABLEVIEW(VendLedgEntry);

    // Add the following lines.
    IF ApplyingVendLedgEntry."Applies-to ID" <> VendEntryApplID THEN
    ApplyVendEntries.SetAppliesToID(ApplyingVendLedgEntry."Applies-to ID");
    // End of the added lines.

    OK := ApplyVendEntries.RUNMODAL = ACTION::LookupOK;
    ...
Note The provided solution only fixes the issue in the Apply Vendor Entries form (233). In order to transfer the solution into the corresponding page, you must use the Transformation Tool. For more information about how to use the Transformation Tool, view the Transforming Forms chapter in the Online Help of Microsoft Dynamics NAV 2009.



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

↑ Back to the top

Article Info
Article ID : 2677839
Revision : 1
Created on : 1/7/2017
Published on : 1/24/2013
Exists online : False
Views : 197