cancel
Showing results for 
Search instead for 
Did you mean: 
Read only

How to report trivial issues to SAP?

ron_meesters2
Explorer
0 Kudos
288

Most of the time, software issues in SAP R/3, are solved by SAP whenever a customer reports this issue. The customer has to report this because it's an issue with some priority. Though lots of issues are reported by consultancies at assignment. They are able to report an issue because their customer assignes the priority. So far so good...

But what if a consultant would like to report an issue for which the customer doesn't assign priority because it's annoying but not relevant for their current project...

For example: how to report an issue with SQ03 which dumps because of a software error?

SQ03 isn't classified as being business critical... But it dumps whenever some trivial setting isn't set.

Each time it occurs to you, you have to dig in your memory what it was all about, look in your notes to discover that it's an perpetual software issue which will never be solved by SAP because there is no business driven need to report it.

And if it's not reported to SAP, you can't find any notes related to this annoying but not business relevant issue.

What SQ03 concerns... if the setting 'Display system objects' isn't set, SQ03 will dump with a MESSAGE_TYPE_X runtime error whenever you want to create or delete a user group. You always have to make sure to set this single setting to prevent runtime errors...

Translations (to Dutch) of the settings in SE16 do have the same kind of destiny, because there is no business driven need of the customer these trivial issues will stay in the software of SAP ... forever...

How to report this kind of trivial issues by consultants which are destined to live with SAP software?

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi,

I completely agree with you. There are a lot of bugs in administration transactions which have been known for years and which seem that they will be never corrected by SAP because there is a workaround and it is possible to "live with it".

An exemple : the controls for system parameters in RZ10 : they are so obsolete that you have to know which errors are "true" errors and which errors are "real" errors. All new system parameters created since 6 or 7 years are not known by RZ10 and displayed as "error : unknown parameter"....

You spoke about translations. they are so bad and even wrong in French for admin transactions that I always logon with English.

It wouls be so easy for SAP to get the system much better and so nicer to work with...

Regards,

Olivier

Former Member
0 Kudos

Whenever I encounter any issue at a customer project site, I still report it using oss with low priority. Althought does not affect customer directly, it does hinder my job which is to support or implement stuff for customer. SAP eventually do look at these issues and if we are lucky, they will resolve it before the message auto closes.