> 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/oracle-fusion-purchase-to-pay-order-to-cash.md).

# Oracle Fusion purchase to pay and order to cash: see where each order waits

Connect Oracle Fusion Cloud to Duaer. It reads the steps of each purchase or sales order through the Fusion REST API, so you see where orders wait and for how long.
## What does Duaer read from Oracle Fusion?

Each purchase or sales order is a case, with the supplier or customer, the business unit, currency and order amount. The steps are:

- Purchase to pay: Requisition created, Order created, Goods received, Invoice posted, Paid.
- Order to cash: Order created, Delivery created, Goods issued, Invoice created, Paid.
- Canceled, deleted or reversed documents are left out. The steps match the purchase to pay or order to cash template, so the boards in My processes on the employee portal work as they are.

## How do you connect Oracle Fusion to Duaer?

1. In Oracle Fusion, prepare a user with read access to procurement, payables, order management and receivables (a read-only role is enough).
2. In Duaer, create an Oracle Fusion Cloud API credential with the instance host (like acme.fa.us2.oraclecloud.com, without https://), the user name and the password.
3. As an owner or admin, open Data sources in the sidebar, select Add source, choose Oracle Fusion under Purchase to pay or Order to cash, choose the credential and select Check connection. Any resource the user cannot read is listed with its status code.
4. The mapping is fixed. Preview, set the schedule and who sees the cases, and confirm.

## How often does it read, and how much?

Each run reads three streams, one page each at most, by last update: orders (with requisitions, receipts or shipments), invoices (with the order's receipts or shipments), and payments or cash receipts. Each stream reads a time window to its end, then goes on from there; a first read covers all past data and finishes over several runs. A step is never written twice. Read only: Duaer never writes to Oracle Fusion.

## 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.
- Each source reads one process; add purchase to pay and order to cash separately.
## Questions

### Does Duaer change data in Oracle Fusion?

No. Duaer only calls the REST API's queries.

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