WF Requirement Cov request EC

[Dart, Jocelyn]

Hi Marina et al.
Can't see your original message but...
 
When evaluating start conditions you need to be sure that the attribute
values
are available AT THE TIME THE START CONDITION IS EVALUATED.
 
In BBP/EBP, due to the self-cleaning of shopping baskets after they have
been
sent to the backend, NOT ALL ATTRIBUTES ARE AVAILABLE ALL THE TIME!
 
So, be very careful that the shopping baskets you are testing against are
valid
for the test.
 
The best way to check start conditions is to create and PARK (i.e. HOLD) a
shopping
basket) via BBP/EBP.
Use transaction SWO1, business object BUS2121, and the "test" option to
check what
attributes are available for your shopping basket at this time.
If you are satisfied that all the attributes are correctly available, then
test
your start conditions.  Otherwise it may be a problem with BUS2121 (or your
delegated
subtype if you are using one).
 
If you are satisfied that the attributes are correct, then go ahead and test
the event.
I.e. Turn on your event log, and use transaction SWUE to
manually raise the BUS2121.SAVED event for your particular shopping basket.
 
Then go back and check your event log as Alan suggests.
 
Hope that helps.
        Jocelyn Dart
Consultant (BBP, Ecommerce, Internet Transaction Server, Workflow)
SAP Australia
Email jocelyn.dart at sap.com <mailto:jocelyn.dart at sap.com>
Tel: +61 412 390 267
Fax: +61 2 9935 4880
 
 
-----Original Message-----
From: Rickayzen, Alan
Sent: Wednesday, 18 April 2001 1:20 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: WF Requirement Cov request EC
 
 
Answer from Ulrich Keil (forwarded by Alan Rickayzen)
 
Hi Marina,
 
if I understand you correctly, you are evaluating the condition
 
(
  Total GBP                     <       5000            and
  Total GBP                     >=      100
 )                                                              and
  purchasing organisation       <> 00000176
 
 
with values   Total GBP = 101,  purchasing organisation = 00000176
and this condition seems to evaluate to 'TRUE' (whereas it should give
'FALSE'),
thus starting a workflow via the 'workflow start conditions' (transaction
SWB_PROCUREMENT).
 
Since I could not reproduce this problem on my reference system, I suggest
that you check two things:
 
1. see whether the condition really evaluates to 'true'. You can do this
from within the workflow condition editor in two steps: a) on the condition
editor screen, chose the function 'enter test data' via the right mouse
menue or via CTRL-SHIFT-F3. You will see a container editor that allows you
to enter values for all variables that are used in your condition. If you
are using BOR-Objects, you will have to enter an object reference using
value help (F4). b) After entering the test data, go back to the condition
editor screen and choose 'Evaluate condition with test data' via the right
mouse menue or F8. You will then get a popup saying whether the condition
gives TRUE or FALSE when evaluated on your test data. If you want to know
why and how this result comes about, you can chose 'Test analysis'
(CTRL-SHIFT-F4), and you will see which lines of the condition and which
operators (and/or) precisely were true or false respectively.
 
If, using these test tools, your condition still evaluates to 'TRUE' - this
is an error. You should then open an OSS message and give us access to your
system so that we can figure out what goes wrong.
 
2. If the condition itself evaluates correctly on your test data, there
might be another reason why your workflow starts: Please use transaction
PFTC to have a look at the 'start events' that are registered for your
workflow. A workflow may have more than one event that causes it to start.
You can then use transaction SWELS to switch on the event trace. Then, you
should use your BBP-transaction to create the event (e.g. create a shopping
cart and save it, in case your object is BUS2121-requirement request). Then,
you can have a look at the event trace using transaction SWEL. Here you will
see precisely which events were raised and which workflows were started as a
result. In case of a starting condition that stops a workflow from being
started, you will see a red light in the workflow trace. A green light
indicates that either there was no starting condition or that the starting
condition evaluated to 'TRUE'.
 
Best regards,
Ulrich Keil
 
-----Original Message-----
From: Ralf Staenglen/top-team.de [mailto:rstaenglen at top-team.de]
Sent: Mittwoch, 11. April 2001 11:26
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: WF Requirement Cov request EC
 
 
Hello Marina,
 
I had a similar problem in BBP 2.0C. When I added additional parenthesis to
every expression like:
 
(
  (total GBP < 5000) and
  (Total GBP >= 100)
)
 
instead of
 
(
  total GBP < 5000 and
  Total GBP >= 100
it worked fine !
Unusual and a little bit strange but it works !
Perhaps you try it like this.
 
Best regards
Ralf Staenglen
 
top-team consulting GmbH
email: rstaenglen at top-team.de
 
Phone: +49(0)7021-9464-19