In this blog, I will outline how the SAP Situation Handling Extended Framework can be leveraged to notify Master Data Specialist when Maintenance Planner creates a maintenance objects such as Task Lists, Maintenance Plans, while implementing SAP Asset Performance Management Recommendations.
Business Value:
Operational Efficiency – Automating notifications eliminates manual follow-ups and reduces delays in master data validation.Improved Collaboration and Transparency – This integration reduces communication gaps and ensures that master data is aligned with operational needs.Optimized maintenance strategies extend asset life cycles and lower total cost of ownership.
If you want to gain a deep understanding of SAP Situation Handling – Standard Framework and SAP Intelligent Scenario Lifecycle Management, dive into my latest blog posts mentioned below.
S/4HANA Intelligent Scenario Lifecycle Management (ISLM) and Situation Handling Scenarios: Part-1 S/4HANA Intelligent Scenario Lifecycle Management (ISLM) and Situation Handling Scenarios: Part-2
let us have a look at the high level process flow of how SAP APM Recommendations integrate with SAP Situation Handling Extended Framework.
SAP APM Recommendations:
SAP Situation Handling Extended Framework:
Also, If you want to gain knowledge on SAP Signavio Process Manager & Process Collaboration Hub, please check out my blog post mentioned below. This blog provides a broad outline of process modelling.
The nuts and bolts of a well-thought-out SAP Signavio : Process Manager & Process Collaboration Hub
My Business Use Case:
In my organization, maintenance planners operationalize the SAP APM Recommendations through maintenance task list and maintenance plans. The master data specialists team ensures governance by monitoring these processes through automated notifications enabled by Situation Handling Extended Framework.
Let us first focus on the key concepts of “Situation Handling – Extended Framework” and setup a situation type-extended for a maintenance object: Task List.
Situation Object: Technical model of a business object used in situation handling. This includes CDS views, navigation targets, events, and actions.
Situation Scenario: Business scenario that builds on situation objects. There are two kinds of situation scenarios.
Object-based: Business scenario that builds on situation objects such as a Task List or a Maintenance Plan or a Maintenance Item.Message-based: Business scenario that builds on system messages from run types and reports.
As per my business use case, we will be exploring object-based situation scenarios listed below.
Situation Template: Template serves as a blueprint for creating a situation type.
Situation Type: Description of a business situation. For example, how a situation instance is triggered and who is informed about it.
Situation Instance: Instance of an exceptional issue which is displayed to the end user. It is generated according to the settings of the enabled situation type:
For Object-based situations: Whenever the conditions defined for the situation type are fulfilled.For Message-based situations: Based on the run type settings for scheduled application jobs.
When situation instances occur, specified end users see the situations in the “My Situations-Extended” app, and also receive notifications on SAP FLP, Emails.
In order to get started with the Situation Handling Extended Framework, we must first define “Responsibility Management” for our object-based situation scenarios.
Intelligent systems need to determine agents(Responsible Persons) who are automatically notified about events and who are responsible for business processes and objects.
The predefined settings in the situation template determine that the notification addresses only members of the “MAINT_MGMT” team category.
Team Information:
Responsibility Definitions and Member Function options allow us to select further filters to determine the users responsible. For Instance, let us choose Main Work Center, Maintenance Planner Group, Maintenance Planning Plant, and Maintenance Plant.
Team Owner and Team Members:
Once we have enabled the Responsibility Team, we can proceed for configuring the situation types-extended.
SAP provides the templates as listed below.
For demonstration purpose, I have used the EAM_MAINTENANCE_TASK_LIST template and created a Situation Type-Extended with an ID : Z_CAL_MAINT_TASK_LIST – Calcination Maintenance Task List.
we can provide the header information and situation instances criteria. However, the navigational actions are predefined with respect to each situation type.
The navigation actions are navigation options to business apps that can help users to solve a situation. In our business use case, we have “Find Maintenance Task List” app as a navigation action.
Now, let us define the conditions,
Mini Note: When we create a Task List via SAP APM Recommendation as part of Implement Recommendations, system creates a task list with status “1-Created” and assigns respective planning plant. So, let us consider the fields that SAP APM considers while creating a Task List.
and Batch job Scheduling parameters.
A situation Instance is created when the overall status of a maintenance task list is “Created” and situation/notification is displayed as per the predefined text template.
Now let us assign the team that was created in the earlier step.
Now let us enable the Situation Type.
Now, let us perform FMEA(Failure Mode and Effects Analysis) assessment and create a “Task List” for one of the FMEA recommendations.
For Instance, I have performed an FMEA on Equipment 10001730 (Reactor 101 DIN2816 AIE). Based on the resulting RPN score, a recommendation was created/reviewed/released for Implementation.
FMEA Assessment:
Creating a Recommendation:
Let us now use “Manage Recommendations” app to update, review, and release the recommendation.
Review:
Ready for Release:
Released:
Once the recommendations are released, maintenance planners can initiate the implementation process.
Implement Recommendations:
As part of the recommendation implementation process, maintenance planners have to update the status of the recommendation to “Implementation In Process”.
Once the status becomes “Implementation In Process”, the maintenance planner can either assign the existing task list and maintenance plan or create a new task list and maintenance plan.
Since there is no task list exists in S/4HANA for this recommendation, let us create a new task list for this recommendation.
Now, as per the conditions maintained in the Situation Type “Z_CAL_MAINT_TASK_LIST”, the system triggered the notifications.
Monitor Situations – Extended app helps us monitor situations created by the extended framework for situation handling. Monitoring Situation instances is enabled by default. We can display the activities performed for situation instances using different chart types and also as a table. To capture and show monitoring data, we must need to enable “Monitor Instances” while configuring the situation type-extended.
Let us first check the Monitor Situations – Extended app to visualize the situation instances that have been created so far.
Now, let us view the Notifications.
Option-1: We can view the notifications using “Bell Icon” on FLP screen.
Options-2: We can view notifications using “My Situations-Extended” app. Using this app, we can view all the situations as per the responsibility area.
Scenario Selection Area: The list view shows all situations. We can go to situation page for further information or close the situation directly in the list view.
Situation Page: The situation page displays the detail information of a situation as of the point in time it was created, however, this can differ from the current date.
The option “Assign To Me” : We can assign a situation to ourselves. Once we assign to ourselves, then the system updates processor details with our name. If we stop working on this situation, we can unassign ourselves and the respective situation is displayed as “Open”.
Now let us use the “Find Maintenance Task List“ app to update the task list operations.
“Find Maintenance Task List” app will navigate us to the “Change Task List” app.
Let us now update the required operations for the task list group 36 and counter 1.
Once the respective Task List is updated, we can close the situation.
😊This brings me to the end of my process walk through on how we can leverage SAP Situation Handling Extended Framework for SAP Asset Performance Management (APM) – Implement Recommendations. I hope this blog proves useful to the Maintenance Management Team. I look forward to the adoption of the Situation Handling Extended Framework as part of SAP APM implementation to improve operational efficiency.
—
Yours Sincerely,
Pardhasaradhi Reddy. Chelikam
In this blog, I will outline how the SAP Situation Handling Extended Framework can be leveraged to notify Master Data Specialist when Maintenance Planner creates a maintenance objects such as Task Lists, Maintenance Plans, while implementing SAP Asset Performance Management Recommendations.Business Value:Operational Efficiency – Automating notifications eliminates manual follow-ups and reduces delays in master data validation.Improved Collaboration and Transparency – This integration reduces communication gaps and ensures that master data is aligned with operational needs.Optimized maintenance strategies extend asset life cycles and lower total cost of ownership.If you want to gain a deep understanding of SAP Situation Handling – Standard Framework and SAP Intelligent Scenario Lifecycle Management, dive into my latest blog posts mentioned below.S/4HANA Intelligent Scenario Lifecycle Management (ISLM) and Situation Handling Scenarios: Part-1 S/4HANA Intelligent Scenario Lifecycle Management (ISLM) and Situation Handling Scenarios: Part-2 let us have a look at the high level process flow of how SAP APM Recommendations integrate with SAP Situation Handling Extended Framework.SAP APM Recommendations:SAP Situation Handling Extended Framework:Also, If you want to gain knowledge on SAP Signavio Process Manager & Process Collaboration Hub, please check out my blog post mentioned below. This blog provides a broad outline of process modelling.The nuts and bolts of a well-thought-out SAP Signavio : Process Manager & Process Collaboration Hub My Business Use Case:In my organization, maintenance planners operationalize the SAP APM Recommendations through maintenance task list and maintenance plans. The master data specialists team ensures governance by monitoring these processes through automated notifications enabled by Situation Handling Extended Framework.Let us first focus on the key concepts of “Situation Handling – Extended Framework” and setup a situation type-extended for a maintenance object: Task List.Situation Object: Technical model of a business object used in situation handling. This includes CDS views, navigation targets, events, and actions.Situation Scenario: Business scenario that builds on situation objects. There are two kinds of situation scenarios. Object-based: Business scenario that builds on situation objects such as a Task List or a Maintenance Plan or a Maintenance Item.Message-based: Business scenario that builds on system messages from run types and reports.As per my business use case, we will be exploring object-based situation scenarios listed below.Situation Template: Template serves as a blueprint for creating a situation type.Situation Type: Description of a business situation. For example, how a situation instance is triggered and who is informed about it.Situation Instance: Instance of an exceptional issue which is displayed to the end user. It is generated according to the settings of the enabled situation type:For Object-based situations: Whenever the conditions defined for the situation type are fulfilled.For Message-based situations: Based on the run type settings for scheduled application jobs.When situation instances occur, specified end users see the situations in the “My Situations-Extended” app, and also receive notifications on SAP FLP, Emails.In order to get started with the Situation Handling Extended Framework, we must first define “Responsibility Management” for our object-based situation scenarios.Intelligent systems need to determine agents(Responsible Persons) who are automatically notified about events and who are responsible for business processes and objects. The predefined settings in the situation template determine that the notification addresses only members of the “MAINT_MGMT” team category.Team Information:Responsibility Definitions and Member Function options allow us to select further filters to determine the users responsible. For Instance, let us choose Main Work Center, Maintenance Planner Group, Maintenance Planning Plant, and Maintenance Plant.Team Owner and Team Members:Once we have enabled the Responsibility Team, we can proceed for configuring the situation types-extended. SAP provides the templates as listed below.For demonstration purpose, I have used the EAM_MAINTENANCE_TASK_LIST template and created a Situation Type-Extended with an ID : Z_CAL_MAINT_TASK_LIST – Calcination Maintenance Task List.we can provide the header information and situation instances criteria. However, the navigational actions are predefined with respect to each situation type.The navigation actions are navigation options to business apps that can help users to solve a situation. In our business use case, we have “Find Maintenance Task List” app as a navigation action.Now, let us define the conditions,Mini Note: When we create a Task List via SAP APM Recommendation as part of Implement Recommendations, system creates a task list with status “1-Created” and assigns respective planning plant. So, let us consider the fields that SAP APM considers while creating a Task List.and Batch job Scheduling parameters.A situation Instance is created when the overall status of a maintenance task list is “Created” and situation/notification is displayed as per the predefined text template.Now let us assign the team that was created in the earlier step.Now let us enable the Situation Type.Now, let us perform FMEA(Failure Mode and Effects Analysis) assessment and create a “Task List” for one of the FMEA recommendations.For Instance, I have performed an FMEA on Equipment 10001730 (Reactor 101 DIN2816 AIE). Based on the resulting RPN score, a recommendation was created/reviewed/released for Implementation.FMEA Assessment:Creating a Recommendation:Let us now use “Manage Recommendations” app to update, review, and release the recommendation.Review:Ready for Release:Released:Once the recommendations are released, maintenance planners can initiate the implementation process.Implement Recommendations:As part of the recommendation implementation process, maintenance planners have to update the status of the recommendation to “Implementation In Process”.Once the status becomes “Implementation In Process”, the maintenance planner can either assign the existing task list and maintenance plan or create a new task list and maintenance plan.Since there is no task list exists in S/4HANA for this recommendation, let us create a new task list for this recommendation.Now, as per the conditions maintained in the Situation Type “Z_CAL_MAINT_TASK_LIST”, the system triggered the notifications.Monitor Situations – Extended app helps us monitor situations created by the extended framework for situation handling. Monitoring Situation instances is enabled by default. We can display the activities performed for situation instances using different chart types and also as a table. To capture and show monitoring data, we must need to enable “Monitor Instances” while configuring the situation type-extended.Let us first check the Monitor Situations – Extended app to visualize the situation instances that have been created so far.Now, let us view the Notifications.Option-1: We can view the notifications using “Bell Icon” on FLP screen.Options-2: We can view notifications using “My Situations-Extended” app. Using this app, we can view all the situations as per the responsibility area. Scenario Selection Area: The list view shows all situations. We can go to situation page for further information or close the situation directly in the list view.Situation Page: The situation page displays the detail information of a situation as of the point in time it was created, however, this can differ from the current date.The option “Assign To Me” : We can assign a situation to ourselves. Once we assign to ourselves, then the system updates processor details with our name. If we stop working on this situation, we can unassign ourselves and the respective situation is displayed as “Open”.Now let us use the “Find Maintenance Task List” app to update the task list operations.”Find Maintenance Task List” app will navigate us to the “Change Task List” app.Let us now update the required operations for the task list group 36 and counter 1.Once the respective Task List is updated, we can close the situation.😊This brings me to the end of my process walk through on how we can leverage SAP Situation Handling Extended Framework for SAP Asset Performance Management (APM) – Implement Recommendations. I hope this blog proves useful to the Maintenance Management Team. I look forward to the adoption of the Situation Handling Extended Framework as part of SAP APM implementation to improve operational efficiency. –Yours Sincerely,Pardhasaradhi Reddy. Chelikam Read More Technology Blog Posts by Members articles
#SAP
#SAPTechnologyblog
