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 "Payment Discount %" field is zero in the sales order if you create the sales order from the customer card in Microsoft Dynamics NAV


View products that this article applies to.

RAPID PUBLISHING ARTICLES PROVIDE INFORMATION DIRECTLY FROM WITHIN THE MICROSOFT SUPPORT ORGANIZATION. THE INFORMATION THAT IS CONTAINED HEREIN IS CREATED IN RESPONSE TO EMERGING OR UNIQUE TOPICS, OR IS INTENDED TO SUPPLEMENT OTHER KNOWLEDGE BASE INFORMATION.

↑ Back to the top


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

↑ Back to the top


Symptoms

Consider the following scenario. There is a payment term code for the customer in Microsoft Dynamics NAV 2009. You create a sales order from the customer card. In this scenario, the "Payment Discount %" field in the header of the sales order is zero. Additionally, if you post the sales order later, no payment discount is calculated.

↑ 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 install this codefix, change the code in the Sales Header table (36) and in the Purchase Header table (38) as follows.

Note The following steps indicate changes that you have to make for the Sales Header table (36). Same changes have to be made for the Purchase Header table (38).
  1. Add a new global variable:

    Name: UpdateDocumentDate
    Data type: Boolean
  2. In the "Bill-to Customer No. - OnValidate()" function, change the code as follows.

    Existing code 1

    IF NOT SkipBillToContact THEN
    "Bill-to Contact" := Cust.Contact;
    "Payment Terms Code" := Cust."Payment Terms Code";
    IF "Document Type" = "Document Type"::"Credit Memo" THEN BEGIN
    Replacement code 1

    IF NOT SkipBillToContact THEN
    "Bill-to Contact" := Cust.Contact;
    "Payment Terms Code" := Cust."Payment Terms Code";
    "Prepmt. Payment Terms Code" := Cust."Payment Terms Code";
    IF "Document Type" = "Document Type"::"Credit Memo" THEN BEGIN
    Existing code 2

    DATABASE::"Customer Template","Bill-to Customer Template Code");
    VALIDATE("Payment Terms Code");
    VALIDATE("Payment Method Code");
    VALIDATE("Currency Code");
    IF (xRec."Sell-to Customer No." = "Sell-to Customer No.") AND
    Replacement code 2

    DATABASE::"Customer Template","Bill-to Customer Template Code");
    VALIDATE("Payment Terms Code");
    VALIDATE("Prepmt. Payment Terms Code");
    VALIDATE("Payment Method Code");
    VALIDATE("Currency Code");
    IF (xRec."Sell-to Customer No." = "Sell-to Customer No.") AND
  3. In the "Payment Terms Code - OnValidate()" function, change the code as follows.

    Existing code
    IF ("Payment Terms Code" <> '') AND ("Document Date" <> 0D) THEN BEGIN
    PaymentTerms.GET("Payment Terms Code");
    IF (("Document Type" IN ["Document Type"::"Return Order","Document Type"::"Credit Memo"]) AND
    NOT PaymentTerms."Calc. Pmt. Disc. on Cr. Memos")
    THEN BEGIN
    VALIDATE("Due Date","Document Date");
    VALIDATE("Pmt. Discount Date",0D);
    VALIDATE("Payment Discount %",0);
    END ELSE BEGIN
    "Due Date" := CALCDATE(PaymentTerms."Due Date Calculation","Document Date");
    "Pmt. Discount Date" := CALCDATE(PaymentTerms."Discount Date Calculation","Document Date");
    IF xRec."Document Date"="Document Date" THEN
    VALIDATE("Payment Discount %",PaymentTerms."Discount %")
    END;
    END ELSE BEGIN
    VALIDATE("Due Date","Document Date");
    IF xRec."Document Date"="Document Date" THEN BEGIN
    VALIDATE("Pmt. Discount Date",0D);
    VALIDATE("Payment Discount %",0);
    END;
    Replacement code
    IF ("Payment Terms Code" <> '') AND ("Document Date" <> 0D) THEN BEGIN
    PaymentTerms.GET("Payment Terms Code");
    IF (("Document Type" IN ["Document Type"::"Return Order","Document Type"::"Credit Memo"]) AND
    NOT PaymentTerms."Calc. Pmt. Disc. on Cr. Memos")
    THEN BEGIN
    VALIDATE("Due Date","Document Date");
    VALIDATE("Pmt. Discount Date",0D);
    VALIDATE("Payment Discount %",0);
    END ELSE BEGIN
    "Due Date" := CALCDATE(PaymentTerms."Due Date Calculation","Document Date");
    "Pmt. Discount Date" := CALCDATE(PaymentTerms."Discount Date Calculation","Document Date");
    IF NOT UpdateDocumentDate THEN
    VALIDATE("Payment Discount %",PaymentTerms."Discount %")
    END;
    END ELSE BEGIN
    VALIDATE("Due Date","Document Date");
    IF NOT UpdateDocumentDate THEN BEGIN
    VALIDATE("Pmt. Discount Date",0D);
    VALIDATE("Payment Discount %",0);
    END;
  4. In the "Document Date - OnValidate()" function, change the code as follows.

    Existing code
    VALIDATE("Payment Terms Code");
    VALIDATE("Prepmt. Payment Terms Code");
    Replacement code
    IF xRec."Document Date" <> "Document Date" THEN
    UpdateDocumentDate := TRUE;
    VALIDATE("Payment Terms Code");
    VALIDATE("Prepmt. Payment Terms Code");
  5. In the "Prepmt. Payment Terms Code - OnValidate()" function, change the code as follows.

    Existing code

    END ELSE BEGIN
    "Prepayment Due Date" := CALCDATE(PaymentTerms."Due Date Calculation","Document Date");
    "Prepmt. Pmt. Discount Date" := CALCDATE(PaymentTerms."Discount Date Calculation","Document Date");
    VALIDATE("Prepmt. Payment Discount %",PaymentTerms."Discount %")
    END;
    END ELSE BEGIN
    VALIDATE("Prepayment Due Date","Document Date");
    VALIDATE("Prepmt. Pmt. Discount Date",0D);
    VALIDATE("Prepmt. Payment Discount %",0);
    END;
    Replacement code

    END ELSE BEGIN
    "Prepayment Due Date" := CALCDATE(PaymentTerms."Due Date Calculation","Document Date");
    "Prepmt. Pmt. Discount Date" := CALCDATE(PaymentTerms."Discount Date Calculation","Document Date");
    IF NOT UpdateDocumentDate THEN
    VALIDATE("Prepmt. Payment Discount %",PaymentTerms."Discount %")
    END;
    END ELSE BEGIN
    VALIDATE("Prepayment Due Date","Document Date");
    IF NOT UpdateDocumentDate THEN BEGIN
    VALIDATE("Prepmt. Pmt. Discount Date",0D);
    VALIDATE("Prepmt. Payment Discount %",0);
    END;
    END;

Prerequisites

To install this codefix, you must have one of the following products installed:
  • Microsoft Dynamics NAV 5.0 Service Pack 1 (SP1)
  • Microsoft Dynamics NAV 2009
  • Microsoft Dynamics NAV SP1

Restart information

You do not have to restart the computer after you apply this codefix.

↑ 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


More Information

MICROSOFT AND/OR ITS SUPPLIERS MAKE NO REPRESENTATIONS OR WARRANTIES ABOUT THE SUITABILITY, THE RELIABILITY OR THE ACCURACY OF THE INFORMATION THAT IS CONTAINED IN THE DOCUMENTS AND THE RELATED GRAPHICS PUBLISHED ON THIS WEB SITE (THE “MATERIALS”) FOR ANY PURPOSE.

THE MATERIALS MAY INCLUDE TECHNICAL INACCURACIES OR TYPOGRAPHICAL ERRORS AND MAY BE REVISED AT ANY TIME WITHOUT NOTICE. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, MICROSOFT AND/OR ITS SUPPLIERS DISCLAIM AND EXCLUDE ALL REPRESENTATIONS, WARRANTIES, AND CONDITIONS WHETHER EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO REPRESENTATIONS, WARRANTIES, OR CONDITIONS OF TITLE, NON-INFRINGEMENT, SATISFACTORY CONDITION OR QUALITY, MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE, WITH RESPECT TO THE MATERIALS.

↑ Back to the top


Keywords: kbmbsquickpub, kbnoloc, kbmbscodefix, kbqfe, kbnotautohotfix, kbmbspartner, kbsurveynew, kbmbssalesandreceivables, kb, kbmbsmigrate

↑ Back to the top

Article Info
Article ID : 980494
Revision : 2
Created on : 9/21/2018
Published on : 9/21/2018
Exists online : False
Views : 334