AC60.1
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 AccountCategory 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 eligibleactivity 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 burdentransaction - the order in which the burden should be calculated (with respect to otherburden 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 - No Description Available.



Referenced Files
ACACCTCAT - No Description Available.
ACACTIVITY - No Description Available.
ACBRDNDTL - No Description Available.
ACBRDNPOOL - No Description Available.
ACGLCODE - No Description Available.



INVOKED Programs
ACAC
ACTA
API4
IFAC
IFCU
IFOB
IFSG
SLSE
SLSU
IFLU
IFUP



File created: Thu Jun 09 11:04:43 2016

Nogalis, inc.
Contact Us

All trademarks and registered trademarks are the property of their respective owners.