Workflow substitution No2

[michel Tallon]

Hi Vincze,
 
Usually, there is a container element named &EXCLUDEDAGENTS& witch contain
workflow initior username and user of already approved validation step.
If this container element is used in the excluded agents part of approval
workitem definition, your process SAPuserA -> SAPuserB -> SAPuserB will
become
SAPuserA -> SAPuserB as last step will be automatically skipped.
 
Regards.
 
-----Message d'origine-----
De : SAP Workflow [mailto:Owner-SAP-WUG at MITVMA.MIT.EDU]De la part de Vincze
Arpad
Envoyi : jeudi 9 aout 2001 10:39
A : SAP-WUG at MITVMA.MIT.EDU
Objet : Workflow substitution No2
 
 
Hi workflowers!
 
 
Here is the time for holyday and substitution problem again...
 
We are working with SAP 4.0b and our workflows (PO approval; inbound invoice
processing, etc) use the PD substitution mechanism (PPOM transaction) as I
have written my previous mail.
 
        *       Let us suppose we approve a PO
        *       We have three level approval, with the following sequence
        SAPuserA -> SAPuserB -> SAPuserC
        *       Using the PD substitution
                   SAPuserB substitutes SAPuserC
             The approval sequence would be
                SAPuserA -> SAPuserB -> SAPuserB
 
 
        Is there any method to obstacle this erroneous sequence?!
        Or this sequence is acceptable (for our customer not) ?!
 
 
 
Any proposal
 
  Arpad
 
 
 
 
 
 
Vincze Arpad
itelligence Hungary Kft.
H-1138 Budapest, Vaci zt 141
Tel.:   (+36 1) 452 3822
Fax:    (+36 1) 452 3839
arpad.vincze at itelligence.hu
 
 
______________________________________________________________________________
ifrance.com, l'email gratuit le plus complet de l'Internet !
vos emails depuis un navigateur, en POP3, sur Minitel, sur le WAP...
http://www.ifrance.com/_reloc/email.emailif