Create ServiceNow incidents directly from RF devices running SAP EWM
Improve SAP EWM support processes by integrating SAP and ServiceNow

Create ServiceNow incidents directly from RF devices running SAP EWM

SAP Extended Warehouse Management is becoming more and more popular as S/4HANA has it embedded since the end of 2016. One crucial part of it is the management of Radio Frequency devices.

The problem

Just like with other SAP user interfaces (SAP GUI, Fiori etc.) there are a lot of different errors that end users may face. However, reporting problems happening on RF devices is very cumbersome because of two reasons. First, it is very difficult to type in long texts on such a small device. Second, these devices are usually used within large warehouses, so if you want to report an error to a key user who has a laptop or a desktop PC, you have to walk a lot and then tell what happened.

The solution

The ITSM Connector for SAP add-on solves both problems: it allows users to create incidents in external ITSM platforms like ServiceNow, Jira etc. directly from RF devices.

How?

Let me show you. Please note that the screenshots were made in a browser window and not a real RF device, but the same is displayed on RF devices.

When you encounter an error, simply press a (configurable) key combination on the RF device.

An error is displayed on the RF screen

After pressing the key combination (for ex. Shift-F1), the ITSM Connector screen is displayed. Here the user can either choose one predefined error template (options 1-5) or create one from scratch (option 6):

Initial screen of the ITSM Connector for SAP on an RF device

If a template is chosen, the subject and long description will be prepopulated with text:

Reporting the error is super easy using preconfigured templates

The user can modify the texts if needed and then press the Send button to create the ticket in ServiceNow (or any other connected platform like Cherwell, Jira, 4me, ManageEngine ServiceDesk Plus etc.). The SAP add-on product then creates the incident and displays the incident number:

The success message with the ticket number

From here your existing incident management processes are started in ServiceNow. The end users are usually notified by email when the ticket is created, modified or closed.

Let's see how the ticket looks like in ServiceNow:

The ServiceNow ticket

As you can see, the ticket is automatically categorized and routed to the relevant team. In this case it is assigned to a support team called "SAP EWM RF", but this can be tailored to your support organization.

Additionally, the product gathers all information related to EWM and the RF device and stores it in ServiceNow (or in a PDF attachment for other ITSM platforms). You'll know the warehouse number, storage bin, RF device details, RF program information etc:

RF device and EWM environment details

Naturally all details of the last error message are saved too, so the developers can jump directly to the relevant source code section and see why this happens:

Error message details with source code position

All field contents displayed on the RF device are saved too:

Field contents with technical details

Let's check another example with an authorization problem. The user gets the error message:

Error: missing authorization

The user invokes the ITSM Connector using a key combination and now chooses the second template:

Template chosen for an obvious authorization problem

The input fields are populated again using dynamic values for the SAP user name, system ID and client number:

The error template for an authorization issue

The ITSM Connector automatically attaches the standard SU53 authorization report to the ticket, so it is easy to identify the missing authorization:

SU53 results attached to the incident

Here is the missing authorization:

The SU53 report output is saved as an HTML file

Watch it

You can watch this here:

Support of Liquid UI

If you use Liquid UI, we got you covered. Watch how it looks like on a mobile:

Prefer emails?

The ITSM Connector can be configured that it sends the error reports as emails to preconfigured distribution lists, instead of creating an incident. Check this out here:

Conclusion

The ITSM Connector for SAP product allows your EWM users using RF devices in the warehouse to conveniently create incidents in external ITSM platforms. The help desk can by bypassed by assigning the ticket to the relevant support team automatically. The support experts will have all relevant details saved to the incident, so they can focus on solving the problem instead of trying to get all details from the end user to be able to reproduce the issue.

Sharing is caring

If you like this article, please share it and subscribe to my newsletter. Additionally,?If you like my posts, please follow me?Tamás Holics?and press the????icon on my profile so you get notified about my new posts:







Debajyoti Roy

Staff Solution Consultant at Walmart Global Tech India

1 年

We have developed both way 1. Create a Service Now incident capturing Error details from EWM mobile applications. Classify and Cluster them. 2. Any Service Now ticket created for certain items catered from warehouses initiates the whole replenishment process in SAP ERP and EWM.??

回复
Daniel Achille L.

SAP Software Engineering Senior Manager

1 年

Munimadhavi Beedam

回复
Adrien C.

Sr. IT Project manager

1 年
回复

要查看或添加评论,请登录

Tamás Holics的更多文章

社区洞察

其他会员也浏览了