Mass change/retirement workflow

[Gramelspacher, Tony]

Thanks for the confirmation from SAP OSS.  That's exactly what we did.  It's
good to know we are following the recommended approach.
 
Tony Gramelspacher
SSC
(314) 589-7996
 
 
> -----Original Message-----
>> From: R Tannert [SMTP:tnn at ornl.gov]
> Sent: Thursday, August 17, 2000 12:06 PM
> To:   SAP-WUG at MITVMA.MIT.EDU
> Subject:      Re: Mass change/retirement workflow
>
> Tony,
>
> Sorry I missed your original message.  I encountered the same problem when
> we upgraded from 3.1H to 4.0B.  I sent an OSS message and got the following
> response:
>
>
> Hello Rob,
> in 4.0 WS25 was enlarged and treats now bulk changes and retirements
> with and w/o revenue. So WS24 became superfluous and was deleted. Use
> WS25 instead (disable the event linkage from AM_AI CREATED to WS24 and
> enable - or create - the event linkage to WS25).
> Kind regards,
> Ingo Severing, development support FI-AA
>
>
> Rob
>
> >Jeff,
> >
> >Thanks for the reply.  I never did receive any answers.  However, I did
> figure
> >out an alternative solution.  We have completely abandoned the WS24
> >workflow and
> >have implemented the WS25 instead.  I found it fairly odd that the WS24
> >definition did not make it into our upgraded (4.6C) system but the event
> >linkage
> >(SWE2 entry) did.  I could simulate the event AM_AI, CREATED and WS24
> >would show
> >up as a workflow to be started but I couldn't use it because the
> >definition was
> >not available.  I guess SAP has abandoned the WS24 workflow as well?
> >
> >After working with the functional folks I believe WS25 will meet our
> >needs.  We
> >have run some tests in our development system with successful mass asset
> >retirements and changes.
> >
> >Tony Gramelspacher
> >SSC
> >(314) 589-7996
> >