Release status of tasks

[Zmudzin,Tomasz,VEVEY,GL-IS/IT]

Let's put it this way:
 
1. Status matters. You cannot argue with the system ... -- it knows better!
2. It definitely helps to have the status matching the REAL object lifecycle
stage.
3. If in some cases SAP is not tidy enough -- it does not mean you have to
follow the bad practice.
 
Kind regards,
Tomasz
(who is also SAP and tries to be tidy)
 
-----Original Message-----
From: Fred Lunaspa [mailto:fredlunaspa at hotmail.com]
Sent: Friday,23. May 2003 11:53
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Release status of tasks
 
 
Robin,
 
Last year when I attended the course BC601 I was told that the release
status of workflows and tasks is purely descriptive (at this moment): this
means the system does not 'look' at this.
 
Regards,
 
Fred Kouw
 
 
>From: Robin Sahasranam <Rsahasranam at worldbank.org>
>Reply-To: SAP Workflow Users' Group <SAP-WUG at MITVMA.MIT.EDU>
>To: SAP-WUG at MITVMA.MIT.EDU
>Subject: Release status of tasks
>Date: Tue, 13 May 2003 14:48:52 -0400
>
>Greetings,
>
>We have several productive workflow standard tasks in a 4.6c system, which
>are
>functioning properly, even though the Release status of these tasks in the
>PFTC
>transaction shows " Not defined". These tasks were created in 4.0b and I do
>not
>recall this  field being available then.
>I also noticed that many SAP delivered tasks are also of status "Not
>defined".
>
>  Is it important to  change the status to "Implemented" or "Released".?
>
>Also what is the difference between "Implemented" and "Released" and which
>should be used when a task is productive?
>
>Thanks for taking the time to respond.
>
>Robin Sahasranam
>World Bank.
 
_________________________________________________________________
Hotmail en Messenger on the move
http://www.msn.nl/communicatie/smsdiensten/hotmailsmsv2/