We have several issues with how AX 2009 handles date and time stamping transactions due to the fact the time difference between where our AX application server is located and one goup of users.
The time difference is 9 hours. During the first couple hours of the users business day the issue we're seeing is the following:
1. they create a sales order which is stamped using the session date and time for that user.
2. If they advance the order to the packing slip stage, we have noticed that the packing slip is using the AOS date and time which in this case is yesterday.
3. in the end it looks like the order was shipped before the order was actually created.
4. This same issues with date and time occurs during our period close process where transactions are not permitted for the first few hours of the users business day because posting date used is the AOS date which is still in the previous period.
As we add addiitional user groups, this issue will only become more apparent. Are there ways to manage this other than telling the business sorry, you can't run transaction for the first few hours of your business day or having them manually change the dates for two hours every day?