O/E G/L Integration Screen

Overview

Use the G/L Integration screen to:

  • Specify when to add General Ledger transactions to the G/L batch: during posting, during Day End Processing, or on request.

    Important! The option you select here can prevent you from printing the O/E G/L Transactions report or consolidating Order Entry transactions, and can also have a significant impact on system performance during transaction processing. For more information, see General Ledger Integration Options.

  • Specify whether to create a separate G/L batch each time you create the G/L batch (and optionally automatically post the batch) or add new transactions to an existing batch.
  • Specify whether to consolidate the G/L batch when you post, or always enter full transaction details in the batch.

    Note: Consolidation reduces the amount of information in the general ledger batch and results in a shorter list when you print the G/L Transactions Listing report, but also reduces information and prevents drilldown from General Ledger. For more information, see General Ledger Integration Options.

  • Assign source codes to General Ledger transactions created by Order Entry and added to G/L batches. (New source codes are automatically added to G/L, but you will have to update G/L source journal profiles to include transactions on source journals.)
  • Select information to appear in the Entry Description, Detail Description, Detail Reference, and Detail Comment fields in G/L transactions created from invoices and shipments. (This information appears for transactions in the G/L Transactions report.)
  • Look up the last Day End Number for which you have created General Ledger batches.

Changing G/L Integration Settings

You can change any of the settings on the O/E G/L Integration screen at any time. However, any changes you make will apply only to General Ledger transactions created after the change, and will not affect existing General Ledger batches.

Important! Before changing any settings on the O/E G/L Integration screen, make sure you understand the impact these settings have on processing within Order Entry. For more information, see General Ledger Integration Options.

Appending General Ledger Transactions to a CSV File

If you do not use Sage 300 General Ledger, or if your Sage 300 General Ledger system is at another location, Order Entry appends its general ledger transactions to a file called oegltran.csv, which can be imported by a Sage 300 General Ledger at another site, or transferred to another general ledger that you use. The file is in Comma Separated Values (CSV) format, and is created in the same directory as your company database.

If you do not use Sage 300 General Ledger in the same database as Order Entry, all general ledger transactions are placed in the same CSV file. Each time Order Entry creates transactions, a message asks whether you want to add transactions to the existing file or replace it.