Exploring the SOW Bid Workflow

After completing this lesson, you will be able to:

After completing this lesson, you will be able to:

  • Explain why an organization would create an SOW Bid.
  • Describe the SOW Bid workflow and its use within the services process.


In a standard SOW project in SAP Fieldglass, the organization needing work completed knows which service provider they want to engage. What happens, though, when a buyer like WorkingNet has the need to procure services but doesn’t know which supplier will best fit their needs? They can create an SOW Bid.

SOW Bids are part of the optional source phase of the services process flow.

Using the SOW Bid functionality, buyers can bid out work to multiple suppliers. SOW Bids outline the scope of the work requested, very similar to an SOW, and multiple suppliers can review, collaborate, and respond to the SOW Bid all within the SAP Fieldglass application.

Buyers like WorkingNet can use the SOW Bid functionality if they want send a project to existing suppliers in SAP Fieldglass without going through a formal sourcing exercise, and see the details of how each supplier would approach the details of the project as well as their estimated costs.

It’s important to note that the SOW Bid itself is non-transactional; invoices do not flow through a bid and characteristics are not marked as complete. However, transactional SOWs can be created from the SOW Bid once an organization awards a supplier the work.

Log in to track your progress & complete quizzes