Acumatica Report Reviews: Transactions for Account

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 Account (GL633500) report in Acumatica allows you to see all the individual Journal Transactions that posted to a specific General Ledger Account.

The General Ledger Account is required and you can only pick one so you can only look at one account at a time. If you want to look at more than one account at a time, you can use the Transactions for Period (GL633000) report which we looked at last week (click here).

The report is grouped by year so you can see a transaction total amount for each year.

You can also click on the link in the Batch Nbr. column to be taken to the Journal Transactions (GL301000) screen for that batch.

Screenshots

Here are some screenshots from the report:

DAC Schema

I went through the DAC relationships on the Relationships tab in the Schema Builder window and came up with the following graphical representation:

Filters

Here is a snapshot of the filters that are being used in the report:

Groups

There is one group on this report and it involves three fields:

1. Ledger_Account_Period
   1. GLHistoryByPeriod.LedgerID
   2. GLHistoryByPeriod.AccountID
   3. GLHistoryByPeriod.FinPeriodID

Additional Notes

• Variables can exist at a group level or at the detail level. This report has variables at both the group level and the detail level.
• The Beginning Balance and Yearly Total balance is calculated by the $LineBalance variable which has a very interesting formula (pictured below).
  
• There are two things that interest me about the above formula:
• 1. NextExists – This is a function that isn’t in the list of functions, yet it’s used in an expression and it appears to be working. I tried it on a test report and it looks like it returns a 0 or 1 depending on whether or not there is a next record. It makes me wonder how many other functions exist that can be used even though they don’t exist in the list of functions.
  2. Raw – I tested printing [GLHistoryByPeriod.BranchID] vs. [GLHistoryByPeriod.BranchID.Raw]. [GLHistoryByPeriod.BranchID] prints the name of the branch like New York, Europe, or San Francisco in the Demo database. [GLHistoryByPeriod.BranchID] gives you the behind-the-scenes number in the database like 5, 6, or 13. It can also be useful for dates. For example, [GLHistoryByPeriod.FinPeriodID] gives you something like 05-2006 whereas [GLHistoryByPeriod.FinPeriodID.Raw] gives you 200605 which can be more useful in some situations.