Lawson Insight Technical Documentation

Generated by:
Documentation generated by Decision Analytics

ERDs Tables Conditions Elements Libraries APIs Forms

AC60


AC60.1 - Burden Codes



Use Burden Codes (AC60.1) to define and maintain burden codes. Burden
codes identify overhead, fringe benefits, or other indirect costs associated
with an activity transaction.



**Process at a Glance


1. Define burden codes on this form
2. Assign burden codes to an activity group or posting activity
on Account Category Burden Assignment (AC61.1)
3. Define burden eligibility criteria on Pool Driver Values (AC62.1)

4. Define burden rates on Burden Pool Rates (AC63.1)



**More Information

Burden codes, burden pools, and burden assignments are used during Activity
Posting (AC190) to calculate and create burden transactions for eligible
activity
transactions. For example, a labor cost transaction may generate two burden
transaction--one for fringe and one for G&A overhead.
Each burden code includes:



- the account category to which the burden transaction should
be posted


- the driver type to determine what transaction data triggers
the burden transaction


- the order in which the burden should be calculated (with respect
to other burden codes)


- information about whether the burden should post to General
Ledger


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. Note that the following driver
types can only be used with employee resource transactions:



- Company and Home Accounting Unit


- Job Code


- Salary Class


- Employee

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





Updated Files

    ACBRDNHDR  -


Referenced Files

    ACACCTCAT  -

    ACACTIVITY -

    ACBRDNDTL  -

    ACBRDNPOOL -

    ACGLCODE   -


AC60.2 - Additional Information


Use Additional Information (AC60.2) if you want to post burdens to General
Ledger or to create off-set burden transactions in Project Accounting or
General Ledger.
Burden transactions are posted to the activity contained in the source
transaction, and to the account category specified in the burden code.


**More Information

You can create offset entries for burden transactions. This lets you
charge one activity/account category with burden costs, and "balance" the
burden transaction by creating an offset transaction that posts to another
activity and account category. Burden offset transactions are posted to the
offset activity and account category specified on AC60.2.
If you post burdens to General Ledger, you must define GL information
to identify where the burden transaction should be posted. The General Ledger
transaction can be posted to an account you specify using the company and
accounting unit in the transaction from which they are triggered, or they
can be posted to a specific company, accounting unit, and account.




Updated Files

    None.


Referenced Files

    ACACCTCAT  -

    ACACTIVITY -

    ACGLCODE   -


INVOKED Programs

    ACAC
    ACTA
    API4
    IFAC
    IFCU
    IFOB
    IFSG
    SLSE
    SLSU
    IFLU
    IFUP