- Low-Code Platform
SAP NetWeaver Mobile, part of the SAP NetWeaver platform, was designed to give users the ability to develop mobile solutions for the SAP Business Suite. NetWeaver Mobile included support for “occasionally connected” workers with some offline capabilities.
SAP ended support of NetWeaver 7.40 in 2020, and options included migrating to NetWeaver 7.50 have until 2024 for NetWeaver Java and 2025 for NetWeaver ABAP before those platforms reach their end of life.
You can continue to use SAP NetWeaver Mobile until its end of support; however, this strategy may limit your ability to optimize your apps as SAP releases modern platforms and applications. Your team will also have only the most basic offline capabilities.
SAP offers Fiori for mobile app development. While this may be a viable option for users whose needs align with Fiori templates, anything more than adding a field or changing a field name will take a significant investment of time and talent to customize the apps.
EdgeReady Cloud allows you to migrate ABAP code to the Pillir platform via low-code/no-code graphical interfaces so that you can continue to use your apps long after SAP NetWeaver reaches the end of support. Moreover, you can continue to use the apps you create as you transition to SAP S/4 HANA or another modern or cloud environment.
SAP NetWeaver users will need to make a change – and that change can lead to more robust offline capabilities. You don’t need to settle for lightweight offline capabilities that enable only form, data capture and read-only apps and support short and infrequent offline use.
Pillir offline app capabilities include:
EdgeReady Cloud enables you to modernize any custom ABAP code. The platform allows you to visualize objects, such as tcodes, methods, RFCs, tables, reports, programs, screens, functions, and data elements for stakeholders with any level of tech expertise. Pillir’s Modernize module provides the total cost of remediating ABAP as well as the total maintenance costs in S/4HANA or other cloud platforms.
Until the SAP SRM end of life, you may choose to continue to use your current SAP system, begin to move incrementally, or decide to maintain a hybrid environment. You choose what you’ll migrate to the cloud, keeping your ECC core clean and reducing total cost of ownership (TCO). Pillir doesn’t lock you into as-is conversion, but it does make modernizing an application as simple as map, review, and publish.
Moving your critical business apps from old SAP solutions into the future used to be milestone projects with hefty budgets and timelines. But not anymore.
Using Low-Code/No-Code automation platforms, you can upgrade and enhance your supply chain apps and future-proof them for your upcoming S4/HANA migrations (and we can help).
SAP NetWeaver Mobile users don’t have to refactor their entire IT environments today – but there’s another option besides waiting for a major overhaul when support ends. Pillir enables you to migrate apps incrementally and at your own pace, allowing an easier transition and minimal disruption to operations.
Furthermore, once you migrate apps to the Pillir platform, you can use them with your current SAP system and mobile devices as well as in other IT environments and with mobile devices you upgrade to in the future. Custom code no longer has to be a barrier to innovation.
We did not struggle with end-user adoption at all, even though this was the first time many field employees used smartphones for their work duties. Field employees can now scan barcodes to identify job information and, in seconds, complete the time card right on the job site….The payroll employee can easily upload time records into SAP Which eliminates two-and-a-half days and two full-time employees from the process