| Description |
The date entery field should be limited to current open periods in the GL Fiscal calandar. When you enter a transaction the date control should prevent you from entering in the wrong period.
*Background:*
We should look at all data validation and determine how to eliminate the need for posting errors. For Example when you post a transaciton it checks to see if the transaciton is in a valid fiscal period. While this is a great check why dont we put it on the entry date box so that only valid dates can be selected.
Take orbitz for example- lets say you are booking a flight - you could not fly yesterday right?
!pastedImage_d37128_0.png!
Nor can you book over 300 days in advance
!pastedImage_d37128_1.png!
Note - today is 5-18 but you could note even select 5-17. I suggest that the calandar control get a start and end date that shows when posing is valid - we should still leave the posting rules in place but we need that start and end date in there to ensure that we are on track.
For General ledger this means:
* User should not be able to enter a post date that is not in an open fiscal period (both forward and back.
* User should not be able to enter a reversing date that is not in an open fiscal period(both forward and backward)
|