Transaction attribute

Note: ME is the default source code for Multi-Book Ledger journal entries. For information on defining system codes, see the General Ledger User Guide.

Transaction attributes are attributes attached to a transaction to track additional information about the transaction. Transaction attributes provide you with additional reporting capabilities and can make reconciliations easier at period-end. Transaction attributes are assigned to a source code that is used to identify the origin of the transaction. For each source code, you can assign up to three attributes and corresponding originating system values. There are two types of transaction attributes:

Transaction attributes originating in Lawson subsystems are attached to Lawson-defined source codes that let you select up to three originating values (called originating system values) from a group of database fields that can be attached to a transaction. Subsystem transaction attributes must be user-defined attributes attached to Lawson-defined elements. The values assigned to those attributes in the subsystems are automatically transferred to General Ledger when the transactions are interfaced. You do not assign a value to these attributes as attributes, because these are fields that are assigned values in the course of a normal transaction. For example, if you select the asset number as one of the attributes for source code AS (Asset Adjustment), any time you specify an adjustment in Asset Management, that adjustment transaction is automatically assigned source code AS and the asset number is automatically attached as an attribute value. When you interface the journal entries resulting from this transaction to General Ledger (and, in future releases, to Multi-Book Ledger), the asset number will display in reports as an attribute value for those entries.
Transaction attributes originating in General Ledger or Multi-Book Ledger can be user-defined attributes attached to user-defined elements. You can use the Lawson-defined source codes (JE for General Ledger, ME for Multi-Book Ledger), or you can define your own source codes. Originating system field values are irrelevant to General Ledger and Multi-Book Ledger and attribute values must be assigned manually to the transaction attributes you define. For example, you can use the same AS source code in a Multi-Book Ledger transaction to specify an asset adjustment entry. However, you must specify the asset number manually on the Multi-Book Ledger journal entry to assign the value to the attribute.

Multi-Book Ledger lets you assign attribute values to journal entries, recurring journal entries, and interfaced journal entries.

Transaction attributes and elements

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

Because subsystem 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.

For example, ASSET (Asset Number) is an originating system value for the AS (Asset Adjustment) source code and is defined with an ASSET element. You must use the ASSET element when defining the transaction attribute to associate the asset number with transactions.