Wrong Dates

[Dukester0122]

We've been having problems with document dates lately. Some users enter 2004 or 2030 instead of 2003 in their documents and some of them gets posted. Do you guys have any suggestion how to solve this issue?

 

[stef315]

They should only post if you have an open fiscal period for that date. Check the fiscal period setup under Company-Fiscal Periods. Make sure you have the periods marked closed (boxes checked) for any periods you don't want posted to. They can easily be unchecked later if they need to be posted to intentionally.

 

[Luvsql]

Actually, Great Plains will still post a transaction date of 2030 if your batch date is setup properly, if you are using Batch Dates as your posting (vs transaction date). Typically, when you create a batch, you enter the transaction into today's date for the batch, but then manually type in the transaction date.

What I would recommend to your user's is the following date shortcuts:

If you are in the current month and date, you do not need to enter the entire date ie if today is 10/22/2003. If I am in a date field and want my date to be 10/15/2003, just type in 15 and tab off.

If you are in the current year and want to change the month and day, type in 1115 to make the date 11/15/2003. You only need to enter the year when it is different from the current year.

 

[stef315]

Sorry, didn't see "document date" instead of "Posting Date".

You either have to do as luvsql said and educate your users how to enter dates and probably more likely, slow down and be careful; or, you can put some constraints on the date. You could use VBA in the places this is most often happening or use SQL. I normally just let the users learn from their mistakes. Good Luck!

 

[Dukester0122]

I think that's a good idea. You're right we are posting by batch date and changing it to trnasaction date would not be feasible. I'll try what you suggested to the users. Tks.