Comments
Interesting that the guys who created these options did neglect to also use last term, next term, this year (year to date), last year, next year.
maybe it would be even better to make it even more flexible so that the admin could opt. for. Similar to the appointment (start time / scheduledstart ...) record fields in ADF. or other records where much more options are already available. If ever there was a clear solution design, why not take over already existing sets... maybe someone does also consider time, like : by 31.12.2021 24:00 UTC, CET etc.
We are implementing french localisation for BCv17 and have faced this issue:
1. Gaps when having posting errors ( i would suggest to make all the checks/validation before fetching the next posting no., because now you know it will post!)
2. When creating the document to fill the gap, the entry does not appear in the G/L Register, hence the Audit file does not contain that entry, this invalidates the file. It also creates a gap in the document no. which invalidates the integrity of the sequence.
3. Deleted document is also posted on the current date instead of the posting date of the document. This messes the no. series as you cannot assign posting no. series before that date. It is an issue if you are still processing a list of sales order of the previous day.