Compensation approval web woes

[Michael Pokraka]

Hi Jeroen,
It's definitely not an org structure one, since the SAP task works
perfectly. The replacement TS9... task doesn't. The annoying thing I find
with MSS is that you can't test half of the things in the backend, so whe=
n
(as is the case here) you have little control over the portal it gets
tricky... The workflow log shows the correct container data (work queue),=
 bu
texecuting it via portal it's blank.
 
On the wild guess: Good answer, but the problem is the other way around -=
 it
DOESN'T work on its own and DOES work in a subflow.
 
Thanks for the info,
Cheers
Mike
 
Van der Burg, Jeroen JA SITI-ITABEE wrote:
> 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 activ=
e
> - The employee should be assigned to a position through an active 008 h=
older
> 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 sam=
e in
> MSS.
>
> On the bonus question: wild guess: does your main flow has any authoris=
ation
> 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 Compensati=
on
> 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 correctl=
y (?)
> 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 containe=
r
> 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 ha=
ndle
> that end of things and don't really have in-depth experience with UWL a=
nd
> SAP workflow in general.
>
> We've gone through note 646601 (MSS: Workflow Execution Handler no long=
er
> 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 i=
n 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 an=
d it
> did work... very confused!
>
>