Manage Maintenance Notifications (F5777) is the next-generation app for the maintenance notification lifecycle consolidating what previously required multiple apps — from creating a maintenance notification to screening, editing, accepting, and creating a maintenance order.
The same app is expected to be used by people with different responsibilities during maintenance execution, but not everyone using F5777 should be able to do the same things within it. This is exactly where authorization control can be achieved by App Authorization Variants (AAVs).
This blog focuses on the different App Authorization Variants for Manage Maintenance Notifications (F5777) app and how they can be leveraged for different roles. To know the fundamentals of App Authorization Variants, please refer to these blogs- SAP S/4HANA Cloud Public Edition 2502: Flexible Business Role Design with App Authorization Variants and Precise Control of Fiori App Access with the App Authorization Variants.
The 4 AAVs of Manage Maintenance Notifications (F5777)-
Each App Authorization Variant corresponds to a persona and defines what that persona can do inside the app.
AAV | Persona | Key Capability |
F5777_EMP_TRAN | Maintenance Employee or Maintenance Technician | Create maintenance notification; edit only on request. |
F5777_MPL_TRAN | Maintenance Planner | Employee access along with Assign/Create maintenance orders for notifications. |
F5777_TRAN | Maintenance Supervisor | Full notification lifecycle except for Order creation/assignment — create, screen, accept, edit throughout. |
F5777_EXCP_TRAN | Operator | Employee access along with creation of Emergency work and Minor work. |
Let us look at each one.
1. F5777_EMP_TRAN | Maintenance Employee | SAP_EAM_BC_MN_MNG_EMP_PC
This variant is designed for maintenance employees or maintenance technicians who spot issues and raise them in the system.
A user with this AAV can create maintenance notifications and read all notification types. However, their ability to edit is limited. They can only edit a notification when:
- The notification is moved to an “Action Required” subphase,
AND - Creator or the User is the or the designated Person Responsible for that notification.
This AAV is part of the standard role template SAP_BR_EMPLOYEE_MAINTENANCE, belonging to business catalog SAP_EAM_BC_MN_MNG_EMP_PC.
Using the standard role template SAP_BR_EMPLOYEE_MAINTENANCE may enable ‘Set Deletion flag' for the user due to additional business authorization coming from other catalogs in the role template.
Fig 1: Actions enabled for employee when notification is in Action Required subphase
2. F5777_MPL_TRAN | Maintenance Planner | SAP_EAM_BC_MN_MNG_MPL_PC
This AAV enables the maintenance planner to create notifications and allows to create or assign maintenance orders for accepted notifications. The Edit authorization is same as in F5777_EMP_TRAN AAV. This variant even allows user to delete and complete the notification.
Fig 2: List report view for user with AAV F5777_MPL_TRAN
Fig 3: Object page view when notification is created
Fig 4: Create and Assign Order enabled for accepted maintenance notification
The variant F5777_MPL_TRAN is part of standard role template SAP_BR_MAINTENANCE_PLANNER, belonging to business catalog SAP_EAM_BC_MN_MNG_MPL_PC.
This role template gives additional authorizations to the user as compared to the App Authorization Variant F5777_MPL_TRAN such as- Creation of minor/emergency work, accepting, and editing the maintenance notification.
Fig 5: Additional actions enabled in standard planner role template for submitted maintenance notification
3. F5777_TRAN | Maintenance Supervisor | SAP_EAM_BC_MN_MNG_PC
A user assigned with this AAV can work with notifications across all phases — from the moment a notification is raised to when it is completed. They can create, view, screen, accept, reject, and edit maintenance notifications. Editing is not phase-restricted; the supervisor can update a notification whether it is unscreened, in action-required state, or already accepted. The user can’t create or assign maintenance order for accepted notifications with this AAV.
Fig 6: Object page view for user with F5777_TRAN AAV when a notification is created
This AAV is part of the standard role template SAP_BR_MAINT_SUPERVISOR, belonging to business catalog SAP_EAM_BC_MN_MNG_PC.
Unlike the AAV F5777_TRAN, the standard role template SAP_BR_MAINT_SUPERVISOR offers the user to even create or assign maintenance order for accepted notifications due to additional authorizations from other business catalogs in the role template.
Fig 7: Additional actions enabled in standard supervisor role template for accepted maintenance notification
4. F5777_EXCP_TRAN | SAP_EAM_BC_MN_MNG_PC
This variant gives a user maintenance employee-level access combined with an expanded emergency and minor work creation authorization for maintenance notifications — beyond what F5777_EMP_TRAN allows, but without the screening scope of F5777_TRAN.
This is the most nuanced of the four, and it exists for a very specific real-world situation – the Operator role.
The operator use case, addressed by F5777_EXCP_TRAN, is a good example of the kind of real-world role complexity that AAVs are designed to handle — cleanly, within the standard SAP authorization model.
Fig 8: Maintenance employee access extended with create minor and emergency work.
Note: The maintenance employee can be restricted to creating either emergency work or minor work along with standard maintenance notification by maintaining restrictions in the role assigned to the user. The restriction should be applied for ‘Maintenance Notification Processing Context' to support either of the options-minor or emergency.
Fig 9: Restriction applied for Emergency Work (01)
Fig 10: User can only create emergency and standard maintenance notifications
This is a small example of how a single app can serve very different personas through AAVs — each variant reflecting a specific set of responsibilities without over- or under-provisioning access.
You can see AAVs give you more precise control over authorizations, but as an admin, while designing roles, you should also consider what additional dependencies should be added to the role apart from the dependencies already proposed when adding an AAV.
Source link