SOW Work Order Edit Start or End Date Upload

Only the data being changed is required in the upload file.

Connector Overview

Component	Detail
Company Type	Buyer Supplier
Version Type	API-A-V1.0
Format	CSV
Prerequisites	Company plug-ins must be turned on for Integration – SOW Work Order Edit Start or End Date Upload. User role permission is turned on for Upload Data and Download Data.
Predecessors	Work Order Upload
Related Connectors	SOW Worker Upload SOW Shell Upload Work Order Revision Upload Work Order Edit Upload Worker Update Upload Worker Close Upload

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.	SOW Work Order Edit Start or End Date Upload
Transaction	Yes	Transaction Type	Transaction Type. The valid type names are: True: If any record errors, the entire upload fails. Optional field containing any specific reference value required by the supplier. False: Only records in error fail. Remaining records are committed successfully.
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) 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)
Buyer	Yes, if supplier upload	Buyer Code	Buyer Code of Buyer for which the SOW Worker Revisions are being uploaded.
Date Format	No	Determines the date format to be used in the file.	The valid values are: MM/DD/YYYY DD/MM/YYYY YYYY-MM-DD If this field is not included in the header, the default value is MM/DD/YYYY.
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

Purchase Order Number Field Header Name	Data Type	Length	Required?	Value(s)/Format	Description/Use/Field Rules
Job Seeker ID	Text	16	Yes, if Work Order ID field is not entered.	Valid SAP Fieldglass Job Seeker ID Example: ABCDJS00000001	Job Seeker ID of the Job Seeker to be Revised.
Work Order ID	Text	16	Yes, if Job Seeker ID field is not entered.	Valid SAP Fieldglass Work Order ID Example: ABCDWO00000012	Must be a valid SAP Fieldglass Work Order ID.
Worker ID			Yes, if Job Seeker Id and Work Order ID not included.	Valid SAP Fieldglass Worker ID Examples: XXXXWK00000001	Must be a valid SAP Fieldglass Worker ID
Start Date	Date			MM/DD/YYYY Example: 01/01/2013	The Start Date for selected SOW Work Order
Time Sheet Start Date	Date			MM/DD/YYYY Example: 01/01/2013	The Time Sheet Start Date for selected SOW Work Order
Comments	Text	1000	No		Comments on the SOW Work Order

Unique Identifier

Job Seeker ID field or Work Order ID field

Configuration Considerations

The company configurations, Buyer and Supplier can change SOW Worker dates without a revision and Tenure policy must be enabled. These settings activate the ability to edit worker start dates via the connector.
If the SOW’s timesheet type is not equal to TIME_SHEET_ENTRY_TYPE_DEFAULT_FROM_TEMPLATE or TIME_SHEET_ENTRY_TYPE_NONE both the Start Date and Timesheet Start Date must be updated together. When the Edit Worker Start Date flag is set to True, only these two fields can be modified in the connector.

Assumptions/Tips

Work Order should be in "Confirmed", "Draft", "Activated", "Closed" status.
Start Date cannot be edited on:
- Confirmed SOW WO (work order) where revision exists.
- Closed Worker
- Rejected Work Order
- Confirmed sequence 0 WO (where worker is closed)

Notes

Tenure Radio Button Logic (UI-Only Behavior): The tenure radio button applies only to bulk updates in the UI, where multiple work orders can be edited in a single operation. Since the connector processes one record at a time, this logic is not applicable, therefore, tenure settings are ignored in connector uploads.
Sequential Record Processing: Connector uploads handle records sequentially (one by one), not in parallel or batches. Because of this design, tenure radio button functionality intended for batch updates is currently not supported in connector operations.