Resource Time Sheet Download / Resource Time Sheet Upload
This integration downloads and uploads resource time sheets that are in Draft (with time entries), Rejected, Itemized or Itemization Failed status, depending on a provided parameter. Refer to the Parameters section below for parameter values.
Connector Overview
|
Component |
Detail |
|---|---|
|
Company Type |
Supplier |
|
Version Type |
1.0 |
|
Format |
CSV |
|
Prerequisites |
The Supplier Company must have Statement of Work (SOW) and Resource services enabled in the Buyer Supplier contract. The associated Buyer Company must have SOW, Time Processing, and Resource configurations enabled. User role permission must be turned on for Resource, Resource Time Sheet, Upload Data, and Download Data. |
|
Predecessors |
N/A |
|
Related Connectors |
N/A |
Triggering Events
Time sheets appear in the download if their status agrees with the parameter value provided at run time. Refer to the Parameters section below.
Parameters
The Parameters indicates what record types to download. Run-time parameters are as follows:
|
Name |
Mandatory? |
Field Type |
Additional Details |
|---|---|---|---|
|
Buyer |
Yes |
Picklist |
Displays the buyer name and code in parentheses. Only displays buyers who have enabled Services and Resource for a supplier. |
|
Date |
Yes |
Date range |
The effective range of dates for the time sheet. The maximum date range is 31 days. |
|
Time Template |
Yes |
Picklist |
Displays the time template name and code in parenthesis. Only includes time templates for SOWs. |
|
Time Sheet Status |
Yes |
Picklist |
Valid values are:
|
File Formatting
Header
|
Component |
Enabled by Default? |
Definition/Use |
Notes |
Value |
|---|---|---|---|---|
|
Type |
Yes |
File Name |
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. |
Resource Time Sheet Upload |
|
Time Template |
Yes |
The Time Template code |
||
|
Number Format |
No |
Determines the number format to be used in the file. |
This is an optional header value. Determines the Number Format used in the company. The valid number format values are:
The quotes are required even if the value does not have a comma in it. If this field is not included in the header, the default value will be #,##9.99. |
|
|
Date Format |
No |
Determines the date format to be used in the file. |
The valid date format values are:
If this field is not included in the header, the default value will be MM/DD/YYYY. |
|
|
Buyer |
Yes |
The Buyer company code |
||
|
Comments |
No |
Download/Upload Comments |
This is a comment field containing notes about the file. |
Immediately following the Header section of the file is one blank line.
Detail
|
Column Header Name |
Data Type |
Length |
Enabled by Default? |
Value(s)/Format |
Description/Use/Field Rules |
|---|---|---|---|---|---|
|
Modification Type |
Text |
1 |
Yes, when uploading the file to add, update, or delete a record. When downloading the contents of the time sheet, this is always empty |
Valid values are:
|
Defines action that the system needs to perform. |
|
Resource Timesheet Attachment |
Text |
100 |
Example:
|
Attachment uploaded to resource time sheets.
The Attachment column can include multiple files, separated by a semicolon (;).
|
|
|
Resource ID |
Text |
14 |
Yes, if the Buyer Reference is blank. |
Valid SAP Fieldglass Resource ID. Example: ABCDRE00001234 The value in this field will be considered only if Buyer Reference field is blank. |
14-character alphanumeric SAP Fieldglass Resource ID. This field must be blank if the Buyer Reference ID is used. |
|
Buyer Reference |
Text |
200 |
Yes, if the Resource ID is blank. |
The value in this field will be considered only if Resource ID field is blank. |
Buyer created reference. This field must be blank if the Resource ID is used. |
|
Last Name |
Text |
100 |
Yes |
The last name of the resource. |
|
|
First Name |
Text |
100 |
Yes |
The first name of the resource |
|
|
Date |
Date |
Yes |
Effective Date against which entered time (hours/ units) will be allocated |
||
|
Time Sheet ID |
Text |
16 |
Yes, for existing time sheets during download. For new time sheets during upload, this field must be left blank.. |
Valid SAP Fieldglass Time Sheet ID | Fieldglass Time Sheet ID |
|
Time Sheet Revision |
Number |
Yes for downloads. No for uploads. |
Displays the current time sheet revision number. Not used when uploading the resource time sheet. |
||
|
Time Sheet Status |
Text |
20 |
For existing time sheets during download, yes. For time sheets during upload, no.
Only time sheets with the following statuses can be uploaded:
|
For time sheets in Rejected, Itemized or Itemization Failed status, lines that haven't been itemized can use the following status options:
For time sheets in Rejected, Itemized, or Itemization Failed status, lines that have been itemized can use the following status options:
|
Time Sheets that are not in Rejected, Itemized or Itemization Failed status can't be edited. Time Sheet line items that are itemized can't be deleted. You can't set all the lines in a time sheet to be deleted. At least one line item is required for an upload. |
|
Non-billable |
Text |
By default the value is No, if left blank. |
Valid values:
|
When set to Yes, the following fields are mandatory:
|
|
|
Line Item Number |
Number |
Yes when editing or deleting existing line items. No for new time sheets or time sheet items. The field is auto-generated. |
The unique number for each itemized time sheet item. |
||
|
Itemization ID |
Text |
16 |
Yes for downloads where itemization has been triggered. No for uploads. |
The itemization reference ID for each itemized event. |
|
|
Itemization Status |
Text |
Yes for downloads where the itemization for event lines has been triggered. No for uploads |
The Itemization status for each line. |
||
|
Statement of Work |
Text |
18 |
Yes |
Example: CRPATQ00000566 |
Open statements of work for the supplier that are valid on the time sheet date. |
|
Event ID |
Text |
100 |
Yes |
Example: CRPAPE00000400 |
Event's system generated ID for any Standard or Limit event from the corresponding statement of work. If downloaded from the last step of the Timesheet grid, these are prepopulated from values entered through the UI. New values can be added, existing values can be edited. |
|
User Defined Segments |
Depends on buyer defined lookups |
Depends on buyer defined lookups |
One or more columns representing the lookups set up by the buyer. For example:
Supplier users can upload values only for the User Defined Segment columns they are familiar with. These values must correspond to a unique row in the lookup table, regardless of how many such columns exist. |
||
|
Account Category |
Text |
1 |
Yes, the validations are processed only if the company configuration is enabled. |
A valid SAP Fieldglass account category. |
The SAP Fieldglass account category. Account category is optional. If not provided, the system derives it from the selected Cost Center. The account category validation behavior depends on the SOW Template rule: Allow management of line item cost allocation when marking line items as complete. For Regular Account Categories (other than U and X) When the rule is enabled: All buyer cost centers associated to the selected account category are valid. When the rule is disabled: Only Cost centers available on the event are valid. For Account Category U When the rule is enabled/disabled, all account categories (including X), except U, are valid. The Cost centers must be associated to the selected account category. For Account Category X: When the rule is enabled: All buyer cost centers associated to all account categories, except U, are valid. The Cost centers must be associated to the selected account category. When the rule is disabled: All event cost centers are valid. |
|
Cost Center |
Text |
100 |
Yes |
A valid SAP Fieldglass cost center code. |
The SAP Fieldglass cost center code. If downloaded from the last step of the Timesheet grid, these are prepopulated from values entered through the user interface. New values can be added, existing values can be edited. Based on rule Allow management of line items cost allocation when marking items as complete on the statement of work, the cost centers uploaded can be any cost centers on the statement of work or any cost centers from the buyer Admin object |
|
Onsite Time |
Number |
No |
This field is for reference only and isn't required for uploads. When the flag Enable onsite time tracking with exception workflow on time template is enabled, this column lists the buyer entered time for each resource in the downloaded Resource Time Sheet. |
||
|
Time Category Code |
Text |
100 |
Yes, if time category is enabled and UOM is Time Worked. | Valid Time Category Code |
Time Category Code applicable to a resource on a specific day. |
|
Quantity |
Number |
Quantity entered by the supplier per time sheet line Item. |
|||
|
Exception Reason |
Text |
When the flag Enable onsite time tracking with exception workflowon time template is enabled, this column lists the reason for exception given by the supplier, when the supplier entered time doesn't match the buyer defined onsite time. If there are multiple lines being modified under the same time sheet, the Exception Reason only needs to be mentioned once against a line item. Only the exception reason in the first line processed is retained. All subsequent reasons are ignored. |
|||
|
Exception Comments |
Text |
When the flag Enable onsite time tracking with exception workflowon time template is enabled, this column lists the comments for exception given by the supplier, when the supplier entered time doesn't match the buyer defined onsite time. Timekeepers can add additional information to justify the action. |
|||
|
Revision Reason |
Text |
Yes, if revising a time sheet. |
A valid reason based on the type of revision. |
During an upload, a Revision Reason must be entered when revising the time sheet. If there are multiple lines being modified under the same time sheet, the revision reason only needs to be mentioned once against a line item. Only the revision reason in the first line processed is retained. All subsequent revision reasons are ignored. |
|
|
Revision Comments |
Text |
No. |
This is an optional field used with the Revision Reason to describe the action in detail. |
||
|
Site Code |
Text |
100 |
Yes |
Valid SAP Fieldglass Site Code |
SAP Fieldglass site code associated with the resource time sheet. |
|
Site Name |
Text |
100 |
Yes |
|
SAP Fieldglass site name associated with the site code above. |
|
Line Item Attachment |
Text |
100 |
Optional |
Example:
|
Attachments uploaded to line items. |
|
Line Item Comments |
Text |
1000 |
Optional |
Comments added to line items |
Unique Identifier
-
Resource ID
-
Date