Defining a Transaction Attribute

You can track additional information about a transaction using transaction attributes. Billing and Revenue Management lets you assign billing rates to transaction attributes for time and materials billing. 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 transaction analysis. Loading Lawson-defined attributes (SCM/FIN)

Procedure flow: Defining a transaction attribute

To define a transaction attribute

  1. Access Attribute (MX00.1).
  2. Define the transaction attribute. Use the following guidelines to enter field values:
    Attribute

    Type or select an attribute name and description.

    Column Heading

    Type a column heading to be used in the Transaction Writer report. The column heading cannot exceed the element name field size.

    Element Name

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

    From Value/Thru Value

    You can assign ranges of valid values to the attribute. Defining valid values ensures consistency for data entry. If you do not define valid values, any entry valid for the attribute's data type and size will be accepted. The values must meet the element parameters you defined in MX00.2 (Element).

    Note: Defining valid values makes your lists more accurate.
    Note: To interface valid attribute value ranges from a non-Lawson system use Attribute Valid Value Interface (MX160). For details, see the Project Accounting User Guide.
    Description

    Type a description for the attribute value range entered.

  3. After adding the attribute, choose the Objects button to open Associate Attribute to Objects (MX00.3).
    Note: You can assign the same transaction attribute to object types ACTRN, GLTRN, MLTRN, and SLTRN.
  4. To assign valid object types to the attribute, use the following guidelines to enter field values:
    Object Type

    Select the Activity Transaction (ACTRN) object type to assign to the attribute. The object type determines where you can use the attribute. You can assign several object types to the same attribute. For example, the Project Lead attribute could be used in General Ledger (with an Account object type), in Project Accounting (with an Activity object type), and in Asset Management (with an Asset object type).

    Required

    Select whether the attribute is required. If you select Yes, a message stating "Set up required attributes using AC13" appears on the Levels tab in Activity (AC10) until the attribute value is populated on Activity Attributes (AC13.1). This is a reminder message, not a hard edit. You can add or change an activity even if required attributes are not defined.

    Apply to Object Group

    You can associate the attribute with an activity group list to limit its use to activities associated with activity groups in the list. Restricting use of an attribute helps you better manage attributes when you have several activity groups that track different kinds of business operations. For example, project lead might be an appropriate attribute for one activity group, but not for another.

  5. Access Source Code (GL05.1) and inquire on the source code to which you want to attach transaction attributes.
    Note: A source code identifies where a transaction was created within a system. For example, PW is the Lawson-defined source code for the Payroll Employee Wages.
  6. Associate up to three transaction attributes with the source code. Use the following guidelines to enter field values:
    Code

    Select a source code which identifies where a transaction was created.

    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. The attribute must exist in Attributes (MX00.1).

    Note: The object type for a transaction attribute will be ACTRN (Activity Transaction).
    Originating System Value

    Select an originating system value. This maps data from the originating system to the transaction attribute. The element associated with the originating system value must match the element name assigned to the transaction attribute in Attribute (MX00.1). For example, in source code AD you can select the Invoice Vendor Number originating system value for a Vendor transaction attribute. The Vendor transaction attribute must be associated with the Lawson-defined Vendor element.

    Note: You cannot change or add information on the Attribute Origin (GL05.3) subform. Adding or changing originating system values require customized program changes.
    Options (AC, GL, SL, and ML)

    Select the system(s) with which you want to be able to use the transaction attribute. Select X (Yes) in the AC field to use the transaction attribute with Project Accounting and Billing and Revenue Management.

    Note: You can capture the same transaction attribute in General Ledger, Strategic Ledger, and Multi 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 Source Code Listing (GL205)
Related topics