SOW Shell Upload
This integration uploads SOW shell data, and can also be used to create a SOW Bid without characteristics and worker/role/site combination and keep the SOW Bid in Draft status.
This is the first of three connectors needed to upload a complete SOW. The other two are Characteristic Upload and SOW Submit Upload.
Connector Overview
|
Component |
Detail |
|---|---|
|
Company Type |
Buyer |
|
Version Type |
API-V1.0 |
|
Format |
CSV |
|
Prerequisites |
Company Details Setting must be turned on for Integration – SOW Shell Upload. User role permission must be turned on for Upload Data and Download Data. |
|
Predecessors |
N/A |
|
Related Connectors |
SOW Submit Upload SOW Supplier Response Upload SOW Worker Upload Characteristic Upload Fee Upload Fee Response Upload |
File Formatting
Header
|
Component |
Required? |
Definition/Use |
Notes |
Value |
|---|---|---|---|---|
|
Type |
Yes |
SOW Shell Upload |
||
|
Transaction |
Yes |
Only applicable for the API-V1.0 version. Transaction Type |
Valid values are:
|
|
|
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)
|
|
|
Number Format |
No |
Chinese (Simplified) This determines the number format for the numeric data in the file. |
The valid values are:
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 “#,##9.99” (Example: ”1,234,567.99”) |
|
|
Date Format |
No |
Date format used in the file |
The valid values are:
If this field is not included in the header, the default value is MM/DD/YYYY.
|
|
|
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 |
|---|---|---|---|---|---|
|
External SOW ID |
Text | 100 | Yes |
An external SOW identifier used by the client for tracking purposes. |
|
|
Contract ID |
Text |
16 |
No |
Six-letter company code, then CT, and numerical string. EXAMPLE:
|
The Contract ID must be provided in order for the statement of work to use a contract. |
|
Owner Username |
Text |
200 |
Yes |
Valid SAP Fieldglass username |
User name of the SOW Owner. If the Enhanced Legal Entity Validation configuration is enabled for the company, the system validates if the owner has visibility to the SOW 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. |
|
Creator Username |
Text |
200 |
No |
Valid SAP Fieldglass username |
User name of the Creator. If the Enhanced Legal Entity Validation configuration is enabled for the company and if the creator username is not the same as the owner username, the system validates if the creator and owner both have visibility to the SOW legal entity, business unit, cost center, and site codes. If even one of these is not associated to either the creator or the owner, the system displays an error message. |
|
Currency |
Text |
100 |
Yes |
Example:
|
Currency of the SOW. |
|
Classification Code |
Text |
400 |
Conditional Required if Classifications are defined for the company. |
Classification. If classifications is not defined for the company, this column can be kept blank. |
|
|
Additional Classifications |
Text |
100 |
No |
Example:
|
For MSOWs that have multiple classifications, this field contains the additional classifications added during creation or revision, and must be separated by a (|) pipe delimiter. Applicable only for MSOWs. If this field is left blank, no Additional Classifications are added. Default value is blank. |
|
Supplier Code |
Text |
6 |
Yes |
Valid supplier code for buyer |
Supplier Code For SOW bid, you can separate multiple values with a tilde (~). |
|
Project ID |
Text |
14 |
No |
Example: ABCDPJ00001212 |
The Project ID that is associated to the given statement of work. The given project must not be closed. If the business unit associated to the statement of work is not found in the list of business units associated to the project, an error occurs. If the currency of the given statement of work does not match the currency of the project, an error occurs. |
|
Supplier Contract ID |
Text |
16 |
No |
Valid approved Contract ID |
The Statement of Work configuration and and the Rates 2.0 configuration must be enabled. |
|
Supplier Master SOW ID |
Text |
100 |
No |
Valid Master SOW ID(s) |
This field is only applicable for SOW Bid. SOW ID to be associated to the given supplier. If more than one supplier is being associated to the given SOW Bid, this field can be tilde (~) delimited to associate an SOW to each associated supplier. If multiple values with tilde (~) delimiter are provided, the SOW IDs are associated to the supplier codes in the same order and delimited location as provided. Blank values can be passed for delimited values where no SOW should be associated to the corresponding supplier For example, if the Supplier Code column has a value of "ABC~JKL~XYZ~0123", associating supplier codes ABC, JKL, XYZ, and 0123 to the SOW Bid. Suppose suppliers JKL and 0123 should be associated to different master SOWs while suppliers ABC and XYZ should have no master SOW. In this case, this Supplier Master SOW ID column should have the following value: "~XXXXTQ00001101~~XXXXTQ00004402" This associates "" (no SOW) to supplier ABC, associates XXXXTQ00001101 to supplier JKL, associates "" (no SOW) to supplier XYZ, and associates XXXXTQ00004402 to supplier 0123. |
|
Additional Suppliers |
Text |
100 |
Conditional |
Valid supplier code(s) for buyer |
Supplier code(s) for Master SOW separated by (|). Company configuration 'Master SOW' and 'Allow Multiple Suppliers' must be enabled. |
|
Billable? |
Text |
3 |
No |
Valid values are:
|
If Yes, SOW line items can be invoiced. If No – The SOW cannot be invoiced since it is not billable. |
|
Is Master Statement of Work? |
Text |
3 |
No |
Valid values are:
|
If Yes, Source column should be template to create Master SOW. |
|
Source |
Text |
10 |
Yes |
Valid values are:
|
The source can be Master SOW or Template. |
|
Template ID |
Text |
16 |
Yes, if Template Name not entered and Source is Template. |
Example:
|
System-generated template ID. If the Enhanced Legal Entity Validation configuration is enabled for the company, the creator and owner must have legal entity and business unit visibility to the template, otherwise the system displays an error message.
If the SOW uses a contract, Use Rates Based on Effective Date is set to Yes, and you enter the template ID, the upload fails with an error message if the associated contract's rates lookup:
|
| Template Name/ Master SOW ID | Text | 200 | Yes, if Template ID not entered. |
SOW Template name or the Master SOW ID . Template Name/Master SOW ID can also have External Master SOW reference as a valid value if Source = 'Master SOW'. If the 'Enhanced Legal Entity Validation' configuration is enabled for the company, the creator and owner must have legal entity and business unit visibility to the template / master SOW, otherwise the system displays an error message.
If the SOW uses a contract, Use Rates Based on Effective Date is set to Yes, and you enter the template name, the upload fails with an error message if the associated contract's rates lookup:
|
|
|
Buyer Reference |
Text |
100 |
No |
|
SOW Buyer Reference. If the statement of work uses a Contract, and Contract Type is set to default this field on statements of work, the Contract's value will be used automatically if field was left blank in file. If this field is locked by the contract, then the value in the file will be ignored. |
|
Name |
Text |
100 |
Yes |
Name of the SOW. If left blank, this field defaults to the template name. If the statement of work uses a Contract, and Contract Type is set to default this field on statements of work, the Contract's value will be used automatically if field was left blank in file. If this field is locked by the contract, then the value in the file will be ignored. |
|
|
Description |
Text |
10000 |
No |
Description about SOW. If the statement of work uses a Contract, and Contract Type is set to default this field on statements of work, the Contract's value will be used automatically if field was left blank in file. If this field is locked by the contract, then the value in the file will be ignored. |
|
|
Start Date |
Date |
Conditional Required if when the Source specified in the file is Template. |
Start date of the SOW. If child SOW and Enforce Date Duration of Master Statement of Work when creating Child Statement of Work = Start date only or On Start and End Dates, this field must be within the start and end dates of the MSOW. If Enforce Date Duration of Master Statement of Work when creating Child Statement of Work is any other value, this field can be any date before the end date of CSOW. If the statement of work uses a Contract, and Contract Type is set to default this field on statements of work, the Contract's value will be used automatically if field was left blank in file. If this field is locked by the contract, then the value in the file will be ignored. |
||
|
End Date |
Date |
Conditional Required if when the Source specified in the file is Template. |
End date of the SOW. If child SOW and Enforce Date Duration of Master Statement of Work when creating Child Statement of Work = End date only or On Start and End Dates, this field must be within the start and end dates of the MSOW. If Enforce Date Duration of Master Statement of Work when creating Child Statement of Work is any other value, this field can be any date after the start date of CSOW. If the statement of work uses a Contract, and Contract Type is set to default this field on statements of work, the Contract's value will be used automatically if field was left blank in file. If this field is locked by the contract, then the value in the file will be ignored. |
||
|
Legal Entity |
Text |
100 |
Conditional |
Valid SAP Fieldglass Legal Entity |
Legal Entity code associated to SOW. Company configuration Use legal entity must be turned on for Services. If the Enhanced Legal Entity Validation configuration is enabled for the company, the creator and owner must have visibility access to the legal entity code. If the legal entity code is not associated with either the creator or the owner, the system displays an error message. If the legal entity is not associated to the SOW template, the system displays an error message. If the statement of work uses a Contract, and Contract Type is set to default this field on statements of work, the Contract's value will be used automatically if field was left blank in file. If this field is locked by the contract, then the value in the file will be ignored. |
|
Site Code |
Text |
200 |
Yes |
Valid SAP Fieldglass Site Code |
The Site Code as defined in the SAP Fieldglass system. If the Enhanced Legal Entity Validation configuration is enabled for the company, the creator and owner must have visibility access to the site code, and the site code must have visibility to the SOW legal entity. If the entered site code is not associated with either the creator or the owner, the system displays an error message. If the site code does not have visibility to the SOW legal entity, the system displays an error message. If the statement of work uses a Contract, and Contract Type is set to default this field on statements of work, the Contract's value will be used automatically if field was left blank in file. If this field is locked by the contract, then the value in the file will be ignored. |
|
Purchase Unit |
Text |
100 |
Conditional |
Valid Purchase Unit Code |
Purchase Unit associated to the Statement of Work. |
|
AP Code |
Text |
200 |
Conditional |
Valid SAP Fieldglass AP Codes defined on the Buyer Side on 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. |
|
Location Code |
Text |
200 |
Conditional |
Valid SAP Fieldglass Location Code(s) |
Location Code is mandatory when a site has more than one Location or at least one sub-configuration for company configuration Use multiple locations is enabled. Multiple locations are separated by a tilde (~) and at least one sub-configuration for company configuration Use multiple locations must be enabled. |
|
Primary Location Code |
Text |
100 |
Conditional |
Valid SAP Fieldglass Location Code |
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. |
|
Business Unit Code |
Text |
100 |
Yes |
Valid SAP Fieldglass Business Unit Code |
The Business Unit Code as defined in the SAP Fieldglass system. If the Enhanced Legal Entity Validation configuration is enabled for the company, the creator and owner must have visibility access to the business unit code and the business unit code must have visibility to the SOW legal entity. If the entered business unit code is not associated with either the creator or the owner, the system displays an error message. If the business unit code does not have visibility to the SOW legal entity, the system displays an error message. If the statement of work uses a Contract, and Contract Type is set to default this field on statements of work, the Contract's value will be used automatically if field was left blank in file. If this field is locked by the contract, then the value in the file will be ignored. |
|
Comments To Supplier |
Text |
2000 |
No |
Comments |
|
|
Defined By |
Text |
8 |
Yes |
Valid values are:
|
Indicates who can define SOW. |
|
Clauses |
Text |
3 |
Conditional Required if it is marked as Mandatory on the template. |
Valid values are:
|
If Yes, the SOW supports the Clauses. At least one payment characteristics or the clauses need to be selected. |
|
SOW Worker |
Text |
3 |
No |
Valid values are:
|
If Yes, the SOW supports the SOW worker. At least one payment characteristics or the clauses need to be selected. Can't be set by the buyer if Allow supplier to control SOW worker rules and create worker roles is enabled on the template. |
|
Use Rates on SOW Workers |
Text |
3 |
No |
Valid values are:
|
Indicates if Rates are used on SOW workers. SOW Workers must be enabled in order to enable this field. If an invalid value is entered or the SOW Type has enabled the Hidden? and/or Locked flag for the Form Page step, the system will default this field according to the SOW Template. If this field is left blank it defaults to the value in the SOW Template. Only visible when Rates 2.0 is enabled. If the statement of work uses a contract, the contract's lookup will automatically override the entry in the file. |
|
SOW Worker Roles Lookup |
Text |
100 |
No |
Valid values are:
|
The name of the SOW Worker Role lookup. If a Buyer uses multiple MSPs, the lookup must be valid for the SOW Template’s MSP Company. When 'Use Rate Schedule' is enabled, the selected 'SOW Worker Roles Lookup' can't use 'Rate Category /UOM' as a value. If an SOW Bid is being created, then the lookup entered can only use SOW Worker Role Code and Site Code as Values, not Rate Category /UOM. The default is the value on associated SOW Template if the Hidden? and/or Locked? flags on the SOW type are enabled for the Form Page setup. If this field is left blank it defaults to the value in the SOW Template. When "Use Rates on SOW Workers" is set to "No", the system ignores the contents of this field, and no lookup is saved. Only visible when Rates 2.0 is enabled. If the statement of work uses a contract, the contract's lookup will automatically override the entry in the file. |
|
Rates Lookup |
Text |
100 |
No |
A valid Rates Lookup with the following Service Type:
|
The name of the Rate 2.0 lookup. If a Buyer uses multiple MSPs, the lookup must be valid for the SOW Template’s MSP Company. The default is the value on associated SOW Template If the Hidden? and/or Locked? flags on the SOW type are enabled for the Form Page setup. If 'Use Rates on SOW Workers' is set to "No" the system ignores the contents of this field and no lookup is saved. Only visible when Rates 2.0 is enabled.
If Use Rates Based on Effective Date is set to Yes, the upload fails with an error message if the rates lookup:
If the statement of work uses a contract, the contract's lookup will automatically override the entry in the file. |
|
SOW Workers with Fees |
Text |
3 |
No |
Valid values are:
|
If Yes, the SOW supports the SOW Worker with fees. At least one payment characteristics or the clauses need to be selected. |
|
Is Maximum Budget entered by supplier? |
Text |
3 |
No |
Valid values are:
|
If Yes, the SOW Maximum Budget is entered by the supplier. |
|
Maximum Budget |
Decimal |
Conditional |
Amount can be specified for SOW Maximum budget. If the SOW Template rule Auto Calculate Max Budget is enabled, this field is not mandatory. If this field is entered, it must match the sum calculated, else an error is generated. If the statement of work uses a Contract, and Contract Type is set to default this field on statements of work, the Contract's value will be used automatically if field was left blank in file. If this field is locked by the contract, then the value in the file will be ignored. |
||
|
Spend |
Decimal |
Conditional Required if Display Spend Allocation has been enabled in the company configuration. |
Amount specified for max budget allocated spend. |
||
|
Adjustments |
Decimal |
Conditional Required if Display Spend Allocation has been enabled in the company configuration. |
Amount specified for max budget adjustment spend. |
||
|
Suppress Budget Amount from Supplier |
Text |
3 |
No |
Valid values are:
|
If Yes, the Budget amount is suppressed from the supplier login view. |
|
Cap on Worker Spend |
Decimal |
No |
If an amount is specified, the Worker Spend Amount cannot exceed this amount. This amount cannot exceed the Maximum Budget amount. When the Allow invoicing from approved Time Sheets flag and the Allow invoicing from approved Expense Sheets flag are both unchecked or set to No, any value in this field is ignored and validation is suppressed. |
||
|
Headcount Cap |
Decimal |
Conditional Required if Head Count Cap rule is enabled for the template. |
Range: 1-9999 |
Specified cap value is validated during the SOW Worker addition to the SOW. |
|
|
Holdback % |
Decimal |
No |
Examples:
|
The holdback % that is set on the SOW. SOW template rule Enable Holdback must be set. |
|
|
Fee Response Holdback % |
Decimal |
No |
Examples:
|
The holdback % that is set on the SOW fee response. SOW template rule Enable Holdback must be set. |
|
|
Adjustment Group |
Text |
200 |
No |
Any valid SAP Fieldglass Adjustment Group |
Adjustment Group is set to the Pay Terms request only if use of Adjustment Group is enabled in the company configuration. |
|
Do Not Exceed Amount |
Decimal |
14 |
Yes |
Positive Decimal value: |
Max Budget set on SOW. If the statement of work uses a Contract, and Contract Type is set to default Maximum Budget field on statements of work, the Contract's value will be used automatically if field was left blank in file. |
|
MSP Service Fee % |
Number |
3 |
No |
Range 0-100 |
For MSP Buyer only. |
|
Discount % |
Decimal |
Conditional |
Valid values are 0-100, up to 3 decimal places |
Discount for SOW. Discounts can be defined on the SOW rule must be set to Yes for the SOW ID, else this field is ignored. |
|
|
Account Category |
Text |
500 |
Yes |
A valid SAP Fieldglass account category. |
The account category of the SOW. |
|
Cost Center Code |
Text |
200 |
Yes |
Valid SAP Fieldglass Cost Center Code |
Cost center code for the SOW. 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 SOW 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 SOW legal entity, the system displays an error message. If entered cost center code is inactive, the system displays an error message. When document supports unknown account category, GLA and SOD Is suppressed. |
|
GL Account Code |
Text |
200 |
Conditional Required if GLA is enabled. |
Valid SAP Fieldglass GL Account Code |
General Ledger Account Code for the SOW. This field is mutually exclusive with Segmented Object Detail field. When Segmented object detail based allocation and Buyer can change line item cost allocation company configurations are enabled for Services cost centers, and when there is unknown account category, the software supports unknown cost center functionality. It also suppresses SOD or GLA allocation for unknown cost centers. |
|
Segmented Object Detail |
Text |
2000 |
Conditional |
Examples:
|
Segmented Object Detail string. Segments are separated by delimiter on the Segmented Object. Valid delimiters are colon (:), semi-colon (;), pipe (|), and dash (-). Required if Segmented object detail configuration set. If the Buyer Company has Segmented object detail based allocation is required company configuration enabled, then the field must be associated to a Pick List that has the first segment as Active Legal Entity. This field is mutually exclusive with GL Account fields. More than one string can appear for a cost center. When Segmented object detail based allocation and Buyer can change line item cost allocation company configurations are enabled for Services, and when there is an unknown account category, the software supports unknown cost center functionality. It also suppresses SOD or GLA allocation for unknown cost centers. |
|
Task Code |
Text |
200 |
Conditional Required if Approver can specify Cost Center and Task Code on Statement of Work Characteristics configuration is enabled. |
Valid SAP Fieldglass Task Code |
Task Code. |
|
Skip Collaboration |
Text |
3 |
No |
Valid values are:
|
Copied from master SOW. If ‘Yes’, this bypasses all of the buyer review and supplier review stages/statuses of the SOW. Only applicable if ‘Defined By’ field is Supplier or Both. Cannot be enabled along with the Allow supplier to control SOW worker rules and create worker roles rule. If left blank, this field defaults to No. |
|
Auto Respond SOW |
Text |
3 |
No |
Valid values are:
|
Appears in the file only if the Allow buyer to auto respond to pay terms flag has been enabled in the company configuration. Sets to the auto respond of the SOW template if left blank. |
|
Allow addition of Workers during approval |
Text |
3 |
No |
Valid values are:
|
Indicates if want to add worker during approval. |
|
Allow Supplier to specify Site on Line Item |
Text |
3 |
No |
Valid values are:
|
Indicates if supplier can specify Site on line item. |
|
Disallow approval of items when Maximum Budget is exceeded |
Text |
3 |
No |
Valid values are:
|
Indicates items cannot be approved if maximum budget exceeded. |
|
Disallow approval of items when Maximum Budget is exceeded for a Cost Center |
Text |
3 |
Conditional |
Valid values are:
|
Indicates items cannot be approved if maximum budget for cost center exceeded. Cannot be selected when the Allow all Cost Centers of the company to be assigned to Workers flag is enabled. |
|
Disallow approval items when Maximum Budget is exceeded for Segmented Object Detail |
Text |
3 |
Conditional |
Valid values are:
|
Indicates items cannot be approved if maximum budget exceeded for SOD. Company configuration Segmented object detail is enabled. This rule cannot be changed on upload if a value is locked on template. |
|
Disallow approval of items when Committed Spend is exceeded |
Text |
3 |
No |
Valid values are:
|
Indicates items cannot be approved if committed spend exceeded. |
|
Statement of Work Revision approval required only when Estimated Spend is exceeded |
Text |
3 |
No |
Valid values are:
|
Indicates that SOW revision approval is needed only if estimated spend is exceeded. |
|
SOW Revision approval required only when Maximum Budget is exceeded |
Text |
3 |
No |
Valid values are:
|
Indicates that SOW revision approval is needed only if maximum budget is exceeded. |
|
Allow addition of Management Events, Schedules, Events and Fees after Statement of Work is created |
Text |
3 |
No |
Valid values are:
|
Indicates that new management events, schedules, events, and fees can be added after SOW creation. |
|
Auto Activate Worker |
Text |
3 |
No |
Valid values are:
|
Used in case of payment characteristic type Team Member is selected for the SOW. |
|
Auto Register SOW Worker |
Text |
3 |
No |
Valid values are:
|
Used in case of payment characteristic type Team Member is selected for the SOW. |
|
Require Approvals on SOW Workers added during SOW Response and SOW Revision Response |
Text |
3 |
No |
Valid values are:
|
Used in case of payment characteristic type Team Member is selected for the SOW. |
|
Allow all Cost Centers of the company to be assigned to Workers |
Text |
3 |
No |
Valid values are:
|
Indicates if the cost center on the time sheet that does not belong to the SOW Worker or SOW can be added. The Propagate Cost Center to SOW Workers Configuration must be disabled. |
|
Allow Supplier Review On Time Sheets |
Text |
3 |
No |
Valid values are:
|
Used in case of payment characteristic type Team Member is selected for the SOW. If Rates 2.0 is enabled, and this field is set to 'Yes" but 'Use Rates on SOW Workers' is set to "No", the system automatically sets this field to "No". |
|
Supplier cannot modify Schedule amounts prior to invoicing |
Text |
3 |
Conditional Required if one of the three rules about schedule amount need to be set is Yes. |
Valid values are:
|
Indicates that supplier can change Schedule amounts prior to invoicing. |
|
Supplier can decrease Schedule amounts prior to invoicing |
Text |
3 |
Conditional Required if one of the three rules about schedule amount need to be set is Yes. |
Valid values are:
|
Indicates that supplier can only decrease Schedule amounts prior to invoicing. |
|
Supplier can increase Schedule amounts prior to invoicing |
Text |
3 |
Conditional Required if one of the three rules about schedule amount need to be set is Yes. |
Valid values are:
|
Indicates that supplier can only increase Schedule amounts prior to invoicing. |
|
Supplier cannot modify Event amounts when marking as complete |
Text |
3 |
Conditional Required if one of the three rules about schedule amount need to be set is Yes. |
Valid values are:
|
Indicates that supplier cannot change Event amounts when marking them as complete. |
|
Supplier can decrease Event amounts when marking as complete |
Text |
3 |
Conditional Required if one of the three rules about schedule amount need to be set is Yes. |
Valid values are:
|
Indicates that supplier can only decrease Event amounts when marking them as complete. |
|
Supplier can increase Event amounts when marking as complete |
Text |
3 |
Conditional Required if one of the three rules about schedule amount need to be set is Yes. |
Valid values are:
|
Indicates that supplier can only increase Event amounts when marking them as complete. |
|
Track Time Sheets |
Text |
3 |
Conditional |
Valid values are:
|
Used in case of payment characteristic type Team Member is selected for the SOW. If SOW Template has enabled Rate Schedules, this field must be Yes. Cannot be set by the buyer if Allow supplier to control SOW worker rules and create worker roles is enabled on the template. If Rates 2.0 is enabled, the following behavior applies: If the SOW Type has enabled 'Use Rates on SOW Workers', this field is locked and not editable. If the user enables 'Use Rates' in the file, the system automatically sets this field to "Yes". If the user leaves 'Use Rates' disabled, the system automatically sets this field to "No". |
|
Time Sheet Type |
Text |
16 |
Conditional Required if Team Member Payment Characteristic Is selected. |
Valid values are:
|
This flag indicates how time and expenses should be recorded for team member. Cannot be set by the buyer if Allow supplier to control SOW worker rules and create worker roles is enabled on the template. If Rates 2.0 is enabled and 'Track Time Sheets' is set to "No", the system ignores this field. |
|
Time Sheet Frequency |
Text |
9 |
Conditional Required if Team Member Payment Characteristic Is selected. |
Valid values are:
|
This flag indicates how frequently time sheets are submitted. If this flag is set to Weekly, then the worker receives a weekly time sheet. If this flag is set to Biweekly, then the worker receives a biweekly 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. Cannot be set by the buyer if Allow supplier to control SOW worker rules and create worker roles is enabled on the template. |
|
Can Supplier change the Rate from Rate Grids Or Can supplier edit the rate value when defining SOW Worker roles |
Text |
19 |
Conditional |
Valid values are:
|
Indicates whether the supplier can reduce and/or increase the rate from the rate grids. Company configurations Statement of Work and Use Rate Grid for SOW Workers on Statement of Work must be enabled. This doesn't apply to Classic SOW Templates or SOWs created from Classic SOW Templates, which always have a value of 'Can Reduce'. If this field is blank, the value defaults to 'Can Reduce'. Classic SOW Templates and SOWs created from Classic SOW Templates always have a value of 'Can Reduce'. 'Can supplier edit the rate value when defining SOW Worker roles' is only visible when Rates 2.0 is enabled. If Rates 2.0 is enabled and this field is set to 'Yes' but 'Use Rates on SOW Workers' is set to 'No', the system automatically sets this field to 'No'. |
|
Allow Daily Verification |
Text |
3 |
No |
Valid values are:
|
Indicates if daily verification applies to SOW worker. 'Track Time Sheets' flag must be set to Yes on the SOW. Company configuration Enable SAP CATS Time Sheet cannot be set to Yes on the Statement of Work. If a value is not entered, this field defaults to No. |
|
Unit Of Measure |
Text |
4 |
Conditional Required if Use Rate Grid for Team Members on Statement of Work configuration is not enabled. |
Valid values are:
|
Download in the file format when the company configuration is turned off. If SOW has enabled Rate Schedules, the system ignores the contents of this column. Cannot be set by the buyer if Allow supplier to control SOW worker rules and create worker roles is enabled on the template. If Rates 2.0 is enabled, this field does not appear. |
|
Hours per Day |
Number |
Conditional Required if Team Member Payment Characteristic Is selected. |
Range: 0-24 |
The standard number of hours worked per day. Cannot be set by the buyer if Allow supplier to control SOW worker rules and create worker roles is enabled on the template. |
|
|
Hours per Week |
Number |
Conditional Required if Team Member Payment Characteristic Is selected. |
Range: 0-168 |
The standard number of hours worked per week. Cannot be set by the buyer if Allow supplier to control SOW worker rules and create worker roles is enabled on the template. |
|
|
Give Workers access to all Task Codes for the Cost Centers |
Text |
3 |
No |
Valid values are:
|
Used in case of payment characteristic type Team Member is selected for the SOW. If Rates 2.0 is enabled, and If 'Use Rates on SOW Workers' and 'Allow use of Fees with SOW Workers' are both set to "No", the system ignores the contents of this field. |
|
Give Workers Access to all Expense Codes for Cost Center |
Text |
3 |
No |
Valid values are:
|
When left blank, defaults to No. |
|
Allow Deductions to be Submitted on Time Sheet |
Text |
3 |
Yes |
Valid values are:
|
Determines whether the workers can submit deductions on their time sheets. It defaults to value from SOW Template if left blank and Company configuration ‘Deduction’ is enabled. It defaults to ‘No’ if company configuration Deduction is not enabled. Company configuration Deduction must be enabled. |
|
Allow Worker to Submit Time Sheets |
Text |
3 |
No |
Valid values are:
|
This is applicable only when 'Give Workers access to all Task Codes for the Cost Centers' is set to Yes. If left blank, the default value is be taken from the selected SOW Template. If Rates 2.0 is enabled, 'Use Rates on SOW Workers' and 'Give Workers access to all Task Codes for the Cost Centers' must both be set to "Yes" in order for this field to be set to "Yes". |
|
Allow invoicing from approved Time Sheets |
Text |
3 |
No |
Valid values are:
|
Used in case of payment characteristic type Team Member is selected for the SOW. Cannot be set by the buyer if Allow supplier to control SOW worker rules and create worker roles is enabled on the template. The following apply if Rates 2.0 is enabled: If this field is set to "Yes" but 'Use Rates on SOW Workers is set to "No", the system automatically sets this field to "No". If 'Use Rates on SOW Workers' is set to "Yes" AND 'Use Rate Schedule' is set to "Yes", this field is automatically set to "Yes". The 'Allow invoicing from approved Time Sheets' must be set to "Yes" when 'Use Rate Schedule' is enabled. |
|
Allow invoicing from approved Expense Sheets |
Text |
3 |
No |
Valid values are:
|
Cannot be set by the buyer if Allow supplier to control SOW worker rules and create worker roles is enabled on the template. If Rates 2.0 is enabled and this field is set to "Yes" but 'Use Rates on SOW Workers is set to "No", the system automatically sets this field to "No" regardless of whether the SOW uses rate schedules. If Rates 2.0 is enabled, and 'Use Rates on SOW Workers' and 'Use Rate Schedule' are both set to "Yes", the system will automatically set this field to "Yes". |
|
Issue warning if Hours per Day are exceeded on Time Sheet |
Text |
3 |
No |
Valid values are:
|
Used in case of payment characteristic type Team Member is selected for the SOW. Cannot be set by the buyer if Allow supplier to control SOW worker rules and create worker roles is enabled on the template. If Rates 2.0 is enabled and this field is set to "Yes", but 'Use Rates on SOW Workers is set to "No", the system automatically sets this field to "No". |
|
Allow Time in Hundredths of Hours on Time Sheet |
Text |
3 |
No |
Valid values are:
|
Allows the capture of time in/time out entries in hundredths of hour format. Cannot be set by the buyer if Allow supplier to control SOW worker rules and create worker roles is enabled on the template. If Rates 2.0 is enabled and this field is set to "Yes", but 'Use Rates on SOW Workers is set to "No", the system automatically sets this field to "No". |
|
Allow Per Diem |
Text |
3 |
No |
Valid values are:
|
Allow Per Diem to team members or not. Cannot be set by the buyer if Allow supplier to control SOW worker rules and create worker roles is enabled on the template. |
|
Estimated Expenses % |
Decimal |
No |
The estimated expense percentage of the total estimated cost for the work orders. If this field is left blank, it defaults to zero. |
||
|
Estimated Additional Spend % |
Decimal |
No |
This is used by SAP Fieldglass to calculate the total estimated cost for the work orders. If this field is left blank, it defaults to zero. |
||
|
Auto Invoice all Characteristics, Time Sheets and Expense Sheets |
Text |
3 |
No |
Valid values are:
|
Indicates if all characteristics, time sheets, and expense sheet should be auto invoiced. |
|
Enforce Date Duration of Master Statement of Work when creating Child Statement of Work |
Text |
3 |
No |
Valid values are:
|
Can specify during creation of CSOW from MSOW. The field 'Is Master Statement of Work?' must = Yes. |
|
For Fees and Roles, Child Statements of Work |
Text |
46 |
Conditional. 'Is Master Statement of Work?' must be set to 'Yes'. |
Valid values are:
|
Indicates how fees, roles, and Child Statements of Work (SOWs) are used from the Master SOW. If 'Is Master Statement of Work?' set to 'Yes' and no value is entered in this field, the upload fails with an error message. |
|
On Child Statements of Work, fee rate and worker rates |
Text |
44 |
Conditional. 'Is Master Statement of Work?' must be set to 'Yes'. |
Valid values are: Cannot be added or edited Can be added, but the value cannot be edited Cannot be added, but the value can be edited Can be added and edited |
Indicates for Child Statements of Work (SOWs) whether fee rates and worker rates can be added and/or edited. If 'Is Master Statement of Work?' is set to 'Yes' and 'Use a subset from Master Statement of Work' is selected for the 'For Fees and Roles, Child Statements of Work' field and no value is entered in this field, the upload fails with an error message. If field or value missing, and if 'Use all defined on Master Statement of Work' or 'Add new items and se a subset from Master Statement of Work' is selected for 'For Fees and Roles, Child Statements of Work', this field is optional. |
|
Must use all Fees Rates and Roles defined on Master Statement of Work |
Text |
3 |
No |
Valid values are:
|
Can specify during creation of CSOW from MSOW. If SOW has enabled Rate Schedules, the system ignores the contents of this column. Not applicable when uploading MSOWs. |
|
Can select a subset of Fees and Roles but not alter the Rates or Can select a subset of Fees and Roles and alter the rate value or Can select a subset of Fees and Roles alter the Rates and add new Fees and Roles or Can select a subset of Fees and Roles, and alter the Rates, but cannot add new Fees and Roles |
Text |
3 |
Conditional. Required if Allow Multiple Currency and Use lookup for Rates are set to Yes. |
Valid values are:
|
These options are the possible answers of the question in the UI: Child Statements of Work created from this Master Statement of Work: Only one of these options should have value of "Yes". The others can be blank or "No". If SOW has enabled Rate Schedules, the system ignores the contents of this column. Option 'Can select a subset of Fees and Roles but not alter the Rates' can add new rates, just cannot alter existing rates. Option: 'Can select a subset of Fees and Roles, and alter the Rates, but cannot add new Fees and Roles', must be MSOW Template ID, and 'Use Rate Schedule' or 'Allow Multiple Currency' flags must = No. Not applicable when uploading MSOWs. |
|
Must use all Fees and Role/Rate Schedule combinations defined on Master SOW |
Text |
3 |
Conditional |
Valid values are:
|
Indicates if one of MSOW options for Rate Schedules is selected. Company configuration Enable Rate Schedules must be enabled. Value cannot match other MSOW option for Rate Schedules, else error. If the SOW Template is not an MSOW Template, or the buyer is using an MSOW as the source, the system ignores the contents of this column. Not applicable when uploading MSOWs. |
|
Can use subset of Fees and Role/Rate Schedule combinations from Master SOW, add new Fees and combinations, and edit Rate Schedule Rates |
Text |
3 |
Conditional |
Valid values are:
|
Indicates if one of MSOW options for Rate Schedules is selected. Company configuration Enable Rate Schedules must be enabled. Value can't match other MSOW option for Rate Schedules. If the SOW Template is not an MSOW Template, or the buyer is using an MSOW as the source, the system ignores the contents of this column. |
|
Allow use of Fees with SOW Workers |
Text |
3 |
No |
Valid values are:
|
Can specify during the creation of MSOW. But while creating a SOW or CSOW, the value for this field is taken from the template in case of SOW – and master SOW in case of CSOW irrespective of values (yes/no/blank) entered. Cannot be set by the buyer if Allow supplier to control SOW worker rules and create worker roles is enabled on the template. |
|
Allow Supplier to select Approver for Events, Fee Responses, and Schedules |
Text |
3 |
No |
Valid values are:
|
Indicates supplier can select approver for line items and fee responses. |
|
Supplier must submit Resume/CV |
Text |
3 |
No |
Valid values are:
|
When submitting SOW workers, oftentimes the supplier would like to include an attachment such as a résumé, so the buyer can review prior to accepting a worker. This field supports a single attachment, and the buyer can make this field mandatory via the new Supplier Must Submit Resume/CV rule on the SOW/RFX template. In addition, a new general Attachments section is now available to suppliers when adding an SOW worker. This section supports multiple attachments. |
|
Prevent Supplier from Responding to Schedules Prior to the Due Date |
Text |
3 |
No |
Valid values are:
|
This rule prevents the supplier from marking a schedule complete prior to the due date. If left blank, this field defaults to No. |
|
Maximum Schedule Budget Entered By User Type |
Text |
8 |
No |
Valid values:
|
Indicates who can enter the maximum schedule budget. |
|
Maximum Schedule Budget |
Decimal |
No |
Maximum budget set for Schedule If it is left blank, the value defaults to zero. |
||
|
Maximum Event Budget Entered By User Type |
Text |
8 |
No |
Valid values:
|
Indicates who can enter the maximum event budget. |
|
Maximum Event Budget |
Decimal |
No |
Maximum budget set for event. If it is left blank, the value defaults to zero. |
||
|
Maximum Fee Budget Entered By User Type |
Text |
8 |
No |
Valid values:
|
Indicates who can enter the maximum fee budget. |
|
Maximum Fee Budget |
Decimal |
No |
Maximum budget set for fee. If it is left blank, the value defaults to zero. |
||
|
Maximum Worker Budget |
Decimal |
No |
Maximum budget set for worker. If it is left blank, the value defaults to zero. |
||
|
Event Lookup Name |
Text |
100 |
Optional |
Use Hierarchical Events must be set to Yes under Characteristics Rules on SOW Template. Lookup type should be Event Hierarchy. Blank values are accepted. If the statement of work uses a contract, the contract's lookup will automatically override the entry in the file. Also supported when 'Is SOW Bid?' = Yes. |
|
|
Is SOW Bid? |
Text |
3 |
Conditional |
Valid values are:
|
Indicates if record is for SOW Bid. If this field is left blank, it defaults to No. |
|
SOW Bid Respond By Date |
Date |
Conditional |
SOW bid respond-by date. This field is only required when the Enforce Bid Respond By Date = Yes on the SOW Template. Please note that this field was previously called Bid Respond by Time and before that Bid Response Due Time. |
||
|
SOW Bid Respond By Time |
Time |
No |
SOW bid respond-by time. Please note that this field was previously called Bid Respond by Time and before that Bid Response Due Time. |
||
|
Bid Evaluators Usernames |
Text |
100 |
Conditional |
Valid SAP Fieldglass username(s). |
Indicates username(s) for SOW Bid evaluator(s). Multiple usernames can be separated with tilde (~). Only applicable if 'Is SOW Bid?' = Yes If the 'Enhanced Legal Entity Validation' configuration is enabled for the company, the system validates if the bid evaluator has visibility to the SOW legal entity, business unit, cost center, and site codes. If even one of these is not associated to the user, the system displays an error message. |
|
SOW Coordinators |
Text |
504 |
No |
A valid username in 'Open' status in the buyer company. Examples:
|
This field is used to identify the SOW Coordinators. If the 'Is SOW Bid?' field is set to 'Yes', this field can also be used to enter in the SOW Coordinators for an SOW bid. Multiple SOW Coordinators can be separated by a tilde (~). If any of the users don't have access to the SOW document's foundational data, the system displays an error message. |
|
Additional Legal Entities |
Text |
100 |
No |
Valid legal entity codes for buyer |
Legal entities for Master SOW separated by (|). Company configuration Master SOW and Allow Multiple Suppliers must be enabled. |
|
Additional Currency |
Text |
100 |
No |
Valid currency codes for buyer |
Currency codes for Master SOW separated by (|). Company configuration Master SOW and Allow Multiple Suppliers must be enabled. |
|
Rate Lookup |
Text |
100 |
Conditional |
Valid rate lookup name as defined in the company |
Name of rate lookup for Master SOW. Company configuration Master SOW and Allow Multiple Suppliers must be enabled. If Rates 2.0 is enabled, this field does not appear. |
|
Allow rates for SOW Worker Roles without invoicing |
Text |
3 |
Conditional |
Valid values are:
|
Indicates if rates for non-billable SOW workers can be entered. Company configuration Use Rate Grid for SOW Workers on Statement of Work must be enabled. The rule Allow Invoicing from Approved Time Sheets must be set to No. The rule 'Use Rate Schedule' must be set to No. If 'Use Rate Grid for SOW Workers' is not enabled, this field defaults to No. If this field is not entered in the upload file, it defaults to the SOW Template value. If Rates 2.0 is enabled, this field does not appear. |
|
Can Select a Subset of Fees and Role/Rate Schedule combinations, but cannot alter rates |
Text |
3 |
No |
Valid values are:
|
Indicates worker role restriction when using rate schedules. If the value for this column is Yes but the Template ID is not a MSOW Template ID, the value in this column is ignored. If the value for this column is Yes, the Template ID is a MSOW Template ID, but rule 'Use Rate Schedule' is set to No, the value in the new column is ignored since the new flag only applies to Rate schedule MSOWs. If the Template ID is an MSOW Template and 'Use Rate Schedule' flag is set to Yes for the template, then only one of the three below columns must have Yes. If not, upload fails for the record.
|
|
Supplier Chat Respond By Date |
Date |
Conditional |
Chat cut-off date for an SOW bid. This field is applicable if SOW Type flag Use to create SOW Bid? is set to Yes and not hidden on custom SOW Types. |
||
|
Supplier Chat Respond By Date Time |
Time |
Conditional |
Chat cut-off time for an SOW bid. This field is applicable if SOW Type flag Use to create SOW Bid? is set to Yes and not hidden on custom SOW Types. |
||
|
Submit |
Text |
3 |
No, this field must be manually added if needed. |
Valid values are:
|
Defines whether the SOW is submitted after creation. When set to YES, the upload submits the SOW after creation. Upon running this upload, this value results in an integration error if the SOW requires additional data that is not supported through this upload. When set to NO, the upload drafts the SOW. By default, this value is set to NO. |
|
[c] Custom Field1 |
Dependent on custom field type. |
Dependent on custom field type. |
Dependent upon custom field type |
Any custom field associated with the SOW. The custom field name should be prefixed with ‘[c]’. 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. If statement of work uses a contract, the values will default from the contract when the field is left blank. |
|
|
[rc] Rate Category/Rate UOM |
Text |
100 |
Conditional Enter only if Team Member Payment Characteristics is selected. |
Valid SAP Fieldglass Rate Code. |
At least one rate need to be entered. If left blank it is considered as not selected. If SOW has enabled Rate Schedules, the system ignores the contents of this column. Company configuration Use Rate Grid for SOW Workers on Statement of Work must be set to No. Cannot be set by the buyer if Allow supplier to control SOW worker rules and create worker roles is enabled on the template. If Rates 2.0 is enabled, this field does not appear. |
|
[Committed Spend Flag] Rate Category/Rate UOM |
Text |
3 |
No |
Valid values are:
|
Sets Use in committed spend calculation flag value on the newly added rates. If SOW has enabled Rate Schedules, the system ignores the contents of this column. Cannot be set by the buyer if Allow supplier to control SOW worker rules and create worker roles is enabled on the template. If Rates 2.0 is enabled, this field does not appear. |
|
[cc-v] cost center1 | segmented object detail 1 |
Text |
200 |
Conditional |
Examples: [cc-v] cc1 | sod1 [5~5~1 |1/2018] |
Indicates multiple cost centers with multiple segmented object details. Indicates Segmented Object Detail (SOD) value. Column Value should always be in brackets. Company configuration Segmented object detail with sub configuration Services cost centers must be enabled. |
|
[cc-p] cost center1 | segmented object detail 1 |
Text |
200 |
Conditional |
Examples: [cc-p] cc1/sod1 [50] |
Indicates multiple cost centers with multiple segmented object details. Value holds percentages for the combination. Column Value should always be in brackets. Company configurations Segmented object detail with sub configurations Apply to Cost Center for Services and Segmented object detail based allocation is required must be enabled. |
Unique Identifier
-
External SOW ID field
Assumptions/Tips
-
This is buyer-side upload.
-
After SOW Shell Upload, the SOW is in 'Draft' status for Defined by 'Buyer' and in 'Pending Buyer Review' status for Defined by 'Supplier' or 'Both'.
-
SOW Shell upload does not upload the SOW characteristics. Characteristics are uploaded through separate uploads.
-
Clauses are not supported by SOW Shell Upload.
-
Only one cost center (Primary Cost Center) can be associated to the SOW by SOW shell upload.
-
Multiple GLA are not supported as of now. If GLA is turned on for the company, the GL Account code column appears in the download file format.
-
Role/Site/UOM combination does not get uploaded through the SOW Shell Upload; it is a separate upload.
-
Creation of SOW from project is not supported in SOW Shell Upload.
-
The factor value of the Factor type of rate selected is defaulted from the admin. and cannot be changed using upload.
-
Field values are copied from the source selected if not entered in the file.
-
Cost center code, GL Account Code, and Task Code are not copied from the Master SOW selected.
-
Amounts are automatically rounded to a whole number but displayed to two decimal points if the currency is Yen.
-
Both Buyer- and Supplier-entered Custom Fields display and can be updated by both parties regardless of who created the Custom Field first.
-
When Legal Entity is enabled for Services, AND Legal Entity is validated on Site, then the Legal Entity propagated Site overrides the 'Prevent Propagation from SOW to Existing Work Order and Workers based on Site & Location' rule.
-
When a statement of work uses a contract, certain fields such as Template ID will be validated to confirm they are appropriate to use with a contract
-
If editing MSOW:
-
For the 'Prevent: all MSOW Budgets' setting of the SOW Template rule, the following fields are optional, and if left blank, there is no change to the existing value on the MSOW:
-
Maximum Schedule Budget
-
Maximum Event Budget
-
Maximum Fee Budget
-
Maximum Worker Budget
-
-
For the Prevent: Maximum Budget only and the No Restriction settings of the SOW Template rule, the system ignores the above budget fields if a value is entered because the fields do not apply in these scenarios.
-
-
If editing CSOW, the system ignores the following fields because these budgets are not collected on CSOWs:
-
Maximum Schedule Budget
-
Maximum Event Budget
-
Maximum Fee Budget
-
Maximum Worker Budget
-
-
For user entered amounts, a validation has to happen on the upload to ensure the value entered is a whole number for those currencies requiring the precision to be zero decimals.
-
If the custom field is configured for SOW Bid Only, an error occurs since this upload supports normal SOW custom fields only.
-
When creating a CSOW via upload, allow the CSOW to be associated to an existing MSOW by either the MSOW’s SAP Fieldglass SOW ID or via the MSOW’s external ID. Field 'PO Number' must also be manually added to upload file for this situation. It sets the PO number field on the SOW.
-
The fields 'Disallow approval of items when maximum budget is exceeded' and 'Disallow approval of items when maximum budget exceeded for cost center' and 'Disallow approval of items when Maximum budget exceeded for Segmented Objected Detail' are mutually exclusive.
-
Regarding the SOW Coordinator field:
If the buyer has an 'SOW Coordinators' custom lookup defined: The custom lookup triggers upon SOW document creation. If the user enters in a username in the 'SOW Coordinators' column, the application adds the SOW Coordinators as per the configured custom lookup and add the user(s) entered in the 'SOW Coordinators' column as SOW Coordinators for the SOW.
If the buyer does not have an 'SOW Coordinators' custom lookup defined: The username entered for the SOW Coordinator field applies to the SOW only. If the 'SOW Coordinators' column is left blank, there is no impact to the SOW. If multiple SOW Coordinators are to be entered via the upload, their usernames need to be delimited by tilde (~) symbol. If multiple SOW Coordinators are entered on the upload and if any of the usernames are invalid or the user doesn't have access to the SOW document, the entire record fails.
-
If the CSOW is using a different currency than the MSOW, then the CSOW budgets are converted into the MSOW's currency to perform validations. Conversion factor is captured when the CSOW is initiated and remains the same through the life cycle of CSOW. It is used for converting any amount field on the CSOW to perform validation against the MSOW budgets.
-
SOW IDs enabled with the 'Disallow Supplier to add SOW Workers until SOW is completely Approved' rule can be uploaded using this connector.
-
When a CSOW is created from a MSOW, the values for the Event Hierarchy Code field and Event Lookup Name field default from the MSOW, but can optionally be changed.
-
This upload cannot be used for an SOW template that uses a Fieldglass Talent Network (FTN) SOW Type.
-
When a SOW is created with this upload, it inherits the 'Automatically Update SOW Owner Name on Existing SOW Line Items after SOW Revision or Edit' rule value from the associated SOW Template.
-
If Creation Type = Integration, this upload cannot be used.
-
SOD grid type custom fields are not supported.
-
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.
-
When the buyer uploads an SOW or SOW bid, the Event Lookup Name will be validated in the following scenarios:
When the event does NOT use a contract-
If "Use Product Group on Hierarchical Events" rule is set to Required on the SOW's Template, the "Event Lookup Name" field will only accept an Event Hierarchy lookup that contains Product Group as a Key.
-
Otherwise, the system will return this error: The 'Use Product Group on Hierarchical Events' rule is set to Required, but the selected Event Lookup Name does not use Product Group as a Key. Select a new lookup or remove the lookup.
When the SOW DOES use a contract-
If "Use Product Group on Hierarchical Events" rule is set to Required on the SOW's Template, the system will confirm that the Contract's Event Hierarchy Lookup contains Product Group as a Key.
-
If lookup does contain Product Group, then no error; the uploaded SOW will use the Contract's EH lookup.
-
If lookup does NOT contain Product Group, then system will return this error: The 'Use Product Group on Hierarchical Events' rule is set to Required, but the Event Hierarchy lookup on the Contract does not use Product Group as a Key. Select a different SOW Template.
-
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). |