Skip to Content
Technical Articles
Author's profile photo Zack Frazier

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

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.

SAP%20Service%20and%20Asset%20Manager%20start%20screens%20for%20Field%20Service%20Technician%2C%20Maintenance%20Technician%2C%20and%20Inventory%20Clerk%20personas

SAP Service and Asset Manager start screens for Field Service Technician, Maintenance Technician, and Inventory Clerk personas

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.

Usage Types

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
Inventory Clerk Standard
Custom Professional

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
Persona II Standard
Persona III Standard
Custom Professional

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

User assignments

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.

Determination logic

The system determines persona based on the following logic and sequence.

System Administration & Monitoring Portal

Users may be assigned to one or more personas in the admin portal, launched in SAP GUI with tcode /n/syclo/admin. This is first considered to determine a user’s persona. If a persona is assigned here, we will not do further checks.

System%20Administration%20and%20Monitoring%20Portal%20/%20Administration%20/%20User%20Management

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:

Persona Authorization Object
Maintenance Technician /MERP/SMT
Field Service Technician /MERP/FST
Inventory Clerk /MERP/SIC

Customers need to create custom role(s) and assigned authorization object(s) accordingly based on their own business and security needs.

Default persona

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 /n/SYCLO/CONFIGPANEL.

Mobile%20Application%20Integration%20Framework%20Configuration%20/%20Mobile%20Application%20Configuration%20/%20SAP_SERVICE_ASSET_MANAGER_2205%20/%20Application%20Persona

Mobile Application Integration Framework Configuration > Mobile Application Configuration > SAP_SERVICE_ASSET_MANAGER_2205 > Application Persona

Feature assignments

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.

Application level

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.

Mobile%20Application%20Integration%20Framework%20Configuration%20/%20Mobile%20Application%20Configuration%20/%20SAP_SERVICE_ASSET_MANAGER_2205%20/%20Features

Mobile Application Integration Framework Configuration > Mobile Application Configuration > SAP_SERVICE_ASSET_MANAGER_2205 > Features

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.

Persona level

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.

Mobile%20Application%20Integration%20Framework%20Configuration%20/%20Component%20Assignments%20/%20SAP_SERVICE_ASSET_MANAGER_2205%20/%20User%20Personas

Mobile Application Integration Framework Configuration / Component Assignments / SAP_SERVICE_ASSET_MANAGER_2205 / User Personas

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.

Performance calibration

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.

oMDO Assignment

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.

Mobile%20Application%20Integration%20Framework%20Configuration%20/%20Component%20Assignments%20/%20SAP_SERVICE_ASSET_MANAGER_2205%20/%20oMDO%20Assignment

Mobile Application Integration Framework Configuration / Component Assignments / SAP_SERVICE_ASSET_MANAGER_2205 / oMDO Assignment

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.

Mobile%20Application%20Integration%20Framework%20Configuration%20/%20Component%20Assignments%20/%20SAP_SERVICE_ASSET_MANAGER_2205%20/%20xChange%20Object%20Assignment

Mobile Application Integration Framework Configuration / Component Assignments / SAP_SERVICE_ASSET_MANAGER_2205 / xChange Object Assignment

You may also modify the active objects individually using the exchange object configuration.

Mobile%20Application%20Integration%20Framework%20Configuration%20/%20Exchange%20Object%20Configuration%20/%20Mobile%20Application%20Filter%3A%20SAP_SERVICE_ASSET_MANAGER_2205%20/%20Exchange%20Object%20By%20Application%20Area%20/%20Technical%20Settings

Mobile Application Integration Framework Configuration / Exchange Object Configuration / Mobile Application Filter: SAP Service and Asset Manager 2205 / Exchange Object By Application Area / Technical Settings

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.

Fine-tuned calibration

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.

Mobile%20Application%20Integration%20Framework%20Configuration%20/%20oData%20Model%20Configuration%20/%20Mobile%20Application%20Filter%3A%20SAP%20Service%20and%20Asset%20Manager%202205%20/%20oData%20Model%20Entity%20Type%20List%3A%20SAP_SERVICE_AND_ASSET_MANAGER_2205%20/%20%28Entity%20Type%29%20/%20EntitySet

Mobile Application Integration Framework Configuration / oData Model Configuration / Mobile Application Filter: SAP Service and Asset Manager 2205 / oData Model Entity Type List: SAP_SERVICE_AND_ASSET_MANAGER_2205 / (Entity Type) / EntitySet

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.

Mobile%20Application%20Integration%20Framework%20Configuration%20/%20oData%20Model%20Configuration%20/%20Mobile%20Application%20Filter%3A%20SAP%20Service%20and%20Asset%20Manager%202205%20/%20oData%20Model%20Entity%20Type%20List%3A%20SAP_SERVICE_AND_ASSET_MANAGER_2205%20/%20%28Entity%20Type%29%20/%20Association%20and%20Set%20List

Mobile Application Integration Framework Configuration / oData Model Configuration / Mobile Application Filter: SAP Service and Asset Manager 2205 / oData Model Entity Type List: SAP_SERVICE_AND_ASSET_MANAGER_2205 / (Entity Type) / Association and Set List

Dependency Object

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.

Mobile%20Application%20Integration%20Framework%20Configuration%20/%20oData%20Mobile%20Data%20Object%20Configuration%20/%20Mobile%20Application%20Filter%3A%20SAP%20Service%20and%20Asset%20Manager%202205%20/%20oData%20Mobile%20Data%20Object%20List%3A%20SAP_SERVICE_AND_ASSET_MANAGER_2205%20/%20%28oData%20Mobile%20Data%20Object%29%20/%20Dependent%20Object

Mobile Application Integration Framework Configuration / oData Mobile Data Object Configuration / Mobile Application Filter: SAP Service and Asset Manager 2205 / oData Mobile Data Object List: SAP_SERVICE_AND_ASSET_MANAGER_2205 / (oData Mobile Data Object) / Dependent Object

EFI configuration

An Enhancement Framework Implementation (EFI) event handler can be assigned to a feature with active flag set to By Feature.

Mobile%20Application%20Integration%20Framework%20Configuration%20/%20EFI%20Assignment%20/%20Mobile%20Application%20Filter%3A%20SAP%20Service%20and%20Asset%20Manager%202205%20/%20Enhancement%20Implementation%20Includest%3A%20SAP_SERVICE_AND_ASSET_MANAGER_2205%20/%20%28EFI%20Include%29%20/%20Assignment

Mobile Application Integration Framework Configuration / EFI Assignment / Mobile Application Filter: SAP Service and Asset Manager 2205 / Enhancement Implementation Includest: SAP_SERVICE_AND_ASSET_MANAGER_2205 / (EFI Include) / Assignment

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.

Additional details

Entity Types

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.

UserFeature

In the /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.Mobile%20Application%20Integration%20Framework%20Configuration%20/%20Mobile%20Application%20Configuration%20/%20SAP_SERVICE_AND_ASSET_MANAGER_2205%20/%20Parameters

Mobile Application Integration Framework Configuration / Mobile Application Configuration / SAP_SERVICE_AND_ASSET_MANAGER_2205 / Parameters

UserPersona

In the MERP/SAP_ONLINE_LOOKUP_EXT_2210 service and /MERP/SAP_SRV_ASSET_MANAGER_2210 service, this entity returns user persona assignment.

UserSyncGroupDetail

In the /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
In-Scope Default-Enabled In-Scope Default-Enabled In-Scope Default-Enabled
CA_ATTACHMENT Attachment support on business objects – DMS/BDS/GOS Y Y Y Y N
CA_AUTO_SYNC Auto-sync capability Y N Y N Y N
CA_BILL_OF_MATERIAL Bill of Material for technical objects Y N N N
CA_BUSINESS_PARTNER Business Partner Y N Y Y N
CA_CLASSIFICATION Classification and characteristics for technical objects Y Y N N
CA_CORE_DATA Core data including org structure, such as Plant, Work Center etc. Y Y Y Y Y Y
CA_CREATE_TECH_OBJECT Create equipment and functional location Y Y N N
CA_CREW_MANAGEMENT Crew management Y N N N
CA_DIGITAL_SIGNATURE Digital Signature Y N N N
CA_GEOSPATIAL_INFO_SERVICE GIS support for ESRI ArcGIS and GEF Y Y Y Y N
CA_GIS_ADD_EDIT Create/update of geospatial data Y Y N N
CA_LOCATION_UPDATE User location tracking Y N Y N N
CA_NO_HISTORY Notification history Y Y Y N N
CA_SERVICE_REPORT PDF Service report generation Y N Y Y N
CA_SIGNATURE_CAPTURE Signature (physical) capture as Image Y N Y Y N
CA_TECH_OBJECT Equipment and Functional location master data Y Y Y Y N
CA_WO_HISTORY Work Order history Y Y Y N N
CS_EXPENSE_REPORT Expense reporting Y N Y Y N
CS_MILEAGE_REPORT Mileage reporting Y N Y Y N
CS_NOTIFICATION Service Notifications N Y Y N
CS_SERVICE_ORDER Service Orders N Y Y N
EAM_CHECKLIST EAM Checklist Y N N N
EAM_EVENT_PRIORITY_MATRIX EAM Event Prioritization Y N N N
EAM_PHASE_MODEL Phase model Y N N N
FOW_ROUTE Field Operations Worker component Y N N N
FSM_SCHED_INTEGRATION FSM integration Y N Y N N
HR_TIMESHEET CATs timesheet Y N N N
IAM_CHECKLIST ASPM Checklist Y N N N
IAM_INDICATORS PdMS indicators Y N N N
ISU_METER_MANAGEMENT Meter Management component Y N N N
MM_GOODS_ISSUE Goods issue for Inventory management N N Y Y
MM_GOODS_RECEIPT Goods receipt for Inventory management N N Y Y
MM_MATERIAL_DATA Material master data Y Y Y Y Y Y
MM_PHYSICAL_INVENTORY Physical Inventory N N Y Y
MM_STOCK_LOOKUP Stock lookup by plant and storage location Y Y Y Y Y Y
MM_STOCK_TRANSFER Stock Transfer N N Y Y
MM_TECHNICIAN_GOODS_ISSUE Goods issue for planned materials on work order Y Y Y Y N
MM_VEHICLE_STOCK Vehicle Stock Y N Y Y N
PM_ASSEMBLY Equipment Assembly Information for work order Y Y N N
PM_CLOCK_IN_CLOCK_OUT Clock in – Clock out Y N N N
PM_CONFIRMATION PM Confirmations for time recording Y Y Y Y N
PM_INSTALL_DISMANTLE Equipment install and dismantle Y Y N N
PM_LINEAR_ASSET_MANAGMENT Linear Asset Management Y N N N
PM_MEASUREMENT Measurement readings Y Y N N
PM_NOTIFICATION PM Notifications Y Y N N
PM_OBJECT_LIST Object Lists on work orders Y Y N N
PM_PRT Production, Resources and Tools Y Y N N
PM_SUPERVISOR_MODE Supervisor mode Y N N N
PM_WORK_ORDER PM Work Orders Y Y N N
QM_CALIBRATION Calibration Orders and Inspection Lots Y N N N

Wrap up

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.

Assigned Tags

      14 Comments
      You must be Logged on to comment or reply to a post.
      Author's profile photo Michael Haydock
      Michael Haydock

      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?

      Author's profile photo Vivian Chong
      Vivian Chong

      Are you using SAP Asset Manager 2110?

      Author's profile photo Michael Haydock
      Michael Haydock

      Yes

      Author's profile photo Vivian Chong
      Vivian Chong

      Development team has provided this note to update the in-scope flags in SAM 2110 configuration.

      https://launchpad.support.sap.com/#/notes/3230572

      Author's profile photo David Raymond
      David Raymond

      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".

      Author's profile photo Syam Yalamati
      Syam Yalamati

      Hi David,

      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.

      Thanks

      Syam

      Author's profile photo David Raymond
      David Raymond

      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.

      Author's profile photo Syam Yalamati
      Syam Yalamati

      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.

      Thanks

      Syam

      Author's profile photo David Raymond
      David Raymond

      Thank you, Syam.  You can reference SAP Incident 568764 / 2022.

      Author's profile photo Syam Yalamati
      Syam Yalamati

      Hi David, the following SAP note was released to fix this issue, we will update the incident with proper details.

      https://launchpad.support.sap.com/#/notes/3235407

      Thanks

      Syam

      Author's profile photo Juan Forero
      Juan Forero

      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,

      Author's profile photo James Murphy
      James Murphy

      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.

      Author's profile photo Juan Forero
      Juan Forero

      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?

      Author's profile photo James Murphy
      James Murphy

      Hi Juan,

      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:
      https://blogs.sap.com/2022/06/16/sap-service-and-asset-manager-2205-now-available-whats-new/#:~:text=SAP%20mobile%20applications%20are%20being%20updated%20to%20the%20SAP%20Fiori%20Horizon%20theme

      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.

      -James
      SAP Premium Hub CoE - Senior Support Consultant.