Work Order Revision Accept Upload

This integration accepts multiple revised work orders.

Connector Overview

Component	Detail
Company Type	Buyer Supplier MSP Partner
Version Type	API-V1.0
Format	CSV
Prerequisites	Company plug-ins must be turned on for Integration – Work Order Revision Accept Upload. User role permission must be turned on for Upload Data and Download Data.
Predecessors	Work Orders
Related Connectors	Work Order Accept Upload

File Formatting

Header

Component	Required?	Definition/Use	Notes	Value
Type	Yes	Upload File Type		Work Order Revision Accept Upload
Transaction	No	Only applicable for the API-V1.0 version. Transaction Type	Transaction Type. Valid types are: True: If any record errors, the entire upload fails. 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. False: Only records in error fail; remaining records are committed successfully. If this field is not included in the header, the default value will be True.
Send Notification?	No	Determines if Messaging Work flow will be utilized	Valid values are: True: Messages will be sent as configured. False: No messages will be sent. This field defaults to True if left blank.
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.	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)
Number Format	No	Number format used in the file	The valid values are: “#,##9.99" (Example: "1,234,567.99”) “#.##9,99" (Example: "1.234.567,99”) “#'##9.99" (Example: "1'234'567.99”) “# ##9,99" (Example: "1 234 567,99”) 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 determined by the Locale value.
Date Format	No	Date format used in the file	Valid values are: MM/DD/YYYY DD/MM/YYYY YYYY-MM-DD
Buyer	Yes, if supplier upload.	Buyer Code	Buyer Company Code
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
Supplier Reference	Text	100	No		Optional external reference information provided by the Supplier
Modification Type	Char	1	Yes	Valid values are: A D	A = Accept D = Decline
Job Seeker ID	Text	16	Yes, If no Work Order ID.	Valid SAP Fieldglass Job Seeker ID Example: XXXXJS00000001	Job Seeker ID for which acceptance is being uploaded.
Work Order ID	Text	16	Yes, if no Job Seeker ID.	Valid SAP Fieldglass Work Order ID Examples: XXXXWO00000001	Work Order ID for which acceptance is being uploaded. Will also accept Work Order external reference.
Worker Email	Text	100	Yes	Valid SAP Fieldglass Worker Email	Worker email to which the registration invitation will be sent.
Remit to Address Code	Text	100	Yes if required by Buyer Config.		Supplier’s Remit to Address
Auto Invoicing	Text	13	No	Valid values are: Time Sheet Expense Sheet Both None Blank	Determines which transactions are to be auto invoiced for the work order. Blank defaults to None.
Comments	Text	2000	No		Comments the supplier would like to add when declining (when the Modification Type is D). You cannot add comments if the Modification Type is A.
Additional Invoice Adjustment Currency	Text	3	No	Valid SAP Fieldglass buyer currency. Examples: USD CAD EUR	Indicates if buyer is able to add additional invoice adjustment currency.
[pr] Rate Category / Rate UOM	Text	100	Yes, if rate is a Markup.		For Worker’s Pay Rate. Only downloaded for buyer side. Supplier side rates must be entered manually. For Rates 2.0: If the work order's job posting has enabled rule Disallow Supplier edits to Pay Rate on Work Order and Work Order Revision accept, then values entered here are ignored. If rule is disabled, the pay rate can be edited EXCEPT when rate uses a Rate Component Group (Pay Rate Based or Bill Rate Based) that contains a Coefficient, OR (Rate uses a Pay Rate Based Rate Component Group AND (at lease one component has a component limit OR at least 1 Component has disabled the Include in MSP Fee Calculation flag, OR at least 1 Component has disabled the Include in Level Subtotal flag). When the job posting rule Disallow Supplier edits to Pay Rate on Work Order and Work Order Revision accept is enabled, the suppliers will see Pay Rates as locked for all Rate types. When this rule is disabled, on work order revision accept, and when the rate uses pay rate based rate component group, the Suppliers will not be able to edit Pay Rate. The system will ignore any values entered in this field for that work order or work order revision.
[c] Custom Field 1	Dependent on Custom Field configuration		Dependent on custom field defined.	Dependent on the custom field defined.	Any custom field associated with the work order revision defined. When Custom Field Type = Segmented Pick List and the Autopopulate Segment rule on the Pick List = Yes, if a segment value is left blank on the upload, the value is auto populated on the document if there is only one possible value based on the previous segment values. If there is more than one possible value, an error message displays.
[a] Adjustment 1	Text	100	No	Dependent on adjustment.	Any adjustment defined by the buyer. Buyer can add MSP adjustments on work order. Only available to supplier if Available to Supplier adjustment flag is enabled.

Unique Identifier

Job Seeker ID field and/or Work Order ID

Assumptions/Tips

User can accept or decline the work order through upload.
User needs to manually add pay rate columns to the file for any rates defined by the buyer.

For example, When rates defined by buyer are ST/Hr and DT/day, user needs to add [pr] ST/Hr and [pr] DT/Day columns to the file.
User needs to manually add custom field columns to the file. The mandatory custom fields (CF) defined by the buyer should be added to the file.

For example, if the buyer has defined CF1 and CF2 to be entered by the supplier on a work order, then while accepting the work order against that buyer, the supplier needs to add [c] CF1 and [c] CF2 columns to the upload file.
Both buyer and supplier entered Custom Fields will display and can be updated by both parties, regardless of who created the Custom Field first.
Enabling the rule Allow Supplier to Edit Value allows the supplier to modify the value of the affected adjustments in an adjustment group.
When a Work Order Revision is accepted, it updates the Consolidated Worker.
Suppliers can add any additional adjustments to the work order accept step, but it doesn't impact the approved committed spend, even if the Include in Estimated and Committed Spend flag is enabled.
If the Work Order Owner doesn't change and if Yes is provided as the value for Set as Supervisor of All Cost Centers field, the upload uses No as the value.
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.
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.
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.