Work Order Upload

This integration uploads work orders.

Connector Overview

Component

Detail

Company Type

Buyer

MSP Partner

Version Type

API-V1.0

API-A-V1.0

Format

CSV

Prerequisites

Company Details Setting must be turned on for Integration – Work Order Upload.

User role permission must be turned on for Upload Data and Download Data.

Predecessors

Job Posting

Job Seeker

Related Connectors

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.

Work Order Upload

Transaction

No

Only applicable for the API-V1.0 version.

Transaction Type

Transaction Type. The valid type names are:

  • True: If any record errors, the entire upload fails.

  • False: Only records in error fail, remaining records are committed successfully.

If this field is not included in the header, the default value is True.

Approval Required?

Yes

Determines if standard approval workflow will be followed.

The valid values are:

  • True: Standard Work Order Revision approval workflow will be followed.

  • False: Work Order Revision will be created bypassing any configured approval workflow.

Buyer

Yes

Buyer Company Code

Buyer Company Code of the buyer for which Work Order Revisions are being processed.

Send Notification?

No

Determines whether normal messaging workflow should be followed.

This flag is used to control sending notifications to users.

Valid values are:

  • True: If the value is set to True, email is sent.

  • False: If the value is set to False, email is not sent.

If this field is not included in the header, the default value is 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.

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

Determines the number format to be 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 is determined by the Locale value.

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.

Supplier Confirmation Required

No

Determines status of work order

This flag is used to indicate status of work order.

Valid values are:

  • True: If the value set to True, the work order status is Created and goes to supplier.

  • False: If the value is set to False, the work order status is Activated and goes to the buyer.

If this field is not included in the header, the default value is False.

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

Buyer Reference

Text

1

No

 

Unique buyer identifier.

Job Seeker ID

Text

16

Yes, if External Work Order Id is not included.

Valid SAP Fieldglass Job Seeker ID.

Example:

XXXXJS00000001

SAP Fieldglass Job Seeker ID for worker that is to be placed on the work order.

Job Posting ID

Text

16

Yes, if External Work Order Id is not included.

Valid SAP Fieldglass Job Posting List

Example:

XXXXJP00000001

SAP Fieldglass Job Posting ID that the Job Seeker is being submitted against.

External Work Order Id

Text

100

Yes if Job Seeker ID and Job Posting ID are not included.

Example:

20220225_WO_CHN_21

An external work order identifier used by the client for tracking purposes. This field can be used to link to the Object ID field found in the Worker Registration file.

Creator Username

Text

100

Yes

Valid SAP Fieldglass User

The valid SAP Fieldglass username of the individual who creates this specific work order. This user must be loaded into SAP Fieldglass prior to this file upload. This user must be the logged-in user who is going to do the upload.

If the 'Enhanced Legal Entity Validation' configuration is enabled for the company, the creator and owner must have visibility access to the cost center code and the cost center code must have visibility to the work order legal entity.

If the entered cost center code is not associated with either the creator or the owner, the system displays an error message.

If the cost center code does not have visibility to the work order legal entity the sytem displays an error message.

AP Code

Text

200

Conditional

Valid SAP Fieldglass AP Codes defined on the buyer side for Remit To Addresses.

The AP Code field appears only when the AP Code Required has been enabled in the company configuration for Contingent and/or Services: Work Orders and Workers.

Custom Lookup: AP Code Selection must be created.

The AP Code is associated to Work Order or SOW.

Start Date

Date

Yes

Example:

  • MM/DD/YYYY

  • DD/MM/YYYY

  • YYYY-MM-DD

The date on which the work order begins. This is the date on which the worker’s assignment begins.

This format will reflect what is listed in the header of the file. Otherwise, the format will be determined by the settings associated with the user performing the upload.

End Date

Date

Yes

Example:

  • MM/DD/YYYY

  • DD/MM/YYYY

  • YYYY-MM-DD

The date on which the work order ends. This is the date on which the worker’s assignment ends.

This format will reflect what is listed in the header of the file. Otherwise, the format will be determined by the settings associated with the user performing the upload.

Trial End Date

Date

No

Example:

  • MM/DD/YYYY

  • DD/MM/YYYY

  • YYYY-MM-DD

The date on which the trial period ends. The trial date is typically used in business contract terms between the buyer and supplier.

This format will reflect what is listed in the header of the file. Otherwise, the format will be determined by the settings associated with the user performing the upload.

Billable per Diem

Decimal

No

Example:

50.00

The amount of per diem allowed to be charged against this work order for each day that the worker charges hours.

Primary Cost Center Code

Text

200

No

Valid SAP Fieldglass Cost Center Code

Primary Cost Center to which the worker is allocated. If left blank, it defaults to the current primary cost center of the worker.

If the 'Enhanced Legal Entity Validation' configuration is enabled for the company, the creator and owner must have visibility access to the cost center code and the cost center code must have visibility to the work order legal entity.

If the cost center code is not associated with either the creator or the owner, the system displays an error message.

If the cost center code does not have visibility to the work order legal entity, the system displays an error message.

If a new cost center is added to the work order and the entered cost center code is inactive, the system displays an error message.

Estimated Expense %

Decimal

No

Example:

1.25

The estimated expense percentage of the total estimated cost for this job posting. This is used by SAP Fieldglass to calculate the total estimated cost for this work order. Example: 1.25% should be entered as ‘ 1.25 ’, not ‘ .0125 ’. Percentage values should NOT be entered.

Estimated Additional Spend %

Decimal

No

Example:

1.25

The percentage assigned to the estimated additional spend allowed on this work order’s total. This is used by SAP Fieldglass to calculate the total estimated additional spend for this work order. Example: 1.25% should be entered as ‘ 1.25 ’, not ‘ .0125 ’. Percentage values should NOT be entered.

Hours per Day

Decimal

Yes

Example:

8

7.5

The standard number of hours worked per day.

Days for Committed Spend

Decimal

Conditional

Example:

40

37.5

The number of days worked per committed spend.

Required if Job Posting Template rule Hours/Days for Committed Spend is set to Creator enters AND committed spend rate UOM is Day.

Hours for Committed Spend

Decimal

Conditional

Example:

40

37.5

The number of hours worked per committed spend.

Required if Job Posting Template rule Hours/Days for Committed Spend is set to Creator enters' AND committed spend rate UOM is ‘Hour'.

Hours per Week

Decimal

Yes

Example:

40

37.5

The standard number of hours worked per week.

Purchase Order

Text

100

No

Example:

4504769787

Any purchase order number assigned to this work order. This is an optional field that allows for the inclusion of purchase order information in the event that the customer has a purchase order system.

Email

Text

100

Yes

Example:

JSmith@abcd.com

The email address of the job seeker. Notifications about submitting time sheets are sent to this email address.

Time Sheet Start Date

Date

Yes

Example:

  • MM/DD/YYYY

  • DD/MM/YYYY

  • YYYY-MM-DD

The date on which the worker is allowed to begin entering time sheets.

This format will reflect what is listed in the header of the file. Otherwise, the format will be determined by the settings associated with the user performing the upload.

Maximum Expense

Decimal

No

Example:

100

The maximum amount for expenses allowed for this particular work order.

Site Code

Text

100

Conditional

Valid SAP Fieldglass Site Code.

The Site Code as defined in SAP Fieldglass.

Location Code

Text

100

Conditional

Valid SAP Fieldglass Location Code(s).

Example:
  • Valid SAP Fieldglass Location Code(s).

    Example:

    loc1~loc2~loc3

The code of the location in which this job posting is located.

Location codes must be defined in the SAP Fieldglass application.

Multiple codes are separated by a tilde (~) when at least one sub-configuration for company configuration Use multiple locations is enabled

Primary Location Code

Text

100

Conditional Valid SAP Fieldglass Location Code(s).

Indicates primary location code.

Enable at least one sub-configuration for the company configuration Use multiple locations.

If the selected primary location isn't listed in the Location Code column, the application displays an error message.

If the Primary Location Code column is blank for records with multiple locations or even a single location, the application displays an error message.

Time Sheet Type

Text

100

Yes

Valid values are:

  • Standard (or Hourly)

  • Time-In/Time-Out

  • No Time Sheets

This flag indicates how time and expenses are recorded for the work order.

If this flag is set to Hourly or Standard, the worker inputs his/her time based on the hours or units worked and tasks worked.

If this flag is set to Time-In/Time-Out, the worker inputs the time he/she arrives to work, leaves work, and times away for lunch or breaks. The worker also allocates hours against the task codes in which they worked. This is also referred to in the industry as 'Time Card' or 'Time & Entry'.

If this flag is set to No Time Sheets, then Time and Expense will not be tracked for this work order. In addition, a notification (not a work item) is sent to the supplier at the time the work order is created.

Time Sheet Frequency

Text

16

Yes

Valid values are:

  • Weekly

  • Biweekly or Bi-Weekly

  • Semimonthly

  • Monthly

  • 8 Day Time Sheet

This flag indicates how frequently time sheets get submitted to the worker.

If this flag is set to Weekly, the worker receives a weekly time sheet.

If this flag is set to Biweekly, the worker receives a bi-weekly time sheet.

If this flag is set to Semimonthly, the worker receives a semimonthly time sheet.

If this flag is set to Monthly, the worker receives a monthly time sheet.

Allow Daily Verification

Text

3

No

Valid values are:

  • Yes or 1

  • No or 0

This flag determines if the buyer is required to use the functionality 'daily verification for desktop'.

This field only applicable if the job posting template flag 'Allow Daily Verification' is not locked. Otherwise, will default to value on job posting template.

Not applicable for Time Sheet Type of ‘No Time Sheets’.

Not applicable if Company configuration 'Enable SAP CATS Time Sheet' is enabled.

Flat Adjustments

Decimal

No

Example:

$1000.00

This field will reflect any flat adjustment amounts associated with a particular work order.

Remit-to Address Code

Text

100

Conditional based on company configuration

The code indicates the supplier address to which paid invoices are sent. The Remit To Address Code must be previously defined in the SAP Fieldglass application.

Auto Invoicing

Text

100

No

Valid values are:

  • Both

  • None

  • Time Sheet

  • Expense Sheet

The flag indicates if Auto Invoicing functionality is to be used.

If the flag is set to Both, then both the workers’ time and expenses will be auto-invoiced.

If the flag is set to None, then none of the workers’ time and expenses will be auto-invoiced.

If the flag is set to Time sheet, then ONLY the workers’ time sheets will be auto-invoiced.

If the flag is set to Expense sheet, then ONLY the workers’ expense sheets will be auto-invoiced.

Issue warning if Hours per Day are exceeded on Time Sheet

Text

3

No

Valid values are:

  • Yes

  • No

This flag generates a warning to workers, following Federal Labor Standards Act (FLSA) time-sheet logic if their entered time sheet standard hours exceed the hours per day or per week specified on the work order.

For backward compatibility, 'Hours per Day Time Sheet Flag' is still accepted when the column header 'Issue warning if Hours per Day are exceeded on Time Sheet' is either not present or has blank value.

Site Tax

Decimal

No

Example:

1.25

Percentage of site tax for work location. Example: 1.25% should be entered as '1.25, not '.0125'. Percentage values should NOT be entered.

Purchase Unit

Text

100

Conditional

Valid Purchase Unit Code

Purchase Unit associated to the Work Order.

Comments

Text

500

No

Comments on the work order to buyer.

Comments To Supplier

Text

500

No

Comments on the work order to supplier.

Tax Service Type

Text

100

Conditional

Valid SAP Fieldglass Pick List for Tax Service Type

Indicates the tax service type of the work order.

Company configuration for Tax Guidance should be enabled.

This field is ignored for Rates 2.0.

Hundredths Of Hours on Time Sheet

Text

3

No

Valid values are:

  • Yes

  • No

This flag allows time to be entered in hundredths of hours.

Start Day of Week

Text

9

No

Valid values are:

  • Sunday

  • Monday

  • Tuesday

  • Wednesday

  • Thursday

  • Friday

  • Saturday

This column holds the start day of the week for the time sheet. It is enabled if the company configuration Start Day of Week is enabled.

Adjustment Group

Text

100

Conditional.

Sets an adjustment group for a work order.

Company configuration 'use adjustment group' must be enabled.

The buyer cannot assign any adjustment group to any work order. The associations of the adjustment group must be present in the work order being uploaded.

If the Job Posting Template rule Creator can change Adjustment Group is enabled, the adjustment group can be modified.

Allow Worker to Submit Time Sheet

Text

3

Yes

Valid values are:

  • Yes

  • No

This field will indicate whether or not the associated worker to this work order can submit time in the application.

Default Shift Schedule

Text

100

Dependent on Rate Schedule Configuration

Indicates default shift schedule for this work order.

Worker Pay Type Code

Text

100

Conditional

Worker Pay Type Code for Rates 2.0. This value must match a Worker Pay Type Code that is valid for the Job Posting.

Company configurations 'Rates 2.0' and 'Worker pay type' must be enabled.

If field left blank for Rates 2.0, this field defaults to the Worker Pay Type Code for the Job Seeker.

Rate Schedule Code

Text

100

Dependent on Rate Schedule Configuration

Indicates Rate Schedule Code.

Number of Tiers

Number

No

This field reflects the number of rate tiers in the rate-change matrix. Cannot be used with Rate Schedules.

When the Rate Change Matrix (RCM) is Buyer-defined, system will ignore the contents of this column because RCM will use RCM Custom Lookup to determine this information.

This field is ignored for Rates 2.0.

Units

Text

100

No

Valid values are:

  • Calendar Days

  • Weeks

  • Months

Optional field for rate-change matrix. Cannot be used with Rate Schedules.

When the Rate Change Matrix (RCM) is Buyer-defined, system will ignore the contents of this column because RCM will use RCM Custom Lookup to determine this information.

Calculate Rate Using

Text

100

Valid values are:

  • Base Rate

  • Cumulative Base Rate

This field determines how the rate-change matrix rates are calculated. Cannot be used with Rate Schedules.

When the Rate Change Matrix (RCM) is Buyer-defined, system will ignore the contents of this column because RCM will use RCM Custom Lookup to determine this information.

Rate Change Matrix Start Date

Date

No

This field indicates the start date of the Rate Change Matrix.

Available when the Rate Change Matrix (RCM) is buyer-defined and Start Date is defined by user. When the RCM is buyer-defined and Start Date is defined by System or by Tenure Policy, the system will ignore the contents of this column and use the Tenure Policy to determine the RCM Start Date

If RCM is not buyer defined, this field will not be processed by the system.

This field is ignored for Rates 2.0.

Rebillable Margin

Decimal

No

This field reflects the numerical value of the re-billable markup percentage.

When the Rate Change Matrix (RCM) is buyer-defined, system will ignore the contents of this column because RCM will use RCM Custom Lookup to determine this information.

Previous Start Date

Date

No

Example:

  • MM/DD/YYYY

  • DD/MM/YYYY

  • YYYY-MM-DD

This field sets the previous start date on the work order for the rate-change matrix.

This format will reflect what is listed in the header of the file. Otherwise, the format will be determined by the settings associated with the user performing the upload.

When the Rate Change Matrix (RCM) is buyer-defined, system will ignore the contents of this column because RCM will use RCM Custom Lookup to determine this information.

Pay Grade

Text

100

No

This field sets the pay grade on the work order for the rate change matrix.

When the Rate Change Matrix (RCM) is Buyer-defined, system will ignore the contents of this column because RCM will use RCM Custom Lookup to determine this information.

Comparator Rate

Decimal

No

Example:

1.25

This field sets the comparator rate on the work order for the rate change matrix. Comparator rate indicates what a permanent worker's equivalent rate would be. All values are in percentage. For example, 1.25% should be entered as 1.25, not .0125.

Company configuration 'Germany Rate Automation' must be enabled.

When the Rate Change Matrix (RCM) is Buyer-defined, system will ignore the contents of this column because RCM will use RCM Custom Lookup to determine this information.

Legal Entity

Text

100

Conditional

Valid SAP Fieldglass Legal Entity

The Legal Entity field appears only when the Legal Entity has been enabled in the company configuration for Contingent and/or Services: Work Orders and Workers.

The Legal Entity code is associated to Work Order or SOW.

If the 'Enhanced Legal Entity Validation' is enabled for the company, the system validates if the owner has visibility to the work order legal entity, business unit,cost center, and site codes. If even one of these is not associated to the owner, the system displays an error message.

Additional Invoice Adjustment Currency

Text

3

No

Valid Fieldglass buyer currency

Examples:

USD

CAD

EUR

Indicates if buyer is able to add additional invoice-adjustment currency.

Auto Register Job Seeker

Text

3

No

Valid values are:

  • Yes

  • No

Indicates if it can register job seeker on work order.

If unlocked on Job Posting Template (JPT) and Yes is entered here, then when the Work Order is in a Confirmed status, the Worker is registered automatically. If unlocked on JPT and No entered here, then when the Work Order is in an Activated status, the Worker has to be registered with the email.

Entered value is ignored when Flag is locked at JPT.

If this field is blank, and if company configuration 'Auto register' is enabled and 'Lock Auto Register' flag on JPT is set to False, then the 'Auto Register' flag is set to True for the job posting.

AP Code

Text

200

Conditional

Valid AP Codes defined on the buyer side on Remit-to Address (RTA) codes.

Accounts Payable Code.

Company configuration 'AP Code Required' must be enabled.

Time Zone

Text

100

No

Examples:

GMT-06:00 Central Time (US & Canada)

or

GMT-05:00 Eastern Time (US & Canada)

or

GMT Greenwich Mean Time

Time zone for worker.

If not entered, it is defaulted to the default setting of buyer's time zone.

[Line n] Line Item

Text

100

Conditional. The company configurations 'Cost allocation is based on spend matrix' and 'Cost center management during contingent work order/revision creation', as well as the related job posting template rule Use Spend Matrix to determine cost allocation structure and budget validation must be enabled to report on Spend Matrix details.

Examples:

3

5 - Expense

Unique line item for the work order.

Required for all spend lines.

The Line Item, Cost Center and Rate Category combination must be unique for a spend line.

This field must be added manually to the upload file.

This field is ignored for Rates 2.0.

[Line <n>] Cost Center

Text

200

Conditional. The company configurations 'Cost allocation is based on spend matrix' and 'Cost center management during contingent work order/revision creation', as well as the related job posting template rule Use Spend Matrix to determine cost allocation structure and budget validation must be enabled to report on Spend Matrix details.

A valid SAP Fieldglass Cost Center code that is already defaulted on the work order.

Example:

1001

Cost center code for the spend line.

A unique line item (line item/cost center/rate category) can have only one cost center (across all spend lines for that line item).

This field must be added manually to the upload file.

This field is ignored for Rates 2.0.

[Line <n>] Rate Category/UOM

Text

100

Conditional. The company configurations Cost allocation is based on spend matrix and Cost center management during contingent work order/revision creation, as well as the related job posting template rule Use Spend Matrix to determine cost allocation structure and budget validation must be enabled to report on Spend Matrix details.

Required for Rate Spend Lines and if Expense Cumulative Spend is blank

Valid Rate Category /UOM

Examples:

  • ST /Hr

  • OT /Hr

  • ST /Day

The rate category/UOM for a rate line.

The field is required if the [Line <n>] Cumulative Quantity is entered.

The [Line <n>] Expense Cumulative Spend must be blank for a rate line. (When the Cumulative Quantity and Rate Category/UOM are entered.)

The [Line <n>] Rate Category/UOM must be blank for a expense line. (When the Expense Cumulative Spend is entered).

The Rate Category / UOM or the Cumulative Quantity and the Expense Cumulative Spend cannot be added in the same line (Line <n>).

This field must be added manually to the upload file.

This field is ignored for Rates 2.0.

[Line <n>] Cumulative Quantity

Numeric

Conditional. The company configurations 'Cost allocation is based on spend matrix' and 'Cost center management during contingent work order/revision creation', as well as the related job posting template rule 'Use Spend Matrix to determine cost allocation structure and budget validation' must be enabled to report on Spend Matrix details.

Required for Rate Spend Lines and if Rate Category is not blank.

Valid values are:

Must be 0 or >0.

The cumulative amount for a rate line.

The field is required if the [Line <n>] Rate Category/UOM is entered.

The [Line <n>] Expense Cumulative Spend must be blank for a rate line. (When the Cumulative Quantity and Rate Category/UOM is entered.)

For an expense spend line, this field must not be blank if the Expense Cumulative Spend is entered.

The Cumulative Quantity and the Expense Cumulative Spend cannot be added in the same line (Line <n>).

This field is ignored for Rates 2.0.

[Line <n]> Expense Cumulative Spend

Decimal

Conditional. The company configurations Cost allocation is based on spend matrix and Cost center management during contingent work order/revision creation, as well as the related job posting template rule Use Spend Matrix to determine cost allocation structure and budget validation must be enabled to report on Spend Matrix details.

Required for Expense Spend Lines and if Rate Category and Cumulative Quantity are blank

Example:

10.00

The expense cumulative spend amount for an expense line.

This field must be blank if the Rate Category/UOM or Cumulative Quantity is entered.

For an expense spend line, this field is required if the Rate Category/UOM or Cumulative Quantity is not entered.

This field must be added manually to the upload file.

This field is ignored for Rates 2.0.

[c] Work Order Custom Field1

Dependent on custom field configuration .

No

Dependent on custom field type.

Example:

[c] cf1

Value1

Work Order custom field(s).

Format and optional/mandatory nature of data dependent on type and configuration of custom field.

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.

SOD grid type custom fields are not supported.

[a] Adjustment

Text

100

No

Examples:

[a] State Tax

10.00

or

[a] State Tax

Delete

Adjustment to be applied to work order.

Delete value will delete adjustment from work order.

Numeric value cannot be negative when the adjustment is a discount.

Adjustments that are part of adjustment group will be ignored.

Buyers can add MSP adjustments on a work order.

[a] Invoice Adjustment Reason

Text

100

No

Any adjustment reason that is associated with the work order. The adjustment reason name should be prefixed with '[a]'. For example, adjustment reason name: State Tax' should be '[a] State Tax.

Invoice Adjustment Reasons added for an Adjustment must be accepted.

Do not include this field if not in use.

[a] Site Tax

Decimal

No

Adjustment to Site Tax % for work location.

Example: State Tax' should be entered as '[a] State Tax'.

If the job posting template has the flag 'Enable cost allocation based on Spend Matrix selection' enabled, then ignore this column and its value.

Do not include this field if not in use.

[br] Rate Category/ Rate UOM

Decimal

Yes

The bill rate provided for this work order. This rate is the final bill rate for the work order.

For Rates 2.0,

  • if there is no rate component group, the system runs a lookup to determine the value and compares to entered value. If no value entered here but rate is on the job seeker, the system uses the job seeker rate but if no rate on job seeker, it defaults to zero.

  • if there is a rate component group, and the rule Allow Buyer to edit Bill Rate on Work Order and Work Order Revision is enabled, the system runs lookup to determine the value and compares to entered value. If no value entered here but rate is on the job seeker, the system uses the job seeker rate but if no rate on job seeker, the rate processes like no rate component group (previous bullet).

  • If calculated rate = Factor and there is no rate component group and rate flag Allow Rate Factor edits by Buyer option disabled, the system runs lookup to determine the value and compares to entered value. If no value entered here but there is a rate on the job seeker, the system uses the job seeker rate but if no rate on job seeker, the rate processes like no rate component group (first bullet).

  • If calculated rate = Factor and there is a pay based rate component group, and Factor uses a different rate component group than its Base, AND Rate flag Allow Rate Factor edits by has disabled the Buyer option, AND rate component group rule Allow Buyer to edit Bill Rate on Work Order and Work Order Revision is enabled, the system runs lookup to determine the value and compares to entered value. If no value is entered here but there is a rate on the job seeker, the system uses the job seeker rate but if no rate on job seeker, factor rate does not have rate component group unless its Base Rate uses a rate component group.

  • If calculated rate = Factor and there is a bill based rate component group, and Rate flag Allow Rate Factor edits by has disabled the Buyer option, the system runs lookup to determine the value and compares to entered value. If no value is entered here but there is a rate on the job seeker, the system uses the job seeker rate but if no rate on job seeker, factor rate does not have rate component group unless its Base Rate uses a rate component group.

  • For factor rate:

    • When no rate component group is used, this field is non editable. In that case, Bill Rate value is calculated using the values of the Base Rate and the Factor.

    • When pay rate based rate component group is used, this field is non editable. In that case, the system ignores any entry in the field, and Bill Rate is calculated using Pay Rate and Components.

    • When bill rate based rate component group is used, this field is non editable. In that case, the system ignores any entry in the field, and Bill Rate is calculated by applying the Factor to the Base Rate's Bill Rate.

[pr] Rate Category/ Rate UOM

Decimal

Yes

Value must be greater than or = zero.

The pay rate for this work order. This rate is the final pay rate for the work order.

If this is a Rate Change Matrix (RCM) enabled work order:

  • This field will be considered only when its a component rate and job posting template rule Allow Buyer to edit Pay Rate on Work Order and Work Order Revision (for Pay Rate Based rates) is enabled.

  • The Supplier Confirmation Required header is defaulted to True when pay rate is not picked from the file.

  • When component rate is present and job posting template rule Allow buyer to edit pay rate is enabled, then the Supplier Confirmation Required header is honored.

For Rates 2.0

  • If no rate component group, values will be ignored if upload header 'Supplier Confirmation Required' is not False.

  • If rate component group and 'Allow Buyer to edit Bill Rate on Work Order and Work Order Revision' is disabled, system runs lookup to determine value and compares to entered value. If no value entered here but rate on job seeker, uses job seeker rate but if no rate on job seeker, the rate will process like no rate component group.

  • For bill rate based rate component group, system will ignore any entry in the field, and pay rate will be calculated using Bill Rate and Components.

  • For calculated rate of factor and no rate component group, upload header 'Supplier Confirmation Required' must = False and value greater than or equal to zero else error.

  • For calculated rate of factor and pay rate based rate component group, the Factor must use a different rate component Group than its Base, AND rate flag Allow Rate Factor edits by has disabled the Buyer option, AND rate component group rule Allow Buyer to edit Bill Rate on Work Order and Work Order Revision must be disabled.

  • For factor rate:

    • When no rate component group is used, the field is editable only when upload header "Supplier Confirmation Required" = False. When the field is non editable, the system ignores any entry in the field.

    • When pay rate based rate component group is used, the field is non editable. In that case, the system ignores any entry in the field, and Pay Rate is calculated by applying the Factor to the Base Rate's Pay Rate.

    • When bill rate based rate component group is used, the field is non editable. In that case, the system ignores any entry in the field, and Pay Rate is calculated using the Bill Rate and Components.

[mspr] Rate Category/ Rate UOM

Decimal

No

If MSP Flat Fee, the value must be greater than or equal to zero.

If MSP %, the value must be between 0-99.

The MSP’s rate for this worker. The rate is the final MSP rate for the work order.

Buyer must use MSP(s), else field is ignored.

[rc] Rate Category/ Rate UOM

Text

No

[rc] DT/Hr

Weekend_Factor

A value in this field will add a new rate code while creating the work order, even though the rate is not present on the associated Job Posting.

When a new rate with the same Rate Category and UOM as existing is specified, the old rate with same Rate Category, and UOM will be removed.

[rcomp] Rate Category/UOM~Rate ComponentCode

Decimal

Optional

Example:

[rcomp] ST/HR~COS

This field accepts the numerical values for the pay rate. Process only the valid and editable rate component values.

If Rates 2.0

  • If no rate component group, field is ignored.

  • If rate component group and flag 'Allow Buyer to Edit Value' is not enabled, field is ignored. If flag enabled, system runs lookup to determine value and compares to entered value. If no value entered here but rate on job seeker, uses job seeker rate but if no rate on job seeker, the rate will process like no rate component group.

[drc] Rate Category/ Rate UOM

Text

No

Example:

[drc] DT/hr

Weekend_Factor

This will remove an existing rate code on the work order. Existing rates present on Job Posting can be removed while creating the work order if the Allow Rate change Flag is Enabled on the Job Posting.

[Committed Spend flag] Rate Category / Rate UOM

Text

3

Yes, if [rc] Rate Category / Rate UOM included

Valid values are:

  • Yes

  • No

This will set the Committed Spend flag on a newly added rate.

For Rates 2.0, values are accepted for rate types Rate and Calculated Rate for Calculated Type = Factor. This column is ignored if the rate is a Calculated Rate with Calculation Type = Rate Rule, and the rate will not be flagged to include in spend. This field is ignored if Work Order uses a Rate Schedule.

[Parity Pay Rate ]Rate Category / UOM

Decimal

No

This field accepts the numerical values for the parity pay rate.

[Supplier Bill Rate] Rate Category / UOM

Decimal

No

This field accepts the numerical values for supplier bill rate.

[Tier n] Rate Category /UOM

Text

100

Yes, if ‘Use Rate Change Matrix’ flag is set to On and Rate Change Type is ‘Rate Value’.

Valid Rate Category /UOM

Example:

  • ST /Hr

  • OT /Hr

  • ST /Day

Rate Category/UOM combination on which rate change will apply when Rate Change Type ‘Rate Value’.

When the Rate Change Matrix (RCM) is buyer-defined, system will ignore the contents of this column because RCM will use RCM Custom Lookup to determine this information.

This field is ignored for Rates 2.0.

Auto allocate cost center

Text

3

No

Valid values are:

  • Yes

  • No

If auto-allocate cost center set to ‘Yes’, all cost centers have equal percentage or amount allocated if the total allocation percentage does not add up to 100% or the total amount.

If left blank, this field defaults to Yes.

When the 'Allocation by' field is set to Percentage, the total percentage for the work order should equal 100. This supports up to 3 decimals. When the 'Allocation by' field is set to Amount, the value will support any amount above zero, up to 2 decimals.

If the 'Allocation by' field is set to Amount, and the cost center amounts do not match the Total Amount, an error is displayed.

Allocation by

Text

10

No

Valid values:

  • Percentage

  • Amount

Determines whether cost center allocation is percentage or amount based.

[cc] cost center code

Decimal

No

Example:

[cc] cc1

50.00

Allocates or edits cost center allocation which is currently associated to the work order.

[dcc] cost center code

Text

No

Valid values are:

  • Delete

Example:

[dcc] cc1

Delete

The Delete value removes cost center from allocation list which is currently associated to the work order.

[M] rate code

Decimal

No

Multiplier used with calculated rates. If added for a certain rate code, the multiplier value will be used during calculation

This field is ignored for Rates 2.0.

[a] Invoice Adjustment / Default Value

Decimal

Condtional

Example:

[a] State Tax / Default Value

10

Default value for invoice adjustment.

Company configuration and Contingent Type/Job Posting Template rule 'Supplier can define adjustments during job seeker submit' must be enabled. Company configuration 'Adjustment groups' must be enabled. Job Posting Template rule 'Include in Estimated and Committed spend' must be enabled. Site configuration 'Tax Guidance' and Tax Management 'Edits Allowed' must be enabled. Invoice adjustment flag 'Available to Supplier?' must be enabled.

[units] Rate Category/Rate UOM

Decimal

No

Indicates maximum units for time sheet allotment.

[factor] Rate Category/Rate UOM

Decimal

Conditional

Value range 00.001 to 1000 (up to 3 decimal places).

Indicates Factor based calculated rate for job seeker.

Company configuration 'Rates 2.0' must be enabled. Rate flag 'Allow Rate Factor edits by' must enable the Buyer option.

Field is ignored if calculated rate is not = Factor.

If no rate component group, system runs lookup to determine value. If no value entered here but rate on job seeker, it uses job seeker rate but if no rate on job seeker, it defaults to zero. If bill/pay rate based rate component group, system runs lookup to determine value and compares to entered value. If no value entered here but rate on job seeker, it uses job seeker rate but if no rate on job seeker, factor rate will not have rate component group unless its Base Rate uses a rate component group.

This field must be manually added to upload format.

Unique Identifier

  • Job Seeker ID field

Assumptions/Tips

  • For Rate schedules, if ‘Capture Time Worked on Time Sheet’ is not enabled and Time Sheet Type = Time In/Time Out, an error will be created.

  • If you want Consolidated Worker match logic, Combine attributes to create a strong match must be enabled in company configuration. When this configuration is enabled, if the only attribute that matches between a document and the Consolidated Worker is the Security ID or the Unique ID, the match is not considered Strong. Strong matches require one of the following combinations: Identical Name + Security ID + Unique ID, Identical Security ID + Unique ID, Identical Name + Security ID when document has no Unique ID, or Identical Name + Unique ID when document has no Security ID.

  • Amounts will be automatically rounded to whole number but displayed to two decimal points if currency is Yen.

  • When Tenure company configuration is enabled, validations are done using tenure policy lookup table. If Worker is in violation of a tenure policy, error will be displayed.

  • When a document from this upload picks up a new Tenure Policy, Display Tenure Notifications will default to Yes for that policy.

  • Even if the company configuration Supplier presented rate defaults as final rate is enabled, this upload will update the pay rate value from the upload file.

  • Combination of header 'Approval Required? = False' and header ‘Supplier Confirmation Required = True’ is not allowed.

  • In the event the Allow Daily Verification flag is locked on the Job Posting Template, then it cannot be overridden through this upload. The Allow Daily Verification flag must be made available for all types of time sheet frequencies.

  • Both buyer- and supplier-entered Custom Fields will display and can be updated by both parties regardless of who created the Custom Field first.

  • Auto Activate plays a role when Supplier Confirmation Required is set to True and Auto Engage is off on the Job Posting Template. Once the Work Order is uploaded, it goes into Created status and once the supplier accepts the Work Order, it goes into Activated status. No need to 'Activate' Work Order from the buyer's side.

  • For user-entered amounts, a validation has to happen on the upload to ensure that the value entered is a whole number for those currencies requiring the precision to be zero decimals.

  • If the Time Sheet Allotment is Mandatory, it must be included in the file. If [pr] or [br] is missing for the Time Sheet Allotment, an error is returned.

  • When the system processes Rate Change Matrix, the entire assignment is considered when applying Rate Change Matrix Sequences.

  • If the config Matches on Security ID only and Unique ID only are not considered Strong is disabled, the application will consider a match on SID Only a strong match (Example: FirstName+LastName NO Match + SID Match + UID Blank on document = STRONG). If there are no strong matches, or if there are multiple strong matches, the document will associate to a new Consolidated Worker.

  • During upload, when Approval Group is not present/no Business Unit is associated to any approval group, work order status will be set as follows:

    Approval Required Flag

    Supplier Confirmation Required Flag

    Auto Register Job Seeker

    Work Order Status

    True / False

    False

    Yes

    Confirmed

    True / False

    False

    No

    Activated

    True / False

    True

    Yes

    Created

    True / False

    True

    No

    Created

  • This connector considers the Corporate Calendar for spend calculation when the company configuration, Spend calculation is based on corporate calendar, is turned on.

  • The system auto generates a new line item number when a new work order or work order revision is created with new a cost center.

  • Activation_time and Respond_time are set to the upload time and are only set when the Supplier Confirmation Required header is set to False. Activation time is set only when a work order is moved to Activation or Confirmed status. Respond time is set only when a work order is moved to Accepted, Activated, or Confirmed status, whichever status happens first.

  • If company configuration 'Cost Allocation Percentage decimal precision' is enabled, when the system calculates the allocation percentage (Spend Matrix), rounding rules account for the company's set decimal precision. Spend matrix is converted from Amount to % base.

  • When 'Approval Required?' is set to False, the connector should behave as follows:

    • When Supplier Confirmation Required is set to True, the uploaded work order routes to the supplier for acceptance. The status is 'Created' and no Consolidated Worker generates until after the supplier accepts the work order.

    • When Supplier Confirmation Required is set to False, the uploaded work order is fully confirmed (assuming auto-register is enabled). Upon creation, a Consolidated Worker is generated.

  • 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.

  • Each line item can be associated with only one rate category. A validation prevents multiple rate categories from being mapped to the same line item. To use multiple rate types, you must create separate line items under the same cost allocation. This validation applies to Contingent Work Orders when Spend Matrix is enabled.

Errors

The following errors can occur when processing this upload file:

Possible Errors and Resolutions

Error Message

Resolution

Adjustment should be greater than zero.

Enter a value greater than zero in the Flat Adjustments column.

AP Code is invalid.

Verify the value in the AP Code column matches an active AP code configured for this company.

AP Code is required.

AP Code is required when the company uses AP Code lists. Enter a valid AP Code in the AP Code column.

Auto Invoicing Type must be Time Sheet, Expense Sheet, Both, or None.

Enter one of the accepted values: Time Sheet, Expense Sheet, Both, or None in the Auto Invoicing column.

Bill Rate {0} does not belong to Job Posting.

The bill rate entered for rate category {0} is not associated with the Job Posting. Verify that the rate category exists on the Job Posting and re-enter the correct bill rate in the corresponding bill rate column.

Bill Rate {0} should be greater than zero.

The bill rate for rate category {0} must be greater than zero. Verify the value in the bill rate column for that rate category.

Business Unit Code visibility: Creator or Owner does not have visibility to the Business Unit Code.

Verify that the creator or owner specified has visibility to the Business Unit Code on this work order. Correct the value in the Business Unit Code column. Applies only when Enhanced Legal Entity configuration is enabled.

Cannot upload Work Order since the Job Posting is not in a status to allow Work Order Upload.

The Job Posting referenced is in a status (Rejected or Pending Submission) that does not allow Work Order uploads. Verify the Job Posting ID column references a Job Posting in an eligible status.

Cost Center Code visibility: Creator or Owner does not have visibility to the Cost Center Code.

Verify that the creator or owner specified has visibility to all cost center codes on this work order. Correct the value in the Cost Center Code column. Applies only when Enhanced Legal Entity configuration is enabled.

Duplicate Job Posting found.

Multiple Job Postings match the Job Posting ID value provided. Supply a unique Job Posting ID in the Job Posting ID column to disambiguate.

End Date cannot be blank.

End Date is required for Temp service type work orders. Enter a valid date in the End Date column.

Evaluations need to be completed.

The Job Seeker's evaluation must be completed before a Work Order can be created. Complete the evaluation for this Job Seeker before uploading.

Hours per Day is invalid.

Enter a valid numeric value for Hours Per Day in the Hours Per Day column.

Hours per Day must be between 1 and 24.

Enter a value between 1 and 24 in the Hours Per Day column.

Hours per Week is invalid.

Enter a valid numeric value for Hours Per Week in the Hours Per Week column.

Hours per Week must be greater than or equal to Hours per Day and less than or equal to 7 times Hours per Day.

Enter a value in the Hours Per Week column that is at least equal to Hours Per Day and no greater than 7 times the Hours Per Day value.

Invalid values for Adjustment Group

The Adjustment Group code could not be resolved. Verify the value in the Adjustment Group column matches an active adjustment group code for this company.

Invalid values for Creator Username

The Creator Username either is not a buyer user with Work Order Manage permission or the role is not permitted. Verify the value in the Creator Username column.

Invalid values for Job Posting ID

The Job Posting ID could not be resolved to a unique active Job Posting. Verify the value in the Job Posting ID column.

Invalid values for Start Date

The Start Date value could not be parsed. Verify the date format and correct the value in the Start Date column.

Job Posting is not of Temp Service Type.

Work Order uploads require a Job Posting with a Temp service type. Verify that the Job Posting ID column references a Temp-type Job Posting.

Job Posting not found.

No Job Posting was found for the resolved Job Seeker. Verify the Job Seeker ID column references a Job Seeker associated with a valid Job Posting.

Job Seeker not found.

No active Job Seeker was found matching the value in the Job Seeker ID column. Verify the Job Seeker ID value is spelled correctly and the Job Seeker is active.

Legal Entity visibility: Creator or Owner does not have visibility to the Legal Entity.

Verify that the creator or owner specified is associated with the Legal Entity on this work order. Correct the value in the Legal Entity column. Applies only when Enhanced Legal Entity configuration is enabled.

Missing data for Job Posting ID

Job Posting ID is required when the Job Seeker ID matches multiple Job Seekers with the same external reference. Enter a value in the Job Posting ID column to disambiguate.

Missing data for Job Seeker ID

Job Seeker ID is required. Enter a valid Job Seeker reference in the Job Seeker ID column.

Missing data for Start Date

Start Date is required. Enter a valid date in the Start Date column.

MSP code of the {0} does not match the MSP code of {1}.

The MSP code of the creator does not match the MSP code of the Job Posting. Verify that the Creator Username column references an MSP user whose MSP code matches the Job Posting's MSP code.

MSP % for Rate {0} does not belong to Job Posting.

The MSP rate for rate category {0} is not associated with the Job Posting. Verify that rate category {0} exists on the Job Posting and enter the correct MSP rate in the corresponding MSP % column.

MSP % of Overtime Rate {0} should be greater than zero.

Enter a valid MSP rate for rate category {0}. For MSP %, enter a value between 0 and 99. For MSP Flat Fee, enter a value of zero or greater.

No Work Order can be created for this Job Seeker until the Supplier enters the Security ID. The Supplier can enter the Security ID by choosing 'Edit Security Information' from the Job Seeker's Action menu.

The Job Seeker record is missing a required Security ID. The supplier must enter the Security ID on the Job Seeker before this Work Order can be uploaded.

Number of Shift Positions must be greater than or equal to 0.

Enter a value of 0 or greater in the Number of Shift Positions column.

Pay Rate {0} cannot be negative.

Enter a pay rate of zero or greater for rate category {0}.

Pay Rate {0} does not belong to Job Posting.

Verify that the pay rate for rate category {0} matches a rate category defined on the Job Posting. Correct the value in the pay rate column for that rate category.

Pay Rate {0} should be equal to or greater than one.

Enter a pay rate of 1 or greater for rate category {0}.

Pay Rate {0} should be equal to or greater than zero.

Enter a pay rate of 0 or greater for rate category {0}.

Primary Cost Center Code visibility: Creator or Owner does not have visibility to the Primary Cost Center Code.

Verify that the creator or owner specified has visibility to the primary cost center on this work order. Correct the value in the Primary Cost Center Code column. Applies only when Enhanced Legal Entity configuration is enabled.

Rate Category / Rate UOM {0} is not valid.

The rate category and unit of measure combination in the column header is not valid for this work order. Verify that the rate category column headers (for example, [br] ST/Hr or [pr] Regular/HR) use a Rate Category/UOM combination that is defined on the associated Job Posting.

Rate Multiplier for Rate {0} does not belong to Job Posting.

The rate multiplier for the specified rate category is not associated with the Job Posting. Verify that the rate category in the rate multiplier column header exists on the associated Job Posting, and enter the correct multiplier value.

Remit-to Address is inactive.

The Remit-to Address code provided references an inactive address. Enter an active Remit-to Address code in the Remit-to Address Code column.

Remit-to Address is required.

Remit-to Address is required for this company or division. Enter a valid code in the Remit-to Address Code column.

Required data is missing for Bill Rate. Please enter value for at least one Rate Category that belongs to Job Posting.

At least one bill rate for a rate category defined on the Job Posting is required. Enter a value in the bill rate column for at least one applicable rate category.

Required data is missing for Pay Rate. Please enter value for at least one Rate Category that belongs to Job Posting.

At least one pay rate for a rate category defined on the Job Posting is required. Enter a value in the pay rate column for at least one applicable rate category.

Selected Cost Center(s) Total Allocation % must be 100.

The percentages across all cost center rows do not add up to 100. Correct the cost center allocation percentages so they total 100.

Selected Cost Centers Total Allocation amount must equal the Total Amount.

The allocated amounts across all cost center rows do not equal the committed spend total. Correct the cost center allocation amounts to match the committed spend.

Shift Position dates must be between Start Date and End Date entered for the Work Order. Adjust the Work Order dates or Shift Position assignments prior to proceeding.

One or more Shift Position dates fall outside the Work Order Start Date and End Date. Adjust the Start Date or End Date columns, or update the Shift Position assignments before uploading.

Site Code visibility: Creator or Owner does not have visibility to the Site Code.

Verify that the creator or owner specified has visibility to the Site Code on this work order. Correct the value in the Site Code column. Applies only when Enhanced Legal Entity configuration is enabled.

The Comments limit of 2000 characters has been exceeded for Work Order {0}.

Shorten the value in the Comments column to 2000 characters or fewer. {0} resolves to the Work Order reference at runtime.

The Work Order cannot be uploaded because multiple Job Seekers with the same External Reference ID exist.

Multiple Job Seekers share the same external reference. Supply a Job Posting ID in the Job Posting ID column to disambiguate, or correct the Job Seeker ID column.

The Work Order cannot be uploaded because multiple Job Seekers with the same Reference ID exist.

Multiple Job Seekers share the same internal Reference ID. Verify the Job Seeker ID column value is unique, or use an external reference to identify the correct Job Seeker.

Time In/Time Out cannot be enabled because Time Worked is not used by Rate Schedule: {0}. Please select a new Rate Schedule or Time Sheet Type.

The selected Rate Schedule does not support Time In/Time Out. {0} resolves to the rate schedule name. Enter a compatible Time Sheet Type or change the Rate Schedule Code column to a rate schedule that allows Time Worked.

Time Sheet Frequency entered is not applicable/enabled for the logged in Company.

The time sheet frequency value provided is not enabled for this company. Enter one of the enabled frequency values for the company in the Time Sheet Frequency column.

Time Sheet Frequency must be Weekly, Biweekly, Semimonthly or Monthly.

Enter one of the accepted values: Weekly, Biweekly, Semimonthly, or Monthly in the Time Sheet Frequency column.

Time Sheet Type entered is not applicable/enabled for the selected Site.

The time sheet type value provided is not enabled for the site associated with this work order. Enter a time sheet type that is enabled for the selected site in the Time Sheet Type column.

Time Sheet Type must be Standard, Time In/Time Out, or No Time Sheets.

Enter one of the accepted values: Standard, Time In/Time Out, or No Time Sheets in the Time Sheet Type column.

Users with the Configuration Manager role cannot be selected.

The user specified in the Creator Username column has the Configuration Manager role, which is not permitted for work order creation. Enter the username of a buyer user with an eligible role.

{0} does not have visibility permission to one or more of the following: Legal Entity, Business Unit, Site, and / or Cost Center.

The Work Order Owner specified does not have the required visibility to the work order's Legal Entity, Business Unit, Site, or Cost Center. {0} resolves to "Owner" at runtime. Verify that the Work Order Owner Username column references a user with the appropriate visibility. Applies only when Enhanced Legal Entity configuration is enabled.

Work Order already exists for Job Seeker.

A Work Order already exists for the Job Seeker referenced. Each Job Seeker can have only one active Work Order. Verify the Job Seeker ID column or confirm whether this record was already uploaded.

Work Order can not be created as the Job Seeker has been Withdrawn by the Supplier.

The Job Seeker has been withdrawn and is no longer eligible for a Work Order. Update the Job Seeker status or use a different Job Seeker ID.

Work Order cannot be uploaded because the Job Posting is closed.

The Job Posting referenced is in Closed status. Verify the Job Seeker ID column references a Job Seeker associated with an open Job Posting.