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.

You cannot run the "Post or Correct Postponed VAT" function on a sales credit memo if the Use Postponed VAT check box is selected in the General Ledger Setup dialog box in the Polish version of Microsoft Dynamics NAV 5.0 Service Pack 1


This article applies to Microsoft Dynamics NAV for the Polish (pl) language locale.

↑ Back to the top


Symptoms

When you select the Use Postponed VAT check box in the General Ledger Setup dialog box in the Polish version of Microsoft Dynamics NAV 5.0 Service Pack 1 (SP1), you experience the following issues:
  • Assume that you create a sale credit memo that has the Postponed VAT check box selected. In this situation, when you run the Post or Correct Postponed VAT function on the sales credit memo, you receive the following error message:
    Use Postponed VAT must be Yes in General Ledger Setup Primary Key=''.
  • Assume that you create a sale credit memo that has the Postponed VAT check box cleared. In this situation, when you run the Post or Correct Postponed VAT function on the sales credit memo, you receive the following error message:
    You cannot post Postponed VAT because it has already been posted.

    Additionally, when you run the Postpone VAT function on the sales credit memo in the VAT Application Worksheet dialog box, you receive the following error message:
    VAT Amount must not be 0 in VAT Entry Entry No.='entry number'.

↑ 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. Change the code in the InitRecord function in the Sales Header table (36) as follow:
    Existing code
    ...
    IF "Document Type" IN ["Document Type"::"Return Order","Document Type"::"Credit Memo"] THEN BEGIN
    Correction := GLSetup."Mark Cr. Memos as Corrections";

    // Delete the following line.
    "Postponed VAT" := GLSetup."Sales Cr. Memo Confirmation";

    END;

    "Posting Description" := FORMAT("Document Type") + ' ' + "No.";
    ...
    Replacement code
    ...
    IF "Document Type" IN ["Document Type"::"Return Order","Document Type"::"Credit Memo"] THEN BEGIN
    Correction := GLSetup."Mark Cr. Memos as Corrections";

    // Add the following line.
    "Postponed VAT" := GLSetup."Use Postponed VAT";

    END;

    "Posting Description" := FORMAT("Document Type") + ' ' + "No.";
    ...
  2. Change the code in the controls in the General Ledger Setup form (118) as follow:
    Existing code
    ...
    ShowCaption=No;
    SourceExpr="Allow VAT Date Change in Lines" }
    { 1470021;Label ;440 ;2640 ;3300 ;440 ;ParentControl=1470020 }

    // Delete the following lines.
    { 1470028;CheckBox ;3850 ;3190 ;440 ;440 ;ParentControl=1;
    InPage=5;
    ShowCaption=No;
    SourceExpr="Sales Cr. Memo Confirmation" }
    { 1470029;Label ;440 ;3190 ;3300 ;440 ;ParentControl=1470028 }
    // End of the lines.

    { 1470026;TextBox ;3850 ;3850 ;2750 ;440 ;ParentControl=1;
    InPage=5;
    SourceExpr="Default Purchase VAT Date" }
    ...
    Replacement code
    ...
    ShowCaption=No;
    SourceExpr="Allow VAT Date Change in Lines" }
    { 1470021;Label ;440 ;2640 ;3300 ;440 ;ParentControl=1470020 }
    { 1470026;TextBox ;3850 ;3850 ;2750 ;440 ;ParentControl=1;
    InPage=5;
    SourceExpr="Default Purchase VAT Date" }
    ...
  3. Change the code in the PostponeVATEntry function in the VATManagement codeunit (12376) as follow:
    Existing code
    ...
    VATEntry.TESTFIELD(Reversed,FALSE);
    VATEntry.TESTFIELD("Postponed VAT",FALSE);
    VATEntry.TESTFIELD("Unrealized VAT Entry No.",0);

    // Delete the following line.
    IF GLSetup."Sales Cr. Memo Confirmation" AND NOT AllowSalesCrMemo AND

    (VATEntry."Unrealized Base" <> 0) AND (VATEntry.Type = VATEntry.Type::Sale) AND
    (VATEntry."Document Type" = VATEntry."Document Type"::"Credit Memo")
    THEN
    ...
    Replacement code
    ...
    VATEntry.TESTFIELD(Reversed,FALSE);
    VATEntry.TESTFIELD("Postponed VAT",FALSE);
    VATEntry.TESTFIELD("Unrealized VAT Entry No.",0);

    // Add the following line.
    IF GLSetup."Use Postponed VAT" AND NOT AllowSalesCrMemo AND

    (VATEntry."Unrealized Base" <> 0) AND (VATEntry.Type = VATEntry.Type::Sale) AND
    (VATEntry."Document Type" = VATEntry."Document Type"::"Credit Memo")
    THEN
    ...
  4. Change the code in the RealizeVATEntry function in the VATManagement codeunit (12376) as follow:
    Existing code
    ...
    VATEntry.TESTFIELD(Reversed,FALSE);
    VATEntry.TESTFIELD("Postponed VAT",TRUE);
    VATEntry.TESTFIELD("Unrealized VAT Entry No.",0);

    // Delete the following line.
    IF GLSetup."Sales Cr. Memo Confirmation" AND NOT AllowSalesCrMemo AND

    (VATEntry."Unrealized Base" <> 0) AND (VATEntry.Type = VATEntry.Type::Sale) AND
    (VATEntry."Document Type" = VATEntry."Document Type"::"Credit Memo")
    THEN
    ...
    Replacement code
    ...
    VATEntry.TESTFIELD(Reversed,FALSE);
    VATEntry.TESTFIELD("Postponed VAT",TRUE);
    VATEntry.TESTFIELD("Unrealized VAT Entry No.",0);

    // Add the following line.
    IF GLSetup."Use Postponed VAT" AND NOT AllowSalesCrMemo AND

    (VATEntry."Unrealized Base" <> 0) AND (VATEntry.Type = VATEntry.Type::Sale) AND
    (VATEntry."Document Type" = VATEntry."Document Type"::"Credit Memo")
    THEN
    ...

Prerequisites

You must have the Polish version of Microsoft Dynamics NAV 5.0 Service Pack 1 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 Use for other considerations.

↑ Back to the top


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

↑ Back to the top

Article Info
Article ID : 2495886
Revision : 1
Created on : 1/7/2017
Published on : 8/5/2011
Exists online : False
Views : 99