Understanding "My Processes" and "My Requests" in SBPA: Empowering Users Through Clarity and Control

[Beneeta]

SAP Build Process Automation is a low-code/no-code platform by SAP that enables businesses to automate workflows and business processes quickly and with minimal programming effort. 

As organizations increasingly adopt automation to streamline business workflows, user-centric features become essential for both transparency and efficiency. Two key views that support this in SAP Build Process Automation are: 
“My Processes” 
“My Requests” 

While they may sound similar, they serve distinct purposes in helping users and teams monitor and interact with automated processes. Let’s explore what they are, why they matter, and how they enhance the overall automation experience. 

Problem Statement: 

As organizations adopt workflow automation to streamline operations, users often struggle to track and manage their interactions with automated systems. Despite automation improving execution speed and consistency, lack of transparency and user feedback remains a major issue. 

 

The Problem: 

Users currently lack intuitive, centralized views within SAP Build Process Automation that clearly separate and present (a) the complex end-to-end business processes they participate in and (b) their individual service or task requests—leading to confusion, inefficient follow-ups, and reduced trust in automation. 

This results in: 

• Uncertainty about the current status of submitted requests (e.g., approvals, service tickets, form submissions) 
• Inability to monitor progress or identify delays in multi-step business processes 
• Increased support queries to help desks or process owners asking for updates 
• Low adoption or engagement with self-service automation tools due to poor visibility 

Why It Matters: 

• Business users need a “My Requests” view to track simple, individual submissions quickly. 
• Power users or process participants need a “My Processes” view to monitor end-to-end workflows they’re involved in or responsible for. 

The Need: 

There is a clear need for two distinct, yet complementary, views: 

• “My Requests” – to provide users with a simple interface for tracking their personal submissions and their current statuses. 
• “My Processes” – to allow users to oversee, participate in, and manage the lifecycle of complex, automated workflows. 

What are "My Processes" Views? 

“My Processes” application is dedicated to Process Participants like Approvers for example. This application would help the Process Participants easily track, understand, and make informed decisions about where their input is needed and how it fits into the larger process.   

Key Use Cases: 

• Tracking the status of an employee onboarding process 
• Monitoring a multi-level purchase approval 
• Managing a customer service workflow 

Benefits: 

• Real-time insight into the process lifecycle 
• Accountability by showing who is responsible for each task 
• Faster issue resolution when processes stall or bottleneck 
• Ideal for process owners, managers, and workflow participants 

What are "My Requests" Views? 

"My Requests” View provides clarity to the Requestors on how their request fits into the workflow, the status of their request, and what actions (if any) they need to take as their request moves through the approval or fulfilment process.   

Key Use Cases: 

• Viewing a submitted IT support ticket 
• Checking status of a travel reimbursement 
• Tracking a leave request form 

Benefits: 

• Self-service tracking—no need to email or call for updates 
• Simple, clean interface focused on the user's submissions 
• Encourages user engagement with automation without needing to understand complex workflows 

Key Differences 

Feature	My Processes	My Requests
Focus	Entire process lifecycle	Individual request status
User Role	Participant or process owner	Requester or submitter
Complexity	Often involves multiple steps	Usually single or few steps

Prerequisites 

Here are a few Prerequisites for My Processes and My Requests View. 

Let’s explore the configuration details:

Configure My Processes Application 

Configure My Requests 

Now that both My Requests and My Processes tiles have been configured, let’s look at how we can visualise them: 

Entry Screen: 

My Requests view provides an overview of at all the requests initiated by you based on the filter criteria. You also have the possibility to look at the details of each request individually, the stage at which the request currently is in, the history of the previous steps, the status of the steps and the details of the approvers. You also have the possibility to look at all the tasks under a sub-process step (even if there is a hierarchy) and gain insights, without moving away from the lead process and much more. 

 My Requests

My Processes application provides an overview of all the processes that you have been given access to. You can also have a look at details of individual process instances and have the same capabilities as in “My Requests” view.  

 My Processes

Additional Key features are listed here. 

Conclusion 

As more businesses embrace automation, features like “My Processes” and “My Requests” ensure that automation remains accessible, visible, and actionable. By making it easier to track, monitor, and engage with automated processes, SAP Build Process Automation delivers not just technical power—but real business value. 

More Information: 

Configure My Processes Application 

Configure My Requests 

Use My Processes Application 

SAP BTP Innboytes blog post

This is only the beginning - stay tuned!