Worker Absence Upload
This integration uploads worker absences into SAP Fieldglass from an external application.
Connector Overview
|
Component |
Detail |
|---|---|
|
Company Type |
Buyer Supplier MSP |
|
Version Type |
API-A-V1.0 |
|
Format |
CSV |
|
Prerequisites |
Company Details Setting must be turned on for Integration – Worker Absence Upload. User role permission must be turned on for Upload Data and Download Data. |
|
Predecessors |
|
|
Related Connectors |
File Formatting
Header
|
Component |
Required? |
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. |
Worker Absence Upload |
|
Transaction |
No |
Transaction type |
Only applicable for API version. The valid values are:
If this field is not included in the header, the default value will be True. |
|
|
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. |
Arabic (Standard Arabic) |
|
|
Date Format |
No |
Determines the date format to be used in the file. |
The valid values are:
If this field is not included in the header, the default value will be MM/DD/YYYY. |
|
|
Buyer |
Conditional |
Required if upload is performed by a Supplier user |
The value in this row should be Buyer= [followed by the buyer code of the buyer company]. Example: Buyer=ABCD |
|
|
Comments |
No |
Upload Comments |
This is a comment field containing notes about the upload file. |
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 |
Text |
16 or 100 |
Yes |
Valid SAP Fieldglass Unique Identifier for the Worker. Example: XXXXJS00000001 XXXXWO00000001 XXXXWK00000001 |
Unique Identifier for the worker. Can be any of the four listed to the left but must be consistent throughout the file. The column header in the file must be changed whichever identifier is used in the upload. For example, if the upload uses Worker ID, then the upload column header would be Worker_ID, and the only valid values would be worker IDs in this column. |
|
Start Date |
Date |
Yes |
Example: 10/01/2020 |
The start date of the absence. |
|
|
End Date |
Date |
Yes |
Example: 12/01/2020 |
The end date of the absence. |
|
|
Reason |
Text |
100 |
Yes |
Example: Sick Day |
The reason for the absence. Note that reasons are created by the Buyer company. The value in the upload file must match one of the reasons created by the Buyer. |
|
Partial Day |
Text |
3 |
No |
Valid values are:
|
Whether or not this is a partial day absence. If no value is provided, the upload will default a value of No. |
|
Duration in Hours |
Decimal |
No |
Example: Valid Values: 5, 5.00 Invalid Values: 5:00 |
Value to be entered for a partial day absence. |
|
|
Comments |
Text |
1000 |
No |
Example: Called in sick yesterday evening. |
Optional comment that can be left on the absence. |
Unique Identifier
-
Job_Seeker_ID/Worker_ID/Work_Order_ID/Buyer_Ref field
Configuration Considerations
-
For buyer users running this upload, the corresponding job posting template for the given worker must allow absences to be submitted by either the supplier or worker (since the buyer is acting on their behalf when running this upload).
-
For supplier users running this upload, the corresponding job posting template for the given worker must allow absences to be submitted by the supplier.