Duaer

Guides

SAP ECC purchase to pay and order to cash: see where each order waits

Connect SAP ECC to Duaer. It reads purchasing and sales documents by calling RFC_READ_TABLE over SOAP and shows the steps of each order; a system inside your network is read through the on-premises data gateway.

What does Duaer read from SAP ECC?

Each purchase order (EKKO) or sales order (VBAK) is a case, with the vendor (LFA1) or customer (KNA1), the company code or sales organization, currency and net value. The steps are:

  • Purchase to pay: requisitions (EBAN), Order created (EKKO), goods receipts and invoices (PO history EKBE; reversed receipts are left out), Paid (clearing date in BSAK).
  • Order to cash: Order created (VBAK), Delivery created and Goods issued (LIKP creation and actual goods issue dates), Invoice created (VBRK; canceled billing is left out), Paid (clearing date in BSAD).
  • Deleted purchase orders are left out. The steps match the process templates.

How do you connect SAP ECC to Duaer?

  1. Activate the /sap/bc/soap/rfc service in SICF.
  2. Prepare a user allowed to call RFC_READ_TABLE (authorization object S_RFC) and read the tables above (S_TABU_DIS or S_TABU_NAM).
  3. If the system is only inside your network, start the Duaer on-premises data gateway there first and list the system's address among its targets.
  4. In Duaer, create an SAP ECC (RFC over SOAP) credential with the system address and port, the client (for example 100), the user and the password.
  5. As an owner or admin, open Data sources, select Add source, choose SAP ECC and the process, choose the credential, select Check connection and confirm.

How often does it read, and how much?

Each run reads a few tables by date window (purchasing: orders, order history, clearing; sales: orders, deliveries, billing, clearing), one page each at most. After each window the next starts two weeks back, to catch documents posted with a past date. A step is never written twice. Only RFC_READ_TABLE is called; read only.

What are the limits?

  • The resources, entities and tables read follow the vendor's published documentation and are not yet checked against a real system; the first real read may need adjustments.
  • RFC_READ_TABLE returns at most 512 characters a row; Duaer reads only the fields it needs.
  • Change documents (CDHDR/CDPOS) and release steps are not read.

Questions

Is this for S/4HANA too?

No. S/4HANA has its own SAP S/4HANA source, which reads the standard OData APIs.

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

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.

Follow-through

NetSuite purchase to pay and order to cash: see where each order waits

Connect NetSuite to Duaer. It reads the documents each purchase order and sales order goes through with SuiteQL, so you see where orders wait and for how long.