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 requires you to fill in the "Property Location" field and the "Property Tax. Acc. No." field in 340 declaration lines when you export the model 340 file for Purchase in the Spanish version of Microsoft Dynamics NAV

The system requires you to fill in the "Property Location" field and the "Property Tax. Acc. No." field in 340 declaration lines when you export the model 340 file for Purchase in the Spanish version of Microsoft Dynamics NAV

View products that this article applies to.

This article applies to Microsoft Dynamics NAV for the Spanish (es) language locale.

↑ Back to the top

Symptoms

When you export the model 340 file for purchase in the Spanish version of Microsoft Dynamics NAV, the system requires you to fill in the Property Location field and the Property Tax. Acc. No. field in 340 declaration lines. However, these fields should only be required for Sales.
This problem occurs in the following products:
  • The Spanish version of Microsoft Dynamics NAV 2009 R2
  • The Spanish version of Microsoft Dynamics NAV 2009 Service Pack 1
  • The Spanish version of Microsoft Dynamics NAV 5.0 Service Pack 1

↑ 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 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 340 Declaration Linetable (10744) as follows:
    Existing code
    ...
    OnModify=BEGIN
    // Delete the following line,
    IF "Operation Code" = 'R' THEN

    TESTFIELD("Property Location");
    IF "Property Location" IN ["Property Location"::"Property in Spain","Property Location"::"Property in Basque / Navarra"] THEN
    TESTFIELD("Property Tax Account No.");
    END;
    ...
    Replacement code
    ...
    OnModify=BEGIN
    // Add the following line.
    IF ("Operation Code" = 'R') AND (Type = Type::Sale) THEN

    TESTFIELD("Property Location");
    IF "Property Location" IN ["Property Location"::"Property in Spain","Property Location"::"Property in Basque / Navarra"] THEN
    TESTFIELD("Property Tax Account No.");
    END;
    ...
  2. Change the code in the 340 Declaration Lineform (10744) as follows:
    Existing code
    ...
    OnQueryCloseForm=BEGIN
    IF OKPressed THEN BEGIN
    SETRANGE("Operation Code",'R');
    SETRANGE("Property Location","Property Location"::" ");
    IF NOT ISEMPTY THEN BEGIN
    RESET;
    OKPressed := FALSE;
    ERROR(Text001);
    END;
    ...
    Replacement code
    ...
    OnQueryCloseForm=BEGIN
    IF OKPressed THEN BEGIN
    SETRANGE("Operation Code",'R');
    SETRANGE("Property Location","Property Location"::" ");

    // Add the following line.
    SETRANGE(Type,Type::Sale);

    IF NOT ISEMPTY THEN BEGIN
    RESET;
    OKPressed := FALSE;
    ERROR(Text001);
    END;
    ...
  3. Change the code in the Make 340 Declarationreport (10743) as follows:
    Existing code
    ...
    OnPostReport=BEGIN
    PopulateAppliedPayments;
    IF TempDeclarationLines.FINDSET THEN BEGIN
    COMMIT;
    IF FORM.RUNMODAL(10744,TempDeclarationLines) = ACTION::LookupOK THEN BEGIN
    CreateFileHeader;
    WriteDeclarationLinesToText(TempDeclarationLines);
    END ELSE
    EXIT;
    END;
    ...
    Replacement code
    ...
    OnPostReport=BEGIN
    PopulateAppliedPayments;
    IF TempDeclarationLines.FINDSET THEN BEGIN
    COMMIT;
    IF FORM.RUNMODAL(10744,TempDeclarationLines) = ACTION::LookupOK THEN BEGIN

    // Add the following line.
    TempDeclarationLines.SETRANGE(Type,TempDeclarationLines.Type::Sale);

    CreateFileHeader;
    WriteDeclarationLinesToText(TempDeclarationLines);
    END ELSE
    EXIT;
    END;
    ...

Prerequisites

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

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

↑ Back to the top

Article Info
Article ID : 2684460
Revision : 1
Created on : 1/7/2017
Published on : 3/9/2012
Exists online : False
Views : 276