Workaround for SAM that is not working as expected after a new client version

[SAPSupport]

Aa a workaround we need to go back to SSAM previous 2405 version.

Please, could you let us know the standard steps to use a previous SSAM version and if this procedure is going to "freeze" any further updates ?

------------------------------------------------------------------------------------------------------------------------------------------------
Learn more about the SAP Support user and program here.

[SAPSupport · Accepted solution]

Hello,

When you are using the out-of-box SSAM Client App, you can just deploy the the 2405 App metadata version to your Mobile Services endpoint using BAS / WebIDE or Visual Studio Code.

Refer to the following product documentation pages:

https://help.sap.com/docs/service-asset-manager/sap-service-and-asset-manager-installation-guide/dow...
https://help.sap.com/docs/service-asset-manager/sap-service-and-asset-manager-installation-guide/imp...
https://help.sap.com/docs/service-asset-manager/sap-service-and-asset-manager-installation-guide/dep...

You need to download the Metadata from the SAP Software Center and upload it so you can deploy it. Please see: 

Remember that, when you do the first synchronization on Version 2405 you may get an error asking to update your App. To fix this you will need to create your own client for distribution. For steps please see:

https://help.sap.com/docs/service-asset-manager/sap-service-and-asset-manager-installation-guide/sap...

About the updates question: each SSAM version will operate in parallel as an independent App on the system. So you control the metadata changes.
You also need to pay attention to the MDK version changes and compatibility, see: 2933065 - SAP Service and Asset Manager - MDK Support Matrix

Hope this helps.

Best regards,
SAP Support