Updates to many of the journals are performed by the Journal Engine, a batch job found in the Postings folder under the Batch Jobs sub folder. The posting logic in this batch job can also be invoked when a document goes to final, given the Application Parameters record for RLTM_JRNL_PSTG is set to True. When set to False, those journals which have an input source of posting lines are not updated until the Journal Engine is run. When online, a user can tell if a document has posted or not by the value in the Journal Posting field found on the Posting tab of any accounting document. When that value is Posted, journals have been updated. When Ready, real time posting has been turned off and the record has not been selected by the Journal Engine. A document that is in the Final or Historical Final Document Status with a Journal Posting value of Not Ready indicates that the Document Control table is set to Asynchronous Posting for that document code and the Journal Posting Initiator batch job (Accounts Payable / Batch Jobs) has not been run to switch the value to Ready so the Journal Engine will select the record.
Periodic assurances should be performed to determine if there are any posting lines that have not posted to journals. When they have not, many batch jobs will not select them as only a few systems assurance jobs select such records from the posting line catalog.
The Rebuild Journal batch job will also update a journal, but this job is not the normal means for posting to journals. Use of this job is when a journal has been corrupted, originally contained incorrect record selection settings, or was deactivated and now needs to be activated and brought up to date.