This post is part of a two year series of posts related to the out of the box reports in Acumatica. For a full list, click here.
The Transactions for Period (GL633000) report in Acumatica allows you to look at each General Ledger account and see all the individual Journal Transactions that posted to a financial period range that you get to specify.
You get to see all the journal entry batches that were posted during the period range so you can easily explore the detailed general ledger activity. Accountants like this kind of stuff.
You can also click on the batch number to be taken to the Journal Transactions (GL301000) screen for that batch. Note: the screenshot below is only showing batches that originated in the GL module, but the report will show you any batch, regardless of the originating module.
Here are some screenshots from the report:
I went through the DAC relationships on the Relationships tab in the Schema Builder window and came up with the following graphical representation:
Here is a snapshot of the filters that are being used in the report:
There is only one group on this report, but it involves two fields:
- I have to admit that I don’t completely understand what is going on with the joins here. The graphical representation above is confusing enough, but there is actually even more going on. For example, in the join to HistoryLast (GLHistory), I don’t understand exactly what is happening with the last row. I think it might have something to do with retained earnings, but I’m not sure.
- The other join that confuses me is the one to GLTran which uses a GreaterOrEqual and a LessOrEqual link condition. I’ve never done something like this in a SQL join before so I’m still trying to wrap my head around it.
- There are a number of different variables being used in groupHeaderSection2 to calculate the ending balance numbers.
- You don’t have to run the report for just one period. You could run it across multiple periods (or years) like, say, December 2014 to February 2015.
- A batch could be listed more than once. It could even be debiting and crediting the same account in the same batch as you can see with batch 00004479 in the screenshot above.