File transfer strategy for RISE with SAP: Clean core, compliance and control

At Redwood Software, we’ve had the privilege of working closely with some of the largest SAP landscapes in the world — across industries, continents and decades of transformation. Today, many of those same enterprises are entering a new chapter: RISE with SAP.

As the Field CTO for Managed File Transfer (MFT) at Redwood, and with our leadership in workload automation (WLA) through RunMyJobs by Redwood, I see firsthand the opportunities RISE unlocks — and the architectural considerations that follow.

One of the most critical, yet often overlooked, shifts? How file movement is handled in RISE.

The clean core brings new rules for file exchange

Most enterprises adopting RISE are modernizing from highly customized, often decades-old SAP environments. These landscapes typically include:

• Multiple ERPs, CRM and legacy systems of record
• OS-level scripts, direct database writes and mounted network shares
• Hundreds of file-based integrations with internal teams and external partners

These legacy approaches depend heavily on infrastructure-level access. But in a RISE architecture, those access models change. SAP clearly defines this shift:

In the SAP S/4HANA Private Cloud environment, direct server access is unavailable.

SAP Community Blog: Proposed Architecture for File Transfer

In short, file transfers must now align with strict ingress and egress controls, with no OS-level jobs or mounted file systems permitted.

This shift creates architectural friction that legacy models can’t easily resolve. What worked for file movement in the past may not translate to a clean core, cloud-first model — especially in hybrid enterprise environments.

SAP BTP and high-volume file transfers

While SAP’s Integration Suite (part of SAP Business Technology Platform (BTP)) can manage file transfers through Cloud Integration flows, it was not designed to serve customers who have a need for a dedicated, large-scale MFT hub. There is a whole industry of MFT solution providers who address this common need for enterprises.

SAP experts acknowledge that files larger than ~400 MB can pose challenges. Streaming, while supported, may still lead to timeouts, memory strain or complex workaround flows in real-world conditions, according to the SAP Community.

Routing thousands of files daily through a multi-tenant integration service can also introduce:

• Latency due to multi-tenant queueing
• High processing costs tied to data volume
• Limits in protocol diversity (e.g., no native AS2 or OFTP2 support)
• Challenges with file-level automation, error handling or audit logging

The bottom line? SAP BTP wasn’t built to be a full-featured MFT platform. For organizations exchanging financial payloads, batch files or high-throughput transactional data, these constraints become increasingly apparent during RISE migration.

RunMyJobs + JSCAPE: Redefining the hybrid automation layer

This is where our customer conversations tend to deepen. File transfers aren’t isolated — they’re tightly woven into broader process automation. That’s why RunMyJobs, the #1 cloud-native WLA platform in SAP’s ecosystem, plays a pivotal role.

Redwood’s customers are using RunMyJobs and JSCAPE by Redwood together to address the demands of modern SAP workloads.

RunMyJobs orchestrates end-to-end processes across SAP and non-SAP systems, offering a wide range of comprehensive connectors and templates for the latest SAP technologies and cloud solutions. These include SAP S/4HANA Cloud, SAP BTP, SAP Integration Suite, SAP Datasphere, SAP Analytics Cloud and non-SAP and partner solutions like Databricks, Snowflake and many others. For SAP customers moving their ERP to the cloud via RISE, RunMyJobs is the only WLA solution that’s part of the RISE reference architecture. 

JSCAPE handles the secure, scalable movement of files across protocols, partners, clouds and compliance boundaries.

JSCAPE capabilities that matter in a RISE world

• Multi-protocol Gateway: Supports SFTP, AS2, OFTP2, HTTPS, RESTful APIs, SharePoint, ad hoc, S3, Azure Blob, Google Storage, SMB and more
• Automation integration: Trigger RunMyJobs or REST APIs based on file events
• Security and compliance: Encryption, integrity checks, SIEM streaming, SSO/LDAP
• Scalability: HA clusters and horizontal scale to support global 24/7 operations
• Cloud-ready: Containerized, hybrid and aligned with zero-trust principles

These two platforms are not just compatible — they’re SAP-endorsed, available on the SAP Store and supported by a single vendor: Redwood.

Trusted by SAP, engineered for what’s next

RISE with SAP customers already trust RunMyJobs as the only scheduler that’s part of the RISE reference architecture, and many are extending that trust by integrating file transfers through JSCAPE.

RunMyJobs’ Secure Gateway is a fully supported, SAP-compliant method for enabling secure, outbound automation from within the RISE model, avoiding inbound firewall rules or non-compliant access patterns.

Together, RunMyJobs and JSCAPE provide a unified, secure framework for automating file transfers and workflows across hybrid SAP environments while respecting clean core principles and future-proofing your architecture. 

Where to go from here

If your enterprise is moving to RISE or you’re simply re-evaluating file movement in a modern SAP architecture, Redwood’s experts would welcome the opportunity to talk about your file transfer plans — without assuming your architecture or prescribing a quick fix.

Instead, they’ll share what they’ve learned through years of customer partnerships and how other organizations like yours are rethinking hybrid file flows, automation triggers and compliance boundaries during their cloud transformations.

Let’s define a file movement strategy that supports your business — and your future state. Find out more about JSCAPE.