...
- Don't use commas in your data field values. Commas are reserved for use as separators.
- If any of the required fields are empty, the upload will fail.
To edit field values, you must correct the values in the spreadsheet file, and upload the file again.
Tip: You can export the existing cost segment values into a CSV file for backup.
| Expand |
|---|
| title | Click here to see the table... |
|---|
|
Notes: - In the following table, required fields are marked with an asterisk (*).
- Allocation names can be no longer than 140 characters.
- The following characters are not allowed: ( ) . ‘ &
- Duplicate allocation names are not permitted.
| | |
|---|
Segment Name* | Required.
Alphanumeric + special characters.
May be up to 30 characters. The following characters are not allowed: ( ) . ‘ & | For example, "Project". Must fully match the name you defined in the Cost Allocation section of the Services | Expense page, but need not be case sensitive. | Allocation Name* | Required.
Alphanumeric + special characters.
May be up to 140 characters. The following characters are not allowed: ( ) . ‘ & | For example, "Project Jupiter". Duplicate names are not permitted. | Allocation Code | Optional.
Alphanumeric + special characters. | For example, "6300". This can be blank or the general ledger (GL) code segment representing the project. NOTE: 'Code' is the expected title of the column and does not change, even if the cost segment name changes. | Parent Allocation Name | Optional. | If applicable, enter the cost segment name that this cost segment belongs to (the parent segment). For example, the “Project” cost segment could be defined as a child segment (subsegment) of another parent cost segment named “Customer”. When the expense report submitter selects a Customer for cost allocation, the Project cost segments for that customer appear. |
|
...