This article applies to Microsoft Dynamics AX 2012 R@for all regions.
When you complete the year-end closing process, the posting layer is not included when nominal account balances are closed and opening entries are created.
This issue occurs when the offset account that is derived from the posting definition is set to Close type of Real. The account has an opening balance transaction created for it if the periods are set up in this manner on the Opening Transactions process form. However, the opening transaction that is created for the account does not respect the posting layer of the closing transactions it is processing.
Hotfix informationA 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, go to the following Microsoft website:
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 informationSee How to install a Microsoft Dynamics AX hotfix for information about how to install this hotfix.
PrerequisitesYou must have Microsoft Dynamics AX 2012 R2 installed to apply this hotfix.
Restart requirementYou must restart the Application Object Server (AOS) service after you apply this hotfix.
Validation of the application hotfix installationTo validate the installation of the application hotfix, open the SysHotfixManifest class in the Application Object Tree (AOT). Then, verify that there is a method name that contains the Knowledge Base (KB) article number of the installed hotfix. Additionally, you can cross-check the affected objects by viewing the KBxxxxxx.txt file against the objects in the AOT. Therefore, you can make sure that the objects are changed correctly in the SYP layer or in the GLP layer.
Note KBxxxxxx.txt is a placeholder for the KB article number of the installed hotfix.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Article ID: 2802602 - Last Review: 2017 Fev 17 - Revision: 2
Microsoft Dynamics AX 2012 R2