Transaction attribute

Transaction attributes are user-defined fields that capture specific transaction information for transactions that originate in Lawson applications. For example, you might attach the vendor number and the cash code to General Ledger transactions that result from payments you interface from Accounts Payable. This enables you to include the transaction attribute information:

  • To customize transaction reports in Strategic Ledger

  • As a dimension in a Strategic Ledger data mart

See Setting up Attribute Matrix and views.

A source code identifies where transactions are created within a system. For example, JE is the Lawson-defined source code for General Ledger Journal Entry transactions. For each source code, you can assign up to three attributes and corresponding originating system values. This enables you to select three originating values from a group of fields that you can transfer from the subsystem and attached to an entry when it is transferred to General Ledger and Strategic Ledger. The system automatically attaches the selected attributes to all entries for the source code when you post entries from the subsystem.

Example

AP is a source code that represents vendor payments originating in the Accounts Payable subsystem. This table is a portion of the Source Code Listing (GL205), which shows the pre-defined fields that can be associated with the AP source code.


              
              Source Code    Description                      Status      Type      Attributes   Description               AC GL SL ML
-----------    ------------------------------   --------    ------    ------------ ------------------------- -- -- -- --
         
   AP         Vendor Payment                   Active      Lawson    INV-USR-01   Invoice User Field 1        N  N  N  Y
                                                                     INV-USR-02   Invoice User Field 2        N  N  N  Y
                                                                     INV-USR-03   Invoice User Field 3        N  N  N  Y

                                                                               Field   Data
                        Subledger Attribute              Element Name          Size    Type     Subledger Field Id
                        ------------------------------   --------------------  ----- --------   --------------------
                        Payment Transaction Type         BANK TRANSACTION TYP    3              CHK-BANK-INST-CODE
                        Payment Cash Code                CASH CODE               4              CHK-CASH-CODE
                        Cash Payment Vendor              VENDOR                  9              CHK-PAID-VENDOR
                        Cash Payment Transaction Nbr     BANK TRANSACTION NBR   10              CHK-TRAN-NBR
                        Invoice user field 1             INVOICE USER FIELD 1   15              ISR-INV-USR-FLD-01
                        Invoice user field 2             INVOICE USER FIELD 2   15              ISR-INV-USR-FLD-02
                        Invoice user field 3             INVOICE USER FIELD 3   15              ISR-INV-USR-FLD-03
                        Invoice user field 4             INVOICE USER FIELD 4   15              ISR-INV-USR-FLD-04
                        Invoice user field 5             INVOICE USER FIELD 5   15              ISR-INV-USR-FLD-05

Transaction attributes and elements

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

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.

For example, Cash Payment Vendor is an originating system value for the AP (Vendor Payment) source code and is defined with a VENDOR element. You must use the VENDOR element when defining the transaction attribute to associate the Cash Payment Vendor with General Ledger transactions.

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

An element represents the database field that holds an attribute value. It defines the maximum number of characters and the data type (alphanumeric, numeric, or date) for the field.

Some elements are Lawson-defined and can be loaded with 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 subsystem transactions.

Business example

The controller of Moose Wood Outfitters is defining an invoice distribution entry. The application automatically assigns a source code of AD (Vendor Invoice Distribution) to the new entry. Three pre-defined originating system values are attached 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 you enter on the invoice will be transferred to General Ledger with the invoice detail lines when distributions are posted.