SOW Supplier Response Upload

This integration uploads supplier responses to statements of work.

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 – SOW Supplier Response Upload.

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

Predecessors

Suppliers

Statements of Work (SOWs)

Related Connectors

SOW Shell Upload

SOW Characteristics Upload

SOW Submit 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 Supplier Response Upload

Transaction

Yes

Only applicable for the API-V1.0 version.

Transaction Type

Transaction Type. The valid type names are:

  • True: If any record errors, 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 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 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, for supplier uploads.

Company Code of the buyer company to which the responses are being sent.

Valid SAP Fieldglass buyer code

Comments

No

Upload comments

This is a comment field containing notes about the upload file.

Mark Clauses Reviewed?

Conditional. Required if any SOW has its status as 'Pending Buyer Review', next step as 'Review Clauses' and it has clauses in 'Pending Collobator Review' status.

Indicates if clauses should be marked as reviewed.

The valid values are:

  • True - Marks the clauses which are in Pending Collaborator Review status as reviewed and the SOW moves to the next step as per the existing functionality.

  • False - System displays an error since clauses are in Pending for Collaborator Review status.

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

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

Statement of Work ID

Text

16

Conditional.  Required if External SOW ID is not entered.

Example:

ABCDTQ00000123

Valid SAP Fieldglass Statement of Work ID

External SOW ID

Text

100

Conditional. Required if SOW ID is not entered.

Example:

SPIO

An external SOW identifier used by the client for tracking purposes.

Maximum Budget

Decimal

No

Example:

100000.00

The maximum budget amount allocated for the SOW/MSOW.

This field is mandatory when the SOW is supplier defined.

The maximum budget will be validated in this upload against all amounts provided in the SOW. When the 'Auto Calculate Max Budget' rule is enabled on the SOW Template, entered value will be ignored.

If the supplier is able to enter budget, the supplier is reviewing or accepting, and if Contract Type is set to default Maximum Budget on SOW, or the file is empty, the Contract's Maximum Budget value will default.

If a contract has locked this field, then the value in the file will be ignored.

Maximum Schedule Budget

Decimal

No

Example:

40000.00

For MSOWs, upload the Maximum Schedule Budget.

The maximum schedule budget amount will be validated against the maximum budget. When the 'Auto Calculate Max Budget' rule is enabled on the SOW Template, entered value will be ignored.

Maximum Fee Budget

Decimal

No

Example:

20000.00

For MSOWs, upload the Maximum Fee Budget.

The maximum fee budget amount will be validated against the maximum budget. When the 'Auto Calculate Max Budget' rule is enabled on the SOW Template, entered value will be ignored.

Maximum Event Budget

Decimal

No

Example:

10000.00

For MSOWs, upload the Maximum Event Budget.

The maximum event budget amount will be validated against the maximum budget. When the 'Auto Calculate Max Budget' rule is enabled on the SOW Template, entered value will be ignored.

Discount %

Decimal

No

Valid values are 0-100, up to 3 decimal places

SOW discount percentage.

The 'Discounts can be defined on the SOW' rule must be set to 'Yes' for the SOW ID, else this field is ignored.

Auto Invoice all Characteristics,Time Sheets and Expense Sheets

Text

3

Conditonal

Valid values are:

  • Yes

  • No

Indicates if all characteristics, time sheets and expense sheets should be auto invoiced.

SOW template flag 'Auto invoice characteristics, timesheets and expense sheets' must be set to Yes and the 'Auto Invoicing for Services' flag for Supplier Admin is not locked.

If the current value of 'Auto invoice characteristics, timesheets and expense sheets' flag on SOW is No, but the current value of 'Auto invoice characteristics, timesheets and expense sheets' flag on the underlying SOW Template is 'Yes', apply this field to SOW.

Only applicable in the scenario where the auto invoice flag for Services is not locked in the buyer supplier contract.

This rule is only allowed if the SOW template is a Master template.

If it is set to 'Yes' in the latest active SOW revision, it cannot be set to 'No'.

Additional Invoice Adjustment Currency

Text

3

No

Valid Fieldglass currency associated with buyer

Examples:

USD

CAD

EUR

Indicates if buyer is able to add additional invoice adjustment currency associated with supplier.

Default Remit-to Address

Text

100

No

Valid remit-to address code for supplier.

Indicates default remit-to address code for supplier.

[c] custom field 1

Dependent on custom field configuration.

Dependent on custom field configuration.

Buyer and supplier 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.

During review or accept, if field was already on the SOW, and was editable by buyer or supplier earlier in workflow, the SOW's value will default.

During review or accept, if the field was only editable by supplier (and there is no value or accept is the first time the supplier is seeing the field), then the contract's value will default. The custom field’s existing value will default if the supplier is accepting the SOW again after a previous review or acceptance.

During Review:
  • If field was already on the statement of work, and was editable by the buyer, the statement of work's value will default.

  • If field was only editable by the supplier (thus had no value on the statement of work), then the contract's value will default.

  • If the supplier is reviewing the statement of work again after a previous review, the custom fields existing value will default.

During Accept:
  • If field was already on the statement of work and was editable by the buyer or supplier earlier in workflow, the statement of works value will default.

  • If field was only editable by the supplier, and accept is the first time the supplier is seeing the field, then the contract's value will default.

  • If the supplier is accepting the statement of work again after a previous acceptance, the existing value will default.

Unique Identifier

  • Statement of Work ID field or the External SOW ID field

Assumptions/Tips

  • This is buyer-side upload.

  • Successful upload will change the status of the SOW from Pending Response to Approved.

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

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

  • When SOW is Pending supplier review and Allow supplier to control SOW worker rules and create worker roles rule is enabled, this upload will be blocked.

  • This upload cannot be used for an SOW response for statements of work that use a Fieldglass Talent Network (FTN) SOW Type.

  • When company configuration SOW owner name updates on existing line items is enabled for SOW and upload changes SOW status from Pending Response to Approved and if the SOW Owner was changed, the new SOW Owner is updated on existing line items.

  • If this SOW revision reaches final response approval, the system re-evaluates the activity checklist to determine if there are additional activity items affected.

  • If Creation Type = Integration, this upload cannot be used.

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

Configuration Considerations

#

Item

Notes

1

External SOW ID

In case the clients are using external ref or testing with external ref instead of SOW ID, then go to SA admin page, edit the bulk upload batch job for company, select the specific batch job ID, and change the column key from SOW ref. to external ref.

Example: For “SOW Characteristic Upload”, it is ‘dbo.get_split_key(data, 1,''' + ''','''')' by default. Change 1 to 2 (column 2 is external ref column).