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.

With our leadership in workload automation (WLA) through RunMyJobs by Redwood, we 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 cloud transformation 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.

The 2027 end-of-mainstream maintenance for SAP PI/PO

As organizations map out their RISE with SAP transformation or Cloud ERP transition, a critical deadline is approaching: SAP PI/PO’s 2027 end-of-mainstream maintenance and 2030 end-of-extended maintenance. For years, PI/PO has served as the workhorse for file-based integrations, yet many enterprises underestimate the impact of its end of support and looming retirement.

The risk is not just the deadline, but rather that SAP Integration Suite is not a full feature-parity replacement for dedicated file transfer. Moving B2B integrations from PI/PO often requires new licensing and trading partner components. Additionally, missing protocols like AS2 client, OFTP2 and SFTP server capabilities may force re-architecture of processes and trading partner connections. 

Failing to plan for these differences can force your organization into two undesirable choices: 

• Building fragile, custom workarounds: Dedicating significant resources to maintaining complex solutions that don’t scale
• Paying for extended maintenance: Settling for temporary support through 2030, which adds cost and delays your transformation without solving the underlying architectural gap

While SAP offers dedicated migration tooling to assist PI/PO customers in their transition, the recommended destination, SAP Integration Suite, falls short of the robust file transfer and data movement requirements mandated by modern, high-volume enterprise organizations. This creates a functional gap, particularly when handling the scale and complexity of data that defines today’s hybrid landscapes.

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 as a dedicated, large-scale MFT hub capable of supporting any file size or file volume. 

SAP experts acknowledge that files larger than ~40 MB frequently see performance degradation. 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, SFTP server, on-demand or OFTP2 support)
• Challenges with file-level automation, error handling or audit logging

Additionally, for organizations in highly regulated sectors, data governance and long-term visibility present another layer of complexity. While SAP Integration Suite offers robust logging, its 30-day retention limit can inadvertently lead to a compliance gap for enterprises governed by mandates like SOX, PCI DSS or GDPR that require significantly longer look-back periods. Without a dedicated, long-term audit trail for every file exchange between trading partners and SAP applications, organizations may find themselves unintentionally non-compliant with strict regulatory requirements — even after a successful technical migration.

The bottom line? SAP Integration Suite 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 events; they’re tightly woven into broader enterprise process automation. That’s why RunMyJobs is so critical. It stands alone as the only SAP Endorsed App that combines agentic orchestration with its status as the leading cloud-native WLA platform. 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 connectors and templates for the latest SAP technologies and cloud solutions. These include SAP Cloud ERP, SAP Cloud ALM, SAP Integration Suite, SAP Datasphere, SAP Analytics Cloud and more, in addition to 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 agentic orchestration platform that’s a part of the RISE with SAP 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: Support SFTP, AS2, OFTP2, HTTPS, REST APIs, SharePoint, on-demand, S3, Azure Blob, Google Storage, SMB and more
• Automation integration: Trigger RunMyJobs or REST APIs based on file events
• Security and compliance: Ensure encryption, integrity checks, SIEM streaming and SSO/LDAP
• Scalability: Enable high availability (HA) clusters and horizontal scaling to support global 24/7 operations
• Cloud-ready: Deploy MFT to be containerized OR hybrid-aligned with zero-trust principles

These two platforms are fully integrated and supported by a single vendor with over 30 years of experience in automation: Redwood Software.

Trusted by SAP, engineered for what’s next

RISE with SAP customers already trust RunMyJobs as the only orchestration platform that’s an Endorsed App and part of the RISE with SAP reference architecture, with many 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 a RISE landscape, 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 to help ensure a successful transformation

We’ll share what we’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.