Transaction attribute overview (AC)

You can track additional information about an activity transaction in user-defined fields called transaction attributes. Transaction attributes provide you with additional reporting capabilities and can make reconciliations easier at period-end. For example, you can attach the vendor number and the invoice description to activity transactions created from Invoice Distribution Closing (AP175). This lets you create reports in Project Accounting that include application specific transaction details.

For each source code, you can assign up to three attributes and corresponding originating system values. This lets you select three originating values from a group of fields that can be attached to an activity transaction when it is transferred to Project Accounting. The system automatically attaches the selected attributes to all entries for the source code when you post entries.

Note: A source code identifies the event that created a transaction. For example, AD represents a vendor invoice, BD is an activity burden, and PW is employee payroll wages.

Example

AD is a source code that represents vendor invoice distributions originating in the Lawson Accounts Payable application. Source Code Listing (GL205), shows the pre-defined fields that can be associated with the AD source code.

Transaction attributes and elements

Because transaction attributes are mapped to originating system values for specific source codes, the transaction attributes must use the Lawson-defined element associated with the originating system value.

Note: You must create user-defined transaction attributes for each originating system value that you assign to a source code.

For example, Invoice Vendor Number is an originating system value for the AD (Vendor Invoice Distribution) source code and is defined with an VENDOR element. You must use the VENDOR element when defining the transaction attribute to associate the Invoice Vendor Number with activity transactions.

Illustration: Originating system values and transaction attributes must share the same element

An element determines the size and type of the attribute field. It defines the maximum number of characters and the data type (alphanumeric, numeric, or date) for the field.

Lawson-defined elements are loaded during Attribute, Element Load (MX100). For example, Vendor is a Lawson element defined as an alpha field, nine characters in length. You must use Lawson elements with attributes attached to transactions that come from other Lawson applications.

Example of using transaction attributes

An Accounts Payable administrator for LGE Corporation is processing a vendor invoice. The system automatically assigns a source code of AD (Vendor Invoice Distribution) to the invoice entry. Previously, she had attached three pre-defined originating system values to that source code: the invoice vendor number, invoice batch number, and the process level. As a result, the values for the vendor number, batch number and process level specified on the invoice will be transferred to Project Accounting with the invoice detail lines when she posts distributions.

These transaction attributes can be included in a column, used as sort criteria, or used as selection criteria on a Transaction Writer report. For example, she can create a Transaction Writer report that includes the invoice distribution transactions including the vendor number and batch number, sorts the transactions by batch number within invoice number, and produces totals by vendor number.