This article applies to Microsoft Dynamics AX for all regions.
Symptoms
Assume that you create an expense report in Microsoft Dynamics AX 2012. You have a line that has a transaction date in a closed period in the expense report. In this situation, when you try to post the expense report, you receive the following error message:
Fiscal period for [transaction date] is not open.
Cause
This problem occurs because the transaction date is used as the accounting date in the expense report.
Resolution
To resolve this problem, install the hotfix that is described in this article.
This hotfix contains the following changes:
-
The accounting date of any document such as the Travel & Expense report can be updated automatically to the next fiscal period open date.
-
For the Travel & Expense report, a new parameter, Allow date corrections for expense reports, is added.
Note This fix will work only if this parameter is enabled. -
A new SSRS report, "Expense report with corrected dates", is added to Microsoft Dynamics AX client under the following location:
Travel & Expense > Reports > TransactionsThis report can display expense reports that have actual transaction dates and corrected accounting dates.
Hotfix information
A supported hotfix is available from Microsoft. There is a "Hotfix download available" section at the top of this Knowledge Base article. If you are encountering an issue downloading, installing this hotfix, or have other technical support questions, contact your partner or, if enrolled in a support plan directly with Microsoft, you can contact technical support for Microsoft Dynamics and create a new support request. To do this, visit the following Microsoft website:
https://mbs.microsoft.com/support/newstart.aspx You can also contact technical support for Microsoft Dynamics by phone using these links for country specific phone numbers. To do this, visit one of the following Microsoft websites:
Partners
https://mbs.microsoft.com/partnersource/support/Customers
https://mbs.microsoft.com/customersource/support/information/SupportInformation/global_support_contacts_eng.htmIn 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 any additional support questions and issues that do not qualify for the specific update in question.
Installation information
If you have customizations for one or more of the methods or the tables that are affected by this hotfix, you must apply these changes in a test environment before you apply the hotfix in a production environment.
For more information about how to install this hotfix, click the following article number to view the article in the Microsoft Knowledge Base:
893082 How to install a Microsoft Dynamics AX hotfix
Prerequisites
You must have Microsoft Dynamics AX 2012 installed to apply this hotfix.
Restart requirement
You must restart the Application Object Server (AOS) service after you apply the hotfix.
File information
The global version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
|
File name |
File version |
File size |
Date |
Time |
Platform |
|---|---|---|---|---|---|
|
Aximpactanalysis.exe |
Not applicable |
60,280 |
09-Apr-2013 |
11:55 |
x86 |
|
Axupdate.exe |
Not applicable |
60,264 |
09-Apr-2013 |
11:55 |
x86 |
|
Dynamicsax2012-kb2724897-extensions.axmodel |
6.1.1108.1256 |
224,552 |
09-Apr-2013 |
11:55 |
Not applicable |
|
Dynamicsax2012-kb2724897-foundation.axmodel |
6.0.1108.1256 |
251,176 |
09-Apr-2013 |
11:55 |
Not applicable |
|
Dynamicsax2012-kb2852252-extensions.axmodel |
6.1.1108.4918 |
4,547,824 |
06-Jun-2013 |
19:08 |
Not applicable |
|
Dynamicsax2012-kb2852252-foundation.axmodel |
6.0.1108.4918 |
12,084,464 |
06-Jun-2013 |
19:08 |
Not applicable |
|
Dynamicsax2012-kb2852252-fpplabels.axmodel |
6.0.1108.4918 |
223,984 |
06-Jun-2013 |
19:08 |
Not applicable |
|
Dynamicsax2012-kb2852252-processmanufacturing.axmodel |
6.0.1108.4918 |
1,116,416 |
06-Jun-2013 |
19:08 |
Not applicable |
|
Dynamicsax2012-kb2852252-projectmanagement.axmodel |
6.0.1108.4918 |
482,560 |
06-Jun-2013 |
19:08 |
Not applicable |
|
Dynamicsax2012-kb2852252-publicsector.axmodel |
6.0.1108.4918 |
2,227,440 |
06-Jun-2013 |
19:08 |
Not applicable |
|
Dynamicsax2012-kb2852252-syplabels.axmodel |
6.0.1108.4918 |
1,346,288 |
06-Jun-2013 |
19:08 |
Not applicable |
|
Axsetupsp.exe |
6.0.1108.4279 |
1,390,872 |
09-Apr-2013 |
11:55 |
x86 |
|
Axutillib.dll |
6.0.1108.806 |
821,480 |
09-Apr-2013 |
11:55 |
x86 |
|
Microsoft.dynamics.servicing.operations.dll |
6.0.888.436 |
35,752 |
09-Apr-2013 |
11:55 |
x86 |
|
Axsetupsp.resources.dll |
6.0.1108.4436 |
391,464 |
09-Apr-2013 |
11:55 |
x86 |
|
Axsetupsp.resources.dll |
6.0.1108.4436 |
375,080 |
09-Apr-2013 |
11:55 |
x86 |
|
Axsetupsp.resources.dll |
6.0.1108.4436 |
379,176 |
09-Apr-2013 |
11:55 |
x86 |
|
Axsetupsp.resources.dll |
6.0.1108.4436 |
379,176 |
09-Apr-2013 |
11:55 |
x86 |
|
Axsetupsp.resources.dll |
6.0.1108.4436 |
375,080 |
09-Apr-2013 |
11:55 |
x86 |
|
Axsetupsp.resources.dll |
6.0.1108.4436 |
383,272 |
09-Apr-2013 |
11:55 |
x86 |
|
Axsetupsp.resources.dll |
6.0.1108.4436 |
375,080 |
09-Apr-2013 |
11:55 |
x86 |
|
Axsetupsp.resources.dll |
6.0.1108.4436 |
379,176 |
09-Apr-2013 |
11:55 |
x86 |
|
Axsetupsp.resources.dll |
6.0.1108.4436 |
375,080 |
09-Apr-2013 |
11:55 |
x86 |
|
Axsetupsp.resources.dll |
6.0.1108.4436 |
379,176 |
09-Apr-2013 |
11:55 |
x86 |
|
Axsetupsp.resources.dll |
6.0.1108.4436 |
375,080 |
09-Apr-2013 |
11:55 |
x86 |
|
Axsetupsp.resources.dll |
6.0.1108.4436 |
416,040 |
09-Apr-2013 |
11:55 |
x86 |
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Note This is a "FAST PUBLISH" article created directly from within the Microsoft support organization. The information contained here in 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.
