Defining an attribute

To define an attribute, assign it a name and associate it with an element and object type. Optionally, you can assign valid values to the attribute and specify whether an attribute is required. Use this procedure to define attributes.

Before defining attributes, load Lawson-defined attribute definitions and available subledger fields for transaction analysis.

Loading Lawson-defined attributes and elements

Define an attribute

If an appropriate element for the attribute does not exist, use Element (MX00.2) to define the element.
Specify this information:
Note: Select Define in the Element Name field on Attribute (MX00.1) to define an element.
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.

Data Type
Select one of these data types:
- A (Alpha)
- D (Date)
- N (Numeric)
- S (Signed Numeric)
Field Size
Specify a field size. The maximum field size depends on the data type:
- Alpha (up to 32 characters)
- Date (eight characters)
- Numeric (up to 18 characters)
Use Attribute (MX00.1) to define the attribute.
Specify this information:

Attribute

This field contains the attribute's name.

Column Heading

Leave this field blank, it is used only for transaction attributes.

Element Name

Select a Lawson-defined or user-defined element to identify the attribute's data type and size.

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, any entry valid for the attribute's data type and size are accepted.

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).

Interfacing valid attribute value ranges to attribute matrix
After adding the attribute, click the Objects button to access the Associate Attribute to Objects (MX00.3) and assign valid object types to the attribute.
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. For Accounts Payable, you can assign these object types:
- Account (ACCNT)
- Accounting unit (ACCTU)
- Cash code (CSHCD)
- Vendor (VENDR)
You can assign several object types to the same attribute.
Required

Select whether the attribute is required. If you select Yes, a message appears on the Attributes subform (from the Attributes button) on Vendor (AP10.1) until the field is populated. This is a reminder message, not a hard edit. You can add or change a vendor even if required attributes are not defined.