Fee Response Update Upload

This integration uploads fee responses or revised fee responses.

Connector Overview

Component

Detail

Company Type

Buyer

MSP Partner

Supplier

Version Type

API-A-V1.0

Format

CSV

Prerequisites

Company plug-ins must be turned on for Integration – Fee Response Update Upload.

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

Predecessors

Statement of Work (SOW)

Fee(s)

Related Connectors

SOW Shell Upload

Fee Upload

SOW Submit Upload

SOW Fee Response 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.

Fee Response Update Upload

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 will be MM/DD/YYYY.

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 will be “#,##9.99 (Example: 1,234,567.99)”

Approval Required

No

Determines if approval is required for fee response.

Valid values are:

  • True: Fee Response created will be send for approval, if approval exists.

  • False: Fee Response will directly be marked as approved.

If field left blank, will default to False.

Submit

No

Indicates whether the fee responses on a successful upload are submitted or saved as a draft.

Valid values are:

  • True: Successful upload will submit the Fee Responses.

  • False: Successful upload will save the Fee Responses as Draft.

If field left blank, will default to True.

Buyer

Yes, if uploaded by supplier.

Indicates which buyer information is being uploaded.

Valid SAP Fieldglass buyer 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

Statement of Work ID

Text

16

Yes

Example:

ABCDTQ00001234

Must be a valid SAP Fieldglass Statement of Work ID associated with the Statement of Work (SOW).

External SOW ID

Text

100

No

External identifier associated with the SOW.

Fee Response ID

Text

16

No

Valid SAP Fieldglass Fee Response ID.

An identifier associated with the fee response.

Contains Fee Response Holdback ID if revising Fee response holdback. 

Sequence

Number

Yes

Example:

1

Indicates sequence of fee on SOW.

Field must be blank if Fee Response ID is of holdback item.

Name

Text

250

Yes

Example: Browser Fee.

Must be a valid name for the fee, as defined on SOW or defined in fee admin object.

Field must be blank if Fee Response ID is for a holdback item.

Description

Text

100

No

Description of the fee.

Field must be blank if Fee Response ID is for a holdback item.

Unit

Number

Yes

Example:

2

Unit must be a valid numeric value, up to the number of decimal places configured on the unit type assigned to the fee.

Field must be blank if Fee Response ID is for a holdback item.

Effective Date

Date

Yes

A valid date.

Example:

  • MM/DD/YYYY

  • DD/MM/YYYY

  • YYYY-MM-DD

Valid effective date for the fee response with valid format.

The Effective Date applies to all items in the Fee Response, all Effective Date entries for the same Fee Response ID must be Identical.

Field must be blank if Fee Response ID is for a holdback item.

Auto Invoicing

Text

3

No

Valid values are:

  • Yes

  • No

Adjustments would be added to the fee response only if Auto Invoice is given the value of Yes.

If the value is set to No, adjustments cannot be added in the fee response, even if adjustments values are entered in the upload file.

The value is applied to the line item if the SOW template flag Auto invoice characteristics, timesheets and expense sheets is set to Yes and the Auto Invoicing for Services flag for Supplier Admin is not locked. Also applied 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.

Otherwise, the value in the column is ignored.

Remit To Address Code

Text

100

Conditional

Valid Remit to Address codes for supplier.

If entered, must be a valid Remit To Address code defined in the admin object for the supplier.

Remit to Address Required rule must be Yes.

Or Buyer Selects AP Code flag on Legal Entity or Business Unit set to Yes.

If the SOW line item belongs to a buyer who has setup the supplier to create CTI, when this field is populated, the code is applied to the line item.

If the legal entity of the SOW line item has setup Remit-To-Address as Mandatory, then this field is mandatory. If this field is left blank, the upload fails and the system displays an error.

If RTA is optional per the legal entity, then this field can be left blank

Approver Name

Text

100

Yes, if Allow Supplier to select Approver for Events, Fee Responses and Schedules is enabled for the SOW

Valid SAP Fieldglass username for buyer user.

Must be a valid username for the buyer user.

If not entered, SOW approval work flow will be followed.

If the 'Enhanced Legal Entity Validation' configuration is enabled for the company and the Template rule Allow Supplier to select Approver for Events, Fee Responses, and Schedules is enabled, the system verifies that the selected approver has visibility access to the SOW legal entity/business unit/site/cost center combination. If the approver does not have visibility, the system displays an error message.

Tax Service Type

Text

100

Yes, if tax guidance Site configuration is enabled

Valid Tax Service Type for SOW.

Used for Tax Adjustment if the Tax Guidance is enabled for the site.

Comments

Text

100

No

Comments about fee response.

Reason

Text

100

Yes if Revision

Valid SAP Fieldglass reason code.

Reason for revision.

[c] Custom field name 1

Text

100

Dependent on custom field configuration

Example:

[c] Email address

Test.email@gmail.com

Must be a valid custom field with the custom field name as header.

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.

There can be multiple custom fields added as different columns with Custom Field name as header.

[a] Adjustment name

Number

No

Valid SAP Fieldglass adjustment.

Example:

[a] State Tax 1

10.63

Must be a valid adjustment name as column header. The value entered in this column will be the adjustment value.

Unique Identifier

  • Statement of Work ID field

  • External SOW ID field

  • Fee Response ID field

  • Effective Date field

  • Name field

  • Sequence field

Assumptions/Tips

  • For multi-line handling, records are grouped with keys as Statement of Work ID + External SOW ID + Fee Response ID, creating a single Response with multiple line items using the multi-line group keys, if the respective multi-line configuration rules are met.

  • For a single response with multiple line items, line items provided in the upload file are only considered and the missing line-items from the previous response are not carried forward if they are not provided in 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.

  • When Fee Availability on SOW flag is set to Available for Associated Suppliers, if a supplier is not selected/associated to a particular fee in the library, that fee will not be available to copy on an SOW, irrespective of who is adding the fee (buyer or supplier).

  • A revision is determined if the Fee Response ID is in invoiced status.

  • Supplier can use this upload to revise fee response holdback.

  • Since a CSOW can have different currency than a MSOW, each line item amount on the CSOW will be converted to the MSOW's base currency using the conversion factor already captured on the CSOW, and then will be validated against MSOW budgets. 

  • Upload will allow Fees whose Start & End Date match with the Fee Response's Effective Date and have Enable Effective Fee Period flag set to Yes. No validation on dates for fees that have Enable Effective Fee Period flag set to No.

  • Enabling the rule 'Allow Supplier to Edit Value' allows the supplier to modify the value of the affected adjustments in an adjustment group.

  • If Can select a subset of Fees and Roles, and alter the Rates, but cannot add new Fees and Roles rule is enabled on a MSOW, the user will be able to use any fees currently on the CSOW.

  • When company configuration SOW owner name updates on existing line items is enabled for the SOW and the SOW Owner has been updated, and when Fee Response ID is in Invoiced status and a Revision is created, the new SOW Owner is reflected on the revised Fee.

  • If the SOW Type/Template flag Set Fee response / revision attachments as mandatory is set to Yes, then the user must add an attachment before submitting the Fee Response.

  • When account category is unknown, the cost center name cannot be Unknown during the buyer submit or approve action on the document. The account category and related cost center must be chargeable.

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