Oracle PeopleSoft and Stedi integration

What moves between them

Purchase requisitions and orders flow from PeopleSoft into Stedi. ml-connector polls PeopleSoft on a configurable schedule, extracts requisition headers and line items, maps them to the Stedi X12 850 purchase order standard, and posts the transaction to Stedi. Stedi then translates the JSON to X12 EDI format and delivers the 850 file to the trading partner via SFTP, FTPS, or AS2 based on the partnership configuration. Inbound 855 purchase order acknowledgments from suppliers arrive at Stedi as webhooks, parse into JSON, and can be mapped back into PeopleSoft if acknowledgment tracking is enabled.

How ml-connector handles it

ml-connector stores both PeopleSoft and Stedi credentials encrypted and handles the distinct authentication models: HTTP Basic Auth or OAuth2 on the PeopleSoft side, and API Key on the Stedi side. Since PeopleSoft has no webhooks, ml-connector polls the PeopleSoft REST endpoints on a configurable cadence tied to your procurement cycle, filtering by creation date to retrieve new orders. Before posting to Stedi, requisition lines are mapped to vendor accounts and ship-to addresses configured in your PeopleSoft instance. Stedi's Idempotency-Key requirement is handled by ml-connector using the PeopleSoft requisition ID as the source, ensuring duplicate requests do not create duplicate EDI files. Inbound 855 acknowledgments from Stedi webhooks are validated, parsed, and optionally posted back to PeopleSoft to update requisition status. Every transaction carries a full audit trail, and ml-connector tracks which orders have been sent to prevent re-transmission.

A real-world example

A mid-sized discrete manufacturer with multiple plants uses Oracle PeopleSoft for procurement and vendor management. The purchasing team creates requisitions in PeopleSoft, but historically those orders were exported as CSV and manually re-keyed into the company's EDI system before sending to suppliers, a process that introduced delays and keying errors. With PeopleSoft and Stedi connected, requisitions created in PeopleSoft flow automatically into Stedi and are translated to standard X12 850 purchase orders within minutes. Suppliers receive orders faster, acknowledgments flow back into PeopleSoft automatically, and the purchasing team eliminates the manual export and re-keying step entirely.

What you can do

• •Extract purchase requisitions and purchase orders from Oracle PeopleSoft and post them to Stedi as X12 850 purchase order transactions.
• •Translate PeopleSoft requisition data, including line items, delivery dates, and vendor accounts, into EDI-compliant X12 format.
• •Authenticate Oracle PeopleSoft with HTTP Basic Auth or OAuth2 bearer token, and Stedi with API Key credentials, with both encrypted in storage.
• •Poll Oracle PeopleSoft on a configurable schedule and route outbound 850 files to suppliers via Stedi's SFTP, FTPS, or AS2 transport.
• •Receive inbound 855 purchase order acknowledgments from Stedi webhooks, validate them, and optionally update requisition status in Oracle PeopleSoft.

Questions

What purchase order data flows from Oracle PeopleSoft to Stedi?

Purchase requisitions and purchase orders from PeopleSoft flow into Stedi as 850 EDI transactions. ml-connector extracts requisition headers, line items, quantities, delivery dates, vendor accounts, and ship-to addresses from PeopleSoft and maps them to the X12 850 standard. Stedi then translates the data to EDI format and delivers it to the supplier via SFTP, FTPS, or AS2 per the partnership configuration.

Does ml-connector handle the different authentication models for both systems?

Yes. Oracle PeopleSoft uses HTTP Basic Auth (OPRID and password) or OAuth2 bearer token depending on the PeopleTools version. Stedi uses a static API Key in the Authorization header with no token expiry. ml-connector stores both credentials encrypted and applies the correct authentication scheme for each system on every request.

How does ml-connector prevent duplicate EDI files if a poll is retried?

Stedi requires an Idempotency-Key header on all write requests. ml-connector derives this key from the PeopleSoft requisition ID, so if the same requisition is polled twice, Stedi recognizes it as a duplicate and does not create a second EDI file. ml-connector also maintains an audit log of sent requisitions to track which orders have already been transmitted.