Lawson Software

Lawson Insight Technical Documentation

Generated by:
Documentation generated by Decision Analytics

ERDs Tables Elements Libraries App Forms

AC59


AC59.1 - Employee Vendor Relationship

** Form purpose
Use Burden Codes (AC60.1) to define and maintain burden codes. A burden code
can be used an additional cost that are assigned to transactions in
percentages to more accurately determine business costs.

** Prerequisites
Before you define burdens, you should analyze the post to account categories
where you want to send general and administration (G&A) expenses and overhead
costs.

** Process at a glance
1. Define burden codes on this form
2. Assign burden codes to an activity structure on Account Category Burden
Assignment (AC61.1)
3. Identify where burdens are used on Pool Driver Values (AC62.1)
4. Identify provisional burden rates on Burden Provisional Rates (AC63.1).

** Decision/Impact
You can associate burdens with multiple transaction types in the Driver Type
field. You can select from Company and Work Accounting Unit, Company and Home
Accounting Unit, Activity Company Accounting Unit, Activity, Account Category,
Job Code, Salary Class, or Employee.

Burden codes are identified by defining rules. These rules include step, post
to account category, and driver.

** More help
A burden is a transaction based allocation that are calculated when you run
Activity Posting (AC190).







Updated Files

    ACEMPVEN   -

    CKPOINT    -


Referenced Files

    APCOMPANY  -

    APPROCLEV  -

    APVENGROUP -

    EMPLOYEE   -

    GLADDRESS  -

    GLCHART    -

    GLSYSTEM   -

    HRSECLEV   -

    PRSYSTEM   -


INVOKED Programs

    API4
    ACAC
    ACCL
    IFCU
    IFSG
    IFAC
    IFAU
    SLSE
    SLSU
    HRFN