Download Sage 300 ERP 2014 General Ledger User's Guide

Chapter 4: Period-End Procedures
If you have some accounts that you consolidate regularly because they
accumulate detail that you do not need, you should consider using the option
to consolidate those accounts during posting.
Note: When you consolidate posted transactions, you lose the ability to drill
down to the original transaction in the source ledger, and you also lose any
optional fields posted with the transaction.
About Source Journals and Consolidation
If you consolidate details, either during posting or at period end using the
Consolidate Posted Transactions screen, the source journal cannot print the
batch number with the consolidated details.
The journal also cannot print the posting sequence number of consolidated
transactions.
To include consolidated transactions on a source journal, when you print the
source journal, you must specify a blank as the starting batch or posting
sequence number on the Ranges tab of the Source Journal Report screen.
Effects of Consolidation
When General Ledger consolidates a group of transactions, the individual
details are erased and cannot be listed on source journals or on the Posted
Transactions Listing.
Consolidation removes the posting entry numbers and batch entry numbers
associated with details:
l
The new posting sequence number is 0.
l
The batch number and entry number on reports is CNSLD.
l
The description and reference fields are set to CONSOLIDATED.
To determine how a transaction was consolidated, check its description and
posting sequence number.
l
l
A transaction created by the Consolidate Posted Transactions screen has the
description "CONSOLIDATED" and has a posting sequence number of 0. The
batch number is 000000.
A transaction consolidated during posting has the description
"CONSOLIDATED POSTING" and it has a posting sequence number.
96 Sage 300 ERP General Ledger