To efficiently solve your issue as fast as possible, these guidelines will help you to write a good bug report for REALTECH software.
Quick recommendations
Be precise
Be clear: explain 1) how to reproduce the situation, step by step, without leaving any room for interpretation, 2) expected behavior, 3) actual behavior. In separate sections.
Include only one specific bug or one specific feature request per task
Include any relevant links and examples
Before you do anything
Can you reproduce the issue?
Try to reproduce your bug using a recent REALTECH software version, to see whether it has already been fixed. If a bug was already fixed in a newer release, you can check our release notes HERE here.
Has someone else already reported the issue?
Use the search box of REALTECH Connect to see if your bug has already been reported, or the feature requested.
If you are unsure whether a bug has already been reported, you should report the bug. It is better to have duplicate bugs than it is to have unreported bugs.
If you report a bug, please provide the following information
Provide a short but precise description of your issue, including the steps you performed to reproduce it.
Provide your exact SAP version and REALTECH product version. For SmartChange, click here for more details.
Inform us about changes to the system prior to the bug that are not directly related to REALTECH software. For example, this may involve SAP system copies, kernel patches or changes to the infrastructure.