Problems in Period Closing when using local time zone.

[Former Member]

Hi Gurus,

Kindly share your experience on what problems can arise for period closing when a company has plants all over USA and having local time zones in their user default - And how to solve them. Thanks.

- Chetan

[Former Member]

We have plants around the world and having local time zones in the user default solved problems for us.

Example:

Australia would come to work on May 1 at 7am. System time was still 5pm April 30. At that time, most user defaults were set to EST USA.

MM period open/close was scheduled for 10pm (EST USA) so Australia (and the entire Far East) would post most of the May transactions a April 30, so they could work. Although one manager did not allow that and day 1 mornging was always spent in other manual work.

We made a project of having all user default times reset to "local"; ran MMPV the day before the last day for Australia and far east. Period end's now run smoothly.

The one item I notice is that the end user local time is associated with date stamps on jobs that they execute.

[Former Member]

The online help gives information on this scenario : http://help.sap.com/saphelp_470/helpdata/fr/50/dc9e10122211d3a54fdfb7b31fd578/frameset.htm