Compensation approval web woes

[Van der Burg, Jeroen JA SITI-ITABEE]

Mike, sounds like your issue is an HR org structure one, you probably =
already checked:
 
The user id you are using should be:
- Authorised to view the employees assigned to him/her
- linked to an employee through IT0105 subtype 0001 and currently active
- The employee should be assigned to a position through an active 008 =
holder relation
- The position should be assigned as a manager position by using an 012 =
manages relation to an org unit
- The org unit should have several positions under it
- The positions should have active holders (employees)
- The employees should be properly set up (no pensioners etc)
 
Note that my experience is limited to MDT, but this should work the same =
in MSS.=20
 
On the bonus question: wild guess: does your main flow has any =
authorisation restrictions and is your subflow classified as a general =
task one?
 
 
Regards,
 
 
Jeroen
 
-----Original Message-----
From: SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU]On Behalf Of
Michael Pokraka
Sent: 23 November 2004 15:08
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Compensation approval web woes
 
 
Good &TIMEOFDAY& all,
 
Running MSS on a 4.7/620 system here, using the Web Approval =
Compensation
adjustment workflow. We have copied the standard compensation approval =
task
TS21300111 to our own.
 
The portal folks have updated the iview so everything is liked correctly =
(?)
to our new task. Here's where the fun begins: we have not been able to =
make
this work, we get an error "No employees found".
 
The task is based on EXTSRV.PROCESS, and as far as we have been able to
establish it calls the correct web service, but it appears the container
data is not passed through. The prime suspect here is something in the =
task
setup on the portal side, however we have a seperate portal team who =
handle=20
that end of things and don't really have in-depth experience with UWL =
and
SAP workflow in general.
 
We've gone through note 646601 (MSS: Workflow Execution Handler no =
longer
supported) and a few related ones... so far no joy.
 
Just wondering if anyone knows of any simple things we may have missed =
out?
 
Cheers
Mike
 
PS: bonus points for answering another really weird one: We plugged the =
SAP
task into our WF to make sure it works.... it didn't, until we put it in =
a
subworkflow - WS21300038 calls WS21300039. We first put the task in our =
WF
directly and it didn't work, then we called WS21300039 from our flow and =
it
did work... very confused!