SAP Fieldglass Standalone SOW with SAP Ariba Contracts Standalone Agreement

Describes the process of creating stand-alone contract from an SAP Fieldglass SOW request.

In this case, the contract originates with SAP Fieldglass and ends with a confirmation that the contract is published in SAP Ariba Contracts. This workflow represents the differences from the Services Procurement with SAP Ariba Services POs workflow.

The following graphic illustrates the integration workflow.

  1. Create stand-alone SOW request in SAP Fieldglass.

    1. Create a stand-alone SOW with buyer user.

    2. The buyer user/users review and approve the stand-alone SOW until it gets to the last level of approval.

    3. Standalone SOW sent to supplier for approval/acceptance.

    4. Standalone SOW is approved and created.

  2. Stand-alone contract created in SAP Ariba Contracts and Publish Job triggered.

  3. Confirm that contract is published.

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

  5. Creation of an SOW Revision follows the same process, creating an amendment in SAP Ariba Contracts. However, Amendment fields such as <Company Code > and <Purchase Org> won't be updated on the ACC contract, even if they were changed in the SOW Revision.