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. The system creates incorrect VAT entries when you post a purchase VAT protocol in the Bulgarian version of Microsoft Dynamics NAV 2009 R2

The system creates incorrect VAT entries when you post a purchase VAT protocol in the Bulgarian version of Microsoft Dynamics NAV 2009 R2

View products that this article applies to.

This article applies to Microsoft Dynamics NAV for the Bulgarian (bg) language locale.

↑ Back to the top

Symptoms

When you post a purchase value-added tax (VAT) protocol in the Bulgarian version of Microsoft Dynamics NAV 2009 R2, the system creates incorrect VAT entries.

↑ 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 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 RunCheck function in the Gen. Jnl.-Check Line codeunit (11) as follows:
    Existing code
    ...
    ERROR(
    Text16200,
    FIELDCAPTION("Bal. Account No."),FIELDCAPTION("VAT Protocol"),"VAT Protocol");
     
    // Delete the following lines. 
    TESTFIELD("Gen. Posting Type",GenJnlLine."Gen. Posting Type"::Sale);
    IF "Bal. Gen. Posting Type" <> 0 THEN
    TESTFIELD("Bal. Gen. Posting Type","Bal. Gen. Posting Type"::Purchase);
    // End of the deleted lines.
     
    END;
    IF "Account No." <> '' THEN
    ...
    Replacement code
    ...
    ERROR(
    Text16200,
    FIELDCAPTION("Bal. Account No."),FIELDCAPTION("VAT Protocol"),"VAT Protocol");
     
    // Add the following lines. 
    TESTFIELD("Gen. Posting Type",GenJnlLine."Gen. Posting Type"::Sale);
    IF "Bal. Gen. Posting Type" <> 0 THEN
    TESTFIELD("Bal. Gen. Posting Type","Bal. Gen. Posting Type"::Purchase);
    // End of the added lines. 
     
    END;
    IF "Account No." <> '' THEN
    ...
  2. Change the code in the InsertVAT function in the Gen. Jnl.-Post Line codeunit (12) as follows:
    Existing code
    ...
    VATEntry."No. Series" := "Posting No. Series";
    VATEntry."VAT Base Discount %" := "VAT Base Discount %";
    VATEntry."Bill-to/Pay-to No." := "Bill-to/Pay-to No.";
    IF "Bill-to/Pay-to No." <> '' THEN
    CASE VATEntry.Type OF
    VATEntry.Type::Purchase:
    BEGIN
    IF Vend."No." <> "Bill-to/Pay-to No." THEN
    Vend.GET("Bill-to/Pay-to No.");
    VATEntry."Country/Region Code" := Vend."Country/Region Code";
    VATEntry."VAT Registration No." := Vend."VAT Registration No.";
    END;
    VATEntry.Type::Sale:
    BEGIN
    IF Cust."No." <> "Bill-to/Pay-to No." THEN
    Cust.GET("Bill-to/Pay-to No.");
    VATEntry."Country/Region Code" := Cust."Country/Region Code";
    VATEntry."VAT Registration No." := Cust."VAT Registration No.";
    END;
    END;
    VATEntry."VAT Date" := "VAT Date";
    VATEntry."Postponed VAT" := "Postponed VAT";
    VATEntry."EU 3-Party Intermediate Role" := "EU 3-Party Intermediate Role";
    ...
    Replacement code
    ...
    VATEntry."No. Series" := "Posting No. Series";
    VATEntry."VAT Base Discount %" := "VAT Base Discount %";
    VATEntry."Bill-to/Pay-to No." := "Bill-to/Pay-to No.";

    // Add the following lines. 
    IF "VAT Protocol" THEN BEGIN
    VATEntry."Country/Region Code" := "Country/Region Code";
    VATEntry."VAT Registration No." := "VAT Registration No.";
    END ELSE
    // End of the added lines. 

    IF "Bill-to/Pay-to No." <> '' THEN
    CASE VATEntry.Type OF
    VATEntry.Type::Purchase:
    BEGIN
    IF Vend."No." <> "Bill-to/Pay-to No." THEN
    Vend.GET("Bill-to/Pay-to No.");
    VATEntry."Country/Region Code" := Vend."Country/Region Code";
    VATEntry."VAT Registration No." := Vend."VAT Registration No.";
    END;
    VATEntry.Type::Sale:
    BEGIN
    IF Cust."No." <> "Bill-to/Pay-to No." THEN
    Cust.GET("Bill-to/Pay-to No.");
    VATEntry."Country/Region Code" := Cust."Country/Region Code";
    VATEntry."VAT Registration No." := Cust."VAT Registration No.";
    END;
    END;
    VATEntry."VAT Date" := "VAT Date";
    VATEntry."Postponed VAT" := "Postponed VAT";
    VATEntry."EU 3-Party Intermediate Role" := "EU 3-Party Intermediate Role";
    ...
  3. Change the code in the OnRun function in the VAT Protocol Post codeunit (16202) as follows:
    Existing code
    ...
    GenJnlLine."Account Type" := GenJnlLine."Account Type"::"G/L Account";
    GenJnlLine.VALIDATE("Account No.",VATProtocolLine."Sales VAT Account");
    GenJnlLine.Description := VATProtocolLine.Description; 
    GenJnlLine."Gen. Posting Type" := GenJnlLine."Gen. Posting Type"::Sale; // BG0001
    GenJnlLine."Gen. Bus. Posting Group" := '';
    GenJnlLine."Gen. Prod. Posting Group" := '';
    IF "Document Type" = "Document Type"::Purchase THEN BEGIN
    GenJnlLine.VALIDATE("VAT Bus. Posting Group",VATProtocolLine."Bal. VAT Bus. Posting Group");

    // Delete the following line. 
    GenJnlLine."Gen. Posting Type" := GenJnlLine."Gen. Posting Type"::Purchase; // BG0001
    // End of the deleted line.

    GenJnlLine."VAT Type" := GenJnlLine."VAT Type"::Purchase;
    END ELSE BEGIN
    GenJnlLine.VALIDATE("VAT Bus. Posting Group",VATProtocolLine."VAT Bus. Posting Group");

    // Delete the following line. 
    GenJnlLine."Gen. Posting Type" := GenJnlLine."Gen. Posting Type"::Sale; // BG0001
    // End of the deleted line.

    GenJnlLine."VAT Type" := GenJnlLine."VAT Type"::Sale;
    END;
    ...
    Replacement code
    ...
    GenJnlLine."Account Type" := GenJnlLine."Account Type"::"G/L Account";
    GenJnlLine.VALIDATE("Account No.",VATProtocolLine."Sales VAT Account");
    GenJnlLine.Description := VATProtocolLine.Description; 
    GenJnlLine."Gen. Posting Type" := GenJnlLine."Gen. Posting Type"::Sale; // BG0001
    GenJnlLine."Gen. Bus. Posting Group" := '';
    GenJnlLine."Gen. Prod. Posting Group" := '';
    IF "Document Type" = "Document Type"::Purchase THEN BEGIN
    GenJnlLine.VALIDATE("VAT Bus. Posting Group",VATProtocolLine."Bal. VAT Bus. Posting Group");
    GenJnlLine."VAT Type" := GenJnlLine."VAT Type"::Purchase;
    END ELSE BEGIN
    GenJnlLine.VALIDATE("VAT Bus. Posting Group",VATProtocolLine."VAT Bus. Posting Group"); 
    GenJnlLine."VAT Type" := GenJnlLine."VAT Type"::Sale;
    END;
    ...

Prerequisites

You must have the Bulgarian version of Microsoft Dynamics NAV 2009 R2 installed to apply this hotfix.

Removal information

You cannot remove this hotfix.

↑ Back to the top

More Information

For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2702956 "Customer No. '[XXXXXXX]' does not exist" error message when you post a purchase VAT protocol that is created as a copy of a posted invoice in the Bulgarian version of Microsoft Dynamics NAV 2009 R2

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

↑ Back to the top

Article Info
Article ID : 2705243
Revision : 1
Created on : 1/7/2017
Published on : 9/19/2012
Exists online : False
Views : 267