System.GenericInstantiate vs. CREATE OBJECT

[Dart, Jocelyn]

Hi Robert,
I have used system.genericinstantiate frequently in workflows and continue to do so and it works fine.
If you are having problems in a particular release then I suggest you report it to OSS.
Remember you need to create workflow container element of the relevant object type in your workflow and
bind that to the task, i.e. your input is object type and object key, your output is the object instance
- don't forget you need to use the "show lines" button to grab the correct output parameter as of course _Wi_object_id
is not relevant with an instance-independent method.
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: Robert van den Berg [mailto:rvdb99 at hotmail.com]
Sent: Friday, 2 May 2003 9:28 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: System.GenericInstantiate vs. CREATE OBJECT
 
 
In earlier forum replies, the use of System.GenericInstantiate was
discussed.
I examined and tested this method (with an object-type and object-key), and
when I test it, it works fine, but in a workflow, it doesn't return an
object.
 
In the method, it uses the SWC_CREATE_OBJECT statement.
What is the difference between "SWC_CREATE_OBJECT" and the "CREATE OBJECT"
statement. The latter works fine (creates an object and I can fill the key
attribute).
 
THNX
 
 
 
_________________________________________________________________
Chatten met je online vrienden via MSN Messenger. http://messenger.msn.nl/