Filtering required for Task used for error handling

[Mike Pokraka]

Yes, complex attributes can affect inbox performance, simple field ones
not so much.
Usually it's best to leave dyn. cols off the standard inbox view, rather
get your users to go via the 'grouped by task' view, where you then set
the columns up.

Re. reporting it depends on what you want to report on.
What I meant is that in many scenarios you can get WF stats from the
application. e.g. if your approvals/rejections match the
released/cancelled documents in the database then you can just as well
report on RSEG/BKPF/whatever and break it down by type from there to get
the rejection ratio by document type.
If your business scenario isn't suitable (e.g. you need to know processing
time by doc type) then you need a custom report to read the container for
each task. Not a big deal, but some extra effort. I 'd say still better
than having an indeterminate number of tasks.

Cheers,
Mike



On Fri, October 27, 2006 11:24, akshay.bhagwat at wipro.com wrote:
>
> Hi Mike,
>
> Thanks for the help, paralley I tried it with Dynamic columns and it
> worked!!
> One doubt: whether use of dynamic columns will affect by any chance for
> Inbox performance?
> Just wanted to know , would it be tedious from reporting point of view
> if we have only one task instead of having different tasks?
>
> Also, will you pls explain the point once again which you have mentioned
> for reporting / statistics?
>
> Thanks in advance.
>
> Regards,
>
> Akshay Bhagwat
>
> SAP Practice
>
> Wipro Technologies
>
> ': +91 20 2293 3700 x 3608
> Fax: +91 20 2293 3756
>
>
> -----Original Message-----
> From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf
> Of Mike Pokraka
> Sent: Friday, October 27, 2006 3:17 PM
> To: SAP Workflow Users' Group
> Subject: Re: Filtering required for Task used for error handling
>
> Hi Akshay,
> Have a look at dynamic columns. They'll do what you're after in the
> inbox.
> Search sap help for your version for keywords "Dynamic Columns Business
> Workplace"
>
> For reporting/statistics you probably have to query the container for
> each task, but usually you're better off reporting on from the business
> object side of things for this type of info (e.e. look to your
> application tables for a breakdown of documents/code),
>
> Cheers,
> Mike
>
> On Fri, October 27, 2006 10:08, akshay.bhagwat at wipro.com wrote:
>>
>> Hi All,
>>  We have a scenario where in we are using one task - to send it as a
>> work item to user- for sending error information for different error
>> codes.
>> i.e. same task is used , only error description is populated in it
>> dynamically based on error/ validations occurred in program.
>> e.g. Error code- MT0001 - Technical error occurred
>>                       MT0002 -  Data validation failed.
>>
>> Now the requirement is that filtering / grouping needs to be done
>> based on error codes sent in the work item.
>> e.g. for MT0001 - how many work items are sent , needs to be found out
>
>> (or grouped in Inbox) One option is to create separate task for each
>> error code. ( However there are 500 odd entries for error codes !)
>>
>> Is there any way out instead of creating so many tasks for achieving
>> the same?
>>
>> Awaiting your response.
>> Regards,
>>
>> Akshay Bhagwat
>>
>> SAP Practice
>>
>> Wipro Technologies
>>
>> ': +91 20 2293 3700 x 3608
>> Fax: +91 20 2293 3756
>>
>>
>>
>>
>>
>> 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_______________________________________________
>> SAP-WUG mailing list
>> SAP-WUG at mit.edu
>> http://mailman.mit.edu/mailman/listinfo/sap-wug
>>
>
>
> _______________________________________________
> 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
>
> _______________________________________________
> SAP-WUG mailing list
> SAP-WUG at mit.edu
> http://mailman.mit.edu/mailman/listinfo/sap-wug
>