Introduction
As businesses modernise their operations, many customers are migrating from SAP Workflow Management to SAP Build Process Automation (SBPA).
This migration is a key step in digital transformation, but it also introduces challenges when processes built on different technologies need to coexist and remain visible together.
That’s where SAP’s “No Correlation” feature in Process Visibility steps in, making it possible to track legacy and new processes in a unified view, without data duplication or reporting disruption.
The Migration Challenge
During migration, organisations often face:
Technology gaps between BTP Workflow and SAP Build Process Automation [SBPA] processes.Disconnected visibility between legacy and new workflows.Reporting inconsistency when both environments run in parallel.
How “No Correlation” Simplifies Migration to SAP Build Process Automation
Let’s say you’ve exported a Visibility Scenario “Insights on Capital Expenditure Process” from SAP Workflow Management and imported it into your SBPA project and you have re-modelled the process “Capital Expenditure Scenario” in SAP Build Process Automation as shown below:
Now, both your legacy Workflow and your newly built SBPA process serve the same business purpose, but run on different technologies.
By enabling “No Correlation” feature, you can:
Create separate Process Groups for each process participant (BTP Workflow & SAP Build Process Automation Process).Use attribute mapping to unify common fields (e.g., Request Number, Employee ID etc.,).Achieve a single, unified dashboard view in the Visibility Scenario Instances app.
Step-by-Step: Applying “No Correlation” for Migration to SAP Build Process Automation
Adding Process Participants:
In your Visibility Scenario Editor, add the Newly Modelled SBPA Process as a Process Participant:
Enable the Feature:
In your Visibility Scenario Editor → General tab → Enable “Visibility Scenario to Include Non-Correlated Processes”
Create Separate Process GroupsOne for BTP Workflow from Workflow ManagementOne for SBPA Process
Both run independently but share the same business context.
Note: A default Process Group is automatically created with all the process participants. You can edit or create new ones depending on your scenario.
Map Common Attributes
Under Attributes → Context tab, map shared business fields like Request ID, CAPEX cost, or Employee ID etc.,
This ensures seamless/unified view of both legacy and SBPA processes in a single Process Visibility dashboard.
Now that we have completed the configuration, the Source attributes would appear in the Process Visibility dashboard View and the Mapped attributes would be hidden.
Business Impact
Unified Process Visibility: Track historical (BTP Workflows) and new (SBPA processes) in one view.
Smooth Migration: Maintain operational reporting continuity during migration.
No Data Duplication: Map common attributes intelligently for consistent analytics.
Future-Ready Operations: Enable co-existence between multiple automation technologies on SAP BTP.
Final Thoughts
The “No Correlation” feature acts as a bridge during migration — helping organisations maintain visibility, accuracy, and performance as they move from SAP Workflow Management to SAP Build Process Automation.
It’s a practical example of how SAP’s intelligent automation tools ensure continuity while paving the way for innovation.
With “No Correlation” feature, you can confidently modernise your process automation landscape without losing sight of your data or insights.
The result is a clean, unified view in the Visibility Scenario Instances dashboard. This allows business users to continue tracking historical and newly migrated processes together, without disrupting reporting or analytics.
IntroductionAs businesses modernise their operations, many customers are migrating from SAP Workflow Management to SAP Build Process Automation (SBPA).This migration is a key step in digital transformation, but it also introduces challenges when processes built on different technologies need to coexist and remain visible together.That’s where SAP’s “No Correlation” feature in Process Visibility steps in, making it possible to track legacy and new processes in a unified view, without data duplication or reporting disruption. The Migration ChallengeDuring migration, organisations often face:Technology gaps between BTP Workflow and SAP Build Process Automation [SBPA] processes.Disconnected visibility between legacy and new workflows.Reporting inconsistency when both environments run in parallel. How “No Correlation” Simplifies Migration to SAP Build Process AutomationLet’s say you’ve exported a Visibility Scenario “Insights on Capital Expenditure Process” from SAP Workflow Management and imported it into your SBPA project and you have re-modelled the process “Capital Expenditure Scenario” in SAP Build Process Automation as shown below:Now, both your legacy Workflow and your newly built SBPA process serve the same business purpose, but run on different technologies.By enabling “No Correlation” feature, you can:Create separate Process Groups for each process participant (BTP Workflow & SAP Build Process Automation Process).Use attribute mapping to unify common fields (e.g., Request Number, Employee ID etc.,).Achieve a single, unified dashboard view in the Visibility Scenario Instances app. Step-by-Step: Applying “No Correlation” for Migration to SAP Build Process AutomationAdding Process Participants:In your Visibility Scenario Editor, add the Newly Modelled SBPA Process as a Process Participant:Enable the Feature:In your Visibility Scenario Editor → General tab → Enable “Visibility Scenario to Include Non-Correlated Processes”Create Separate Process GroupsOne for BTP Workflow from Workflow ManagementOne for SBPA Process Both run independently but share the same business context.Note: A default Process Group is automatically created with all the process participants. You can edit or create new ones depending on your scenario.Map Common AttributesUnder Attributes → Context tab, map shared business fields like Request ID, CAPEX cost, or Employee ID etc.,This ensures seamless/unified view of both legacy and SBPA processes in a single Process Visibility dashboard.Now that we have completed the configuration, the Source attributes would appear in the Process Visibility dashboard View and the Mapped attributes would be hidden. Business ImpactUnified Process Visibility: Track historical (BTP Workflows) and new (SBPA processes) in one view.Smooth Migration: Maintain operational reporting continuity during migration.No Data Duplication: Map common attributes intelligently for consistent analytics.Future-Ready Operations: Enable co-existence between multiple automation technologies on SAP BTP. Final ThoughtsThe “No Correlation” feature acts as a bridge during migration — helping organisations maintain visibility, accuracy, and performance as they move from SAP Workflow Management to SAP Build Process Automation.It’s a practical example of how SAP’s intelligent automation tools ensure continuity while paving the way for innovation.With “No Correlation” feature, you can confidently modernise your process automation landscape without losing sight of your data or insights.The result is a clean, unified view in the Visibility Scenario Instances dashboard. This allows business users to continue tracking historical and newly migrated processes together, without disrupting reporting or analytics. Read More Technology Blog Posts by SAP articles
#SAP
#SAPTechnologyblog
