Exceptions to the Summarization Rules

There are a few exceptions to the summarization rules covered earlier. These exceptions are based on system code and source code.

System Code Exceptions

Distributions originating in certain system codes and distributions interfacing to certain system codes will never be summarized. Specifically, you will want to note the following exceptions:

  • Entries in General Ledger (GL), Recurring Journal (RJ), and Allocations (CA) are never summarized.

  • Project Accounting (AC) transactions are never summarized because they are created for detailed analysis.

  • Strategic Ledger (SL) transactions do not post to General Ledger, so summarization rules do not apply.

Source Code

Note: To use journal books, select Yes in the Journal Book Required field on Company (GL10.1) and assign a journal book value to all journal entries. Journal books are defined in Journal Book (JB00.1).

For certain source codes transactions will be automatically summarized regardless of flags. A source code identifies where transactions are created within a system; each source code is associated with a system code. With the following source codes, you can only get detail if you use journal books.

System

Code

Source

Code

 Posting Program
AP AC (Accrual Side) Invoice Distribution Closing (AP175), Match Discount Accrual (AP176)
AP AP Payment Closing (AP170)
AP AU Unrealized Gain and Loss (AP191)
AP BE Bill of Exchange Distribution (AP185)
AP DS Match Discount Accrual (AP176)
AP VP Invoice Reinstatement (AP190)
CB CL (Accrual Side) Transaction Postings (CB175)
CB CL (Expense Side) Transaction Postings (CB175)
EE AC Accrual Posting (EE175)