List

A list can consist of accounting units, accounts, activities, assets, leases, user analyses, and so on. You can define an automatic or manual list.

Note: You cannot define lists for transaction attributes.

Automatic lists

To define an automatic list, you must select attributes belonging to the object type of your choice (for example, ANLYS) and define value ranges for these attributes. You can define automatic lists using a combination of user-defined and Lawson-defined attributes. Attribute Matrix automatically builds a list of members that meet the criteria specified in the list. Automatic lists are updated automatically any time you use the list.

Manual lists

A manual list enables you to select specific accounts, accounting units, activities, user analysis values, assets, or leases. Manual lists are not based on attributes. For example, you can select individual user analysis without identifying an attribute that is common to all of them. The only members of a manual list are those that you define.

Defining a manual list, as the name implies, is a manual process. Any changes to the list, such as adding or removing user analyses, must also be done manually. For these reasons, manual lists are not often used to define large lists.

You can convert an automatic list to a manual list. A common practice is to define an automatic list first, convert it to a manual list, and then manually add or remove a few select user analyses. It's important to note that you cannot convert a manual list back to an automatic list.

Business scenario information

To help MWO determine what kind of outlet store to construct based on the products consumers are purchasing, MWO wants to set up a data mart organized by quality bracket information stored in the MWO_QUAL attribute. To do this, MWO needs to define an attribute view. Because a view is based on attribute lists, MWO must first set up attribute lists.

MWO wants to view transactions for products organized by quality bracket: High, Medium, and Low. To get the desired view, MWO needs to define three lists that collect information for each quality bracket.