Tasks using call transactions

Dart, Jocelyn jocelyn.dart at sap.com
Thu Oct 17 07:46:34 EDT 2002


Hi Abby,
You can put a call transaction directly in your method or within a function
module within your method - it should still work. You don't mention if your
method is dialog or background?  If background, using a BAPI if you have one is
better than using call transaction.
 
The order in which you have performed your tests is good - that helps narrow
it down.
 
Remember that the business object test is good but makes some assumptions
- e.g. the business object instance is checked for validity before you
even run your method. If you have a problem with full versus partial key
yes that definitely could be part of your problem - suggest you investigate further.
 
The task level brings in a couple of other factors:
1. You need to check the task container to see what object instance was actually
passed to the task and whether it is ok.
2. You need to check the workflow log (even a task on its own creates one) to
see if any error messages are shown - check the technical view of the workflow
log.
3. If you are using "call transaction using..." make sure you use the "...messages msgtab"
option to pick up any error messages sent by the call.
 
Hope that helps.
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: Abby Dywan [mailto:abby.dywan at us.ibm.com]
Sent: Thursday, 17 October 2002 6:01 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Tasks using call transactions
 
 
Hi all -
 
Have a question for y'all I was hoping you could help me out with.  I have
to write a call transaction to release a project for a task in one of my
workflows.  I put this call transaction inside of a function module inside
of a method I called Release for a custom business object ZBUS2001, which
is delegated to business ojbect BUS2001.
 
If I test just the function module, the call transaction works.  If I test
the method, the call transaction works.  If I test the task, the work item
is logically deleted and the call transaction does NOT work.   I've tried
it with both the full object key and the regular key in testing
scenarios... the full key makes the transaction fail when testing through
the business object (not through workflow).  I'm not sure if that's a part
of it or not.
 
Do I need to put the call transaction directly inside of the method?  Or
can I not use call transactions within tasks?
 
I've been working on this all day and haven't been able to figure it out.
Any help would be greatly appreciated!
 
Thanks!
Abby  :)
 


More information about the SAP-WUG mailing list