Guides
SAP Business One purchase to pay and order to cash: see where each order waits
Connect SAP Business One to Duaer. It reads the steps of each purchase or sales order through the Service Layer.
What does Duaer read from SAP Business One?
Each purchase or sales order is a case, with the business partner, the company database, currency and amount. The steps are:
- Purchase to pay: Order created (purchase order), Goods received (goods receipt PO), Invoice posted (A/P invoice), Paid (outgoing payment).
- Order to cash: Order created (sales order), Goods issued (delivery), Invoice created (A/R invoice), Paid (incoming payment).
- Documents are followed back to the order through their base documents: an invoice based on a goods receipt counts for the original purchase order. Canceled documents are left out.
How do you connect SAP Business One to Duaer?
- Check that the Service Layer is running and note its address (usually https://server:50000).
- Prepare a user who can view purchasing and sales documents.
- If the Service Layer is only inside your network, or has an http:// address only, start the Duaer on-premises data gateway there first.
- In Duaer, create an SAP Business One Service Layer credential with the Service Layer address, the company database, the user and the password.
- As an owner or admin, open Data sources, select Add source, choose SAP Business One under Purchase to pay or Order to cash, choose the credential, select Check connection and confirm.
How often does it read, and how much?
Each run reads orders, receipts or deliveries, invoices and payments by update date, one page each at most. Update dates carry no time, so each read starts at the beginning of the day again; a step is never written twice. Read only.
What are the limits?
- The tables, entities 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.
- Approval procedures and draft documents are not read.
Questions
Does it work on both SQL Server and HANA?
Yes. Duaer reads through the Service Layer only, never the database itself.
In this section
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.
ProcessSee 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.
ProcessProcess 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-throughSAP 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-throughOdoo purchase to pay and order to cash: see where each order waits
Connect Odoo to Duaer. It reads the steps of each purchase or sales order over JSON-RPC, so you see where orders wait and for how long.