You can upload task budget data into People Hub using a structured text file. This guide covers the file format requirements, data column rules, and how to resolve any validation errors that appear during upload.

📌Note: This guide is intended for administrators.

File name requirements

Before uploading, ensure your file meets the following naming requirements:

The file must be a text file with a .txt extension (e.g. filename.txt).
The filename must follow the format Prefix_Description.txt:
- Prefix — up to 10 characters in length (e.g. TSKBUD).
- Description — a descriptive label following the underscore.

🤓Tip: For scheduled interfacing, the filename must contain a set prefix followed by an underscore and description. For example, TSKBUD_Description.txt.

Data column requirements

Each record in the file must include the following columns in order:

Column	Field name	Max length	Mandatory
1	TEAM_AREA_CODE	6 characters	Yes
2	TASK_CODE	13 characters	Yes
3	START_DATE	YYYYMMDD	Yes
4	END_DATE	YYYYMMDD	Yes
5	BUDGET_TYPE	—	Yes
6	BUDGET_VALUE	—	Yes

Budget types

The BUDGET_TYPE field determines how budget and duration values are expressed. The following types are supported:

Budget type	Description
Hours / Minutes (HH:MM)	Budget and duration expressed in hours and minutes in HH:MM format. For example, `02:30` = 2 hours 30 minutes.
Hours / Minutes Decimal	Budget and duration expressed as a decimal hours value where the decimal represents a fraction of an hour. For example, `2.5` = 2 hours 30 minutes, `1.25` = 1 hour 15 minutes. Note: this is not hours and minutes notation — `2.30` would mean 2 hours 18 minutes, not 2 hours 30 minutes.
Units	Budget expressed as a unit count rather than a time value (e.g. number of items processed). Duration is not applicable for unit-based tasks.

File layout examples

Tabular format

The following shows a sample layout with representative data:

TEAM_AREA_CODE	TASK_CODE	START_DATE	END_DATE	BUDGET_TYPE	BUDGET_VALUE
100	150	20260313	20260322	D	0.5
1003	157	20260313	20260322	D	1.5
1003	12	20260313	20260322	D	1.5
1004	14	20260313	20260322	D	10

CSV format

The same data represented in CSV format:

100,150,20260313,20260322,D,0.5 1003,157,20260313,20260322,D,1.5 1003,12,20260313,20260322,D,1.5 1004,14,20260313,20260322,D,10

Validation and error messages

When you upload a file through People Hub, an initial validation check is performed to confirm:

File format.
Field size validation.
Mandatory fields are populated.

If any records fail validation, error messages are displayed to help you identify and resolve the issue.

Validation errors

#	Field	Error message
1	TEAM_AREA_CODE	Please enter a Team Area Code - this field is required. Record [n]
2	TASK_CODE	Please enter a Task Code - this field is required. Record [n]
3	START_DATE	Please enter a Start Date - this field is required. Record [n]
4	END_DATE	Please enter an End Date - this field is required. Record [n]
5	BUDGET_VALUE	Please enter a Budget Value - this field is required. Record [n]
6	START_DATE	The start date "[value]" isn't a valid date format. Please use YYYYMMDD format. Record [n]
7	END_DATE	The end date "[value]" isn't a valid date format. Please use YYYYMMDD format. Record [n]
8	TEAM_AREA_CODE	The team area "[value]" wasn't found in the system. Please enter a valid team area. Record [n]
9	TASK_CODE	The task code "[value]" wasn't found in the system. Please enter a valid task code. Record [n]
10	TEAM_AREA_CODE	The team area code exceeds the maximum length of 6 characters. Record [n]
11	TASK_CODE	The task code exceeds the maximum length of 13 characters. Record [n]
12	BUDGET_VALUE	The budget value exceeds the maximum allowed size. Record [n]
13	TASK_BUDGET	Duplicate task budget found: Team Area "[value]", Task Code "[value]", Start Date "[value]", End Date "[value]" appears [n] times in the file.

Result messages

#	Message
14	We found validation errors in your file, so no records were saved. Please fix the errors above and upload again.

Re-running a file

When you need to re-run an interface, a full file is required for the relevant team area code, task codes, and date range.

When a new file is processed, the validation routine automatically removes any previously loaded records that match the same team area code, task code, start date, and end date — then replaces them with the values from the new file.

📌Note: When completing re-runs, the validation routine deletes and replaces all matching transactions. Always provide a full file for the relevant team area code, task codes, and dates.

Example

The following example shows how re-processing works when a new file is received:

File 1 — initial load:

TEAM_AREA_CODE	TASK_CODE	START_DATE	END_DATE	BUDGET_VALUE
1000	150	20260313	20260322	0.5

File 2 — new file received:

TEAM_AREA_CODE	TASK_CODE	START_DATE	END_DATE	BUDGET_VALUE
1000	150	20260316	20260322	1.25

When File 2 is processed, the record for Team Area 1000, Task Code 150, Start Date 20260316, End Date 20260322 is removed and replaced with the new budget value of 1.25.

Frequently asked questions

If some records fail validation, will the rest of the file still upload?

Yes. Records that pass validation will upload and display in People Hub. Failed records are reported to you with a reason for the failure.

What happens when the file is rejected?

Where records fail validation, the file is given a status of unprocessed and you are advised of the errors.

What else should I be aware of?

All interface types to be loaded must be configured as an interface type before loading data.
The file must use the prefix of the fixed filename as configured on the interface.
Nightly loads are completed via Oracle DBMS_JOBS.
If a day is missing from the file, it will not be populated with data — add dummy data of 0 for any missing days.
You can only load a file for a period or a specific date.

Upload a task budget file in People Hub