Defining a Transaction Attribute

You can track additional information about a transaction using user-defined fields called transaction attributes. Transaction attributes provide you with additional reporting capabilities and let you create reports in General Ledger with application-specific information in them. This procedure describes only items that are unique when defining a transaction attribute.

Before defining attributes, load Lawson-defined element and attribute definitions and available subledger fields for transactions analysis. Loading Lawson-defined attributes (SCM/FIN)

Note: Only transaction attributes for General Ledger, Recurring Journal, and Allocations can use either a user-defined element or a Lawson-defined element.

To define a transaction attribute

  1. If an appropriate element for the transaction GL, RJ, or CA attribute you are going to define does not exist, use Element (MX00.2) to define the element. Use the following guidelines to enter field values:
    Element Name

    Type a name for the element. An element represents the database field that holds an attribute value. It defines the maximum number of characters and the data type (alphanumeric, numeric, or date) for the field.

    Because transaction attributes are mapped to originating system values for specific source codes, transaction attributes (for all systems except GL, RJ, and CA) must use the Lawson-defined element associated with the originating system value.

    For example, Cash Payment Vendor is an originating system value for the AP (Vendor Payment) source code and is defined with a VENDOR element. You must use the VENDOR element when defining the transaction attribute to associate the Cash Payment Vendor with General Ledger transactions.

    Note: To view the element used by an originating system value, use Source Code (GL05.1) to inquire on the source code. Then select Define in the Originating System Value field on this subform. Use this subform to display available field names for the source code and associated element names.
    Data Type

    Select one of the following data types:

    • A (Alpha)

    • D (Date)

    • N (Numeric)

    Field Size

    The maximum field size depends on the data type:

    • Alpha (up to 32 characters)

    • Date (eight characters)

    • Numeric (up to 18 characters)

  2. Use Attribute (MX00.1) to define the attribute. Use the following guidelines:
    Element Name

    Select an element. Transaction attributes must use the Lawson-defined element associated with the originating system value.

    Note: A source code identifies where a transaction was created within a system. For example, CB is the Lawson-defined source code for the Intercompany Balancing transactions.
  3. Access Source Code (GL05.1) and inquire on the source code to which you want to attach attributes.
  4. Associate up to three transaction attributes with the source code. Use the following guidelines to enter field values:
    Originating System Value

    If you are defining a transaction attribute for GL, RJ, or CA, leave this field blank. There are no originating system values for these systems.

    For other systems, select an originating system value. This field indicates where in the database to retrieve the transaction attribute value from. This value must match the element name assigned to the transaction attribute in Attribute (MX00.1).

    Note: You cannot change or add information on the Attribute Origin (GL05.3) subform. Adding or changing originating system values require customized program changes.
    Attribute

    Select the attribute you want to associate with the source code. The attributes you define in this form are automatically assigned to transactions with the associated source code.

    You can only select user-defined attributes as transaction attributes. The attribute must exist in Attributes (MX00.1).

    Note: The object type for a transaction attribute will be GLTRN (General Ledger Transaction).
    Options (AC, GL, SL, and ML)

    Identify the system(s) you want to be able to use the transaction attribute. Select Yes in the GL field to use the transaction attribute with General Ledger transactions.

Related Reports and Inquiries

To Use
List Lawson and user-defined attributes Attribute Listing (MX201)
List source code information set up for all companies by system code including transaction attributes assigned to the source codes Source Code Listing (GL205)
Related topics