Oracle PeopleSoft and SFTP / Flat Files integration

What moves between them

The main flow runs from Oracle PeopleSoft into SFTP. Invoice inquiry operations, purchase order status, vendor records, journal entries, employees, cost centers, and payroll data are read from Oracle PeopleSoft service operations on a schedule you define, transformed into structured file formats (CSV, X12, EDIFACT, or fixed-width), and written to the outbound folder on the remote SFTP server. A reverse flow polls the SFTP inbound folder for acknowledgment files and response files from trading partners or downstream systems, which can be logged or trigger downstream processing. Large result sets are managed by filtering on date ranges and other parameters available in the inquiry service operations.

How ml-connector handles it

ml-connector stores the SFTP hostname, port, and SSH credentials encrypted and connects via SSH key authentication or password over the encrypted SSH channel. On the Oracle PeopleSoft side, it accepts the unique hostname, port, and node name for your self-hosted instance, authenticates with HTTP Basic Auth or OAuth2 depending on your PeopleTools version, and queries the service operations you have activated in Integration Broker. Because Oracle PeopleSoft is pull-only, ml-connector polls on a schedule tied to your data change cadence rather than relying on a push from the ERP. Service operation results are paginated using date ranges and business key filters, since pagination schemes vary across PeopleTools versions. The records are parsed from REST JSON or SOAP XML responses, mapped to your file format specification (column order, delimiters, X12 segment layout), and deposited into the SFTP outbound folder. Host key verification is enforced in production to prevent man-in-the-middle attacks. Response files from SFTP inbound are monitored on the same schedule and can be replayed if a downstream system fails to process them. Every file and API call carries a full audit trail.

A real-world example

A mid-market financial services company runs Oracle PeopleSoft for AP, GL, and HR across multiple offices. They use a legacy vendor management portal that accepts vendor and invoice data only via SFTP CSV files, and they also exchange payroll data via EDI with an external PEO (Professional Employer Organization). Before the integration, the AP team exported vendor lists and invoice inquiries from Oracle PeopleSoft each week, reformatted the data in Excel to match the partner's column layout, and uploaded it manually via SFTP. Payroll files were prepared by hand and EDI documents were not validated before upload, causing rejects and re-keying. With Oracle PeopleSoft and SFTP connected, vendor and invoice exports run on the partner's schedule automatically, payroll records are validated against the EDI schema before deposit, acknowledgment files from both partners are logged and flagged if rejects arrive, and manual file handling is eliminated.

What you can do

• •Export Oracle PeopleSoft invoice inquiry, purchase order, vendor, employee, and journal data as CSV, X12, EDIFACT, or fixed-width files to SFTP outbound folders on a schedule you control.
• •Map Oracle PeopleSoft cost centers, GL accounts, and business units to your SFTP file structure and trading partner column layouts.
• •Poll SFTP inbound folders for acknowledgment files (X12 997, EDIFACT CONTRL) and flag processing errors for manual review or retry.
• •Handle Oracle PeopleSoft's unique hostname and port for each self-hosted instance, manage both HTTP Basic Auth and OAuth2 authentication, and parse REST JSON and SOAP XML service operation responses.
• •Enforce SSH host key verification, encrypt credentials at rest, and maintain a complete audit trail of every file deposit and retrieval.

Questions

How does ml-connector handle Oracle PeopleSoft's unique hostname and port for each customer?

Each customer's Oracle PeopleSoft instance runs on their own infrastructure with a unique hostname, port, and Integration Broker node name. ml-connector accepts these values in the credential set and constructs the full service operation URL at runtime. The connector also manages both HTTP Basic Auth (OPRID plus password) and OAuth2 Bearer tokens depending on the customer's PeopleTools version, refreshing the token when needed.

What file formats can ml-connector export from Oracle PeopleSoft to SFTP?

ml-connector exports records in the format your trading partner requires: CSV with custom column layouts, X12 EDI (810 invoices, 850 POs, 820 payments), EDIFACT (INVOIC, ORDERS), or fixed-width files with positional columns. Column order, delimiters, segment separators, and field widths are all configured per trading relationship. Acknowledgment files (X12 997 or EDIFACT CONTRL) are generated after processing inbound files.

Does ml-connector push data to SFTP, or does it wait for the partner to pull?

ml-connector writes files to the SFTP outbound folder on your schedule (typically 5 to 60 minutes after Oracle PeopleSoft data changes). The remote partner system is responsible for polling or receiving a notification to retrieve files from outbound. ml-connector monitors the SFTP inbound folder on the same schedule to detect and process acknowledgment files and response data from the partner.