Lawson Software

Lawson Insight Technical Documentation

Generated by:
Documentation generated by Decision Analytics

ERDs Tables Elements Libraries App Forms

GL05

GL05.1 - Source Code

Use GL05.1 (Source Code) to define and maintain user- and Lawson-defined
source codes. A source code identifies where transactions are created within a
system. For example, JE is the Lawson-defined source code for the General
Ledger Journal Entry transactions.

You can also associate up to three transaction attributes with the source
code. Each time you assign the source code to a transaction, the attributes
you define in this form are automatically assigned. You can also limit the use
of the transaction attribute to the Activity Management, General Ledger, and
Strategic Ledger systems.

Before you use this program, you should have run GL105 (System, Source Code
Load) to load Lawson-defined source codes.

To define multiple source codes or source code options at the same time,
choose the Multiple Entry button to open the Source Codes subform.

Run GL205 (Source Code Listing) to list all source codes and any attributes
assigned to a source code.

Updated Files

    GLELMLIST  - All records associated to a source code are deleted when the
                 source code is deleted.


    GLSCCAT    - Used to store the source code transaction attributes
                 maintained by this program.


    GLSRCCODE  - Used to store the source code definitions maintained by this
                 program.


    MXOBJCAT   - Stores a transaction / attribute relationship for all
                 attributes assigned to a source code.



Referenced Files

    MXCATDEF   - Used to validate the existence of an attribute.


GL05.2 - Source Codes

Use GL05.2 (Source Codes) to define and maintain multiple user- and
Lawson-defined source codes at one time. A source code identifies where a
transaction was created within a system. For example, ES is the Lawson-defined
source code for the General Ledger Error Suspense transactions.

Source codes are used to identify and group similar transaction lines for
reports and analysis. You can also assign up to three attributes to the source
code. The attribute must exist in MX00.1 (Attribute). These three attributes
are identified as default analysis.

Before you use this program, you should have run GL105 (System, Source Code
Load) to load Lawson-defined source codes.

To define transaction attribute information for a Lawson- or user-defined
source code, choose the Attributes button to open the Source Code Attributes
subform. An asterisk displays next to the button if transaction attributes are
defined for a source code.

Updated Files

    GLELMLIST  - Used to associate a source code transaction attribute to a
                 subledger field. Associated records are deleted when a source
                 code is deleted.


    GLSCCAT    - Stores all the source code transaction attributes maintained
                 by this program.


    GLSRCCODE  - Stores all source codes maintained by this program.

    MXOBJCAT   - Used to store transaction object/attribute relationship
                 records.



Referenced Files

    MXCATDEF   - Used to validate the existence of an attribute.


GL05.3 - Attribute Origin

Use GL05.3 (Attribute Origin) to display and maintain the available field
names for the source code and associated element names.

Updated Files

    GLELMLIST  - Used to store the subledger field definitions maintained by
                 this program.


    GLSRCCODE  - This file is updated with the last subledger field sequence
                 number when a new subledger field is added.



Referenced Files

    GLSCCAT    - Used to validate the existence of a source code attribute
                 associated to the subledger field.


    MXELEMENT  - Used to validate the existence of the element name.