> For the complete documentation index, see [llms.txt](https://doc.duaer.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.duaer.com/guides/sap-ecc-purchase-to-pay-order-to-cash.md).

# 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.

## Related

- [Add a process source in Duaer](https://doc.duaer.com/build/process-sources.md)
- [See the process in your data and generate workflows in Duaer](https://doc.duaer.com/build/process.md)
- [Process findings and SOP conformance in Duaer](https://doc.duaer.com/build/process-findings.md)
- [SAP S/4HANA purchase to pay: see where each order waits](https://doc.duaer.com/guides/sap-s4hana-purchase-to-pay.md)
- [NetSuite purchase to pay and order to cash: see where each order waits](https://doc.duaer.com/guides/netsuite-purchase-to-pay-order-to-cash.md)