Oracle PeopleSoft and TrueCommerce integration

What moves between them

Purchase orders, invoices, and shipment notices move from TrueCommerce into Oracle PeopleSoft on a schedule you control, typically daily or hourly. ml-connector polls TrueCommerce's SFTP at your configured interval, retrieves inbound X12 documents, normalizes them, and submits them to PeopleSoft via SOAP component interfaces. Each document references a trading partner EDI ID that ml-connector maps to a PeopleSoft vendor record. Shipment notices update PeopleSoft's receipt and inventory status. Invoice documents post into PeopleSoft's payables module. The flow is unidirectional: TrueCommerce supplies the documents, PeopleSoft receives and processes them.

How ml-connector handles it

ml-connector maintains encrypted credential storage for both systems. On the PeopleSoft side, it stores the operator ID, password, and the unique hostname and port for the customer's on-premise instance, or accepts the OAuth2 bearer token for cloud-managed versions. It validates that each Integration Broker service operation is activated in the customer's PeopleSoft console before attempting a call. For TrueCommerce, ml-connector stores SFTP credentials and the path to the customer's specific integration directories. On each poll, it connects to TrueCommerce SFTP, retrieves files matching the configured document types, and parses each X12 document using EDI control numbers to detect and skip duplicates. It then normalizes each document into the schema expected by PeopleSoft's component interfaces, performs a lookup to map the trading partner EDI ID to the vendor record in PeopleSoft, and submits the document via SOAP. If TrueCommerce credentials require firewall exceptions or reverse-proxy configuration, ml-connector logs these requirements for the customer's network team. PeopleSoft's on-premise architecture means each customer has a unique hostname; ml-connector stores this per-customer and does not assume a shared base URL. Errors are tracked with full context so failed documents can be replayed once the root cause is fixed.

A real-world example

A mid-sized food distributor operates Oracle PeopleSoft for procurement and payables. Their major suppliers use TrueCommerce to send purchase order acknowledgments, invoices, and shipping notices in X12 format. Before the integration, the purchasing department received these documents through TrueCommerce but had to manually enter key details into PeopleSoft three times a week, creating data entry errors and delaying matching between invoices and receipts. With TrueCommerce and PeopleSoft connected, each inbound X12 document from suppliers flows automatically into PeopleSoft, matched to the correct vendor and cost center. The invoice matching process now starts with accurate, deduplicated supplier data, and manual re-entry is eliminated.

What you can do

• •Poll TrueCommerce SFTP on a schedule you control and retrieve inbound X12 purchase orders, invoices, and shipment notices.
• •Normalize X12 EDI documents and map trading partner EDI IDs to Oracle PeopleSoft vendor records using a configurable lookup table.
• •Post normalized documents into PeopleSoft procurement and payables via SOAP component interfaces, updating purchase orders, receipts, and invoices.
• •Deduplicate inbound documents using EDI control numbers and maintain a full audit trail of every document transformation and submission.
• •Handle the unique hostname, port, and node configuration required by each on-premise PeopleSoft instance, with firewall and reverse-proxy logging where needed.

Questions

Which direction does data move between Oracle PeopleSoft and TrueCommerce?

The flow is unidirectional, from TrueCommerce into Oracle PeopleSoft. EDI documents arrive at TrueCommerce from suppliers and trading partners, and ml-connector retrieves them on a schedule, normalizes them, and posts them into PeopleSoft's procurement and payables modules. PeopleSoft does not send data back to TrueCommerce.

How does ml-connector handle PeopleSoft's on-premise architecture and variable hostnames?

Oracle PeopleSoft is self-hosted with a unique hostname, port, and Integration Broker node name for each customer. ml-connector stores these per-customer during setup and does not assume a shared base URL. It validates that required service operations are activated in the Integration Broker console before attempting calls, and logs firewall or reverse-proxy requirements for the customer's network team.

How does deduplication work when TrueCommerce sends the same EDI document multiple times?

EDI documents in X12 format carry an ISA control number that uniquely identifies each transmission. ml-connector extracts this control number, checks the audit log, and skips documents that have already been posted to PeopleSoft. This prevents duplicate invoices and purchase order acknowledgments from being entered twice.