BDI Connects SAP Across Six Countries With Files.com—Without Running Transfer Servers

BDI is an industrial distributor supplying bearings, power transmission, motion control, and related MRO products to manufacturing and industrial customers. Based in the United States, it also has branch operations in Poland, Romania, Serbia, Hungary, China, and India.

Its back office runs on SAP, and SAP is in constant conversation with the world outside the company: file flows with banks in both production and QA, feeds arriving from suppliers, a feed going out to the e-commerce channel, and exchanges with overseas branches. In industrial distribution, that traffic moves the way it has for decades: as files, over SFTP. Files were always going to cross BDI's boundary. The entire footprint was under 10 GB, but those files connected SAP to business-critical relationships across Europe, Asia, and North America. The open question was what channel would carry them.

A Transfer Problem Measured in Counterparties, Not Gigabytes

The difficulty was never volume; it was breadth. The channel had to carry bank production and QA flows, multiple supplier feeds, an e-commerce feed, and branch exchanges across six countries. Each was an independent relationship that needed its own credentials, isolation from every other counterparty, and consistent directory paths for SAP integrations.

BDI had also set a bar for the channel itself: files encrypted in transit and encrypted at rest, on every flow, for every counterparty. The company's SAP Basis administrator made that the starting requirement, not a preference.

Without a hosted service that cleared the bar, the choice landed on the SAP team, and neither side of it was good. Build the channel in-house, and an ERP team takes on transfer servers to run and patch, plus credential administration for every bank, supplier, and branch connection: permanent infrastructure work for a team hired to run SAP. Skip the build, and counterparty exchange runs below the company's own encryption requirement.

A Channel BDI Would Not Have to Host or Patch

The requirement was short and strict. The channel had to be hosted; nobody at BDI was going to operate transfer infrastructure. It had to encrypt files at rest and in transit, making the security requirement a property of the platform rather than a duty of the team. It had to accept SFTP connections from banks, suppliers, branch sites, and SAP. And it had to give each counterparty its own login against a structured directory tree, so isolation held and paths stayed consistent.

BDI selected Files.com to be that hosted exchange layer.

One Site, a Login and a Directory Per Counterparty

What BDI built on Files.com was a single site organized as a structured directory tree for its SAP integrations: areas for bank flows, supplier feeds, and the branch network, with production and QA kept apart. Each counterparty now connects over SFTP with its own login, scoped to its own directory, so no bank, supplier, or branch touches another's traffic. On BDI's side, SAP integrations read and write against those paths.

BDI's cybersecurity manager built out the site configuration alongside the SAP team.

Every External Flow on One Encrypted Layer

With the Files.com site in production, BDI replaced a build-or-compromise decision with one governed exchange layer for everything that crosses its boundary.

Bank flows in production and QA, supplier feeds, the e-commerce feed, and branch exchanges across six countries now move through a single encrypted platform administered in one place. The SAP team manages integrations against fixed paths rather than transfer servers. Adding another counterparty follows the same model: a login and a directory in the tree, without changing the pattern SAP relies on.

Under 10 GB That Carry the Back Office

The instinct in file transfer is that a managed platform earns its keep on volume: terabytes moved and heavy pipes. BDI's deployment says otherwise. The whole estate holds under 10 GB, and on it ride the bank flows, supplier feeds, and branch exchanges that BDI's back office depends on. What Files.com carries for BDI is not weight but relationships: two banks, a supplier network, an e-commerce channel, and branches across Europe and Asia, each isolated and encrypted within a directory structure SAP can use consistently.

Before Files.com, holding all of that to BDI's own security bar would have meant an ERP team running transfer servers as a side job. Now the SAP team writes integrations, the encryption requirement is enforced by the platform itself, and the exchange layer is measured by the thing that mattered all along: not how much data it stores, but how much of the business depends on what it moves.