Question:
HI WF Gurus,
I've a strange problem.
Start transaction PFTC_DIS.
With a user I can see workflow template 00200061.
With another user I can not (when I click ENTER, no name appears for the task and if I try to view it I receive the message task does not exist).
With authorization check (SU53) there are not problem: All authorization checks have so far been successful.
I also triede giving the profile SAP_ALL to the user but still the same problem.
How can I solve it? Where is the problem?
Thanks in advance
Pernilla
Answer:
Hi Pernilla,
This dosent seem to be an issue, yeah if Authorization is not given to the user, then the user will not be able to see the Work item and nor will the text appear even after you enter the WF template.
As this is what i had seen in case where the auhorizaton team had disabled for some users, they couldnt even see the workflow.
Definately some Parameter settings/Authorization issue.
Answer:
Thanks Kuntz,
but if I copy the user who can not see the wf template to another new user with the same authorizations this last new user can see the wf template in the pftc_dis the old user not. So I think it's not an authorization problem: the new user is identical to the old with the exception of the username.
Why the new user can see the wf template and the old not?
Thanks in advance
Pernilla
Answer:
Hi,
It could simlpy be an incorrect SAP gui install. Try if it's computer related by logging in on that same computer with another user.
Kind regards, Rob Dielemans
Answer:
Hi Rob,
it's computer independent: the old user doesn't work in two computer and the new works in both computer.
Pernilla
Answer:
hi,
What is the message number and class? Maybe there's extra information in the long text, if it exists.
Other things to check, can be the OM, or differences in user parameters, if all of this fails, you should raise an OSS message.
Kind regards, Rob Dielemans
Answer:
Hi,
message is Task does not exist (5W 304).
Long text: This object is not a valid task.
In OSS there is only one note (539195) but this is old for my system.
May be I will contact OSS to solve this problem.
Pernilla
Answer:
Hi,
If you know a bit of ABAP try to do the following,
before you press enter, activate system debugging by typing /HS
then press enter.
In debugging create a watchpoint for sy-msgno = 304
Then click F8.
And see if the reason for not finding the task is expected behaviour.
I just remember, that I had this problem before, but this was authorization related for object PLOGI or something similar.
Kind regards, Rob Dielemans
Answer:
Take a look at tcodes OOSB and OOSP and see if there are any structural authorizations that are preventing this user from seeing the task.
I have seen structural authorization issues before and did not see them when running SU53.