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 indicate whether an attribute is required. Use this procedure to define attributes.

Before defining attributes, you should load Lawson-defined attribute definitions and available sub-ledger fields for transaction analysis. See Loading Lawson-defined attributes (SCM/FIN).

Note: Select Define in the Element Name field on Attribute (MX00.1) to define an element.
  1. If an appropriate element for the attribute you are going to define does not exist, then use Element (MX00.2) to define the element. Use these guidelines to specify the field values:
    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.

    See Defining a Transaction Attribute.

    Data Type

    Select one of these 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 these guidelines to specify the field values:
    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/Through 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, then any entry for the attribute will be considered valid for the data type and will be accepted.

    Note: Defining valid values makes your lists more accurate. To interface valid attribute value ranges from a non-Lawson system use Attribute Valid Value Interface (MX160).

    See Interfacing data into General Ledger.

  3. After adding the attribute, click Objects to open the Associate Attribute to Objects (MX00.3) and assign valid object types to the attribute. Use these guidelines to specify the field values:
    Object Type

    Select the object types that you want to assign to the attribute. The object type determines where you can use the attribute. In General Ledger, you can assign these object types:

    Required

    Select whether the attribute is required on Accounting Units - Account (GL20.1). If you select Yes, then you receive a message stating that 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

    You can associate the attribute to a company group for the accounting unit (ACCTU) object type, or account group for the account (ACCNT) object type. This lets you use the attribute only in companies in the company group, or accounts in the account group. 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