MuleSoft Accelerator for SAP icon

MuleSoft Accelerator for SAP

1.6.x
(6 reviews)

Use case 2 - Procure-to-pay

Procure-to-pay is a fully integrated solution designed to support an end-to-end process for procurement, invoicing, and payment management. This use case relies on Coupa as the expense management system and SAP S/4HANA as the ERP system.

Overview

Before you begin

bulb.png The Getting Started with MuleSoft Accelerators guide provides general information on getting started with the accelerator components. This includes instructions on setting up your local workstation for configuring and deploying the applications.

High-level architecture

sap-p2p-high-level-architecture.png

The procure-to-pay flow proceeds through the following steps:

SAP is the source of truth for all data related to Suppliers and Chart of Accounts. Supplier data can be bulk loaded from SAP to Coupa using the APIs in the accelerator. The assumption for the flow below is that the Supplier and Chart of Accounts data has been synced from SAP to Coupa. Please note that bulk load for Chart of Accounts will be added in a future release.

  1. A Purchase Request is created in Coupa. After the Purchase Request is created, it goes through an approval process in Coupa and is converted to a Purchase Order.
  2. The Purchase Order is automatically populated in SAP.
  3. Once the goods associated with the Purchase Order are received, a Goods Receipt is created in Coupa, which is also sent to SAP.
  4. When the goods are received, the Supplier will send an invoice that gets populated in Coupa against the Purchase Order.
  5. The Invoice proceeds through an approval process and once approved for payment, it is sent to SAP.
  6. The Invoice payment is initiated from SAP and once it is paid, it needs to be reflected in Coupa. Eventually, the payment is received by the supplier, which concludes the full process.
sap-p2p-workflow-diagram.png

Systems involved

  • Coupa
  • SAP S/4HANA

Activity diagram

sap-p2p-activity-diagram.png

Setup instructions

SAP S/4HANA

SAP S/4HANA should have the following APIs enabled with read and write access for the corresponding objects:

S/4HANA APIDescriptionREST API ResourceBusiness Context
API_BUSINESS_PARTNEREnables operations on SuppliersSuppliersBusiness Documentation
API_SUPPLIERINVOICE_PROCESS_SRVEnables operations on InvoicesInvoicesBusiness Documentation
API_OPLACCTGDOCITEMCUBE_SRVEnables operations on Invoice PaymentsInvoice PaymentsBusiness Documentation
API_PURCHASEORDER_PROCESS_SRVEnables operations on Purchase OrdersPurchase OrdersBusiness Documentation
API_MATERIAL_DOCUMENT_SRVEnables operations on Goods ReceiptsGoods ReceiptsBusiness Documentation
API_PRODUCT_SRVEnables operations on ProductsProductBusiness Documentation

Coupa

Coupa should have an API key enabled for use via Mule. This API key should have read and write access for the corresponding objects:

  • Suppliers
  • Inventory-transactions
  • Purchase-orders
  • Invoices

Mule Projects

Use the README instructions in the following Mule templates to set up, deploy, and run these projects.

Note: Deploy the object-specific system API along with the process API to start the data sync. The process API properties need to be correctly set up to point to the system APIs.

Downloadable assets

Accelerator Coupa System APIs

Accelerator SAP S/4HANA System APIs

Accelerator Process APIs

Reviews