Work Order Worker Custom Field Update Upload
This integration uploads custom field edits. This upload differs from the Custom Field Update Upload in that it can update all work order revisions at the same time. You can also use Work Order ID, Worker ID, Consolidated Worker ID, Resource ID, and/or Profile Worker ID in the same upload file.
File Formatting
Assumptions/Tips
-
If a Work Order, Worker, Consolidated Worker, Profile Worker, or Resource ID is used, the column header should remain as Object ID.
If a Security ID is used to update all records that contain that ID, the column head needs to be changed to Security ID.
-
Due to a requirement for tracking of the changes to values for Personally Identifiable Information (PII), SAP creates an audit trail for the following worker/user fields: Usernames, Names, Addresses, Phone Numbers, Email Addresses, Employee ID, Unique ID, Security ID, Attachments, and any custom fields configured as PII.
-
Both buyer and supplier entered custom fields display and can be updated by both parties regardless of who created the custom field first.
-
When the 'Revise All Work Order?' field is specified as Yes, the custom field(s) should be present on all the work order revisions.
-
If the Upload Column Transform setting (which is present in Connector Configurations) has the column 'Revise All Work Order?' default value as 'Yes', whenever the CSV file is uploaded, irrespective of providing a 'Revise All Work Order?' value or not, it picks up the value as 'Yes' and therefore all the revisions of the Work Order will be updated.
-
When updating a linked Worker custom field that has the same name from Contingent and SOW modules, the upload updates based on the type of worker record.
-
For any record, an error occurs if values for the Object Buyer Ref ID and Buyer Ref columns are given. (A column cannot be updated when it is being used as a primary key.)
-
When a worker custom field is edited:
-
If custom fields that are being edited are not tenure lookup keys, tenure recalculation is not triggered. Therefore, any prior violations are not triggered or monitored.
-
If the custom fields that are being edited are tenure lookup keys, tenure is recalculated. This could cause a previous violation to trigger again. However, a custom field that is tenure-relevant and has been altered must adhere to compliance measures, and therefore, the update requires a work order revision instead of a worker update.
-
-
For a worker/work order, if a custom field already has a value and the upload is sent with a blank, the already populated custom field value is blanked out.
-
Regarding leading and dependent custom fields:
-
When leading and dependent custom fields have been set up, and a buyer downloads a blank upload template for this connector from the user interface, leading and dependent custom fields are automatically added as individual columns.
-
The system reads the value of the leading custom field and validates the first dependent custom field. This process continues for all dependent custom fields in the defined sequence until it is completed.
-
-
For work orders for SOW Workers, the revision time is only updated if the Buyer Reference is provided.
Using global identifiers (Consolidated Worker ID and Security ID)
When a Consolidated Worker ID or Security ID is used, the upload applies the custom field update across all associated records. (Note that archived records are not included.) The records included depend on the identifier type and each record's current status:
|
Record type |
Consolidated Worker Object ID path |
Security ID path |
|---|---|---|
|
Contingent Workers (WK) |
Active and Closed |
All statuses |
|
Work Orders (WO) |
Accepted, Activated, Confirmed |
All statuses |
|
SOW Resources (RE) |
All statuses except closed |
All statuses except closed |
|
Profile Workers (PW) |
Active |
All statuses |
Note the following behavior when closed SOW Resources are included:
-
If the identifier is associated with a mix of open records and closed SOW Resources, the closed resources are skipped and all other records are updated successfully.
-
If the identifier resolves only to closed SOW Resources, the upload fails with an error.