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 Accounts Payable:
Note: An attribute can be used with more than one object type.
| Object type | For attributes assigned to |
|---|---|
| ACCNT | Accounts |
| ACCTU | Accounting units |
| CSHCD | Cash Code |
| VENDR | Vendors |
Note: Ignore these object types: AMBKS, AMITM, APVND,
ICLOC, ICITM, and POBUY. These object types are used only by Lawson-defined
data mart attributes and cannot be assigned by users.
These additional object types are available to be associated with attributes in other Lawson applications:
| Object type | For attributes assigned to | In this application |
|---|---|---|
| ASSET | Assets | Asset Management |
| ACCNT | Accounts | Accounts Payable, General Ledger, Inventory Control, Purchase Order |
| ACCTU | Accounting units | Accounts Payable, General Ledger, Inventory Control, Purchase Order |
| CSHCD | Cash Code | Accounts Payable and 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, Requisitions |
| 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 vendors
When you use attributes with vendors, you have the flexibility to store additional information and select specific vendors for reports, inquiries and processing. The previous example shows how you can run reports based on vendors who sell a specific product type.