Simple Workflow for EBP 1.0

[Dart, Jocelyn]

Hi Cristian,
This should work (I've done something similar in EBP 2.0)..
 
Just prior to the approval step, add a condition step to check
your total value, if above 800K use a container operation to set
the ApprovalState flag to the rejected value ("1" I think from
memory), otherwise do the normal approval process.
 
You may also want to set a "dummy" rejector, e.g. WF-BATCH, if you are=20
showing the rejector on the rejection notification.=20
 
Check the approval applet in the "Change Shopping Basket and Check =
Status"
transaction still looks ok - I didn't have to make any changes for=20
EBP 2.0 so hopefully the same will apply to EBP 1.0.
 
Regards,
        Jocelyn Dart=20
Consultant (BBP, Ecommerce, Internet Transaction Server, Workflow)=20
SAP Australia
Email jocelyn.dart at sap.com <mailto:jocelyn.dart at sap.com>=20
Tel: +61 412 390 267
Fax: +61 2 9935 4880
 
 
-----Original Message-----
From: Gonz=E1lez Cartagena Cristi=E1n [mailto:E_CGonzalez at entel.cl]
Sent: Saturday, 2 June 2001 9:33 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Simple Workflow for EBP 1.0
 
 
Hi all,
 
We have developed several workflows for shopping basket approval, =
varying
from 1 to 9 levels of approval and with many different starting =
conditions
based on amount, selected catalog, type of user and other criteria. It =
was a
huge task. It works fine.
 
But now, we have to implement a very simple workflow but don't find how =
to
do it:
the user (a technician)  creates the shopping basket, and if the total =
value
is greater than 800K, then the shopping basket must be automatically
rejected. If less, it goes to the approver.
 
Any help would be appreciated.
 
Cristian Gonzalez
BBP Project Manager at Entel