Next steps when replatforming apps to ServiceNow using ERP Semantic Mining
Summarize
Summary of Next steps when replatforming apps to ServiceNow using ERP Semantic Mining
This guidance helps ServiceNow customers transition legacy ERP (Enterprise Resource Planning) applications to the ServiceNow AI Platform using ERP Semantic Mining. Although ERP Semantic Mining is being prepared for deprecation starting with the Zurich release, it remains supported on existing instances and serves as the initial tool to identify ERP customization candidates for replatforming.
Show less
Key Steps in the Replatforming Process
- Identify legacy ERP customizations: Use ERP Semantic Mining to find candidates for replatforming and access related remote and extraction tables containing ERP data.
- Build new apps consuming ERP data: Utilize ServiceNow Studio or other low-code/pro-code builders to create applications that directly use ERP data, improving efficiency by potentially pulling data directly from third-party sources instead of the ERP system via the Zero Copy Connector.
- Consolidate similar candidates: When multiple similar ERP apps are identified, consider designing a single enhanced app that addresses the needs of multiple candidates, leveraging low-code tools on the ServiceNow AI Platform.
- Use ServiceNow builders for app development: Citizen developers and professional builders can use ServiceNow Studio, Workflow Studio (Flows and Playbooks), Table Builder, UI Builder, and Workspace Builder to rapidly create apps with ERP data, including custom fields from systems like SAP.
- Access ERP data programmatically: The Glide API supports querying ERP data to integrate with new ServiceNow apps.
- Post-replatforming cleanup: After successful replatforming and confirming legacy code is not referenced elsewhere, remove outdated code from the ERP system to streamline IT landscapes.
Why This Matters
Replatforming legacy ERP apps onto the ServiceNow AI Platform enables improved data integration, streamlined app development, and modernization of IT workflows. It reduces dependency on legacy ERP systems for data retrieval, simplifies maintenance, and leverages ServiceNow’s low-code tools for faster innovation and better user experiences.
What to Expect
- Efficient identification of ERP customization candidates using ERP Semantic Mining.
- Access to ERP data through remote and extraction tables, enabling seamless app development.
- Flexible app building options with multiple ServiceNow builders tailored to different developer skill levels.
- Improved data workflows by pulling data directly from third-party sources when possible.
- Reduction of legacy ERP code after successful migration, maintaining a cleaner system environment.
After you use ERP Semantic Mining to identify legacy ERP (Enterprise Resource Planning) candidates, use additional ServiceNow AI Platform products and resources to replatform your app.
First, identify the customization you want to replatform from the ERP system with ERP Semantic Mining.
Then, use the remote tables and extraction tables linked in the candidate mining results for fast access to ERP data.
That ERP data can be used as a data source when you build new apps on the ServiceNow AI Platform, for example, with ServiceNow Studio.
Build a ServiceNow app that consumes ERP data
The next step in replatforming with ServiceNow Studio for ERP (Enterprise Resource Planning) is to build an app on the ServiceNow AI Platform that consumes the ERP data.
As you plan to replatform a legacy app on the ServiceNow AI Platform, consider where the data is coming from. For example, an old app may retrieve data from a third party into the system of record. When you build a new, replatformed app on the ServiceNow AI Platform, you can configure the new app to pull data directly from that third party. Using that method, the Zero Copy Connector for ERP model no longer pulls the data from the ERP system, which adds an extra step of retrieval.
Working with similar candidates when replatforming apps
If ERP Semantic Mining shows that a candidate has a number of similar candidates, consider building one app that meets the needs of some or all similar candidates when you replatform.
When you replatform a custom app from the system of record, you don't have to replicate the old app exactly. Use the replatforming process to design a better app. For example, an app that addresses the needs of multiple similar candidates in a single, new app built using low-code tools on the ServiceNow AI Platform. ServiceNow Studio is the quickest app to use, but there are other builders available to you, depending on your licensing.
ServiceNow low- and pro-code builders
After you identify ERP data to replatform, citizen developers can use ServiceNow builders to create apps quickly from the data. Any custom fields that exist in the ERP system of record, such as SAP, can be leveraged by the apps you build using the ServiceNow AI Platform. For more on citizen development, see Exploring Delegated Development.
For example, use in ServiceNow Studio, use a template (or build the app from the ground up) and incorporate remote tables using ERP models and remote tables. You can combine legacy data from the ERP models and remote tables with other ServiceNow data in tables.
Using Glide to query ERP data
You can also access data from the system of record through the Glide API.
For more information, see Sample Glide query for ERP data in ERP Semantic Mining.
After you replatform custom code to a ServiceNow app
Replatformed apps on the ServiceNow AI Platform use live data from the system of record without writing any code back to it.
After you have identified candidates to replatform and taken the recommended action in ERP Semantic Mining, you must only use Zero Copy Connector for ERP to access the remote tables and extraction tables. These tables are data sources for building apps, flows, and workspaces.
If you're sure that legacy code on the system of record isn't referenced elsewhere, you can remove it from the system after it's replatformed.