What it is. A focused family of native C Business Functions delivering full-fidelity SFTP support directly inside the JD Edwards Enterprise Server. The BSFNs install on the Enterprise Server, are called by name from any JDE C or NER function, and use the well-established core JDE BSFN execution model — the same model your existing developers already know.

Why “in the core” matters. SFTP is everywhere a modern business needs to move files: outbound to bank reconciliations, supplier feeds and partner integrations; inbound for invoices, statements, EDI documents and reference data. Doing it outside JDE means standing up an external SFTP agent, scheduling it independently of JDE, dealing with credentials and certificates in two places, and adding a separate failure surface to monitor. Doing it inside JDE means a single deployment, a single audit trail, a single security boundary, and one fewer thing for the CNC team to look after at 3 a.m.

The capability set:

• Full SFTP operation coverage — the BSFN set is flexible enough to perform any required SFTP operation.
• Latest encryptions supported.
• Certificate authentication supported — alongside password / key-based authentication.
• All JDE releases from XE through E920 are supported.
• Windows x32/x64 Enterprise Servers are all supported.

For Developers

Call SFTP from inside JDE the way you call every other BSFN — from C, from NER, or from anywhere else in the JDE programming model that already calls BSFNs.

What you get:

• Use existing skills. These are native JDE C Business Functions. Your existing JDE developers can call them today, without re-training and without hiring developers with a different skill-set.
• Use existing infrastructure. The functions are compiled into JDE executable libraries that run as part of the core JDE BSFN execution. No new servers, no new daemons, no new bolt-ons that need their own lifecycle.
• Always faster than the alternative. Compiled C runs inside JDE — you skip every step of marshalling the call out to a Java agent, an external scheduler, an external scripting layer or a separate transfer process.
• Composable. Call SFTP from a UBE, an APPL, or another BSFN. Loop, branch, retry, log — the surrounding ER and C code is yours to control.
• Certificate-aware. Modern key and certificate authentication is built in; you are not stuck with passwords.

For IT & CNC

From a CNC perspective, the goal is to reduce moving parts — not add them. Easy JDE SFTP installs once on each Enterprise Server, uses the existing JDE BSFN execution model, and has no additional service to monitor or restart.

Deployment & operations:

• Per Named Server install. No client-side install, no end-user install, no Deployment Server impact beyond the standard Object distribution.
• No new ports, no new daemons. The SFTP traffic originates from the JDE Enterprise Server itself, using its existing outbound network configuration.
• No additional scheduler. File transfers run when the JDE Object that calls them runs — under the standard JDE Scheduler or any other JDE submission path. One scheduler, one queue, one place to look.
• One audit trail. The transfer is part of the JDE job, so it shows up in the JDE logs alongside the work it belongs to.

Security:

• Latest encryptions are supported.
• Certificate authentication is supported, in addition to password / key authentication.
• Credentials never leave the Enterprise Server — there is no external agent to also trust with them.
• Removing the external SFTP middleware removes one piece of attack surface.

OS: MS Windows (x32 or x64)
CPU: Intel / AMD
System Type: Physical or Virtual
JDE Releases: all releases from XE to the latest E920
JDE Backend Database Platforms: DB-Server-independent — all platforms supported by JDE are supported

This software is licensed Per Named Server.

The optional Yearly Update / Upgrade Subscription is available at the time of purchase (not available separately) for an additional yearly fee. It is payable in advance per licence, per year. It includes premium support and all software updates released during the paid period. Its cost is calculated as 20% of the product’s list price at the time of invoicing, as may change from time to time. Unless the software is purchased for a single, short-term application, we generally recommend opting in for this Subscription: any future JDE Tools Releases and Releases / Updates may require an updated version of this solution, and the Subscription is generally more cost-efficient than one-off Upgrades.