Query Journal Service

This service is in theWmOAFIN1227 package and has the following fully-qualified service name: generalLedger1227.queryOA.journal:queryJournal.

This service queries for Journal information (general, recurring, mass allocation, and reversing journal entries) based on the following parameters:

While configuring the queryJournalTxn service, a java.outOfMemory error can occur. Because the database can have so many records, it would be unable to configure the service. One workaround is to use a restricting condition in the query, that is, 1 = 2, so that the service gets configured successfully. After you have configured this service, remove the restricting condition from your transaction definitions. In addition, update the SQLOut parameters of the service’s transactionRecord in the Designer and remove the restricting condition. (In this example, you remove the 1 = 2 condition.)

This service uses the same database scripts as the Send Journal service.

Note:
If you use this service but you do not use the Send Journal service, you should run the wm_disable_from_journal.sql script to disable the triggers installed by the Send Journal service.

For a detailed description of these database scripts, see Send Journal Service. For more information about using database scripts, see Database Scripts.

This service uses the following transaction definition:

The main flow executes as follows:

queryJournalTxn queries for any Journal information matching the parameter values. The parameters are defined as the input to this service.

For more details on query services, see Using Query Services.

This service uses the same business document structure as the Send Journal service. For a detailed description of the business document structure, see Send Journal Service.