Business Requirements and Assumptions

The following considerations apply to importing SAP Ariba Contracts into SAP Fieldglass:

• SAP Ariba APIs enhance the integration between SAP Fieldglass and SAP Ariba Contracts. The APIs make the integration process more efficient and allow a greater flow of information between the two applications.

• SAP Fieldglass uses the new APIs to pull and search SAP Ariba for new or revised contracts. If found, subsequent calls retrieve the contract data, terms, line items, and documentation used to create or revise an MSOW or SOW in SAP Fieldglass.

• The APIs streamline the process, only sending SAP Fieldglass-specifc contract information, eliminating the need for SAP Fieldglass to find the relevant contracts for its system. They also enable better communication between the systems, keeping contracts and MSOWs or SOWs in sync.

• The SAP Ariba contract must have a CLID file in the contract for the integration to import the contract lines necessary to create the SOW in the SAP Fieldglass application.

• Master Agreements exist in SAP Ariba Contract Management.

  • Collaborative efforts needing SAP Fieldglass support are exported to SAP Fieldglass.

• Release (Planned) and No Release (Unplanned) contracts are both supported.

  • CID only distributed when released contract is available.

• All upstream contracts are supplier level.

• Single-Line Services only are supported. Hierarchical services aren't supported.