Creating a workflow with several steps

[Dart, Jocelyn]

Abby,
Each activity step is its own logical unit of work and can have whatever commits you like.
Suggest you check out whatever routine you are using in your third step.  Perhaps it is missing
a commit work or call to BAPI_TRANSACTION_COMMIT. Or perhaps it just doesn't save data.
Regards,
        Jocelyn Dart
Consultant (SRM, EBP, Workflow)
and co-author of the book
"Practical Workflow for SAP"
SAP Australia
email: jocelyn.dart at sap.com
phone: +61 412 390 267
fax:   +61 2 9935 4880
 
 
 
 
-----Original Message-----
From: Dywan, Abby [mailto:adywan at clarkstonconsulting.com]
Sent: Friday,5 September 2003 5:00 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Creating a workflow with several steps
 
 
Hi experts -
 
I'm creating a workflow with several steps doing several things - in the first step, we make some changes to a service order.  In the second step, we confirm the service order.  In the third step, we TECO it, and in the fourth step, we close the notification.
 
The first two steps work just fine - but the third step is coming back with a positive result, but it looks like it's not saving it.  The first two steps both involve commits to the database - and so does the third.  I'm wondering if you can have too many commit statements in a workflow, and this is why the method in the third step works but does not appear to save.  When I run the standard task by itself, it works just fine.  has anyone seen this before?
 
Any suggestions / advice would be greatly appreciated!
Abby :)