You use this program to create General Ledger journals from the transaction journals produced using the AR Invoice Posting, AR Initial Invoice Capture, AR Finance Charge Calculation, Sales Order Entry, Document Print and AR Post Permanent Entries programs.
The program must be used to create the GL journals when the Create general ledger journal option is not enabled for Accounts Receivable (General Ledger Integration).
| Field | Description |
|---|---|
| Start Processing | Create the General Ledger journals according to the
selections and entries made in the Information
pane. Once the journals are created, they are automatically posted into the General Ledger if the Post general ledger journal option is enabled for the module (General Ledger Integration). Use the GL Journal Report program to generate a report of these journals. If the Post general ledger journal option is not enabled for the module, then you need to use the GL Journal Entry or GL Post Multiple Normal Journals program to post the journals into the General Ledger once they are created. See also: Notes and warnings. |
| Print the information currently displayed in the Report pane. | |
| Save Form Values | This option is only enabled in Design mode (Automation Design). Your selections are saved and applied when the
program is run in automated mode. Form values and defaults are applied at operator level. They are not saved at role or group level. |
| Field | Description | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Journal options | |||||||||
| Function | Indicate the sub module transaction journal for which to create, or
to create and post, the General Ledger journal.
See also: Hints and tips. |
||||||||
| After processing completed |
These options are displayed within programs that can be automated. They enable you to indicate the action you want to perform once processing is complete (see Automation Design). |
This pane displays the results of the processing function you selected once processing is complete (unless you selected the option to close the application from the After processing completed section).
The details of the General Ledger journal(s) created are displayed and include:
- the year and period of the journal
- the General Ledger journal number created for the transaction
The following applies for invoices processed to more than one warehouse control account:
-
*Multiple* is printed on the report instead of the General Ledger codes:
-
when Accounts Receivable is integrated as Not linked to GL - distribution report
-
if Accounts Receivable was integrated as Linked to GL in summary at the time the invoice was posted, even if you subsequently changed this to Linked to GL in detail.
-
-
The register number will not print for the warehouse control if Accounts Receivable is integrated as Linked to G/L in summary.
-
'Wh: is printed in the comment line if Accounts Receivable is integrated as Linked to GL in summary.
In all other cases, the General Ledger codes for the multiple warehouses are printed on the report.
![[Note]](images/note.png)
|
|
|
The warehouse codes are taken from the GL Journal Detail file. If you maintained the Warehouse entries in the GL Journal, then the changed ledger entries are printed on the report and could cause the report not to balance. |
|
-
A list of journals can be processed by running this program from the SYSPRO Main Menu (using Ctrl+R) and supplying the list of journals to process using parameters as follows:
ProgramCode LST:YYYYMMJnlNumber YYYYMMJnlNumber YYYYMMJnlNumber
where:
-
ProgramCode represents one of the following program codes: APSPGI, APSPGP, ARSPGI, ARSPGP, ASSPGI, INVPGM, INVPGG, TPMPGI, WIPPGM or WIPPGI.
-
YYYY indicates the year in which the journal was processed.
-
MM indicates the month in which the journal was processed.
Journals processed in the Current, Previous 1 and Previous 2 months can be specified within the same list.
-
JnlNumber indicates the 10 digit sub ledger module journal number or register to process.
Leading zeroes must be entered.
Examples:
APSPGI LST:2017030000000123 2017040000000128 2017050000000131
INVPGG LST:2017030000000123 2017040000000128 2017050000000131
WIPPGI LST:2017030000000123 2017040000000128 2017050000000131
A maximum of 200 journal numbers can be specified. Journals already processed are ignored.
-
-
This program can only be accessed if Accounts Receivable is linked to the General Ledger either in detail or in summary (General Ledger Integration).
-
No General ledger journals are created for invoices processed using the AR Initial Invoice Capture program. The journals can, however, be printed using the AR Invoice Register program.
-
If sales tax is integrated to General Ledger at tax code level, then the ledger code held against the tax code is used for integration.
While the transaction journals are created automatically when you successfully process a transaction, the corresponding General Ledger journals are created and posted according to your selections for the module in the General Ledger Integration program. Refer to Effect of automation level selected.
This program checks that all sales interface entries exist. These include the interfaces for Branch, Warehouse, Product Class and Geographic Area as defined in the General Ledger Integration program. You use the Sales Transactions Maintenance program to correct invalid entries and then rerun this program to create the General Ledger journals for the registers.
-
When errors are detected during the creation of the General Ledger journals from the sub-module transaction journals, the journal may or may not be created depending on the type of error.
Refer to General Ledger Integration Error Handling for additional details.
-
You can use the AR Sales Transaction Journals program to identify the transaction journals for which ledger journals have not yet been created.
-
In process registers found
This message indicates that at least one operator is currently posting Accounts Receivable invoices.
If no operators are posting AR invoices, then use the GL Integration Utility program to reset the 'in process' register flags.
-
GL journal cannot be created because the interface records are missing
If you are running this program manually, then a detailed error message is displayed and the details of the missing sales interface records are written to the Job Logging Query program.
If this program is called from within a posting program (i.e. you selected to automatically create GL journals for Accounts Receivable then the error is only written to the Job Logging Query program.
-
If the GL analysis required option is enabled for a ledger account used in this program (General Ledger Codes or GL Structure Definition) then the Capture GL Analysis Entries program is displayed when you post the transaction, so that you can enter the analysis details. For a sub module transaction, the sub module must also be linked to the General Ledger in Detail at company level (General Ledger Integration) or at ledger account code level (General Ledger Codes or GL Structure Definition). GL analysis entries cannot be entered from sub modules if the sub module is linked to the General Ledger in Summary at company level or at ledger account code level.
Note that the GL analysis required option is ignored for all GL codes which are defined in General Ledger Integration. This applies even when the GL code is manually entered in a posting program. Although GL integration programs may be entered manually, they may also be called automatically by other programs or may be automated, which means that they can never be stopped to allow GL analysis entries to be captured.
If the GL analysis code used does not exist in the GenAnalysisCat table, then a message to this effect is displayed and the program will not prompt for analysis again. The GL journal will be created but not posted until the GL code, GL analysis code and GL journal are corrected.
The Ask Me Later function is only available when the option: Force GL Analysis - GL journal posting is enabled for the sub-module (General Ledger Integration).
General Ledger analysis entries are always distributed in the local currency, regardless of the currency in which the original transaction is processed.
Electronic Signatures provide security access, transaction logging and event triggering. This enables you to increase control over your system changes.
Access to the following eSignature transactions within this program can be restricted at Operator, Group, Role or Company level. You configure this using the eSignature Setup program.
| eSignature Transaction | Description |
|---|---|
| GL Create journal from sub module |
Controls access to the creation of journals from a sub module journal. The GL integration programs which are affected by this eSignature are:
|
| GL Create and post journal from sub module |
Controls access to the creation and simultaneous posting of journals from a sub module journal. The GL integration programs which are affected by this eSignature are:
|
Inserting Application Help
You would typically follow this procedure to display help for the current program in a customized pane that can be pinned to the program window.
Information includes step-by-step instructions for the various functions available within the program, including a brief overview of what the program does, what setup options are required and how to personalize the program.
-
Open the program for which you want to insert application help into a customized pane.
This functionality is only available for a program that has panes.
-
Right-click any form field.
You can also click the triangle menu icon that appears in the title area of a pane.
-
Select Insert Application Help from the context-sensitive menu.
The application help appears in a pane within your program. You can reposition the pane using the docking stickers or pin it to the program window.
Removing the Application Help pane
If you no longer want to display application help in a pane for your current program, you can simply remove it.
-
Select the Close icon in the right-hand corner of the application help pane.
-
Confirm that you want to delete the pane.