User Analysis Entry (SL40.6)
Use User Analysis Entry (SL40.6) to select the user analysis values you want to associate with a transaction. You can have as many user analyses as you need as long as the size of the data for all user analyses in a transaction, including the comma separator automatically placed between each field, does not exceed 103 characters. If you assign user analysis values in header areas, those user analysis values default to all detail lines. You can override user analysis values in each detail line.
Processing Effect
The processing cycle includes:
1. Maintaining transaction errors using SL40.1 (Error Transaction Edit).
2. View transactions using SL90.1 (Strategic Ledger Transaction Analysis).
3. Defining a Strategic Ledger using SL50.1 (Strategic Ledger).
4. Post strategic ledger transactions using SL190 (Strategic Ledger Posting).
5. Analysis posted information using SL95.1 (Ledger Analysis).
More Information
There are three conditions that affect how you can select user analysis values. (The user analyses you can select values from display on the left.)
- If you only attached a user analysis group to a chart of accounts, you can select any user analysis value defined for the user analysis fields included in the group, including blank values.
- If you attached a user analysis relation to a general ledger detail or summary account, you can only select user analysis values according to the conditions you defined for the user analysis relation.
- If you did not define any values for the user analysis field in the group you attached to the chart of accounts, you can define any value for that user analysis field. However, any value you type is used for that transaction only. You cannot define any value in a transaction if you assign a user analysis relation to a general ledger detail or summary account.
For example, in SL00.1 you define two user analyses: User Analysis A and User Analysis B. Each contains the following values and classes. (Note: The user analysis values must be active.)
| Values | Class | |
|---|---|---|
| User Analysis A | Milk | 001 |
| Butter | 002 | |
| Eggs | 003 | |
| User Analysis B | Truck | 004 |
| Driver | 005 | |
| Miles | 006 |
In SL01.1 you combine User Analysis A and User Analysis B into User Analysis Group AB.
Use SL02.1 to assign user analysis group AB with a user analysis relation. In the ClassX column, you select the classes associated with the user analysis values defined in SL00.1 you can use for the account. (Note: You CAN assign classes more than once to create as many relations as necessary.) For example:
|
User Analysis A Class 1 |
User Analysis B (these display Class 2 (fixed)001 |
|---|---|
| 001 | 004 |
| 001 | 004 |
| 002 | 004 |
| 004 | 006 |
When you are in a processing form that contains an account code, GL40.1 (Journal Entry) for example, select the account number you assigned the relation to. (Remember: in GL00.4 or GL00.5) In this form, User Analysis A and User Analysis B display on the left. This is where the relation is used as the validation mechanism. If you select Milk (Class 001) in the User Analysis Value field for user analysis A, you can ONLY select Truck (Class 004) or Driver (Class 005) for user analysis B because of the relation you set up in SL02.1.
Also, if you select Butter (Class 002) in the User Analysis Value field for user analysis A, you can only select Truck (Class 004) or Miles (Class 006) for user analysis B.
After you process transactions for the Lawson application you included user analysis values in (for example, GL40.1 (Journal Entry)), you must complete the Strategic Ledger processing cycle to summarize and analyze strategic ledger data.