Journal and Ledgerization Logs

The Journal Log (JLOG) page is used by many system processes to control processing within an instance of the process and to record where one process left off for the next to read and start processing at that point. The Ledgerization Log (JLOGLDGR) uses the same set of records but filters only for those created by the Ledger Engine and the Ledger Rebuild processes. More details on what each of the Process ID values mean can be found in the run sheets.

The fields on Journal Log and Ledgerization Log pages are as follows:

Field Name	Field Description
Process ID	LDGRPOST, LDGRRBLD, and LDGRINSTRC values, which come from the Ledger Engine and Ledger Rebuild job, are displayed on the Ledgerization Log. The Journal Log shows these same process IDs in addition to several others.
Run Date	When a record is inserted, the date is recorded at the time of insert from the application server.
Source Journal/Ledger ID	The ID, as defined on the Journal/Ledger Control reference page, that records the particular input source into the system process logged.
Journal/Ledger Name	The Journal/Ledger Data Object Name associated with the Source Journal/Ledger ID is displayed for informational purposes.
Status	There are many Journal Log status values that represent the different phases for a range of records that a process is working on or has worked with. Not all processes use all of the status choices. Intended (1) represents a unit of work that has been identified but has not yet been selected for processing. Final (2) represents a unit of work that has been processed successfully. Historical (3) represents a block of work that has successfully been processed. Failed (4) - represents a block of work that could not be processed successfully Gap Found (5) represents a block of work that was not found on the source journal. Values less than and greater than that range were found. The missing range is recorded as the range may be completed later if multiple servers are running and reserving blocks of record numbers. The range may never be filled and the range becomes 'stale’. Gap Intended (6) represents a block of work from a previous Gap Found range that has now been used. Gap Final (7) represents a previous Gap Found range that has been successfully processed by either batch job in process gap mode. The status does not mean that records were found with the missing range but that a process has examined the gap and determined that none, some, or the entire original gap has been filled in. Such a status will ensure the record is not selected when processing gaps later. Gap Stale (8) represents a range of journal records that has been identified by the Identify and Archive Stale Gaps Batch Process as being older than the specified days for retention parameter in that job. Such a record will be purged by that same job when run in purge mode. Gap Failed (9) represents a gap identified as being filled which could not be posted successfully to the applicable ledger or ledgers. This block of work should be ledgerized by running the Ledger Engine or Ledger Rebuild job to process failed work. Unprocessed (10) is a status that is used as a holding status. Records that remain in this status and do not progress deserve investigation because they have likely been bypassed.
Begin Transaction UNID	When a journal record is created for a transaction, a unique transaction ID is assigned to that record, which is different than the online transaction ID of Transaction Code, Transaction Department, Transaction ID, and Version number. This separate UNID is assigned by the Unique Numbers page. Tracking individual transactions by this UNID in the journal is easier for the Ledger Engine and Rebuild Ledger job and is more efficient than the online ID.
Begin Transaction Line ID	When a journal record is created for a transaction, a unique transaction line ID is assigned to each journal record. This ID is automatically assigned by the application and is equivalent to a numbering of journal records created by a transaction. Each Journal Log record created by a ledger job will contain a value in this field to identify the starting line number of the starting transaction.
End Transaction UNID	The last unique transaction ID selected in a block of work.
End Transaction Line ID	The last unique line ID selected in a block of work.