Oracle JD Edwards and SFTP / Flat Files integration

What moves between them

Oracle JD Edwards GL ledger entries, AP invoices, supplier records, purchase orders, and item masters flow outbound to SFTP as flat files on a schedule tied to your close calendar or daily processing run. Incoming SFTP files (vendor catalogs, price updates, remittance advice) can be read and ingested into JD Edwards via the orchestration layer if configured. The main flow is read-heavy - exporting GL and AP data to archive and EDI trading partners - with optional inbound support for supplier master updates and payment advices.

How ml-connector handles it

ml-connector stores the JD Edwards AIS Server URL and credentials encrypted, refreshes the session token when it approaches expiry, and polls the data service tables (F0911 for GL, F0411 for AP, F0401 for suppliers) with date filters on UPMJ (date updated) to find new records. On the SFTP side it authenticates with your SSH private key or password, connects to the partner-provided host, and deposits formatted files into the outbound folder. File format mapping is configured per trading partner - CSV column layout, X12 segment structure, fixed-width field positions. ml-connector tracks which files have been sent, retries on network errors, handles host key verification, and maintains a complete audit log of every export. Because JD Edwards has no webhooks and SFTP has no push mechanism, both sides rely on polling on a predictable schedule. Pre-built orchestrations in JD Edwards must be imported manually before the first run.

A real-world example

A mid-sized discrete manufacturer uses Oracle JD Edwards on-premises for procurement and GL, and sends daily GL summaries and AP invoice registers to an archive server via SFTP for compliance and reporting. Before the integration, a finance clerk exported GL and AP data from JD Edwards each close day, formatted it as CSV, and uploaded it manually to the archive SFTP server. With Oracle JD Edwards and SFTP connected, each GL posting and AP invoice reaches the archive automatically on schedule, formatted to the archive spec, with no manual touch. The GL export runs nightly after batch posting completes, and AP invoices flow to trading partners as X12 files for their receipt posting.

What you can do

• •Export Oracle JD Edwards GL ledger entries to SFTP as CSV or fixed-width files on your close and reporting schedule.
• •Post AP invoices and supplier master records to SFTP in X12 EDI, EDIFACT, or CSV format for trading partners and archive systems.
• •Refresh AIS Server session tokens and handle token expiry automatically so authentication does not break mid-sync.
• •Authenticate SFTP connections with SSH keys or password, verify host keys, and map JD Edwards records to your partner-specific file format.
• •Maintain a complete audit trail of every GL, AP, and supplier record sent to SFTP, with replay capability if a downstream system fails.

Questions

Which direction does data flow between Oracle JD Edwards and SFTP?

The primary flow is outbound - GL ledger entries, AP invoices, supplier records, and purchase orders flow from Oracle JD Edwards to SFTP as flat files. Inbound support is optional - remittance advice, supplier price updates, and vendor catalogs can be read from SFTP and ingested into JD Edwards if you configure the receiving orchestration. The connector does not write directly to JD Edwards tables; all inbound updates go through the orchestration layer.

How does ml-connector handle the AIS Server token and SFTP authentication?

ml-connector stores both credential sets encrypted. On the JD Edwards side it exchanges username and password for a session token via the /jderest/v2/tokenrequest endpoint, tracks token expiry, and refreshes automatically before the token expires. On the SFTP side it presents your SSH private key or password to authenticate, verifies the remote host key to prevent interception, and maintains the SSH session across multiple file transfers. Both sides are monitored for failures and retried with exponential backoff.

What file formats does the connector support for SFTP export?

ml-connector handles CSV (with configurable column layout), fixed-width (positional field mapping), X12 EDI (810 invoices, 850 purchase orders, 820 payments), EDIFACT (INVOIC, ORDERS), and XML. The file format and column order are configured per trading partner - Oracle JD Edwards records are mapped to your partner's spec at export time. Standard SFTP folder structure (inbound, outbound, processed, error, acks) is required, and X12 or EDIFACT acknowledgments are produced and deposited after receipt if applicable.