Challenge of the day - "beginner" errors in SAP-delivered transactions

[former_member181923]

1. Read this post here:

2. Name another SAP-delivered transaction that exhibits the same incorrect behavior as SWUI_SINGLE and SWUI_START.

Note: Assume that the behavior of these transactions at this customer site is not due to an error in system config, but rather to insufficient internal SAP QA/QC.

If the behavior of SWUI_SINGLE and SWUI_START is not due to a config error at this customer site, these are really remarkable transactions. I've never seen SAP transactions delivered with such gross "beginner" errors.

Have you?

djh

[suresh_datti]

David,

These Transactions(SWUI_SINGLE and SWUI_START ) might not be meant for explicit calls.. hence no menu options.. I don't think they can be labelled as errors..

~Suresh

[former_member181923]

Hi Suresh -

"not meant for explicit calls" - do you mean that these two are meant to be used in program-internal "CALL TRANSACTION" statements only ???

Please clarify ...

Thanks

djh

[suresh_datti]

Yes.. Pl take a look at the source code in the function module SWU_START_WORKFLOW_TASK.

~Suresh

[former_member181923]

I thought that's what you meant.

But even though it may not be technically an "error", it is certainly sloppy work by SAP.

If they don't want code the full user interface for an "internal" transaction, then it should be in a special system "auth" class so not even WF admin's can execute it.

After all, wouldn't that be a legitimate part of the "enhanced user experience" that we keep on seeing so many blogs about ???

I mean, gee whiz! We have all kinds of fancy widgets in SAP-land, but a user can still get stuck in an "internal" transaction that he or she decided to execute to see what it does ...

Thanks again for taking the time to reply ...

djh

[stephenjohannes]

David,

All you need to do is just teach your users "/nex", and they will never be stuck in those transactions again :).

As far as transactions with beginner mistakes, I think EEWB is on the top of my list, but for other reasons. Can someone please tell me why currency and quantity fields were never though of as desired extensions?

Take care,

Stephen

[former_member181923]

Hi Stephen -

How could I teach them "/nex" when I had deliberately forgotten it myself ... I'm the guy you love to hate when you're standing behind him watching him try to get something done "fast" ... I still go up to the menu bar for copy/paste/cut in Office sometimes ...

It's my way of being old-fashioned - like the engineers who wouldn't give up their rules for calculators ...

As far as EEWB goes, well I can see why nobody cares about it ... remember the old saying:

"Real programmers don't program in wussy languages like LISP ... they program right down to the bare metal" ...

... same goes for any tool that has "easy" and "workbench" in it ...

Just kidding, of course ...

djh

[Former Member]

Try SPO1 (that's an Oh, not a zero)...

It is indirectly used by drag&relate. The good thing is a user should never get there, although they often mistype SP01 (that's zero), which is used to look at spool jobs.

Cheers

[former_member181923]

Hi Michael -

That sounds like a good one except at this customer site, I'm not authorized to use it.

Of course, that should be the case for the two I mentioned as well ...

Thanks for taking the time to reply.

djh