cancel
Showing results for 
Search instead for 
Did you mean: 

PREVENT WORKITEM FORWARDING

Former Member
0 Kudos

Is there any way to prevent user from forwarding the workitem from sap inbox.The task attribute set is GENERAL TASK .

We are not going to use the FORWARDING NOT ALLOWED option for task.Can this be done through coding or some config setting.

Accepted Solutions (1)

Accepted Solutions (1)

pokrakam
Active Contributor
0 Kudos

Why not use Forwarding not allowed? That's what it's there for!

Perhaps if you explain the business requirement we can address that instead of building complex technical solutions.

There is an authorization object for forwarding, but that means you cannot forward anything and it doesn't necessarily apply to a substitute.

Former Member
0 Kudos

thank folks for ur views.

Actually our business requirement is to prevent any type of workitem forwarding.Can tell me how can we set that authorization object to restrict user from workitem forwarding.I searched the thread but was not able to locate on sdn.

pokrakam
Active Contributor
0 Kudos

Hello,

You have still not answered the question of why you cannot use the "No forwarding" setting on a task? I think that's far easier to address and - as I said - authorizations are a potentially unreliable solution.

Simple to find though, just remove the WF-related auths from a user, give them access to the inbox and try to forward an item and see which auth fails.

Cheers,

Mike

Former Member
0 Kudos

The problem in that solution is that we have to always assign the responsible agents in the task.This will impact the flexibility ...as if someone has always make changes in workflow to assign responsible agents.

Is there some way to assign whole org structure as the responsible agent as that will solve my problem.

imthiaz_ahmed
Active Contributor
0 Kudos

Are you talking about possible agent or responsible agent?

pokrakam
Active Contributor
0 Kudos

OK, now we're getting somewhere! Think outside the box, you do not need to assign an org unit. If the task is indeed for everyone then you can assign any role that everyone has (the one that grants access to the inbox is usually a good one).

Don't forget about task groups either - they can simplify your maintenance a great deal if you have multiple tasks with the same agents.

Another trick if you have a scenario where you need to modify your agents frequently but do not want to change possible agents, you can always use a dummy responsibility rule.

The possibilities are endless...

Have fun,

Mike

Former Member
0 Kudos

Thanks mike............i got your point.

I need to set task attribute to no forwarding and assign the role in place of posssible agents.The role should be such that every user should have that role added to his profile.

Can you shed some more light on the role..........realted stuff b'cos i have never used that thing.

pokrakam
Active Contributor
0 Kudos

Sure, just go to txn SU01 (SU01D if not authorized) and display your user.

In the roles tab it should be easy to spot the base role assigned to all users, I cannot tell you what it is because it's usually a custom Z role. ZALLUSERS or maybe there's a specific inbox one or ZBASE or ... you get the idea.

Then goto your possible agent assignment and assign the role just as you would normally assign a user or org unit.

This is also a great way of restricting general tasks. So for a material-related task you could assign a "display material" role as possible agent and so on.

Cheers,

Mike

Former Member
0 Kudos

thanks mike for your reply.

I have got the basic funda how to use roles.I think it is going to be very helpful for me in future too.I want to ask one more thing is there any place where i can get more details about using roles and task group approach in workflow.I read your replies and there u mentioned about task group usage.If u got some stuff about that...please forward me that thing.

Edited by: anil raina on Jun 6, 2008 5:40 AM

pokrakam
Active Contributor
0 Kudos

Hello,

Task groups can be created in PFTC. The idea is that you can assign many tasks to one TG and then assign possible agents to the TG and not the individual tasks.

This is all documented in the online help, just plug 'Task Group' into the search and you'll find it easily.

Cheers,

Mike

Answers (1)

Answers (1)

Former Member
0 Kudos

I think you can put some authorization that will restrict forwarding of workitems.

Please check in this forum I think this was discussed before.

Thanks

Arghadip