Aggregate Financial Transaction General Ledgers by Month

You can configure a batch process to aggregate financial transaction general ledger (GL) data by month so that the application does not need to sum up the transactions every time a query is issued. Using your scheduler of choice, configure and schedule the following batch process to run monthly:

• Batch Control: C1-FTGMA

• Batch Name: Aggregate FT GLs Monthly

• Parameters: The following parameters are used to determine the start and end dates of an aggregation period.

  • Aggregation Horizon: The number of months in which financial data will be included in the aggregation.

  • Aggregation Lag: The number of months in which financial data will be excluded in the aggregation as calculated from the current month.

Example Steps and Parameters

1. Run a one-time batch process to aggregate historical financial transaction GL data.

   For example, let's say you are currently in the month of April 2022. If you have historical financial transaction GL data going back three years and four months, then set the Aggregation Horizon to 38 months. This means data would be aggregated by month from January 2019 through February 2022. Then set the Aggregation Lag for one month, which excludes the data for March 2022. (March is excluded in this case because updates may still be made to the financial transactions of that month.)

   Note:

   This one-time batch process covers a long period of time, and so it may take a while to run. Wait until the process is finished before beginning the next step.

2. Use a batch scheduler of your choice to run the batch process on a recurring monthly basis. In this case, you would set the Aggregation Horizon to 2 (for two months prior to the current month of April), and the Aggregation Lag to 1 (for one month prior to the current month of April, so that any financial data that is still in progress would be excluded). This means that for the next month (May), the aggregation period would shift to February through March.