Duaer

Guides

SAP Ariba purchase to pay: see where each order waits

Connect SAP Ariba to Duaer. It reads the steps of each purchase order, from requisition to payment, through the Operational Reporting API.

What does Duaer read from SAP Ariba?

Each purchase order is a case, with the supplier, company code, currency and amount. The steps are Requisition created, Order created, Goods received, Invoice posted (invoice reconciliation) and Paid. Canceled or rejected documents are left out. The steps match the purchase to pay template.

How do you connect SAP Ariba to Duaer?

  1. In the SAP Ariba developer portal, create an application, request access to the Operational Reporting API for Procurement (synchronous), and get the application key and the OAuth client ID and secret.
  2. In Duaer, create an SAP Ariba API credential with the realm, the API host, the OAuth host, the application key, the client ID and the client secret.
  3. As an owner or admin, open Data sources, select Add source, choose SAP Ariba under Purchase to pay, choose the credential, select Check connection and confirm.

How often does it read, and how much?

Duaer creates its own reporting views in the realm (named starting with Duaer) and reads requisitions, orders, receipts, invoice reconciliations and payments 31 days at a time; a first read starts two years back and finishes over several runs. Each run makes at most 130 API calls, to stay within Ariba's rate limits. A step is never written twice. Read only.

What are the limits?

  • The tables, views, models and fields read follow the vendor's published documentation and are not yet checked against a real system; the first real read may need adjustments.
  • Purchase to pay only, and documents of the last two years only.

Questions

Does Duaer change documents in Ariba?

No. Duaer only creates its own reporting views and reads them.

In this section

Process

Add a process source in Duaer

A process source tells Duaer where to read the steps of your cases: a CSV or XLSX file, files dropped in an S3 or SharePoint folder, PostgreSQL, MySQL, Microsoft SQL, Oracle, TiDB, OceanBase, KingbaseES, SAP HANA, IBM Db2, Dameng DM8, Teradata, Vertica, Snowflake, BigQuery, Databricks, Microsoft Fabric, Amazon Redshift, Azure Synapse Analytics, ClickHouse, Trino, a Feishu Base, or Feishu, DingTalk or WeCom approvals. The wizard takes you through columns, mapping, a preview of issues and a schedule; after you confirm, Duaer reads new rows on that schedule.

Process

See the process in your data and generate workflows in Duaer

Duaer reads the steps every case went through from the tables, databases or Feishu apps you already have: where cases wait too long, where they branch and who did each step. From that it generates three kinds of workflow, Watch, Coordinate and Execute, and replays each over past days before you publish it.

Process

Process findings and SOP conformance in Duaer

Process findings list the steps where cases wait too long or are done again, and which kind of case they happen to most. Propose any of them as a card rule and compare the 30 days before and after it was adopted. SOP conformance compares the SOP in your knowledge base with the steps cases really took.

Follow-through

Coupa purchase to pay: see where each purchase order waits

Connect Coupa to Duaer. It reads the requisitions, receipts, invoices and payments of each purchase order through the Coupa Core API, so you see where orders wait and for how long.

Follow-through

SAP S/4HANA purchase to pay: see where each order waits

Connect SAP S/4HANA, Cloud or on-premise, to Duaer. It reads each purchase order's steps from requisition to payment through SAP's standard OData APIs, so you see where orders wait and for how long.