Uses of attributes (DST)
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 Order Entry, Warehouse, and Billing:
Note: An attribute can be used with more than one object type.
Object type | For attributes assigned to |
---|---|
ITEM | Items (Order Entry and Warehouse) |
CUST | Customers (Order Entry, Billing, and Warehouse) |
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 | General Ledger, Inventory Control, and Purchase Order |
ACCTU | Accounting units | General Ledger, Inventory Control, and Purchase Order |
CSHCD | Cash Code | Cash Management |
CUST | Customer | Accounts Receivable, Order Entry, Billing, and Warehouse |
GLTRN | General Ledger transactions | General Ledger |
ITEM | Items | 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, and Purchase Order |
Using attributes with items
When you use attributes with items, you have the option to store additional information and select specific items for reports, inquiries, and processing. The previous example shows how you can run reports and sales analysis based on items from a specific sales region.