Workflow Question - FB08 Transaction

[Carson, Wayne]

How do you make sure that the update (reversal) has completed before
executing the next step in the workflow if the STANDARD SAP transaction
doesn't raise a Terminating Event?  Assuming that the next step in the
workflow requires information from the result of the reversed transaction.
(reversal number, for example)
 
I don't understand the Linking of Reversal Document to Reversed Document.
What will this do?
 
Wayne R. Carson
SAP Technical Applications Lead
Solvay Information Technologies
713-525-4143
WAYNE.CARSON at SOLVAY.COM
 
 
-----Original Message-----
From: Dart, Jocelyn [mailto:jocelyn.dart at sap.com]
Sent: Monday, August 05, 2002 2:52 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Workflow Question - FB08 Transaction
 
Hi Wayne,
Rule of thumb:
 
Display methods should usually be synchronous
Update methods should usually be asynchronous with terminating events
to cover exactly the sort of scenario you are talking about.
 
As the FB08 creates a new document then yes I would expect a created event
from it.  If you added an attribute in your BKPF subtype linking reversal
document to reversed document that might help you in matching the event
with the waiting workflow.
Regards,
        Jocelyn Dart
Consultant (SRM, EBP, Workflow)
and co-author of the book
"Practical Workflow for SAP"
SAP Australia
 jocelyn.dart at sap.com
 +61 412 390 267
+61 2 9935 4880
 
 
 
 
 
-----Original Message-----
From: Carson, Wayne [mailto:Wayne.Carson at solvay.com]
Sent: Saturday, 3 August 2002 1:41 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Workflow Question - FB08 Transaction
 
 
We have a large that is used in the AP department for processing invoices.
We scan the invoices using iXOS Enterprise Scan and Index them using an SAP
transaction.  The AP clerk receives a work item via a custom role that we
developed.  The accounting transaction is entered, it may be MIRO or FB60.
Accounting Document is created and it is routed for approval.  If the
Approval is rejected by the "approver", then the AP clerk receives a work
item.  AP clerk clicks the work item and FB08 transaction is stared
(Reversal).  We created a new method that is defined as SYNC and basically
does a CALL TRANS.  We a problem where the workflow continues to the next
step even though the reversal document may not have completed.  We are
thinking that if we change the METHOD to ASYNC and add a Terminating event
to the Task, then the Workflow won't continue until after the database has
been updated with the reversal information.  Later tasks (steps) use the
reversal information.  What confused us is that there doesn't appear to be a
"reversal" event defined in SWO1.  There is a CREATED and CHANGED EVENT.
Will the EVENT CREATED get raised after the Reversal?  I could use SWEL to
tell which events are being raised.
 
 
 
Is this a GENERAL RULE.  If you use METHODS containing CALL TRANSACTION
where there are database updates, you should define your METHOD as ASYNC and
add a terminating event for the TASK?
 
 
 
As mentioned before, the METHOD was SYNC but SAP is still doing it's thing
after our method has executed.
 
 
 
OBJECT TYPE - BKPF.
 
 
 
Thanks,
 
 
 
Wayne R. Carson
 
 
 
 
 
---------------------------------------------------------------------------
This e-mail is confidential.
If you are not the addressee or an authorized recipient of this message,
any distribution, copying, publication or use of this information for any
purpose is prohibited.
Please notify the sender immediately by e-mail and then delete this message.
 
Ce message est confidentiel.
Si vous n'etes pas le destinataire designe de ce message ou une personne
autorisee a l'utiliser, toute distribution, copie, publication ou usage a
quelques fins que ce soit des informations contenues dans ce message sont
interdits.
Merci d'informer immediatement l'expediteur par messagerie electronique et
d'ensuite detruire ce message.
---------------------------------------------------------------------------
---------------------------------------------------------------------------
This e-mail is confidential.
If you are not the addressee or an authorized recipient of this message,
any distribution, copying, publication or use of this information for any
purpose is prohibited.
Please notify the sender immediately by e-mail and then delete this message.
 
Ce message est confidentiel.
Si vous n'etes pas le destinataire designe de ce message ou une personne
autorisee a l'utiliser, toute distribution, copie, publication ou usage a
quelques fins que ce soit des informations contenues dans ce message sont
interdits.
Merci d'informer immediatement l'expediteur par messagerie electronique et
d'ensuite detruire ce message.
---------------------------------------------------------------------------