PeopleSoft purchase to pay: see where each purchase order waits

What does Duaer read from PeopleSoft?

Each purchase order is a case (business unit and PO ID), with the supplier, business unit, currency and amount. The steps are Requisition created (PS_REQ_HDR), Order created (PS_PO_HDR), Goods received (PS_RECV_HDR), Invoice posted (posted vouchers in PS_VOUCHER) and Paid (PS_PAYMENT_TBL). Canceled orders and receipts, unposted vouchers and void payments are left out.

How do you connect PeopleSoft to Duaer?

1. In PeopleSoft's Oracle database, create a read-only user with SELECT on the purchasing, receiving, payables and vendor tables in the SYSADM schema.
2. If the database is only inside your network, start the Duaer on-premises data gateway (0.2.0 or later) there with tcp://database-host:port in ALLOWED_TARGETS; the credential's host and port must match it.
3. In Duaer, create an Oracle Database Credentials API credential for this user.
4. As an owner or admin, open Data sources, select Add source, choose PeopleSoft under Purchase to pay, choose the credential, enter the schema when it is not SYSADM, select Check connection and confirm.

How often does it read, and how much?

Each run reads orders, receipts, vouchers and payments by their last update, one page each at most, and goes on with the next time window when one is read. A step is never written twice. Queries 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.
• Purchase to pay only, and PeopleSoft on Oracle Database only for now.