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. "You must not specify Applies to Id in Vendor Ledger entry No. [Number]" error message when you run the Suggest Vendor Payments report in Microsoft Dynamics NAV

"You must not specify Applies to Id in Vendor Ledger entry No. [Number]" error message when you run the Suggest Vendor Payments report in Microsoft Dynamics NAV

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. You stop running the Suggest Vendor Payments report. For example, a vendor has a different Pay-to number. You want to change the Pay-to number before you run the report. Then, you run the Suggest Vendor Payments report again. In this scenario, you receive the following error message:
You must not specify Applies to Id in Vendor Ledger entry No. Number.

This problem occurs in the following products:
  • Microsoft Dynamics NAV 2009 Service Pack 1
  • Microsoft Dynamics NAV 2009
  • Microsoft Dynamics NAV 5.0 Service Pack 1
  • Microsoft Dynamics NAV 5.0

↑ Back to the top

Cause

This problem occurs because the Applies-to ID field is not cleared for vendor ledger entries when you stop running the Suggest Vendor Payments report.

↑ 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, 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. Add the HideValidationDialog global variable as the Boolean type in the Gen. Journal Line table (81).
  2. Change the code in the Account No. - OnValidate trigger in the Gen. Journal Line table (81) as follows:
    Existing code
    ...
          "VAT Bus. Posting Group" := '';
          "VAT Prod. Posting Group" := '';
          IF (Vend."Pay-to Vendor No." <> '') AND (Vend."Pay-to Vendor No." <> "Account No.")  THEN BEGIN
            OK := CONFIRM(Text014,FALSE,Vend.TABLECAPTION,Vend."No.",Vend.FIELDCAPTION("Pay-to Vendor No."),
            Vend."Pay-to Vendor No.");
            IF NOT OK THEN
              ERROR('');
          END;
          VALIDATE("Payment Terms Code");
        END;
      "Account Type"::"Bank Account":
    ...
    Replacement code
    ...
          "VAT Bus. Posting Group" := '';
          "VAT Prod. Posting Group" := '';
          IF (Vend."Pay-to Vendor No." <> '') AND (Vend."Pay-to Vendor No." <> "Account No.") AND
            NOT HideValidationDialog
          THEN BEGIN
            OK := CONFIRM(Text014,FALSE,Vend.TABLECAPTION,Vend."No.",Vend.FIELDCAPTION("Pay-to Vendor No."),
            Vend."Pay-to Vendor No.");
            IF NOT OK THEN
              ERROR('');
          END;
          VALIDATE("Payment Terms Code");
        END;
      "Account Type"::"Bank Account":
    ...
  3. Add the SetHideValidation procedure in the Gen. Journal Line table (81). To do this, follow these steps:
    1. Add the NewHideValidationDialog local variable as the Boolean type.
    2. Add the code in the SetHideValidation procedure as follows:
      HideValidationDialog := NewHideValidationDialog;
  4. Add a text constant in the Suggest Vendor Payments report (393), and then specify the text constant as follows:
    • Name: Text025
    • ConstValue: 'ENU="The %1 %2 has a %3 %4. "
  5. Add a local variable in the MakeGenJnlLines function in the Suggest Vendor Payments report (393), and the specify the variable as follows:
    • Name:Vendor
    • DataType:Record
    • Length:23
  6. Change the code in the MakeGenJnlLines function in the Suggest Vendor Payments report (393) as follows:
    Existing code
    ...
                OldTempPaymentBuffer."Document No." := "Document No.";
              END;
            END;
          "Account Type" := "Account Type"::Vendor;
          VALIDATE("Account No.",TempPaymentBuffer."Vendor No.");
          "Bal. Account Type" := BalAccType;
          VALIDATE("Bal. Account No.",BalAccNo);
          VALIDATE("Currency Code",TempPaymentBuffer."Currency Code");
    ...
    Replacement code
    ...
                OldTempPaymentBuffer."Document No." := "Document No.";
              END;
            END;
          "Account Type" := "Account Type"::Vendor;
          SetHideValidation(TRUE);
          VALIDATE("Account No.",TempPaymentBuffer."Vendor No.");
          Vendor.GET(TempPaymentBuffer."Vendor No.");
          IF (Vendor."Pay-to Vendor No." <> '') AND (Vendor."Pay-to Vendor No." <> "Account No.") THEN
            MESSAGE(Text025,Vendor.TABLECAPTION,Vendor."No.",Vendor.FIELDCAPTION("Pay-to Vendor No."),
              Vendor."Pay-to Vendor No.");
          "Bal. Account Type" := BalAccType;
          VALIDATE("Bal. Account No.",BalAccNo);
          VALIDATE("Currency Code",TempPaymentBuffer."Currency Code");
    ...

Prerequisites

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

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

↑ Back to the top

Article Info
Article ID : 2275759
Revision : 2
Created on : 9/20/2018
Published on : 9/20/2018
Exists online : False
Views : 312