No problem, this happens frequently when writing requirements for reports. I understand what you're asking (in theory), however, there is really no such field as a 'batch date' in GP. Sometimes, people refer to the GL Posting Date for the batch as the batch date, but I do not think that's what you want here. Let me give you a scenario an as example:
1. I receive an invoice on 3/2/09 (date 1).
2. The invoice is dated 2/23/09 (date 2).
3. I physically enter and save this invoice into GP on 3/5/09 (date 3a) with a document date of 2/23/09 (date 3b) and a GL posting date of 2/28/09 (date 3c).
4. I pull up the saved invoice on 3/6/09 (date 4), make a change, then re-save it.
5. I physically click the Post button on the batch on 3/7/09 (date 5).
To report on these:
Date 1 - unless you enter this somewhere in GP, there is no way to report on it, no field stores or asks for this date.
Date 2 - this will only be stored if you also use this as the document date (date 3b). Many businesses will not put the real invoice date in for various reasons, depending on the cut off dates for the end of the month and other factors.
Date 3a - there is a modified date for each transaction, but this will only save the last modified date, so the modified date can be used here if step 4 is not done or if it's ok to use the last modified date.
Date 3b - document date.
Date 3c - GL posting date.
Date 4 - this will be the modified date, but if there are multiple changes on different dates, only the last one will be saved.
Date 5 - this is the posted date. (post-ED as opposed to the GL post-ING date in 3c)
And we have not even started talking about the payment dates! Once you can determine what dates your users are really looking for, you should be able to add them to the framework setup in the view on my blog to get your report.
Victoria Yudin
Dynamics GP MVP 2005 - 2009
Flexible Solutions - home of GP Reports
blog: