SAP WM RF technology replacement - which is the best in market - ITS Mobile / Mobisys / ??

[jaycc0127]

Hello Experts,

Please note that we are working on an RF device replacement project in which we are replacing existing SAPConsole based RF devices to latest RF devices. In that direction, I am requesting feedback on below two basic but important questions:

1. What will be the better choice for RF software? One segment of our org. uses Mobisys with SAP EWM. But the present scope in hand is for ECC WM and we will upgrade to EWM in 1-2 yrs. My understanding is ITS mobile is the better option for SAP WM/EWM instead of Mobisys. However, if anyone has the experience, knowledge of comparison on these two technologies, or any other better-suited option, that will be highly appreciated.

2. Can anyone suggest a few best-of-the-breed device models?

BR,

Jayc

[verreydthans]

Hi Jacs,

Maybe this is something for you? Best is to use ITS and change the HTML template so they are responsive and can be used on every devices! 😉
https://blogs.sap.com/2021/09/13/using-fiori-as-frontend-for-sap-ewm-rf-its-screens-part-2/

Regards,

Hans

[DominikTylczyn]

Hello jayanta.chakraborty1

Ad 1. Comparing Mobisys to SAP Console / ITS Mobile is like comparing apples to oranges. SAP Console / ITS Mobile are relatively simple solutions. They purpose is grab an ABAP dynpro screen and render it as a text screen in telnet session or as a web page in a web browser respectively. They provide very few options to manipulate the screen. Of course you can style the screen with CSS if you use ITS Mobile but you can build new screens or merge existing ones. In contrast Mobisys is a full development environment for mobile enabled applications. Personally I don't have experience with Mobisys, but that's how I understand their web side information.

I'd advise not to use Mobisys unless you have very compelling reasons to. It's not like I have anything against this product - as I said, I don't know it. However I'd rather stick to SAP provided solutions, that don't incur additional licensing costs. Also if you stick to SAP Console / ITS Mobile, you can develop mobile transactions in familiar ABAP environment without the learning curve of a separate product.

Both, SAP Console and ITS Mobile can be perfectly used with EWM, LE-WM or custom developed transactions. The technology and the functionality is always the same - get ABAP screen and make it available on a RF device. It really doesn't matter what the screen does, what SAP system (EWM, ERP, S/4HANA) it is used with.

Now, about SAP Console vs ITS Mobile. In my opinion both are valid options and I wouldn't dare to tell which one is better. They are just different and have it pros and cons. In brief:

SAP Console: delivered with SAP Gui; requires telnet server installation; if a decent telnet server is used (e.g. Georgia Softworks), SAP session can be sustained if WiFi connection is lost or is battery dies; present ABAP screens in a simple, text form; telnet client needs to be installed on RF device.

ITS Mobile: integrated with NetWeaver; doesn't require additional installation; presents ABAP screens in a nice form of HTML pages; Web browser needs to be installed on RF device; to my knowledge doesn't sustain SAP sessions.

Choose the one that works for you. But stick to one solution, so it's easy to maintain.

Ad 2. Any decent model will work. It just needs to either run telnet client for SAP Console or a Web browser for ITS mobile. Decision factors here could be e.g. scanning range or protection against environmental hazards or service level provided by the supplier.

[ChristianHeck]

Hello Jayc,

we have a customer with the same issue. It is not so easy to find the right way here. At least with the selection of the mobile operating system it has become easy. For the most part, there are only devices with Android as OS.

SAP has also a clear strategy for mobile user interfaces. This is SAP UI5. For our customer, although we are a Mobisys partner, we decided to build a solution on UI5. The advantage of this is, in particular, that the customer can then switch seamlessly between new Fiori apps from SAP and their own UI5 dialogs, without having to use a different app or a different interface. This also makes sense especially if WM is used in some plats parallel to EWM in other plants. After all, it doesn't matter to the user which warehouse management system is used. However, the interface should always remain the same. For EWM we have been able to build up this solution on the existing EWM RF transactions. So the existing development could remain.

I hope my answer helps you.

Greetings

Christian