Where to use attributes
An object type identifies where an attribute can be used. Each attribute must be associated with at least one object type. Object types are Lawson-defined. This table lists the object types that can be associated with attributes in Lawson applications:
| Object type | For attributes assigned to | In this application |
|---|---|---|
| ACCNT | Accounts |
General Ledger Inventory Control Purchase Order |
| ACCTU | Accounting units |
General Ledger Inventory Control Purchase Order |
| ACGRP | Activity group | Project Accounting |
| ACTRN | Activity transactions | Project Accounting |
| ACTVY | Activities | Project Accounting |
| ASSET | Assets | Asset Management |
| CSHCD | Cash Code | Cash Management |
| CUST | Customer |
Accounts Receivable Order Entry Billing Warehouse |
| GLTRN | General Ledger transactions | General Ledger |
| ITEM | Item |
Inventory Control Purchase Order Order Entry Warehouse Production Order |
| LEASE | Leases | Lease Management |
| ANLYS | User analyses | Strategic Ledger |
| SLTRN | Strategic Ledger transactions | Strategic Ledger |
| VENDR | Vendor |
Accounts Payable Invoice Matching Purchase Order |
Using attributes with accounts
You can use attributes to classify and group accounts. For example, you might want to determine how well your organization can meet its immediate current debt obligations. To do this you want to look only at assets that can be converted to cash quickly. You could classify select asset accounts with an attribute of Liquid Asset and compare those accounts to your liabilities.
An alternative to using attributes with accounts is to use account groups. Account groups let you combine sequential or nonsequential account ranges into a group for reporting and inquiries. For example, to define a report on the consolidated totals of accounts 4000 through 4999 and 6000 through 6999, you can define an account group to include those accounts. If you would select the sequential range of 4000 through 6999, all account would be included.
When creating account groups, you can only select accounts by account number. In contrast, using attributes lets you group accounts using a wide range of characteristics for selection.
You define groups of accounts using Account Group (RW40.3) or List (MX10.1), and can select those groups of accounts when using Account Analysis (GL95.1) for inquiry or when creating Report Writer reports. Using lists
Using attributes with accounting units
When you use attributes with accounting units, you have the flexibility to view your organization from different perspectives without actually changing your company structure. The previous example shows how ABC Company used attributes to view their profitability based on the region in which a store was located. They could associate additional attributes with each accounting unit that would let them view profitability by store size, by person responsible, and more.
An alternative to using attributes with accounting units for grouping is to use level groups. Level groups let you combine sequential or nonsequential level ranges into a group for reporting and inquiries. For example, to define a report to show the consolidated totals for accounting units with a level addresses of 01-101, 01-103, and 01-109, you can define a level group to include just the three ranges representing each accounting unit. If you would select the sequential range 01-101 to 01-109, the range includes values from other accounting units.
When creating level groups, you can only select accounting units by level address. In contrast, using attributes lets you group accounting units using a wide range of characteristics for selection.
You define groups of accounting units using Level Group (RW40.1) or List (MX10.1), and can select specific groups of accounting units when using Account Analysis (GL95.1) for inquiry or when creating Report Writer reports.