SOW with Bid Download
This integration downloads SOW and SOW bid information.
Triggering Events
|
Activity |
User |
SOW Status |
|---|---|---|
|
Buyer submits SOW/Bid for approval |
Buyer |
Pending Approval |
|
Buyer rejects the SOW/Bid |
Buyer |
Rejected. |
|
SOW/Bid approved by Buyer |
Buyer |
Pending Response |
|
Suppliers accepts SOW/Bid |
Supplier |
Response Pending Approval |
|
Suppliers declines SOW/Bid |
Supplier |
Declined |
|
Buyer Approves the SOW/Bid |
Buyer |
Approved |
|
SOW/Bid is edited |
Buyer |
Approved |
|
SOW/Bid is edited |
Supplier |
Approved |
|
SOW Revision created |
Buyer |
Pending Supplier Review |
|
Supplier Reviews/Submits SOWR |
Supplier |
Pending Buyer Review |
|
Buyer submits SOWR for approval |
Buyer |
Pending Approval |
|
SOWR approved by Buyer |
Buyer |
Pending Response |
|
Supplier accepts SOWR |
Supplier |
Response Pending Approval |
|
Buyer Approves the SOWR |
Buyer |
Approved |
|
SOW/Bid is closed |
Buyer |
Closed |
File Formatting
Assumptions/Tips
-
If the buyer company has multiple MSPs, when the MSP supplier user downloads records, they will see only records for their MSP.
-
The system includes any inactive cost centers associated with the document.
General Conventions
SOW and SOW Bid information will appear in the download if a triggering event has occurred since the last time the download was run. The Last Run Date is stored in SAP Fieldglass each time the connector is successfully run. Therefore, the download will pull any records that have changed since Last Run Date. In the event that previous data is required again, you can contact your SAP Fieldglass representative and they can update this date to the date you request.
This is a multi-line download, if a SOW/Bid is associated with more than one cost center, SOW/Bid information is downloaded in more than one record.
Custom Fields
-
Cost Center
-
Business Unit
-
Site
-
Statement of Work
-
SOW Response
-
SOW Revision
-
SOW Bid
The client can specify the custom fields they wish to include in the file and the order in which they want to see in the file.
At the time the connector is activated for the client, the client will be required to supply a list of the custom fields and their order. This list will be stored in SAP Fieldglass against the setup of the connector. If no custom fields are supplied, the download will not include any custom field values.
Custom fields that are included will always appear at the end of the column layout after all of the native, either default or optional, SAP Fieldglass fields have been output.