Draft Rejected Time Sheet Download
This integration downloads time sheets in draft/rejected approval status. The Draft Rejected Time Sheet Download has a format that matches that of the Time Sheet Upload, and as such, is meant to be used as a pre-populated template for making mass site updates.
The output of this download is in the file format of the Time Sheet Upload connector.
Connector Overview
|
Component |
Detail |
|---|---|
|
Company Type |
Buyer Supplier MSP Partner |
|
Version Type |
1.0 |
|
Format |
CSV |
|
Prerequisites |
Company plug-ins must be turned on for Integration – Draft Rejected Time Sheet Download. User role permission must be turned on for Upload Data and Download Data. |
|
Predecessors |
Time Sheets Workers |
|
Related Connectors |
Time Sheet Upload Approved Time Sheet Fixed Format Download |
Triggering Events
Timesheets will appear in the download if they agree with the parameter values provided at run time. Refer to the Parameters section below.
Parameters
-
The first parameter indicates the start date of time sheets in MM/DD/YYYY format.
-
The second parameter indicates the buyer company for which time sheets are to be downloaded.
File Formatting
Header
|
Component |
Enabled by Default? |
Definition/Use |
Notes |
Value |
|---|---|---|---|---|
|
Type |
Yes |
Upload File Type |
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. |
Timesheet |
|
Transaction |
No |
Transaction Type |
Transaction type. The valid values are:
If this field is not included in the header, the default value will be True. |
|
|
Approval Required |
No |
Determines if the time sheets will be required to go through an approval process. |
The valid values are:
If this field is not included in the header, the default value will be True. |
|
|
Messaging Required |
No |
Determines if notifications related to the creation of time sheets will be sent to users. |
The valid values are:
If this field is not included in the header, the value will default to True. |
|
|
Language |
No |
Determines the language to be used for values in the file, such as drop-down lists and radio buttons. Column headers always default to the upload user's preferred language. |
The valid language values are: Arabic (Standard Arabic)
|
|
|
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. |
|
|
Submit |
Yes |
Determines the status in which the timesheets will be saved. |
The valid values are:
|
|
|
Buyer |
Yes if supplier download. |
Company Code of the buyer company to which the time sheets are to be saved. |
If unknown, code can be found under
|
|
|
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 who uploaded the time sheet. |
Immediately following the Header section of the upload is one blank line.
Detail
|
Column Header Name |
Data Type |
Length |
Enabled by Default? |
Value(s)/Format |
Description/Use/Field Rules |
|---|---|---|---|---|---|
|
Job_Seeker_Id |
Text |
16 |
Yes |
Valid Job Seeker ID Example:
|
Unique identifier for the worker. |
|
Last_Name |
Text |
200 |
No |
Worker’s last name. |
|
|
First_Name |
Text |
200 |
No |
Worker’s first name. |
|
|
Date |
Date |
Yes |
Time sheet week starting date. |
||
|
Week_Start_Date |
Date |
Conditional |
Valid values are:
|
This field is only necessary when using bi-weekly or 8 day time sheets. For 8 day time sheets, enter hours via the Date and Week Start Date columns similar to the existing bi-weekly requirements. |
|
|
Cost_Center_Code |
Text |
200 |
Yes |
Valid SAP Fieldglass Cost Center Code. |
Cost Center Code for which time is to be adjusted. |
|
Cost_Center_Name |
Text |
200 |
No |
Cost Center Name for which time is to be adjusted. |
|
|
Task_Code |
Text |
100 |
Yes |
Valid SAP Fieldglass Task Code. |
Task Code for which time is to be adjusted. |
|
Task_Name |
Text |
100 |
No |
Task Name for which time is to be adjusted. |
|
|
GL_Account_Code |
Text |
100 |
Conditional |
Valid Active GL Account Code. |
Must be from the list of current active GL account codes and must have an association to the worker for which time is being booked. This column is applicable only if GLA allocation on job postings and statements of work is required plug-in is On. This field is mutually exclusive with Segmented Object Detail field. |
|
GL_Account_Name |
Text |
100 |
No |
Name related to the GL Account Code entered above. | |
|
Segmented Object Detail |
Text |
2000 |
Conditional |
Examples:
|
Segmented Object Detail. Segments will be separated by delimiter on the Segmented Object. Valid delimiters are colon (:), semi-colon (;), pipe (|), and dash (-). Required if “Segmented object detail’ set. This field is mutually exclusive with GL Account fields. |
|
Rate_Category_Code |
Text |
100 |
Yes |
Valid SAP Fieldglass Rate Category Codes. Examples:
|
Rate Category Code for which time is to be adjusted. Rate Category Code listed will determine which of the worker’s rates to apply to the hours entered. |
|
Rate_Category_Name |
Text |
100 |
No |
Examples:
|
Rate Category Name for which the time is to be adjusted. |
|
UOM |
Text |
5 |
Yes |
Valid values are:
|
Unit of measure for this given Rate Category. |
|
Sun_Hrs |
Decimal |
No |
Example:
|
Difference, in hours, from original time sheet. The maximum negative value allowed will be equal to the original time sheet hours for that period. Enter 0 or null if no change. |
|
|
Mon_Hrs |
Decimal |
No |
Example:
|
Difference, in hours, from original time sheet. The maximum negative value allowed will be equal to the original time sheet hours for that period. Enter 0 or null if no change. |
|
|
Tue_Hrs |
Decimal |
No |
Example:
|
Difference, in hours, from original time sheet. The maximum negative value allowed will be equal to the original time sheet hours for that period. Enter 0 or null if no change. |
|
|
Wed_Hrs |
Decimal |
No |
Example:
|
Difference, in hours, from original time sheet. The maximum negative value allowed will be equal to the original time sheet hours for that period. Enter 0 or null if no change. |
|
|
Thu_Hrs |
Decimal |
No |
Example:
|
Difference, in hours, from original time sheet. The maximum negative value allowed will be equal to the original time sheet hours for that period. Enter 0 or null if no change. |
|
|
Fri_Hrs |
Decimal |
No |
Example:
|
Difference, in hours, from original time sheet. The maximum negative value allowed will be equal to the original time sheet hours for that period. Enter 0 or null if no change. |
|
|
Sat_Hrs |
Decimal |
No |
Example:
|
Difference, in hours, from original time sheet. The maximum negative value allowed will be equal to the original time sheet hours for that period. Enter 0 or null if no change. |
|
|
Location Code |
Text |
100 |
Conditional |
Valid SAP Fieldglass location code |
Retrieves the location code of the hours against the Rate/Rate Category for that day. Enable at least one sub-configuration for the company configuration Use multiple locations. If the download’s parameters pull a time sheet with multiple locations, the row is repeated with the exact same information in all columns except the location columns. There will be as many duplicated rows as there are number of locations on the time sheet. This field does not display unless this download is configured to do so via the Enabled Fields tab's '+Add Native Fields' hyperlink. |
|
Work Location Name |
Text |
100 |
Conditional |
Retrieves the location name of the hours against the Rate/Rate Category for that day. Enable at least one sub-configuration for the company configuration Use multiple locations. If the download’s parameters pull a time sheet with multiple locations, the row is repeated with the exact same information in all columns except the location columns. There will be as many duplicated rows as there are number of locations on the time sheet. This field does not display unless this download is configured to do so via the Enabled Fields tab's '+Add Native Fields' hyperlink. |
|
|
[c] Custom field name |
Dependent on custom field configuration. |
Dependent on custom field configuration. |
Example: [c] ABC ID 12345 |
All enabled custom fields will be downloaded in this format unless the column name is customized. |
*Note: When the Buyer has the enter 100th hour on TS flag on, the hours can be entered in 100th hour increments, i.e., 8.01, 8.02…..8.99. However, if the flag is not turned on, then hours must be entered in quarter or 10th hour increments, i.e., 8.10, 8.20, 8.25, etc.
Unique Identifier
-
Job_Seeker_Id, Date, Cost_Center_Code, Task_Code, GL_Account_Code, Rate_Category_Code, and UOM fields
Custom Fields
-
The download file will include custom fields from the time sheet and task code (associated to time sheet) modules in SAP Fieldglass.
-
Custom fields that are included will always appear at the end of the column layout after all of the native default or optional SAP Fieldglass fields have been output.
-
Custom field headers will be displayed in the format “[c] CustomFieldName”.
Assumptions/Tips
-
The system includes any inactive cost centers associated with the document.

