Highlight
Successful together – our valantic Team.
Meet the people who bring passion and accountability to driving success at valantic.
Get to know us
FAQs
SAP Service and Asset Manager (SSAM)
The following FAQs are based on the most frequently asked questions asked during our webinars on SAP Service and Asset Manager. They provide a concise overview of the aspects that participants are particularly interested in.
Webinar | Optimize your mobile processes with SAP Service and Asset Manager
Learn more about the new features and benefits of SAP Service and Asset Manager—look forward to new ideas, smart solutions, and a clear view of the future! Learn more!
To the webinar recording
To the webinar recording
For work permits, the configurations must be carried out both in the backend and in MAIF for SAP Service & Asset Manager. The illustration in SSAM can also be viewed in the SAP demo.
Yes, scanning QR codes is also supported in SAP Service & Asset Manager.
The maintenance technician can carry out the checklists created in the backend on SAP Service & Asset Manager and record the results. It is not possible in the standard system to create the checklist (QM) from SAP Service and Asset Manager in a troubleshooting order. Here you can see the various forms from our demo.
When logging in to SSAM, external technicians are authenticated via the same IDP as FSM using SAP BTP Mobile Services.
For more information: community.sap.com/t5/enterprise-resource-planning-blog-posts-by-sap/sap-service-and-asset-manager-integration-with-fsm-crowd-service-for/ba-p/14020377
The phase model is supported for “Emergency Work Notifications” on SAP Service & Asset Manager.
No, technical objects are supported in the Windows version of SAP Service and Asset Manager.
For more information about the functionalities of SSAM in the Windows version:help.sap.com/docs/SAP_SERVICE_ASSET_MANAGER_WINDOWS/06ac7c6ba5c74a0fa3b85a77900c8f6b/13b1b33cb5944c89b5819cd7038ac6fe.html
The only information available about the new version comes from the last keynote speech. The final name of the version will depend on the release date. We have summarized the planned priority features in our “Outlook” slide.
Data synchronization is one of the biggest challenges associated with offline functionality, as it is necessary to define in advance which specific data should be loaded onto the SSAM so that the amount of data to be synchronized is limited and the synchronization time remains acceptable.
The rapid development of SSAM also poses challenges. With each update or new version, new functionalities are added. Accordingly, there is also potential for new bugs. For this reason, it is important to establish a structured error analysis at the beginning of the project so that errors can be corrected.
There are two aspects to consider here:
1. Offline functionality: If your company needs a mobile solution that can also be used offline, then SSAM is the right choice for you.
2. Functional requirements: First of all, you should define which processes/functions the mobile application should solve or serve. This will allow you to analyze which SAP mobile solution would be suitable for your company.
1. Early collaboration between Moduler and developers is beneficial. Developers are usually involved later on, but it makes sense to involve them very early in the project, as they also provide input on the entire process.
2. Early involvement of the specialist department (employees), as they know and live the current processes. Based on this, the processes can be modified and optimized. Often, the specialist department is brought in too late, which means that processes have to be revised. Involving the specialist department in the development of solutions plays a major role in acceptance in the change management process.
SAP Service & Asset Manager has already been introduced and implemented at several customers in the GMP environment, and no problems regarding validation capability have arisen.
Normally, data is not lost if synchronization fails. It is still stored locally on the mobile application. However, there are also special cases, e.g., if two employees want to make a “final confirmation” for a process and synchronize it at the same time, an error message will appear. In this case, the data (in this case, the feedback) is deleted and the employees would have to enter the feedback again. Such cases must be resolved organizationally.
The usage decision can also be made on the mobile device. This function is disabled by default and is only possible in the backend (GUI/Fiori). Depending on requirements, it can be enabled for mobile processing.
No, that should not be confused. The SAP Fiori Launchpad is the entry point to all SAP Fiori applications, including different modules (Finance, Controlling, PM, MM, etc.). Each user only sees the applications assigned to them. SAP Service & Asset Manager is an SAP product with a primary focus on maintenance. This means that users “only” have access to maintenance functions and the maintenance processes selected for their company in the app.
The application is basically designed as an offline application. Some areas can be “online,” such as material searches and inventory displays. Furthermore, SAP now allows certain objects to be exchanged automatically or assigned a “trigger.” This means that messages can be synchronized without manual intervention as soon as the status or other information has changed.
If the question relates to the Service & Asset Manager, it certainly depends on the scope of the processes and the requirements. Roughly speaking, however, it takes at least 3, but more likely 6 months from start to implementation. We tend to have longer projects and many customization requests from customers. Accordingly, the projects are also longer and a go-live is sometimes divided into phases in order to start with the most important functions early on.
