O/E G/L Integration Screen
On the Transactions tab, click Open to open the O/E G/L Integration Detail screen. You use this screen to specify the information that will appear in fields in General Ledger transactions that are created from invoices, shipments, credit notes, and debit notes.
For more information, see O/E G/L Integration Detail Screen .
On this tab, you select settings that control how and when batches of General Ledger transactions are created from Order Entry transactions.
Specify whether Order Entry consolidates transaction details for the same General Ledger account into a single detail, or whether it posts unconsolidated transaction details to General Ledger.
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.
Specify when to create General Ledger transactions.
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.
-
During Posting. Depending on when you create subledger transactions in Inventory Control, you can select this option to create General Ledger transactions during posting.
Warning! This selection can have a significant impact on the speed of processing inventory transactions and transactions in Order Entry. If you want to speed up order processing, switch to creating transactions when you run Day End Processing.
-
During Day End Processing. Depending on when you create subledger transactions in Inventory Control, you can select this option to create General Ledger transactions when you run Day End Processing in Inventory Control.
Note: If you select this option, you cannot print the O/E G/L Transactions, and you cannot consolidate Order Entry transactions that are posted to General Ledger.
-
On Request Using Create Batch Icon. Select this option if you want to create General Ledger transactions manually using the O/E Create Batch screen.
If you prefer to create General Ledger transactions automatically each time you post Order Entry transactions or each time you run Day End processing in Inventory Control, select During Posting or During Day End Processing for the Create G/L Transactions option.
Important! You must select this option if you want to print the O/E G/L Transactions Report, or if you want to consolidate transactions in Order Entry.
For more information, see General Ledger Integration Options.
Specify whether to add new General Ledger transactions to an existing batch, to a new batch, or to a new batch that Order Entry posts automatically to General Ledger.
To have all transactions appended to a single General Ledger batch, select the Adding to an Existing Batch option. Order Entry must use the same database as Sage 300 General Ledger.
Note: Remember to create and post all General Ledger batches for outstanding transactions before locking periods for General Ledger.
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.
In General Ledger, a source code comprises a source ledger code and a source type code. This table lists source ledger codes and source type codes for each type of transaction generated by Order Entry.
You can change the source type code for each type of transaction created by Order Entry, but you cannot change the source ledger code.
If you change a source type code, the new source code is automatically added to General Ledger, but you must update General Ledger source journal profiles to include transactions on source journals. For more information, see the General Ledger help.
This column displays source type codes for all General Ledger transactions created by Order Entry.
You can change the source type code for a transaction type. If you change it, the new source code is automatically added to General Ledger, but you must update General Ledger source journal profiles to include transactions on source journals. For more information, see General Ledger help.
On this tab, you can review the information that will appear in transaction description, detail reference, detail description, and detail comment fields in the General Ledger transactions created from Order Entry transactions.
To select and arrange the Order Entry information that will appear in these fields, and to specify a separator (such as a hyphen) that appears between this information, select a detail line and click the Open button to open the O/E G/L Integration Details screen.
For more information, see O/E G/L Integration Detail Screen and General Ledger Integration Options.
This field displays the type of information that will appear with unconsolidated details in the Comment column on the O/E G/L Transactions report, on the G/L Journal Entry screen, and on other reports in General Ledger.
To select and arrange the Order Entry information that will appear in these fields, and to specify a separator (such as a hyphen) that appears between this information, select a detail line and click the Open button to open the O/E G/L Integration Details screen.
This field displays the type of information that will appear with unconsolidated details in the Description column on the G/L Transactions report and in that field in the general ledger batch. (The Detail Description field is the description on each detail line, not the main description for the General Ledger transaction.)
To select and arrange the Order Entry information that will appear in these fields, and to specify a separator (such as a hyphen) that appears between this information, select a detail line and click the Open button to open the O/E G/L Integration Details screen.
This field displays the type of information that will appear with unconsolidated details in the Reference column on the G/L Transactions report and in that field in the general ledger batch.
To select and arrange the Order Entry information that will appear in these fields, and to specify a separator (such as a hyphen) that appears between this information, select a detail line and click the Open button to open the O/E G/L Integration Details screen.
This field displays the type of information that will appear in the Description field for a General Ledger transaction (not in the description for a detail line).
To select and arrange the Order Entry information that will appear in these fields, and to specify a separator (such as a hyphen) that appears between this information, select a detail line and click the Open button to open the O/E G/L Integration Details 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.