CrystalWorks: How Crystal Reports Keeps Running in IFS Cloud After 26R1 | OasisPro

OasisPro · CrystalWorks · Crystal Reports IFS Cloud · SAP-Approved · Zero Rebuild

Crystal Reports in IFS Cloud is ending.
Here is exactly how CrystalWorks keeps every RPT file running.

 · 9 min read ·  IFS Cloud CrystalWorks 26R2 Removes Crystal Reports

CrystalWorks Crystal Reports IFS Cloud RPT files SAP approved OasisPro

CrystalWorks is the only SAP-approved solution that keeps existing Crystal Reports RPT files running natively inside IFS Cloud after 26R1 removes the native Crystal Reports integration. No rebuilding reports. No migrating to IFS Report Studio. No retraining users. Your RPT files continue to run exactly as they always have — from inside IFS Cloud, triggered by your users, outputting to PDF or Excel, through a middleware layer that sits invisibly between IFS Cloud and your Crystal Reports runtime.

IFS Cloud 26R1 is the final version where Crystal Reports integration exists. From 26R2 onwards, it is gone. Every RPT file your business has built over years — sales orders, delivery notes, invoices, compliance documents, maintenance work orders, management reports — stops working the moment your environment moves past 26R1.

Most IFS partners will tell you to migrate to IFS Report Studio. That means rebuilding every report from scratch, with no automated conversion, followed by retraining every user who currently runs a Crystal Report. For businesses with substantial Crystal Reports libraries, that project runs into months and significant cost.

CrystalWorks takes a fundamentally different approach. Rather than replacing Crystal Reports, it bridges the gap between IFS Cloud and the SAP Crystal Reports runtime. Your RPT files stay exactly as they are. SAP Crystal Reports continues to render them. OasisPro, as the only SAP partner providing CrystalWorks, ensures the entire arrangement is fully SAP-licensed and approved.

CrystalWorks: the middleware that makes Crystal Reports invisible to IFS Cloud's removal.

CrystalWorks sits between IFS Cloud and the SAP Crystal Reports runtime engine. When a user in IFS Cloud triggers a report, CrystalWorks intercepts the request, passes it to Crystal Reports, receives the output, and delivers it back into IFS Cloud. From the user's perspective, nothing has changed. The report runs. The PDF arrives. The process is identical.

Zero RPT file changes Zero user retraining SAP-approved runtime On-premise or hosted IFS Cloud 26R2+ compatible PDF and Excel output All IFS modules covered Deployed in days
0
Changes required to existing RPT files when CrystalWorks is deployed
26R2
The IFS Cloud version where Crystal Reports is permanently and completely removed without CrystalWorks
1
SAP partner providing CrystalWorks to IFS Cloud customers globally: OasisPro
Days
Typical CrystalWorks deployment timeline, compared to months for a Report Studio migration project

How CrystalWorks works: the full technical picture

CrystalWorks is middleware. It does not modify IFS Cloud. It does not modify your RPT files. It operates as a service layer between them, handling the translation that IFS Cloud's native integration used to perform internally.

1
User triggers a report inside IFS Cloud
Everything starts the same way it always has. The user navigates to the report in IFS Cloud, selects their parameters, and clicks to run. They see the same interface they have always used. Nothing about the front-end experience has changed.
2
CrystalWorks intercepts the report request
Instead of IFS Cloud attempting to call the removed Crystal Reports integration, CrystalWorks intercepts the request. It receives the report name, the parameters the user selected, and the data context from IFS Cloud. This interception is invisible to the user and transparent to IFS Cloud.
3
CrystalWorks calls the SAP Crystal Reports runtime
CrystalWorks passes the request to the SAP Crystal Reports runtime engine along with the relevant RPT file and the parameter set. The runtime renders the report exactly as it always has, pulling live data from IFS Cloud through the same data connection the RPT file has always used.
4
Crystal Reports renders the output
The SAP Crystal Reports runtime renders the RPT file with live IFS Cloud data. All formatting, groupings, subtotals, custom fonts, images, subreports, conditional formatting, and cross-tab tables are preserved exactly as defined in the RPT file. Nothing about the rendered output changes.
5
Output delivered back into IFS Cloud
CrystalWorks receives the rendered output from the Crystal Reports runtime and delivers it back to IFS Cloud in the format the user selected. PDF, Excel, or other output formats supported by Crystal Reports are all available. The user sees their report output exactly as they always have.

The entire CrystalWorks process is invisible to the end user. The report runs. The output arrives. The experience is identical.

Users do not need to know CrystalWorks exists. They do not need retraining. They do not need new workflows. From their perspective, Crystal Reports still works inside IFS Cloud. The only thing that changes is the middleware layer underneath, and that is OasisPro's responsibility to deploy and maintain.

What CrystalWorks covers: every report type your business uses

CrystalWorks works with any RPT file that currently runs inside IFS Cloud. There are no report type exclusions, no module restrictions, and no format limitations. If Crystal Reports can render it, CrystalWorks can serve it.

🧾
Sales orders and quotations
Customer-facing documents with branding, terms, and pricing layouts built in Crystal Reports over years
📦
Delivery notes and despatch
Warehouse and logistics documents with barcodes, packing lists, and customs data
💰
Invoices and credit notes
Finance documents with VAT breakdowns, payment terms, and bank account details
🔧
Maintenance work orders
MRO and asset management documents including job cards, inspection checklists, and safety records
📋
Purchase orders and GRNs
Procurement documents sent to suppliers with terms, delivery instructions, and line item detail
📊
Management and board reports
Executive-facing reports with cross-tabs, charts, KPI dashboards, and multi-company consolidated views
🏭
Production and shop floor
Manufacturing documents including production orders, route cards, quality control sheets, and BOM print-outs
📝
Compliance and regulatory
Regulatory documents with specific formatting requirements, audit trails, and controlled document standards
🤝
Customer-specific formats
Bespoke report formats built to specific customer or trading partner requirements over the lifetime of the IFS deployment

Why SAP approval matters: the licensing question other solutions ignore

The SAP Crystal Reports runtime is proprietary software. Using it requires a valid SAP licence. When IFS provided native Crystal Reports integration, the licensing was managed through the IFS and SAP partnership. When IFS removed that integration, the licensing obligation did not disappear.

Any solution that continues to use the SAP Crystal Reports runtime after IFS removes native support must do so under a valid SAP licence arrangement. Solutions that do not address this create potential SAP licensing compliance risk for the businesses using them.

CrystalWorks is SAP-approved. OasisPro is the only SAP partner providing it. That distinction matters.

CrystalWorks uses licensed SAP Crystal Reports runtime components within the terms of SAP's licensing framework. OasisPro holds the SAP partner status that makes this possible. No other IFS partner or third-party tool currently provides an SAP-approved Crystal Reports continuation solution for IFS Cloud customers. This is not a marketing claim. It is a verifiable SAP partnership fact.

Deploying CrystalWorks: on-premise, hosted, and what to expect

CrystalWorks is available in two deployment models depending on your IFS Cloud environment setup and your organisation's infrastructure preferences.

🏢

On-premise deployment

CrystalWorks is deployed within your existing infrastructure, sitting alongside or near your IFS Cloud on-premise components. Your RPT files remain in their current location. Your Crystal Reports data connections remain unchanged. OasisPro handles the CrystalWorks middleware installation and configuration.

☁️

Hosted deployment

For IFS Cloud environments running fully in the IFS cloud, CrystalWorks is deployed as a hosted service. OasisPro manages the hosted environment. Your RPT files are migrated to secure hosted storage. The integration to your IFS Cloud tenant is configured and maintained by OasisPro.

In both cases, deployment is measured in days. OasisPro's deployment process covers the CrystalWorks middleware installation, RPT file library configuration, data connection validation, IFS Cloud integration testing, and a user acceptance testing phase before go-live. No ERP upgrade is required. No IFS Cloud changes are needed. CrystalWorks works alongside whatever version of IFS Cloud you are running, from 26R1 onwards.

Also from OasisPro
Solved your Crystal Reports problem? Now solve your permission sets problem.

IFS Cloud permission sets are the other manual, error-prone process that slows down every upgrade and every new user onboarding. PermissionWorks automates permission set creation from real screen navigation — no IFS Solution Manager, no manual mapping, no post-upgrade permission gaps.

Read: How PermissionWorks works →

Frequently asked questions about CrystalWorks

What is CrystalWorks?

CrystalWorks is an OasisPro middleware product that keeps existing SAP Crystal Reports RPT files running natively inside IFS Cloud after IFS removes the native Crystal Reports integration from 26R2 onwards. It intercepts report requests from IFS Cloud, passes them to the SAP Crystal Reports runtime, and returns the rendered output to IFS Cloud. Users see no change. Reports run exactly as before.

Does CrystalWorks require changes to existing RPT files?

No. CrystalWorks requires zero changes to existing RPT files. Your reports continue to run exactly as they do today. All formatting, data connections, subreports, conditional logic, cross-tabs, charts, and custom elements in your RPT files are preserved and rendered unchanged by the SAP Crystal Reports runtime.

Is CrystalWorks SAP-approved?

Yes. CrystalWorks is SAP-approved and uses licensed SAP Crystal Reports runtime components within the terms of SAP's licensing framework. OasisPro is the only SAP partner providing CrystalWorks to IFS Cloud customers. Running Crystal Reports outside an SAP-approved solution after 26R1 creates potential SAP licensing compliance risk that CrystalWorks avoids entirely.

When does CrystalWorks need to be deployed?

CrystalWorks should be deployed before upgrading past IFS Cloud 26R1. IFS Cloud 26R2 removes Crystal Reports completely. Any IFS Cloud environment that upgrades to 26R2 or later without CrystalWorks in place will lose all Crystal Reports functionality immediately on upgrade with no recovery path other than migrating to IFS Report Studio.

How long does CrystalWorks take to deploy?

OasisPro deploys CrystalWorks in days. The deployment covers middleware installation, RPT library configuration, data connection validation, IFS Cloud integration testing, and a user acceptance testing phase. Timelines depend on environment complexity and the size of the RPT file library but are consistently far shorter than any Report Studio migration project for the same library.

CrystalWorks: keep what works. Skip the migration project entirely.

The IFS Cloud 26R1 deadline for Crystal Reports is not a future concern. 26R2 arrives at the end of 2026. Every business that has not resolved their Crystal Reports situation before that upgrade lands will lose their entire reporting library on the day of the upgrade.

CrystalWorks is the only SAP-approved way to avoid that outcome without rebuilding every report from scratch. OasisPro can deploy it in days. Talk to us and we will confirm exactly how CrystalWorks works in your specific IFS Cloud environment.

OasisPro are IFS Cloud specialists and the only SAP partner providing CrystalWorks to IFS Cloud customers globally.  ·  info@oasispro.co.uk  ·  01865 538071  ·  oasispro.co.uk