Defining a transaction attribute

You can track additional information about a transaction in user-defined fields called transaction attributes. Transaction attributes provide additional reporting capabilities and let you create reports in Project Accounting that include application-specific transaction details. This procedure describes the unique procedure for defining a transaction attribute.

For detailed procedures on defining an activity attribute, see Defining an attribute.

Before defining attributes, load Lawson-defined element and attribute definitions and available subledger fields for transactions analysis. See Loading Lawson-defined attributes (SCM/FIN)

Access Attribute (MX00.1).
Define the transaction attribute. Use these guidelines to specify the field values:

Attribute

Specify or select an attribute name and description.

Column Heading

Specify a column heading to be used in Transaction Writer report.

Note: The column heading must not exceed the element name field size.

Element Name

Select an element.

Note: Transaction attributes must use the Lawson-defined element associated with the originating system value.

From Value

Specify the values that you want to include in the attribute. The values must meet the element parameters you defined in MX00.2 (Element). Select a specific range of values to include in the attribute. Specify the beginning value in this field.

Through Value

Select a specific range of values to include in the attribute. Specify the ending value in this field. If you leave this field blank, then the beginning value is set as default.

Description

Specify a description for the attribute value range entered.
After adding the attribute, click Objects to open the Associate Attribute to Objects (MX00.3) subform. Assign the attribute to the ACTRN (Activity Transaction) object type. Select whether or not the attribute is required in Accounting Units - Accounts (GL20.1), Activity Attribute (AC13.1) Asset Attribute (AM23.1) and User Analysis Values (SL00.1). You can associate the attribute to an Object Group as well.

Note: You can assign the same transaction attribute to object types ACTRN, GLTRN, MLTRN, and SLTRN.
Access Source Code (GL05.1) and inquire on the source code to which you want to attach transaction attributes. A source code identifies where a transaction is created within a Lawson application. For example, RS is the Lawson-defined source code for Resource Time Entry transactions created in Project Accounting.
Assign up to three transaction attributes to the source code. Use these guidelines to specify the field values:

Attribute

Select the attribute that you want to associate with the source code. The attributes you define in this form are automatically captured in transactions generated using the source code. The attribute must exist in Attributes (MX00.1).

Originating System Value

Select an originating system value. This maps data from the originating system to the transaction attribute. The element associated with the originating system value must match the element name assigned to the transaction attribute in Attribute (MX00.1). For example, in source code AD you can select the Invoice Vendor Number originating system value for a Vendor transaction attribute. The Vendor transaction attribute must be associated with the Lawson-defined Vendor element.

Note: You cannot change or add information on the Attribute Origin (GL05.3) subform. Adding or changing originating system values require customized program changes.

Options (AC, GL, SL, and ML)

Select the applications in which you want to capture the transaction attribute. Select X (Yes) in the AC field to use the transaction attribute in Project Accounting transactions.

Note: You can capture the same transaction attribute in General Ledger, Strategic Ledger, and Multi Ledger transactions.

Related reports and inquiries


To	Use
List Lawson and user-defined attributes	Attribute Listing (MX201)
List source code information set up for all companies by system code	Source Code Listing (GL205)