Ladies and Gentlemen of the jury, I put it to you:-
Getting an actual bug in standard SAP code fixed via the service marketplace, OSS, whatever you want to call it, is unbearable agony, with a slim chance of success.
What hope then, have we of achieving anything if I logged a call saying (for example) the message about setting structures as "cannot be enhanced" is annoying/misleading/pops up at the wrong time. It's not as if it affects the business users.
If an SAP employee read the comments to this blog, would they actually be allowed to spend the five minutes cleaning up such nonsense, or would they be too busy having to change all the circular icons to squares because it is "clearer" and then in the next release turning them all into triangles because it is "clearer" and then in the next release turning them all back into circles because it is "clearer"?
At my company we spotted some horribly inefficient database access in standard SAP code, all nested SELECTS and geometric nested loops on internal tables, and sent in a detailed proposal for improving the performance.
From the response we got back you'd thing we had called the persons grandmother a dirty old cow who works for Cynthia Payne for free.
Nonetheless as we have seen if everyone keeps the pressure on for about ten years SAP sometimes caves in. Two examples are the return f bug fixes and enhancements to SAP business workflow (which was mothballed about 2002 in the hope everyone would buy a separate software system with an extra licence from SAP to handle this) and the good old "purchase orders with multiple account assignment" chestnut where if you have a PO with two cost centres on one line the accounting postings are not quite illegal, but false accounting by any definition I learned at university. For a dozen years fixing that was "impossible" until they caved in and gave the task to an intern on their first day on the job, who forged ahead and mixed up BUKRS and WERKS and used them interchangeably . The fix worked but caused so many side effects it took over 50 (honestly) OSS notes to stabilise the whole MM module.
They must have wanted to through the guy out on the street after that, but instead I think they got him to design the 740 GUI. It would explain a lot given how that behaved on it's first release.
Cheersy Cheers
Paul