The generic JournalEntry business object is designed to facilitate movement of General Ledger (GL) transactions between collaborative applications.
JournalEntry is a hierarchical business object that contains header-level data at the parent level. It can contain at least one, ideally at least two, JournalEntryLine child business objects. Each of the child business objects represents a debit or credit journal entry. Typically, the total of debit values represented in the JournalEntryLine business objects equals the total of credit values. The debit and credit values must be equal for the overall JournalEntry to represent an atomic, fully balanced GL transaction.
Figure 1 illustrates JournalEntry and JournalEntryLine.
Figure 1. Generic JournalEntry business object structure
The JournalEntry header contains such data as the transaction's creation and posting dates, the organization level at which a full set of legal financial books are maintained, the source financial entity that identifies where the journal entry originated (such as Receivables, WIP, or Inventory), currency and exchange rate information, fiscal period, status, the running total of the entire balanced GL transaction, and tax code.
JournalEntry contains the following child business object:
Child business object | Description | Cardinality |
---|---|---|
JournalEntryLine | Contains the Amount of the transaction, whether it is a Debit or a Credit, the GL Account number to be posted, the Posting Key, and such account allocation attributes as Cost Center, ProductLine, and Project | n |
IBM uses JournalEntry with the Create verb for event notification, that is, to represent a GL transaction triggered in the source application.
For a listing of JournalEntry's attributes, use System Manager or Process Designer Express.