Microsoft Dynamics AX Support

This blog contains posts by the Microsoft Dynamics AX Support Teams Worldwide

Microsoft Dynamics AX Module Status Setting for Fiscal Periods

During monthly closing it is important to manage the fiscal period’s status in Microsoft Dynamics AX, on the other hand differentiate between the operational closing, and financial closing.

The operational closing represents the departments completion of the transactions of which belongs to the current month (month being closed) for example procurement department finalizing the purchase orders confirmations, sales department completing sales order confirmation, and invoicing, warehousing and inventory department receiving and issuing the goods.  The financial closing represents Finance/controllership department completion of the transactions of which belongs to the current month whether transactions related to operations vendor and customers payments along with settlements, in addition to the transactions belongs to financial closing entry such as fixed assets depreciation, foreign currency revaluation, and adjusting entries.

Microsoft Dynamics AX gives a control point to manage fiscal periods during month closing based on module, users’ whether all users, particular user group, or none, in the other hand the period status whether Open for all transactions, On-hold which formerly known as stopped in Dynamics AX 2009 this status represents a temporary prevention of posting any transactions on this particular period, and it could be back to Open status. The third status is closed this represent permanent close of the period and could not be re-opened again.

In case the module status set to Closed the system will through the following confirmation

In case the module status set to on-hold, or closed the user will got the following Infolog message

 

In case the module status set to open, and access level set to none the user will got the following Infolog message

There is a rationale behind setting Module status for example for vendor as None is to prevent the users to post transactions from the Account payable Sub module not from the general ledger module, and as long as the general ledger under Module status is set to All so that users will be able to post vendor transactions from the General Ledger module only.

 

In case you still have Microsoft Dynamics AX 2009 and users are able to post vendor transactions from the sub module, there is a hotfix addressing this issue KB2977606 or update to latest version of Microsoft Dynamics AX 2012 R3.

 

Check the following TechNet articles about Fiscal periods.

Specify which users can post to a period [AX 2012]
Place a period on hold [AX 2012]
Close periods in the general ledger [AX 2012]