Single Step Task - Should Have been Easy
akshay.bhagwat@wipro.com
akshay.bhagwat at wipro.com
Wed Jan 11 00:23:03 EST 2006
Hi ,
In relation to this agent assignment attribute for single step task
context, needed some basic input.
In my scenario , I am using a Role to find out to determine agent ( i.e.
suitable position ) who will be responsible for processing this step. In
this case, what should be agent assignment attribute?
Should I maintain task attribute as General task / General forwarding
allowed / General forwarding not allowed?
Or Should I maintain this role as agent assignment for this task?
Thanks in advance.
Regards,
Akshay
________________________________
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
Of Mark Pyc
Sent: Friday, January 06, 2006 7:16 PM
To: SAP Workflow Users' Group
Subject: Re: Single Step Task - Should Have been Easy
G'day Vineet,
For the created Workitems do you see the company code populated? Are you
binding the Company Code of the Sales Organisation attribute or
something else?
Have you set the Role to fail if no result is found?? If so try removing
the responsibility for one company code and test - if it doesn't fail I
think you'll have to assume you're not passing the Company Code
correctly.
Have fun,
Mark
On 1/5/06, Mehta, Vineet <vineet.mehta at scglobal.com> wrote:
SAP Version: 4.6c
Bus. Object Type: BUS2094
Event : "Changed"
Event gets raised fine. Bindings okay.
Agent Assignment Attribute: General task forwarding allowed
Org Structure has 4 positions. One position per company code.
(These positions and org unit created just for WF routing).
WF Standard role Created - Company Code as a Container Element
Role Container fine, Binding Fine.
Responsibilty section - Positions and Corresponding
I have positions defined in the org structure. Each position is
specific for a company code.
Company code is passed correctly through the containers.
I have created a Standard Role (workflow Role). I have defined
company
code in the container elements also.. This role defines the
positions
and the holder relation for the tasks based on company code.
Binding form the object and task looks good too.
When I test the PFAC, I get good results based on company code
also.
I clear the buffer SWU_OBUF as well.
When I change the credit memo, it routes to users for all 4
positions..
What am I missing?
_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug
The information contained in this electronic message and any attachments to this message are intended for the exclusive use of the addressee(s) and may contain proprietary, confidential or privileged information. If you are not the intended recipient, you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately and destroy all copies of this message and any attachments.
WARNING: Computer viruses can be transmitted via email. The recipient should check this email and any attachments for the presence of viruses. The company accepts no liability for any damage caused by any virus transmitted by this email.
www.wipro.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20060111/67a8052e/attachment.htm
More information about the SAP-WUG
mailing list