Using Task Group in Workload Analysis (RSWILOAD)

[Rivera, Raul]

Thank you for your comprehensive reply Mark.

Have done what you have suggested and raised an OSS. I will post the end
result to this list as an FYI.

Raul

-----Original Message-----
From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf Of
Mark Pyc
Sent: Friday, March 04, 2005 3:15 AM
To: SAP Workflow Users' Group
Subject: Re: Using Task Group in Workload Analysis (RSWILOAD)

G'day Raul,

I'm amazed by this little find! I'm currently in a 640 system and the
problem still exists. It's a bug plain and simple, but there is
nothing I can find in OSS. I guess this shows how little the reporting
functions around Workflow are really used. I've still never found a
customer who is interested in such data.

Anyway, I would raise it with OSS. In the mean time you can get passed
the problem by debugging, or take a copy of the report or simply
repair it.

Here is the code extract from my version - may not be an exact match,
but probably close:

>>>>>
AT SELECTION-SCREEN ON taskgrou.

  REFRESH task2.
  CLEAR text4.

  IF not taskgrou is initial.

    CALL FUNCTION 'RH_WF_OBJID_UNPACK'
      EXPORTING
        act_object_ext = taskgrou
      IMPORTING
        act_object_ext = taskgrou.

    CALL FUNCTION 'RH_CHECK_ORG_OBJECT_EXISTS'
      EXPORTING
        act_object_ext       = taskgrou
      IMPORTING
        act_stext            = task_text
      EXCEPTIONS
        no_active_plvar      = 01
        no_org_object        = 02
        org_object_not_found = 03.

    CASE sy-subrc.
      WHEN 00.
        IF taskgrou(2) = 'T '.

          text4 = task_text.

          task2-option = 'EQ'.
          task2-sign = 'I'.
<<<<<

The problem is with "IF taskgrou(2) = 'T '." This should be "IF
taskgrou(2) = 'TG'."

To get passed the problem in debugging set a break-point on this line.
Put your task group in prefixed with TG, so in your case TG90000001,
in the selection screen and execute. When the debugger kicks in at
your break point, change the value of taskgrou(2) to be 'T ', execute
the line and then change it back to being 'TG' and hit continue.

A bit painful, so copying the report to your own Z version is probably
the way forward. In the words of Jocelyn - report it to OSS!

Have fun,
Mark

On Thu, 3 Mar 2005 10:19:14 -0800, Rivera, Raul
<Raul.Rivera at absu.accenture.com> wrote:
> We are in 4.6c
> 
> We have created a task group (90000001) that groups our custom tasks. We
> intend to use the task group as input parameter in workload analysis
> (RSWILOAD).
> 
> However, we are getting a 'No task available with the specified number'
> message from SWI5. Moreover, the system appends 2 zeros in the task ID
> converting the 8 digit ID into a 10 digits (90000001 --> 9000000001).
We've
> also entered an SAP provided task group and got the same result.
> 
> Are we missing something here?
> 
> Raul
> 
> _______________________________________________
> 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