Defining attributes

To define an attribute, you need to give it a name and associate it with an element and object type. Optionally, you can assign valid values to the attribute, limit an attribute's use to the accounting units within a company group or to the accounts within an account group, and specify whether an attribute is required. Use this procedure to define attributes.

Attribute Matrix

Attribute

Where to use attributes

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

Note: Select Define in the Element Name field on Attribute (MX00.1) to define an element.

Define an attribute

  1. If an appropriate element for the attribute you are going to define does not exist, use Element (MX00.2) to define the element.
  2. Specify this information:
    Element Name

    Specify a name for the element. A user-defined element name does not have to match the attribute name, since the element can be used by several attributes. The name must be unique in the system.

    Note: Different rules apply when defining an element for a transaction attribute.

    Defining a transaction attribute

    Data Type

    Select one of these types:

    • A (Alpha)

    • N (Numeric)

    • D (Date)

    • S (Signed Numeric)

    Field Size

    The maximum field size depends on the data type:

    • Alpha (up to 20 characters)

    • Date (eight characters)

    • Numeric (up to 18 characters)

  3. Use Attribute (MX00.1) to define the attribute.
  4. Specify this information:
    Attribute

    This field contains the attribute's name.

    Column Heading

    You can specify a column heading to be used in Transaction Writer reports where this attribute is used.

    Element Name

    This field is required. You can associate a Lawson-defined element or a user-defined element with a user-defined attribute.

    From Value/Thru Value fields

    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 for the attribute is considered valid for the data type and is accepted.

    Note: Defining valid values makes your lists more accurate.
  5. After adding the attribute, click the Objects button to open the Associate Attribute to Objects (MX00.3) and assign valid object types to the attribute.
  6. Specify this information:
    Object Type

    Select the object types you want to assign to the attribute. The object type determines where you can use the attribute.

    In Multi-Book Ledger, you can assign this object type:

    • Multi-Ledger Entry (MLTRN)

      In General Ledger, you can assign these object types:

    • Accounts (ACCNT)

    • Accounting Units (ACCTU)

    • GL Transactions (GLTRN)

      Defining a transaction attribute

    Required

    Select whether the attribute is required on Accounting Units - Account (GL20.1). If you select Yes, you receive a message stating Values are not defined for required attributes until the attribute value is populated. This is reminder message, not a hard edit; you can add or change an accounting unit even if required attributes are not defined.

    Apply to Object Group

    Depending on the object, you can associate the attribute to a company group, activity group collection, user analysis, or account group. This lets you use the attribute only in companies in the company group, activities in the collection, accounts in the account group, or values in the user analysis. Restricting use of an attribute can be a valuable tool for managing attributes in companies with unique accounting units and attributes. For example, store size might be an appropriate attribute in one company, but not applicable in another.

    Note: When using a company group, only the accounting units associated with companies in that company group can use the attribute.
Related topics