Oracle PeopleSoft and Orderful integration

What moves between them

The integration runs from Oracle PeopleSoft into Orderful. On a customer-defined schedule, ml-connector polls PeopleSoft for new purchase orders and related documents, maps the vendor codes and line items to Orderful's transaction format, and posts each order as an 850 PURCHASE_ORDER or related X12 transaction type to Orderful. Orderful then translates the transaction to the format each supplier expects and delivers it via EDI channels such as AS2, SFTP, or direct HTTP. The flow is one-way; ml-connector does not pull back acknowledgments or confirmations from Orderful, though customers can set up a separate flow from Orderful to PeopleSoft for inbound 855 PURCHASE_ORDER_ACKNOWLEDGMENTs if needed.

How ml-connector handles it

ml-connector stores the PeopleSoft OPRID and password encrypted and uses HTTP Basic Auth on every PeopleSoft REST call to authenticate. For Orderful, it stores the API Key encrypted and passes it in the orderful-api-key header. The connector polls PeopleSoft at a cadence you define, filtering by document creation date to retrieve only new orders since the last sync. For each order, it extracts the supplier ISA identifier from the vendor master record and validates that the supplier is active in Orderful. Line items are mapped to Orderful's Mosaic JSON schema, with item codes, quantities, and unit prices aligned to X12 850 format. Because PeopleSoft has no standard pagination, large result sets are filtered by date range. ISA identifiers must be configured in Orderful before the first order; ml-connector validates that the ISA exists before posting. Every transaction is logged with its PeopleSoft order number, Orderful transaction ID, timestamp, and status, so if a downstream delivery fails, the order can be retransmitted.

A real-world example

A mid-market distributor uses Oracle PeopleSoft for procurement and vendor management and needs to send orders to suppliers worldwide. Before the integration, procurement staff created orders in PeopleSoft, then manually re-entered them into their EDI platform or emailed supplier ASNs, causing delays and errors. With Oracle PeopleSoft and Orderful connected, each new purchase order flows automatically to Orderful, which translates it to the format each supplier expects and delivers it via EDI or direct API. Suppliers receive orders faster, and the procurement team can see an audit trail of every order sent, acknowledged, and shipped, all in one place.

What you can do

• •Send purchase orders from Oracle PeopleSoft to Orderful as X12 850 transactions on a schedule you define.
• •Map PeopleSoft vendor codes to Orderful ISA identifiers so orders route to the correct suppliers.
• •Authenticate PeopleSoft with HTTP Basic Auth and Orderful with API Key, storing both encrypted.
• •Poll PeopleSoft on a configurable schedule and log every transaction sent to Orderful with a full audit trail.
• •Support test and live streams in Orderful so you can validate orders before sending them to real suppliers.

Questions

How does ml-connector map PeopleSoft vendors to Orderful trading partners?

Each supplier must have an ISA identifier configured in Orderful before the first order. ml-connector extracts the vendor code from the PeopleSoft order, looks up the supplier's ISA identifier from the PeopleSoft vendor master, and includes that ISA in the Orderful transaction so the order routes to the correct trading partner.

Can the integration send acknowledgments back to PeopleSoft from Orderful?

The primary flow sends orders from PeopleSoft to Orderful. Acknowledgments and ship notices from Orderful back to PeopleSoft can be set up as a separate flow if needed. ml-connector can poll Orderful for inbound 855 PURCHASE_ORDER_ACKNOWLEDGMENT or 856 SHIP_NOTICE transactions and post them back to PeopleSoft.

What happens if a purchase order fails to post to Orderful?

Every transaction is logged with its PeopleSoft order number, timestamp, and result. If a post fails, the order remains in the audit log with an error message. ml-connector can retransmit failed orders on the next polling cycle, or you can manually trigger a resend from the audit interface.