Use this format to import an entire burden template which has been created using a software application outside MPM. You can create new or update existing burden templates. Importing burden template data does not completely replace a burden template. Any burden templates not affected by the import file remain unchanged by the import.
Burdens should be imported in the burden template import file in the order you want them applied against the resource.
Importing a burden template for an existing burden template will not replace the entire burden template. Only the requested fields are updated.
Fields 4 and 5 may be repeated to include a maximum of ten burden codes in each burden template.
To successfully import your data, the import file has be in comma delimited ASCII file format.
In the table that follows, an * indicates a required field.
In the Type column:
A = alphanumeric
N = numeric
Y/N = Yes or No
For more information on the table, see Import File Formats Legend.
Field Position |
No. of Chars |
Type |
Field Content |
1* |
3 |
A |
Global import type: enter TMP for Burden Templates |
2* |
20 |
A |
Burden Template ID |
3 |
40 |
A |
Burden Template Description |
4 |
10 |
A |
Burden Code; must already exist |
5 |
1 |
N |
Apply burden rates against: 1 = Hours |
Each record must contain a minimum of four commas, one after each field except the last field (even those being left blank), and end with a carriage return.
This record imports the ENG1 burden template which applies the EOH burden against Prime, the FOH burden against Previous Subtotal, the G&A burden against Total Burdened, the COM burden against Total Cost, and the LF burden against Total Cost.
TMP,ENG1,Engineering Burden,EOH,2,FOH,3,G&A,5,COM,6,LF,6