Daily Time Entry Upload

This integration uploads daily time entries. It enables hours entry per day against a time sheet, with time entry date, cost center, task,code/gla and rate category combination.

Connector Overview

Component

Detail

Company Type

Buyer

Supplier

MSP Partner

Version Type

API-A-V1.0

Format

CSV

Prerequisites

Company Details Setting must be turned on for Integration – Daily Time Entry Upload.

User role permission must be turned on for Upload Data and Download Data.

Predecessors

Workers

Related Connectors

Time Sheet Credit Debit Memo Upload

Full Time Sheet Credit Debit Memo Upload

TITO Time Sheet Detail Upload

Daily TITO Upload

Time Sheet Submit Upload

File Formatting

Header

Component

Required?

Definition/Use

Notes

Value

Type

Yes

Time sheet

If you have a custom connector name for a standard connector, you may use the exact same custom name for the Type header; otherwise, you must use the standard name shown in the Value field.

Daily Time Entry Upload

Language

No

Determines the language to be used for values in the file, such as drop-down lists and radio buttons. Column headers will always default to the upload user's preferred language.

The valid language values are:

Arabic (Standard Arabic)
Chinese (Simplified)
Chinese (Traditional)
Dutch (Netherlands)
English (United Kingdom)
English (United States)
French (Canada)
French (France)
German (Germany)
Hebrew (Israel)
Hungarian (Hungary)
Italian (Italy)
Japanese (Japan)
Korean (Korea)
Mongolian (Mongolia)
Polish (Poland)
Portuguese (Brazil)
Portuguese (European)
Russian (Russia)
Spanish (Mexico)
Swedish (Sweden)

Number Format

No

Determines the number format to be used in the file.

The valid values are:

  • “#,##9.99" (Example: "1,234,567.99”)

  • “#.##9,99" (Example: "1.234.567,99”)

  • “#'##9.99" (Example: "1'234'567.99”)

  • “# ##9,99" (Example: "1 234 567,99”)

The quotes are required even if the value does not have a comma in it. If the header field is not present, the value will default to "#,##9.99" (Example: "1,234,567.99").

Date Format

No

Determines the data format used in the file.

The valid values are:

  • MM/DD/YYYY

  • DD/MM/YYYY

  • YYYY-MM-DD

If this header field is not present, the value will default to MM/DD/YYYY.

Buyer

Yes if supplier upload

Indicates which buyer information being uploaded

Valid SAP Fieldglass buyer code

Comments

No

Upload comments.

Any text the user would like to enter may be entered here.

Values entered in this header field will appear in the Comments field at the bottom of all time sheets included in the upload file and will be visible to any application user that has access to view the time sheet. The comment entry date will be the time stamp of the upload and the author name will be the name of the user that uploaded the time sheet.

Immediately following the Header section of the upload is one blank line.

Detail

Field Header Name

Data Type

Length

Required?

Value(s)/Format

Description/Use/Field Rules

Job_Seeker_ID

or

Work_Order_ID

or

Worker_ID

or

Buyer_Ref

or

Time Sheet ID

Text

14 or 100

Yes

Valid SAP Fieldglass IDs.

Example:

  • Job_Seeker_ID: ssssJS00000001

  • Work_Order_ID: XXXXWO00000001

  • Worker_ID: XXXXWK00000001

  • Time Sheet ID: XXXXTS00000432

Unique identifier for the worker. Can be any of the those listed to the left, but must be consistent throughout the file.

Last_Name

Text

200

No

Worker’s last name.

First_Name

Text

200

No

Worker’s first name.

Time Entry Date

Date

Yes

Format should match that of the format configured for the company in the application.

Date for which time is being recorded.

Time Sheet Start Date

Date

No

Format should match that of the format configured for the company in the application.

Time sheet start date for the Worker. This field is not required if Time Sheet ID is used.

Cost_Center_Code

Text

200

Yes

Valid SAP Fieldglass cost center code.

Cost Center Code that the worker’s hours are to be assigned. Value must be from the list of currently active Cost Centers in Fieldglass at the time of the upload and must be associated with the worker.

Cost_Center_Name

Text

200

No

Name related to the Cost Center Code listed above.

Task_Code

Text

100

Yes

Valid SAP Fieldglass task code

Task Code that the worker’s hours are to be assigned. Value must be from the list of task codes. The Task Code must be active and assigned to the worker booking time against it.

Task_Name

Text

100

No

Name related to the Task Code listed above.

Segmented Object Detail

Dependent on segmented object detail

200

Conditional

Valid SAP Fieldglass segmented object detail code

Examples:

  • IS|Admin|12001

  • IS-Admin-12001

  • IS;Admin;12001

  • IS:Admin:12001

Segmented object detail codes to be associated with the statement of work or job posting template.

Values to populate within the segmented object detail (if one segment)

OR

Segment values delimited by delimiter defined in the statement of work or job posting.

Valid delimiters are colon (:), semi-colon (;), pipe (|), and dash (-).

Number of segments should be equal to or less than the number of segments defined.

Rate_Category_Code

Text

100

Yes

Valid SAP Fieldglass rate category code

Rate Category code that hours for current record should be recorded against. Rate paid for the hours entered will be those related to the Rate Category Code entered here. Value must be a current active Rate Category associated with the worker.

Rate_Category_Name

Text

100

No

Name related to the Rate Category Code listed above.

UOM

Text

100

Yes

Valid values:

  • Hr (for hour)

  • Day

  • Mo (for month)

The unit of measure assigned to the Rate Category Code listed above.

Hrs

Decimal

Yes

Hours worked.

Validated

Text

3

Conditional

Valid values are:

Yes

No

Indicates if time entry date has been validated.

Required when Configuration flag Allow Daily Verification is unlocked and Worker’s time entry needs to be verified.

Comments

Text

100

Conditional

Any comments related to the verification.

Required when Configuration flag Allow Daily Verification is unlocked and Worker’s time entry needs to be verified.

Username

Text

100

Conditional

Valid SAP Fieldglass username.

Username with user role permission for daily verification.

Required when Configuration flag Allow Daily Verification is unlocked and Worker’s time entry needs to be verified.

If the Enhanced Legal Entity Validation configuration is enabled for the company, the verifier's username must have visibility to the legal entity of the time sheet. If the verifier username does not have visibility to the time sheet legal entity, the system displays an error message.

[c] Task Code Custom Field 1

Dependent on custom field configuration

Dependent on custom field configuration

Dependent on custom field configuration

Dependent on custom field configuration

Any custom field associated with the task code. The custom field name should be prefixed with '[c]'. For example, 'Task Code Custom Field 1' should be '[c] Task Code Custom Field 1'.

Valid values of the custom field are configured during the setup of the SAP Fieldglass application.

When Custom Field Type = Segmented Pick List and the Autopopulate Segment rule on the Pick List = Yes, if a segment value is left blank on the upload, the value is auto populated on the document if there is only one possible value based on the previous segment values. If there is more than one possible value, an error message displays.

Do not include this field if not in use.

Unique Identifier

  • Each unique combination of the following fields will require another record: Job_Seeker_ID/Work_Order_ID/ Worker_ID/ Buyer_Ref/Time Sheet ID, Time Entry Date, Cost_Center_Code, Task_Code, and Rate_Category_Code. The position of the primary key fields is important and cannot be moved.

    Uniqueness Examples:

    • A worker with both Straight Time and Overtime hours will require at least two lines.

    • A worker booking time to three Cost Centers will require at least three lines.

    • A worker with two different Cost Centers and two different Task Codes will require a minimum of four lines.

Configuration Considerations

#

Item

Notes

1

Custom Fields

Prior to adding custom fields, determine if the value will be constant within a given time sheet or could have multiple values within a single time sheet. 

If only a single value per time sheet is required, then a time sheet custom field may be best. If it varies throughout the week, then a task code custom field is likely the best choice.

2

Data Feed Timing

If implementing an automated solution, it is important that the owners of both SAP Fieldglass and the time sheet system fully understand the data and processes of each system and ensure that the timing of data flowing between the two is set up to best ensure data integrity.

For example, if workers are only downloaded on Sundays and the time sheets are uploaded on Fridays, it is likely there will be issues with end dates and/or start dates as the updates to worker profiles do not arrive until after the worker’s time sheet data.

3

Associations

Cost Centers, Task Codes, and Rate Categories can only be based on the list of those associated with the worker. If new items are required for booking of time, other than those currently associated with the worker, then those associations must be updated prior to uploading the hours.

4

Task Code Custom Field(s)

If a Task Code Custom Field is based on values within a pick list, then only those values will be valid in the Time Sheet Upload. If working with an external system, be sure that both application owners understand the full set of values that may be populated in this type of non-standard field.

Assumptions/Tips

  • The time sheet must be in Draft or Rejected status.

  • If a subsequent file receives the time entry for the same day, it will remove the earlier time entry and will create a new time entry with given values.

  • This connector does not support revised time sheets.

  • This connector will support Contingent and SOW workers' time entries.