Element
An element defines the maximum number of characters and the data type for an attribute value. An element must be assigned to every attribute and the element must exist before you can define an attribute that uses that element.
An element can be Lawson-defined or user-defined. If you define an element, you can define it as:
-
Alpha type (up to 32 characters)
-
Numeric type (up to 18 characters)
-
Date type (eight characters)
Note: Lawson-defined elements are pre-loaded, along with Lawson-defined attributes, using Attribute, Element Load (MX100).
Lawson-defined attributes have a one-to-one correspondence with Lawson-defined elements. For example, the Account attribute is associated with an element called Account. Examples of Lawson-defined attributes and corresponding Lawson-defined elements:
| Attribute | Element | Type | Size |
|---|---|---|---|
| Account | Account | Alpha | 6 |
| Account Depth | Account Depth | Numeric | 2 |
| Accounting Unit | Accounting Unit | Alpha | 15 |
| Person Responsible | Person Responsible | Alpha | 15 |
You can also create user-defined elements within the data type and size restrictions listed above. User-defined elements can be more generic than Lawson-defined elements, and can be associated with more than one attribute. Examples of user-defined attributes and user-defined elements:
| Attribute | Element | Type | Size |
|---|---|---|---|
| Store Manager | Alpha 15 | Alpha | 15 |
| Region | Alpha 15 | Alpha | 15 |
| Date Opened | Date | Date | 8 |
| Square Feet | Numeric 9 | Numeric | 9 |
You can also associate a Lawson-defined element with a user-defined attribute. For example, you might use the Person Responsible element (Lawson-defined) with the Store Manager attribute (user-defined).
The relationship between transaction attributes and elements is unique.