Oracle PeopleSoft and IBM Sterling integration

What moves between them

The flow is unidirectional, from IBM Sterling into Oracle PeopleSoft. EDI purchase orders and invoices arrive in Sterling from trading partners via AS2, SFTP, or other protocols, where they are stored in Sterling mailboxes and awaiting processing. ml-connector polls Sterling's mailbox API every 2 to 5 minutes, extracts each new EDI document, parses the transaction (purchase order, invoice, or ASN), and posts the data into PeopleSoft via SOAP Component Interface services. PeopleSoft journal entries, vouchers, and receipts are created with references back to Sterling message IDs for traceability. Master data such as vendors and cost centers are validated against PeopleSoft before any financial document is created.

How ml-connector handles it

ml-connector accepts the customer's PeopleSoft hostname, port, and node name, along with HTTP Basic Auth credentials (OPRID and password), and the IBM Sterling host, port, and non-admin API account. On each polling interval, ml-connector fetches the list of new mailbox messages from Sterling via GET /B2BAPIs/svc/mailboxMessages with a timestamp filter, then extracts the EDI payload for each document. It parses X12 850 (purchase order), 810 (invoice), and 856 (advanced ship notice) transactions, looks up the sending Trading Partner to identify the supplier or customer, and maps the EDI line items to PeopleSoft items and GL accounts. It validates that the vendor exists in PeopleSoft before creating a voucher, and that the requisition's department and cost center exist before posting. If validation fails, the record is logged with a full error trace and held for manual review; if validation succeeds, ml-connector uses PeopleSoft's SOAP Component Interface to insert the transaction. Because PeopleSoft's REST polling endpoints do not guarantee ordering, ml-connector tracks processed Sterling message IDs to avoid duplicate posting, and if a downstream SOAP call fails, the record is queued for replay on the next cycle. PeopleSoft's asynchronous message format is XML; if the customer has configured Integration Broker outbound routing, ml-connector can also subscribe to those events as a supplementary trigger.

A real-world example

A mid-sized distributor uses Oracle PeopleSoft for general ledger, accounts payable, and procurement. Their trading partners - manufacturers and logistics providers - send orders and shipping notifications to IBM Sterling in ANSI X12 format via AS2 or SFTP. Before the integration, the procurement team exported EDI documents from Sterling once a day, manually parsed them in a spreadsheet, and typed the orders into PeopleSoft, a process that caused delayed requisition creation, invoice reconciliation errors, and month-end scrambling to reconcile received goods against both systems. With Oracle PeopleSoft and IBM Sterling connected, each inbound EDI purchase order or invoice is automatically parsed from Sterling and posted into PeopleSoft within minutes, creating purchase requisitions and vouchers with the correct vendors and account codes. The goods receipt workflow in PeopleSoft can then proceed without manual data re-entry, and three-way matching (PO, receipt, invoice) works as designed.

What you can do

• •Post inbound EDI purchase orders (850) from IBM Sterling into Oracle PeopleSoft as purchase requisitions, validated against vendors and cost centers.
• •Create accounts payable vouchers from EDI invoices (810) arriving in Sterling, with automatic GL account mapping and vendor validation.
• •Record goods receipts from EDI advanced ship notices (856) against open purchase orders, updating PeopleSoft inventory and audit trails.
• •Authenticate Oracle PeopleSoft with HTTP Basic Auth or OAuth2 bearer token and IBM Sterling with non-admin HTTP Basic Auth or OAuth2 Client Credentials.
• •Poll Sterling mailbox messages on a configurable schedule, parse EDI transactions, validate business rules, and replay failed records with a complete audit trail.

Questions

Does ml-connector translate EDI syntax into PeopleSoft entities automatically?

Yes. ml-connector parses ANSI X12 850 (purchase order), 810 (invoice), and 856 (advanced ship notice) transactions, maps Trading Partner IDs in Sterling to vendor codes in PeopleSoft, extracts line items and amounts, and posts them into PeopleSoft using the SOAP Component Interface. Mapping is configured once per customer and applied to every transaction.

What happens if a PeopleSoft vendor or cost center does not exist when an EDI document arrives?

ml-connector validates against PeopleSoft's existing vendors, GL accounts, and cost centers before posting any financial record. If validation fails, the document is logged with a detailed error message and held for manual review or correction. Once the missing master data is created in PeopleSoft, ml-connector can replay the held record on the next cycle.

How does ml-connector handle EDI documents that are out of order or arrive multiple times in Sterling?

ml-connector tracks Sterling message IDs to detect and skip duplicate documents, ensuring no invoice or purchase order is posted twice. Polling timestamps and message sequencing are managed per Trading Partner to handle out-of-order arrival, and every transaction is logged with its source Sterling ID for auditability.