About versions for mobile agentry apps (SAP Inventory Manager )

[mcg2607]

Hello,

Long time no posting here! Well, I have a question and I need help from the community.

I know the agentry app SAP Inventory Manager 4.0 is out of Mainstream maintenance, but I was wondered if this version is compatible with SAP Mobile Platform 3.1.x OnP version?

I think the answer is no and the person have to upgrade the app version to at least SAP Inventory Manager 4.3 if they want to stay in an all OnP landscape (mobile server y backend server), but I want to confirm this with the experts. Thanks in advance for the help

Best regards,

Mariana

[oliver_kaluscha3 · Accepted solution]

Hi Mariana,

are you aware of the end of maintenance of SMP 3.1? Looking at SAP PAM for that product, it has only maintenance until 30.11.2022 - so roughly in 8 months you need to switch to a non prem solution anyway as we have been told in a different project by SAP.

So before you invest a lot of time and resources into this solution, clarify your support window of SMP3.1 first.

Beside this: Chances are high that it is working fine. Testing this can be done in a few hours. We have older versions of WorkManager running with SMP3.1 and cause it is the same technology it should be fine in your case as well.

Regards,
Oliver

[oliver_kaluscha3]

Hi,

at the end the bad thing on WorkManager was always the update process. It meant basically you have to do the customization again. It helps if you have a very detailed documentation of what had been done in regards of customization last time. If the document is not available, but the original old version, than you can run a delta check and see what has been changed.

So in most cases this has to be done again in the latest version.

Means a lot of work, but slightly less than last time, cause you already have the relevant code and changes available.

So if you have to upgrade to that version to be able to run in the cloud that would be the process.

On the other hand: Did you evaluate Asset Manager? The upgrade hassle is far less due to a stable enhancement process and it covers the WorkManager processes cause you can see it as the follow up version of WorkManager. In your case you could check if it covers your needs, but before you invest in the upgrade process perhaps it makes sense to have a look.

Regards,
Oliver

[mcg2607]

Hi Oliver!!

Thank you very very much for the answer. Well, the thing is we are using inventory /warehouse manager mobile app. Its like the little brother of work manager mobile app, but focusing on warehouse activities: goods receipt, counts, goods movements with TO, etc. So I cant migrate to asset manager, I guess the only alternative that I have if I want to keep using this app, is move really quicky to cloud edition. Obviously we have to evaluate several scenarios to see which one is the better and less traumatic. The good thing is we have documented every single custom change we made to the app 🙂

Thanks for your recommendation anyway

Best Regards,

M

[mcg2607]

Hi Oliver,

Thanks for your answer. Yeap I saw that, but I also read in the migration documentation the following:

"In case of Agentry-based solutions like SAP Work Manager or SAP Inventory Manager, the migration path is to reuse the exiting application with SAP Work Manager, cloud edition or SAP Inventory Manager, cloud edition, respectively. In this case, migration is straightforward as cloud products allow running the existing, customized on-premises version on an Agentry Cloud Edition (ACE) based infrastructure. Prerequisite to this path include:

• Migrating a license to a cloud edition
• Upgrading to the latest Work Manager (6.4.1+) or Inventory Manager (4.3.1+) version before migration and stabilize it"

The thing is we have to move up from a very old version of SAP Inventory / Warehouse Manager, but we cannot go direct to cloud edition. So what I understand of you comment is: problaby we have to go to a hybrid landscape: Backend OnP + SAP Inventory Manager Cloud Edition without testing and stabilizing the service on an OnP SMP 3.1.x?

What happens If we have a lot of customization on screens? (agentry rules, add screens and other stuff) is straightforward as the documentation remarks?

Thanks in advance for your reply

Best Regards,

M