Defining an attribute (DST HCM)

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, limit an attribute's use to the items within an item group list, and indicate 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. See Loading Lawson-defined attributes and elements.

Follow these steps to define an attribute:

  1. If an appropriate element for the attribute does not exist, then use Element (MX00.2) to define the element.

    Use these guidelines to specify the field values:

    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)

    • Signed Numeric (up to 99 characters)

  2. Use Attribute (MX00.1) to define the attribute. Use these guidelines to specify the field values:
    Attribute

    This field contains the name of the attribute.

    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 data type and size of the 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 valid for the attribute's data type and size 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 valid attribute value ranges to Attribute Matrix (DST).

  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 you want to assign to the attribute. The object type determines where you can use the attribute. For Order Entry and Warehouse, you can assign these object types:

    • Item (ITEM)

    • Customer (CUST)

    For Billing, you can assign these object type:

    • Customer (CUST)

    You can assign several object types to the same attribute.

    Required

    Select whether the attribute is required.

    Apply to Object Group

    You can associate the attribute with an item list to limit its use to items associated with item groups in the list. Restricting use of an attribute helps you better manage attributes when you have several item groups that track different kinds of business operations.

Related topics