SAP is the leading ERP system in the world used by most of the top global companies. There are tens of thousands of customers facing the same challenge: how to optimize the support of their SAP systems.
The problem SAP developers have with incomplete bug reports
A lot of time is wasted in SAP software testing and maintenance processes due to incomplete or incorrect error reports from users and testers. Support people (analysts, developers) usually have to ask for more information about the error. This takes a lot of valuable working time from both the reporters of the error and support people. Solving the problem is often blocked until every information is available.
Some typical examples:
- Missing basic information
- Users forget to enter critical data into the error reports, for example which system is affected, which SAP transaction was running, which Sales Order has the incorrect data etc. You simply can’t start investigating the problem without information like this.
- Incorrect information entered
- Users mistype information, for example enter a wrong material number etc. This can make your developers debug for hours just to come back to the user that everything works fine. “Ooops, sorry it was Purchase Order 112000898 and not 112000989.”
- No technical information
- Users can’t add technical data, for example they don’t know how to get the program and screen number of the current transaction. This is fine, why would they be trained to know this?
- Missing attachments
- Users forget to add a screenshot, short dump or an authorization report that will be required by the support staff anyway. If you had one dollar each time your IT support asked for a screenshot or a SU53 authorization report, you’d probably read this post on your yacht in Monaco.
Also, there are so many different ITSM tools out there. In order to report an error in SAP, users have to open new browser windows to launch the ITSM tool to report the error. There of course they have to enter all data manually that may take some time. Some organizations have more than five ITSM tools implemented. Test system connected to HP Quality Center, production system connected to ServiceNow, a development project using Bugzilla. Different UIs, different processes. No wonder end-users may become confused.
The solution to improve SAP support processes
STA Ticket System provides an elegant and effective solution for all the problems listed above.
Key features are:
- Errors can be reported directly from the SAP UI (all different types: classic SAP GUI, SAP Enterprise Portal, SAP Business Client, SAP Fiori Launchpad, Webdynpro applications, CRM WebUI)
- The program creates an incident in the existing ITSM tool of your choice
- The program automatically attaches all technical information (system, program, user and authorization data) as a PDF file
- Users can add the business context using a few clicks (screen field values of the current program)
- The program attaches a screenshot, short dump and authorization report automatically (when applicable)
How does it work?
The first screenshot shows you how you can report an incident from SAP. Business Partner 331 is displayed using transaction BP. If there is any error (for example a screen field is incorrect), simply create an incident using the System menu. This is great because you don’t have to leave the current screen at all.
The following screenshots show that the main screen of STA Ticket System is displayed in a popup window. Here you can enter a short and a long description.
The lower half of the screen is a customer subscreen – a place where you can easily add your own fields. This means that if you have some custom fields defined in your existing ticketing tool, you can simply add them using your own customer subscreen. This takes maximum a few hours even for a beginner SAP developer.
Users can attach any number of files here as well that will be attached to the incident.
The next screenshot shows a very important and convenient feature of the tool. Users can add screen field contents to the ticket with a few clicks. The program lists all screen fields that are displayed on the running program and the user can simply select which ones to include. No manual typing means no typos.
When the user presses “Complete”, the program creates the incident. The next screenshot shows the incident generated by STA Ticket System. All fields are set as defined on the SAP screen. Notice the attachments added automatically (screenshot and PDF).
In this integration example with ServiceNow, we have done the following:
- Created a new Contact type (“Sent from SAP”)
- Created a new subcategory (“SAP”) under category “Software”
- Created two custom fields in ServiceNow
- Scope (Entire SAP system, Entire department, Entire team or group, Single User)
- Type (Authorization, Functional correctness, Fatal error, Performance, User Experience)
- Defined groups per SAP module, like SAP Finance, SAP Material Management, SAP Security etc.
If you are using ManageEngine ServiceDesk plus, integration can be done easily
Ticket integration with Zendesk works great
You can use even the free Spiceworks to open tickets
Here are some screenshots of the PDF document that was generated using STA Ticket System. All this information will be available for every incident your users create.
The PDF layout can be adjusted very easily by modifying the delivered SmartForm layout
Blocks of information can be hidden using customizing, there is no need to manually modify the SmartForm
Business context (screen field values) are added by the program. No manual typing required, zero chance of typos.
You can download a full PDF incident report from the following link:
An additional great function is that depending on the context of the current program, additional attachments are added to the incident.
- The program takes a screenshot automatically (must be confirmed by the user)
- An authorization report (SU53) can be added as well. Your SAP basis and security people will love this feature.
- If the current program results in a short dump (SAP’s BSOD), the program can attach it as HTML
A screenshot is taken and attached automatically to the incident.
A short dump attached as an HTML file.
An authorization report (SU53) attached as an HTML file.
You can use the product from SAP Enterprise Portal too. Simply launch it from the top of the portal or from the System menu of Transaction iViews
The program is launched from SAP Enterprise Portal and displayed in a browser.
It is easy to see how your company can benefit from integrating SAP and your existing ticketing tools using STA Ticket System.
- Reduce non-value added communication resulting from incomplete or incorrect bug reports
- Speed up debugging and maintenance tasks by providing additional information to developers
- Less system downtime can reduce losses resulting from errors in production systems
- Quicker response time and faster problem solving from SAP (OSS messages)
- Boost job satisfaction of the support staff by reducing unnecessary communication and possibly unneeded debugging
- Reduce the time needed to create an incident
- As a result of all the above, save SAP IT costs by reducing time to resolve incidents significantly
You can save a lot of time if your IT support is located far away from your end-users. Due to a big difference in time zones, often support people have to wait a whole day for some missing information. Very common for big multinational companies or for companies with outsourced IT support.
Another “danger zone” is every holiday season. If a user reports an error before leaving for a long holiday, developers won’t be able to work on the incident unless it is flawless. Forgot which SAP transaction he was using? He forgot to enter which system he was using out of the 30 the company uses? Forgot to enter which Sales Organization and Distribution channel did he use when starting the problematic report? This is how you can lose a month, degrade KPIs and fail SLAs.
For more information on STA Ticket System, please visit http://sta-technologies.com/products/ticket-system/
You can see it in action connected to ServiceNow in this video: