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.
This article applies to Microsoft Dynamics NAV for the Norwegian (no) language locale.
Consider the following in the Norwegian version of Microsoft Dynamics NAV 5.0 with Service Pack 1 or the Norwegian version of Microsoft Dynamics NAV 2009 with Service Pack 1 (SP1):
You select the Application always Allowed check box in the General Ledger Setup dialog box.
You specify an "Allow Posting From" date in the General Ledger Setup table (98) or in the User Setup table (91).
You post an application in a closed VAT period for a customer in the Apply Customer Entries dialog box. For example, you apply an invoice or a payment for the customer and then post the application.
In this scenario, you receive the following error message:
Posting Date is in a settled and closed VAT period (yyyy period mm) in Gen. Journal Line Journal Template Name='',Journal Batch Name='',Line No.='Line_number'.
Note In this error message, yyyy and mm represent the actual year and the actual month of the closed VAT period. Line_number represents an actual line number for the application.
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 service pack or the next 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.
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.
Note Always test code fixes in a controlled environment before you apply the fixes to your production computers.
To install this hotfix, change the code in the CustPostApplyCustLedgEntry trigger in the Gen. Jnl.-Post Line codeunit (12) as follows.
You must have the Norwegian version of Microsoft Dynamics NAV 5.0 with Service Pack 1 or the Norwegian version of Microsoft Dynamics NAV 2009 with Service Pack 1 installed to apply this hotfix.
You cannot remove this hotfix.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
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.