Decision step text ?

[Former Member]

Hey,

On a regular decision step we have the option ,

<i>Cancel and keep work item in inbox.</i> - Now this is SAP std.. can we change the name of this text... or change position of the Button ?

[Former Member · Accepted solution]

Hi Abhishek

I had a quick debug through the decision step process, and it is probably possible for you to change this, but it's going to take quite a lot of hacking of function group <b>SWU2</b>.

Firstly, the actual text <i>Cancel and keep work item in inbox</i> is stored as Text Symbol 301 in the main program <b>SAPLSWU2</b>.

The screen that is called to display the decision steps is screen 300 and is called in function module <b>SWU_PROCESS_MANUEL_DECISION</b>. The actual HTML for the buttons is set up in subroutine <b>ADD_DECISION_HTML</b>, and it is here that you might be able to fiddle with the order of the buttons.

All seems like quite a lot of work, though

Good Luck

Lyal

[Former Member · Accepted solution]

Hey Lyal ,

I was about to start the debug process... thanks for foresight...

I think i will just tell them sorry u have to live with it...

and the ofcourse i can say 3000 hrs required.....

But i might just do it for the kicks of it ...

[Former Member · Accepted solution]

Well Lyal.. u did solve the problem for me... ...

I am not gonna do this for them

[Former Member · Accepted solution]

Hi Abhishek,

Im releaved that you don't have to change the standard.

It is the job of a consultant to not only execute the wishes of the client, but also to educate them.

Kind regards, Rob Dielemans

[KjetilKilhavn]

There is a good reason for this button. It is the only button which lets you tell SAP that «Oops I did it again» - I started a work item which I should not handle just yet. Press any other button and the work item is completed and thus disappears from the inbox.

Remove that button and the only option available for the users who want to keep the work item in their workflow inbox is to close the SAP window.

As suggested by others... reconsider this requirement. If they persist, give them an estimate of 3000 hours 😆

[Former Member]

> As suggested by others... reconsider this

> requirement. If they persist, give them an estimate

> of 3000 hours 😆

Hehe, this is exactly what I try to do in these cases. Another option is by telling them, NO this is not possible in SAP.

Also try to quantify the requirement (how many users have a problem with this and how many times approximately does this cause troubles, and in some cases how much money is gained by implementing this). In one case I was asked to give an estimate for the "removal" of the F12 button functionality in all of SAP, in the end it was contributed to 1 user who sometimes accidentally pressed the F12 instead of the backspace button

[Former Member]

I have never given a estimate like 3000 hrs... i might just go ahead and do that

[pokrakam]

Hehe, careful about joking around with silly estimates - I once gave a 1600 hour estimate for a WF which we ended up building

The estimate was for 200 man-days and kept four people entertained for a few months totalling 210 days by the time we hit UAT.

[Former Member]

Hi,

what is the reason for changing this SAP standard behaviour?

I''ve had a lot of ludicrous wishes from the business in my career, all of them related to users who are not used to changed and were only recently working with SAP.

I think in projects which involve using a new system, the training of the personnel could use a lot more attention than usually is the case.

But to come back to your question, as Lyal pointed out, it is possible to change this text and yes it will probably solve the "problems" encountered by users. But keep in mind that this is only temporary, also if the users don' get used to it now, they probably never will and you could expect more issues to arrive.

Kind regards, Rob Dielemans

[Former Member]

<b>sigh</b>

Life would be so much easier without users...

[Former Member]

Hi Lyal,

I disagree with you. I think that underestimating training of personnel and also not involving them in new projects at an early stage can cause these problems.

[Former Member]

Well i totally agree that it is a useless requirement... The just are confused by the text .. it seems to be a trainin issue more than anything here....

and if I do go ahead and change the text.. it would probably effect all the decision steps.. do i guess will give that a pass......

and we cannot just give them everythin they want... just like the fact that we should not spoil children ...

Thanks for the input

[Former Member]

I must say that sound like an awful lot of work. Why not just create your own decission step, with a screen just like you want it?

If you use resultparameter you can easally get the outcome branches similar to those from the generic user dec.

Kind regards

Mikkel

[Former Member]

Yep thats a workaround.. i was just wondering if one could mess around with the std stuff