Configuring Features and Personas in SAP Service and Asset Manager
The SAP Service and Asset Manager 2205 release introduces many new features along with some updates to the backend configuration.
The latest release is not a new application, rather a rebranding to reflect our expanded support for persona-centric use cases encompassing maintenance, service, and inventory operations. The standard technical upgrade process employed for previous releases is still applicable for 2205.
This article will introduce the configuration options available and walks through the steps to enable/disable features and personas.
Table of Contents
- Supported scenarios
- Usage Types
- User assignments
- Feature assignments
- Performance calibration
- Fine-tuned calibration
- Additional details
SAP Service and Asset Manager 2205 is delivered with three personas — Maintenance Technician, Field Service Technician, and Inventory Clerk. The mobile application will load a different start page based on the persona assignment.
By default, all personas are available in the Mobile Application Integration Framework Configuration, a.k.a., the config panel, with
MAINTENANCE_TECHNICIAN set as the default.
Each persona is categorized by usage type, either Professional or Standard user. This determines the Full Use Equivalent (FUE) valuation according to the updated licensing model for SAP Service and Asset Manager.
Professional usage type is one (1) FUE and Standard is one-half (1/2) FUE. In the base configuration, Maintenance Technician is considered Professional, with Field Service Technician and Inventory Clerk considered Standard. Customers may also define a custom persona which is considered an Professional usage type.
It is important to note that the usage type is not necessarily specific to a persona, but rather the feature sets available. For example, a single FUE is the maximum value for any single user which allows access to all available features, meaning the Professional Use type is configured with more feature support than the Standard User usage type. More on this later.
The key difference is when a customer is using a standard Mobile Application Integration Framework (MAIF) application, e.g., SAP Service and Asset Manager, and only needs inventory or field service functionality. In this case, one (1) FUE could cover two users since those personas are Standard Use with only one-half (1/2) FUE value.
The following table depicts what usage type can be configured for different application types:
|Application Type||Persona Type||Usage Type||Changeability|
|MAIF application||Maintenance Technician||Professional||
No change allowed in customer system
Changes allowed in SAP development system only
|Field Service Technician||Standard|
Change allowed in customer system
Custom persona can be created in customer namespace only
|Partner-defined MAIF application||Persona I||Professional||Can only be changed in partner development system|
Change allowed in customer system
Custom persona can be created in customer namespace only
|Custom-defined MAIF application||Custom||Professional||
Change allowed in customer system
Custom persona can be created in customer namespace only
SAP Service and Asset Manager allows a single user to be assigned multiple personas, and she may switch between them in the Profile Settings screen of the mobile application.
Let’s look at the ways personas are assigned to a user.
The system determines persona based on the following logic and sequence.
System Administration & Monitoring Portal
Authorization objects or roles
If no assignment is found in the admin portal, the system will check authorization objects.
Each persona is associated with a pre-defined authorization object in SAP Service and Asset Manager. Customers may assign the pre-defined authorization objects to users as needed. The authorization objects are then used to determine the user persona.
These are typically assigned to a role in SAP GUI via t-code
PFCG. By default, three standard authorization objects are delivered:
|Field Service Technician||/MERP/FST|
Customers need to create custom role(s) and assigned authorization object(s) accordingly based on their own business and security needs.
Lastly, if neither of the above are found, the system will use the default persona. There must be a default persona configured; Maintenance Technician is the default in standard delivery.
Customers may update the default persona based on their business needs by selecting the default checkbox in config panel, launched in SAP GUI with tcode
Customers may turn off a feature if it is not relevant in their business scenario, regardless of the personas in use. There are two ways to do this.
The list of features delivered in SAP Service and Asset Manager are shown in the config panel. Customers may define new features in a customer namespace only.
Each feature has an Active check mark that can be toggled. This acts as the master switch across the application. Some features such as Supervisor Mode and Crew Management are disabled by default and need to be enabled if you are using this functionality.
Note that enabling a feature does mean that the customer system is qualified for the feature or no. For example, if your system does not support SAP IS-U Meter Management, but you enable
ISU_METER_MANAGEMENT in the feature list, you may see errors on the backend.
You may also toggle features related to a persona. Each persona is configured with a list of features supported in the standard delivery of SAP Service and Asset Manager.
You may view a list of features by persona in the config panel. Each feature has an In-Scope checkbox meaning that feature is allowed for that persona. In-scope features are not editable in customer or QA environments. Only in-scope items can be enabled/disabled using the Active Flag checkbox.
It is possible to enable a feature in one persona but disable the same feature in another persona. The list can be filtered using the User Persona or Application Feature Id dropdown to find the entries directly.
Note that if the feature is disabled at the application level — the master switch — the feature is still considered disabled regardless of the Active Flag status at the persona level.
During mobile client synchronization, all active data objects are sent to the mobile user. This can lead to increased sync times if data is being sent to the mobile user that is not needed by the client application.
It is important to disable the data objects that are not used in your workflow. There are several ways to accomplish this.
Each feature is associated with one or more oData Mobile Data Object (oMDO) which provides business logic for a business object used in the mobile application and is mapped to OData requests for a business object on the backend.
You may view an oMDO list in the config panel and choose which entities are required and disable the others to avoid requesting unnecessary data during the mobile sync.
Like feature assignments, the In-Scope checkmark indicates the data objects that are supported for each feature. Only In-Scope items can be enabled/disabled using the Active Flag checkbox, and In-scope features are not editable in customer or QA systems.
Exchange Object Assignment
Features may also be linked to an exchange object which combines technical objects, such as an exchange class handler, an exchange table, and a lock object, with configuration rules.
You may view an exchange object list in the config panel and choose which are required and disable the others.
You may also modify the active objects individually using the exchange object configuration.
If the exchange object is assigned to a feature, you will see the note Activation controlled by Application Feature next to the Active flag checkbox.
This control is like the master switch, if the activation is disabled here, it will be disabled in all places regardless of the active flags set in previously covered methods. However, it is also important to note that if the object is active here, but disabled by other methods, then the related exchange will not be executed when there are changes to the object. This prevents an unnecessary exchange being triggered if feature is not applicable for the customers.
Lastly, there are a few objects in configuration panel where we support activation by feature. This allows you to go further down the hierarchy to control entities, dependency objects, and such.
oData Model Entity Type
You can specify a particular entity to be enabled only if the assigned feature is activated. In the example below, the
EAMChecklistLink entity set is applicable to the Enterprise Asset Management (EAM) checklist functionality. Here only when
EAM_CHECKLIST feature is enabled,
EAMChecklistLink is available for the client.
Association and navigation
Like an entity type, association and navigation can be assigned to a feature. Only when the assigned feature is enabled, the association is then available to mobile client.
If the disabled flag is active, the object would not be visible to the mobile client regardless of whether the feature is enabled or not.
If activation by feature is configured in a dependent object, and if the assigned feature is not enabled, dependency objects will not be generated in dependency queue.
An Enhancement Framework Implementation (EFI) event handler can be assigned to a feature with active flag set to By Feature.
Note, there is a limitation here as we only support one feature assignment per object (e.g., entity type, association, navigation, EFI). Therefore, you cannot assign multiple features to the object in configuration panel.
The following entity types are introduced in SAP Service and Asset Manager 2205 to return persona- and feature-related configurations to the mobile client. The client logic looks at these entity types to check the user personas assignment(s) and to check if features are enabled. This is used on the mobile client application to determine which user interface elements should be displayed on certain screens and sections.
/MERP/SAP_ONLINE_LOOKUP_EXT_2210 service, this entity returns a list of features that are applicable based on user persona(s). With the support of UserFeature, enabled parameters are no longer defined in AppParameters.
MERP/SAP_ONLINE_LOOKUP_EXT_2210 service and
/MERP/SAP_SRV_ASSET_MANAGER_2210 service, this entity returns user persona assignment.
/MERP/SAP_ONLINE_LOOKUP_EXT_2210 service, this entity returns list of entity sets that are applicable based on user persona(s).
Feature persona matrix
You may refer to this table to see which features in the standard delivery are in-scope for each persona and see their default settings.
|Feature||Feature Description||Maintenance Technician||Service Technician||Inventory Clerk|
||Attachment support on business objects – DMS/BDS/GOS||Y||Y||Y||Y||N|
||Bill of Material for technical objects||Y||N||N||N|
||Classification and characteristics for technical objects||Y||Y||N||N|
||Core data including org structure, such as Plant, Work Center etc.||Y||Y||Y||Y||Y||Y|
||Create equipment and functional location||Y||Y||N||N|
||GIS support for ESRI ArcGIS and GEF||Y||Y||Y||Y||N|
||Create/update of geospatial data||Y||Y||N||N|
||User location tracking||Y||N||Y||N||N|
||PDF Service report generation||Y||N||Y||Y||N|
||Signature (physical) capture as Image||Y||N||Y||Y||N|
||Equipment and Functional location master data||Y||Y||Y||Y||N|
||Work Order history||Y||Y||Y||N||N|
||EAM Event Prioritization||Y||N||N||N|
||Field Operations Worker component||Y||N||N||N|
||Meter Management component||Y||N||N||N|
||Goods issue for Inventory management||N||N||Y||Y|
||Goods receipt for Inventory management||N||N||Y||Y|
||Material master data||Y||Y||Y||Y||Y||Y|
||Stock lookup by plant and storage location||Y||Y||Y||Y||Y||Y|
||Goods issue for planned materials on work order||Y||Y||Y||Y||N|
||Equipment Assembly Information for work order||Y||Y||N||N|
||Clock in – Clock out||Y||N||N||N|
||PM Confirmations for time recording||Y||Y||Y||Y||N|
||Equipment install and dismantle||Y||Y||N||N|
||Linear Asset Management||Y||N||N||N|
||Object Lists on work orders||Y||Y||N||N|
||Production, Resources and Tools||Y||Y||N||N|
||PM Work Orders||Y||Y||N||N|
||Calibration Orders and Inspection Lots||Y||N||N||N|
I hope you have found this to be a useful guide for configuring personas and features in SAP Service and Asset Manager. We welcome your comments and feedback.
Great detail, thanks. In our system none of the "In-Scope" fields are checked, which makes the configuration UI choke when we try to turn features on or off. Is this a known issue?
Are you using SAP Asset Manager 2110?
Development team has provided this note to update the in-scope flags in SAM 2110 configuration.
Nice to have this feature configuration capability. Unfortunately, in a customer system using 2205, we cannot toggle the Active checkbox for SAP-delivered application-level features. On save, the Configuration Panel errors with "Choose the key from the allowed namespace".
Are you trying to enable features with In-Scope flag active? For OOB persona set-up, you can only enable In-Scope features and other features are restricted. If you want more features than listed in the delivered persona then we will recommend setting up custom persona and activate relevant features for your scope.
Yes, we are trying to enable a feature at the application level that is "In-Scope" at the persona level. For example, the SAP-delivered QM_CALIBRATION feature has both the "In-Scope" and "Active" flags checked for the MAINTENANCE_TECHNICIAN persona (which is the default persona for the SAP_SERVICE_ASSET_MANAGER_2205 application). Yet, checking the "Active" flag for this feature at the application level and saving triggers the error "Choose the key from the allowed namespace". Further, attempting to uncheck the "Active" flag for the PM_SUPERVISOR_MODE (or any other SAP-delivered feature) at the application level results in the same error.
Hi David, we are not able to reproduce this issue in our environment and verified with other customer environment also and updates seems to be fine. Can you create a customer incident, so that we can validate the issue in customer system.
Thank you, Syam. You can reference SAP Incident 568764 / 2022.
Hi David, the following SAP note was released to fix this issue, we will update the incident with proper details.
I checked the very nice screens in the SAP mobile start (Mobile Experience Solutions from SAP) SSAM is not part of that initiative from the 16 screens is see in that link, but there is one for inventory Manager (10/16) how does SSAM integrates to all this functionality? will SSAM transition to mobile start? curious if we adquire the license to SSAM for plant maintenance how the use of Mobile start will affect our road map. Thanks,
SSAM is also following the same UX design language as SAP Mobiel Start ( making use of the SAP Fiori Horizon Theme). Giving users a similar/unified UX feel.
In that presentation, the personas/roles focus on web app capabilities launched within SAP Mobile Start.
On point 3: Key Capabilities, you note the reference to "native business applications" on the second built point. This is where you would set up SAP Mobile Start to link to SSAM. This could then launch the native SSAM mobile app from within SAP Mobile Start and then the SSAM user would carry out the more intensive maintenance work inside of the native mobile app which would have a similar UX to SAP Mobile start.
This way SAP Mobile Start is still the central native mobile entry point for the user, then based on the task, Task Center approvals, web apps, news feeds or native apps, it can either handle it inside mobile start or hand-off to the native mobile app.
Hope this answers your question.
Thanks for your explanation: but that UX is not available yet, or is it? I downloaded the Svc&Asset Mrg app from the app store, it doesn't look anything like the screens in the SAP Mobile Start screen in the slides in the website above... what is the time line for that UX to be available.. I we plan to start using SSAM in April 2023 will that UX be available then or should we retrain Techs, with the new UX at some point later?
SAP Mobile start is leading the mobile adoption of the SAP Fiori Horizon Theme, other applications from SAP are also adopting this design.
SAP Asset Manager has started this adoption in SSAM 2205, with the SAP font 72 and colour palette as well as other features from the Horizon design language. Further Design features will be adopted with each release of both SAP Mobile Start and SAP Service and Asset Manager.
See below for more details on SSAM 2205 and the SAp Fiori Horizon theme:
With regards to the timeline, I cannot comment as I'm not from the product team, this might also change under the Standard SAP disclaimer for any forward-looking statements.
SSAM is currently on a bi-yearly release plan, target releases are generally around May/June and Oct/Nov.
SSAM will be releasing its next release 2210 later this year, which should include some further UX updates. please keep an eye out and review the UX to see if it is in line with your expectations.
Please note, that SSAM is an intensive offline application which covers complex business processes and the UX is focused to support that user persona. SAP Mobile Start is more focused as the native entry point.
SAP Premium Hub CoE - Senior Support Consultant.
We are in Process of Implementation of SSAM 2205 for on Premise S4HANA 2021 FPS01 using TCI route.
During Implementation it is observed that SAM2205 is not allowing FLOC edit compare to previous version of Asset Manager i.e. 2010, 2110.
For SSAM2205 when we click on edit its only allow attachment.
Could you please confirm if the edit FLOC is no more available in SSAM 2205 or we are missing some configuration.
We are majorly concern about Edit Classification in FLOC.
Thanks & Regards