|
|
GL01.1 - System Control
**Form Purpose
Use System Control (GL01.1) to define and maintain system interfacing and
closing options for a general ledger company and system code. Interface
controls determine how subsystem journal entries transfer to the General
Ledger system. Closing controls determine whether you must close a subsystem
period before the general ledger period. For example, if you select AP
(Accounts Payable) in the System field, you can only post transactions from
the AP system to the company you select.
You can create as many system control relationships for one company as
necessary.
Note Before you use this program, you should have run GL105 (System, Source
Code Load) to load Lawson-defined system and source codes.
Updated Files
GLCODES - Used to store the company / system code relationship
definitions maintained by this program.
JBOOKHDR - Used to validate the journal book and update the journal book
used flag.
Referenced Files
GLADDRESS - File is accessed by a common routine used by this program.
This file is not used by this program.
GLCHART - File is accessed by a common routine used by this program.
File is not used by this program.
GLHOLDCODE - Used to validate the hold code.
GLSYSTEM - Used to validate the company.
JBKOPCODE - Used to validate operator access to the entered journal book.
JBKSYSCODE - Used to validate that the journal book is not restricted from
this system code.
SYSTEMCODE - Used to validate the existence of the system code.
GL01.2 - System Control
**Form Purpose
Use System Control (GL01.2) to link a multiple system codes to a general
ledger company and define and maintain options to control system interfacing
and closing.
Interface controls determine how subsystem journal entries transfer to the
General Ledger system. Closing controls determine whether you must close a
subsystem period before the general ledger period. For example, if you select
AP (Accounts Payable) in the System field, you can only post transactions from
the AP system to the company you select.
You can create as many system control relationships for one company as
necessary.
Note Before you use this program, you should have run GL105 (System, Source
Code Load) to load Lawson-defined system and source codes.
Updated Files
GLCODES - Used to store the company / system code relationship
maintained by this program.
JBOOKHDR - Used to validate the existence of the journal book. Updates
the journal book used flag.
Referenced Files
GLADDRESS - This file is accessed by a common routine used by this
program. This file is not used by this program.
GLCHART - This file is accessed by a common routine used by this
program. This file is not used by this program.
GLHOLDCODE - Used to validate the existence of the hold code.
GLSYSTEM - Used to validate the company.
JBKOPCODE - Used to validate the operator's access to the journal book.
JBKSYSCODE - Used to validate the journal book's restriction from the
system code.
SYSTEMCODE - Used to validate the existence of the system code.
GL01.4 - System Codes
**Form Purpose
Use System Codes (GL01.4) to define remote site processing information or to
define system codes for non-Lawson Software applications. You can also
determine whether commitments are updated and budget amounts are edited for
activities that are transferred to the Activity Management system.
**More Information
If you work in a multiple machine or multiple database environment, choose
the Remote Site button to open the Remote Site Indicator subform. On each
machine or database that creates subsystem transactions, use the subform to
identify the machine or database you want to transfer general ledger
transactions to. An asterisk (*) displays next to the button if remote site
information is defined.
Updated Files
SYSTEMCODE - Used to store the system code definition maintained by this
program.
Referenced Files
None.
INVOKED Programs
IFSG
|
