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. Prepmt. VAT Amount Inv. (LCY) field is missing after you upgrade from Microsoft Dynamics NAV 2009 to Dynamics NAV 2013

Prepmt. VAT Amount Inv. (LCY) field is missing after you upgrade from Microsoft Dynamics NAV 2009 to Dynamics NAV 2013

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

When you upgrade from Microsoft Dynamics NAV 2009 to Dynamics NAV 2013, the Prepmt. VAT Amount Inv. (LCY) field is missing in the sales and purchase lines. If a prepayment invoice is posted before the upgrade and you try to create a credit memo for the prepayment invoice, you receive an inconsistency message when posting the prepayment credit memo.

↑ 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 2013 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 Dynamics NAV client users are logged off the system. This includes Microsoft Dynamics NAV Application Server (NAS) services. 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 Upgrade function in the Upgrade New Version Codeunit (104048) as follows:
    Existing code
    ...
    UpdateItemLedgerEntry(StateIndicator);
          UpdateDOCreditCard(StateIndicator);
          UpdateSalesOrderDate(StateIndicator);
          UpdateOutlookSynchFilter(StateIndicator);
          UpdateOutlookSynchField(StateIndicator);
          DeleteRemovedPermissions(StateIndicator);
    ...
    Replacement code
    ...
    UpdateItemLedgerEntry(StateIndicator);
          UpdateDOCreditCard(StateIndicator);
          UpdateSalesOrderDate(StateIndicator);

    // Add the following lines.
          UpdateSalesLines(StateIndicator);
          UpdatePurchLines(StateIndicator);
    // End of the added lines.

          UpdateOutlookSynchFilter(StateIndicator);
          UpdateOutlookSynchField(StateIndicator);
          DeleteRemovedPermissions(StateIndicator);
    ...
  2. Add the following functions: 
    LOCAL PROCEDURE UpdateSalesLines@62(VAR StateIndicator@1000 : Record 104037);
    VAR
          SalesLine@1001 : Record 37;
          LastDocumentNo@1002 : Code[20];
          PrepmtInvReminderAmount@1003 : Decimal;
        BEGIN
          WITH SalesLine DO
            IF StateIndicator.UpdateTable(TABLENAME) THEN BEGIN
              TimeLog.TimeLogInsert(TimeLog,TABLENAME,TRUE);
              SETCURRENTKEY("Document Type","Document No.","Line No.");
              IF FINDSET THEN
                REPEAT
                  StateIndicator.Update;
                  IF ("Document Type" = "Document Type"::Order) AND ("Prepayment Amount" <> "Prepmt. Amt. Incl. VAT") THEN BEGIN
                    IF "Document No." <> LastDocumentNo THEN BEGIN
                      LastDocumentNo := "Document No.";
                      PrepmtInvReminderAmount := 0;
                    END;
                    IF ("Prepmt. Amount Inv. (LCY)" <> 0) AND ("Prepmt. VAT Amount Inv. (LCY)" = 0) THEN BEGIN
                      "Prepmt. VAT Amount Inv. (LCY)" :=
                        CalcRndedAmount("Prepmt. Amount Inv. (LCY)","Prepayment VAT %" / 100,PrepmtInvReminderAmount);
                      MODIFY;
                    END;
                  END;
                UNTIL NEXT = 0;
              TimeLog.TimeLogInsert(TimeLog,TABLENAME,FALSE);
              StateIndicator.EndUpdateTable(TABLENAME);
            END;

    LOCAL PROCEDURE UpdatePurchLines@63(VAR StateIndicator@1000 : Record 104037);
        VAR
          PurchaseLine@1001 : Record 39;
          LastDocumentNo@1002 : Code[20];
          PrepmtInvReminderAmount@1003 : Decimal;
        BEGIN
          WITH PurchaseLine DO
            IF StateIndicator.UpdateTable(TABLENAME) THEN BEGIN
              TimeLog.TimeLogInsert(TimeLog,TABLENAME,TRUE);
              IF FINDSET THEN
                REPEAT
                  StateIndicator.Update;
                  IF ("Document Type" = "Document Type"::Order) AND ("Prepayment Amount" <> "Prepmt. Amt. Incl. VAT") THEN BEGIN
                    IF "Document No." <> LastDocumentNo THEN BEGIN
                      LastDocumentNo := "Document No.";
                      PrepmtInvReminderAmount := 0;
                    END;
                    IF ("Prepmt. Amount Inv. (LCY)" <> 0) AND ("Prepmt. VAT Amount Inv. (LCY)" = 0) THEN BEGIN
                      "Prepmt. VAT Amount Inv. (LCY)" :=
                        CalcRndedAmount("Prepmt. Amount Inv. (LCY)","Prepayment VAT %" / 100,PrepmtInvReminderAmount);
                      MODIFY;
                    END;
                  END;
                UNTIL NEXT = 0;
              TimeLog.TimeLogInsert(TimeLog,TABLENAME,FALSE);
              StateIndicator.EndUpdateTable(TABLENAME);
            END;

    LOCAL PROCEDURE CalcRndedAmount@64(LineAmount@1000 : Decimal;Ratio@1001 : Decimal;VAR Reminder@1002 : Decimal) RndedAmount : Decimal;
        VAR
          Amount@1003 : Decimal;
        BEGIN
          Amount := Reminder + LineAmount * Ratio;
          RndedAmount := ROUND(Amount);
          Reminder := Amount - RndedAmount;
        END;

Prerequisites

You must have Microsoft Dynamics NAV 2013 installed to apply this hotfix.

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 Usefor other considerations.

↑ Back to the top

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

↑ Back to the top

Article Info
Article ID : 2923212
Revision : 1
Created on : 1/7/2017
Published on : 1/14/2014
Exists online : False
Views : 207