Generate General Ledger Posting Data using the GL Posting Utility

Run the gl_posting.jar utility to generate General Ledger (GL) posting data. The data can be saved to XML in a generic XML file format.

Before you begin

This utility posts these GL journal entry fields by default:
  • Account1
  • Account2
  • TxnType
  • GlCenter
  • Amount

To add additional fields, edit the aggregateByFields property (for the aggregate mode) or the exportFields property (for the non-aggregate mode) in the gl_posting.yaml file.

To change the number of journal entries in each output file, edit the numEntryPerFile property in the gl_posting.yaml file.

This procedure assumes that you have set up your base Event Repository and any tenant repositories, and configured GL information processing. For more information about setting up the Event Repository and configuring GL information processing, see the discussions about Event Repository and configuring general ledger records.

About this task

Perform this task for a given period (GL date range) using a start GL date and an end GL date. The posting utility writes GL journal entries for the requested period to XML files.

Run these commands on the machine on which you ran the gl_posting.jar utility.

Note: If you use multi-tenancy, add a [tenantId] to your commands.

Procedure

  • To run in aggregate mode: 
    java -jar gl_posting.jar startDate(yyyy-mm-dd) endDate(yyyy-mm-dd) outputFolder outputFilePrefix gl_posting.yaml [tenantId]
    Where:
    • startDate(yyyy-mm-dd) is the start date of the GL date range within which this utility aggregates all journal entries from the GL daily summary records stored in your MongoDB system.
    • endDate(yyyy-mm-dd) is the end date of the GL date range within which this utility aggregates all journal entries from the GL summary records stored in your MongoDB system.
    • outputFolder is the is the path to the folder to store the output files.
    • outputFilePrefix is the prefix of the output file names. For example, if the prefix is 2018March, then the output files are 2018March_1.xml, 2018March_2.xml, and 2018March_3.xml.
    • gl_posting.yaml is the directory path of the properties file the utility uses at runtime.
    • tenantId is the tenant ID, if you use multi-tenancy.
    For example: 
    java -jar /opt/mtx/bin/gl_posting.jar 2018-03-01 2018-03-31 posting 2018March /opt/mtx/data/gl_posting.yaml tenantId
  • To run in non-aggregate mode: 
    java -jar gl_posting.jar -noaggr startDate(yyyy-mm-dd) endDate(yyyy-mm-dd) outputFolder outputFilePrefix gl_posting.yaml [tenantId]
    Where:
    • -noaggr runs this utility in non-aggregate mode. GL journal entries are listed in the requested date range without summing the journal amounts.
    • startDate(yyyy-mm-dd) is the start date of the GL date range within which this utility aggregates all journal entries from the GL daily summary records stored in your MongoDB system.
    • endDate(yyyy-mm-dd) is the end date of the GL date range within which this utility aggregates all journal entries from the GL summary records stored in your MongoDB system.
    • outputFolder is the is the path to the folder to store the output files.
    • outputFilePrefix is the prefix of the output file names. For example, if the prefix is 2018March, then the output files are 2018March_1.xml, 2018March_2.xml, and 2018March_3.xml.
    • gl_posting.yaml is the directory path of the properties file the utility uses at runtime.
    • tenantId is the tenant ID, if you use multi-tenancy.
    For example: 
    java -jar /opt/mtx/bin/gl_posting.jar -noaggr 2018-03-01 2018-03-31 posting 2018March 
     /opt/mtx/data/gl_posting.yaml tenantId