Services Procurement with SAP Ariba Services POs

Describes the end-to-end flow of information between SAP Fieldglass, SAP Ariba, SAP Business Network, and Ariba Cloud Integration Gateway (CIG) for SAP Ariba Services Purchase Order (PO) integration.

This integration supports Service Procurement Orders between SAP Fieldglass and SAP Ariba. As part of this feature, when a Statement of Work (SOW) or Work Order (WO) is created in SAP Fieldglass, a service requisition is created in SAP Ariba Buying. This in turn creates a service PO for invoicing through SAP Integration Suite, the managed gateway for spend management and SAP Business Network.

After the Service Entry Sheet (SES) is submitted in SAP Fieldglass, the service requisition is posted to SAP Business Network and SAP Ariba Buying and Invoicing. An invoice gets created in SAP Business Network from the SES record and reconciled in SAP Ariba Buying and Invoicing. The corresponding statuses are sent to SAP Fieldglass via SAP Integration Suite, the managed gateway for spend management and SAP Business Network.

The following graphic illustrates the integration workflow.

  1. Create/Revise SOW/WO. When a SOW/WO is closed (or re-opened) in SAP Fieldglass, a PO close CIG message is sent to SAP Ariba. The PO is updated to closed (or re-opened) in SAP Ariba.

    1. Create an SOW/WO with buyer user.

    2. The buyer user/users approve the SOW/WO until it gets to the last level of approval.

    3. SOW/WO is locked because of the punchout account and it's pushed to CIG with the event driven config described below.

  2. PR is created in SAP Ariba and SAP Ariba/CIG sends back the PR number and status information on the following upload:

    1. Ariba PR Response Upload connector.

    2. The SOW/WO is still locked in SAP Fieldglass until the PO information is received.

  3. PO is created in SAP Ariba and the PO information is sent back to SAP Fieldglass via CIG.

    1. Ariba P2P Requisition XML Upload connector.

    2. The PO number in the SOW/WO is updated and approved. The SOW/WO is now in 'Approved' status in SAP Fieldglass.

  4. Supplier Submits SES (Fee, Event, Schedule).

    1. SES is approved and sent to SAP Business Network on the last level of approval.

    2. The Service Confirmation SES payload includes the taxes and discounts that appear on the corresponding invoice. This applies to all SES items.

      1. Taxes appear at both the line level and the summary level of the SES payload.

      2. Discounts appear at the line level.

      3. A Tax Group level greater than 1 isn't supported

      For more information on configuring taxes in SAP Fieldglass, refer to Tax Guidance

  5. Once the SES is created and approved in SAP Ariba, SAP Fieldglass receives back from SAP Business Network confirmation the SES was approved through 'Service Entry Sheet Status Upload' connector.

    1. It also approves the SES and auto-generates an invoice in SAP Fieldglass in 'Approved' status.

  6. Once the invoice is created and approved in SAP Business Network, SAP Fieldglass receives back a confirmation through the 'Ariba Network Invoice Upload' connector to update the custom fields.

  7. SAP Ariba then sends invoice status updates (using the 'Ariba Status XML Upload' connector) through the entire process until it's paid. SAP Ariba sets the invoice status from 'Payment Pending', 'Paid', and 'Rejected'.