SAP Ariba Master Agreement with SAP Fieldglass Contract and SOW

Describes the process of creating SAP Fieldglass Contract and SOWs from an SAP Ariba Master Agreement.

This workflow begins with creating a Master Agreement in SAP Ariba Contracts and ends with updating the Master Agreement with the SAP Fieldglass statement of work (SOW) ID. This workflow represents the differences from the Services Procurement with SAP Ariba Services POs workflow.

The following graphic illustrates the integration workflow.

  1. A master agreement is created in SAP Ariba Contracts.

  2. SAP Fieldglass polls SAP Ariba for new or changed contracts using Ariba Contracts API.

  3. An SAP Fieldglass Contract is created in SAP Fieldglass. If there's a rate, a CLI rate data set is also created in SAP Fieldglass from the CLID.

    1. The SAP Ariba Contracts master agreement is updated with SAP Fieldglass SAP Fieldglass Contract ID using the Ariba Contracts API.

    2. An SAP Fieldglass Deep Link to the SAP Fieldglass contract is created in the SAP Ariba MSOW, allowing users to access SAP Fieldglass using single sign-on.

  4. A user creates a SOW request in SAP Fieldglass.

    1. The SAP Ariba Contracts master agreement is updated with the SAP Fieldglass CSOW ID using the Ariba Contracts API.

    2. An SAP Fieldglass Deep Link to the SOW is created in the SAP Ariba MSOW, allowing users to access SAP Fieldglass using single sign-on.

  5. The buyer user/users review and approve the SAP Fieldglass Contract until it gets to the last level of approval.

  6. The SAP Fieldglass Contract is sent to a supplier for approval/acceptance.

  7. The SAP Fieldglass Contract is approved and created.

  8. Finish the Services Procurement with SAP Ariba Services POs process.