System.GenericInstantiate

[Lücking Claus]

Thank you Jocelyn and Menne.
 
I think programmed binding is the way - maybe I misunderstund the =
meaning of
System.GenericInstantiate. I thought it was a way of creating an object
reference, when the key fields was known as separate values.
 
Regards
 
Claus.
 
-----Original Message-----
From: Dart, Jocelyn [mailto:jocelyn.dart at sap.com]=20
Sent: 24. april 2003 04:55
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: System.GenericInstantiate
 
 
Claus,=20
I was actually suggesting that you have a new background method to do =
the
whole thing,=20
i.e. input matnr + werks and output the YMARC object instance.
 
If you have a second object you are using, e.g. BUS2009 (requisition) =
that
has a relationship to the material/plant combination you could also set =
up
an attribute on the e.g. BUS2009 object to=20
return the YMARC object instance.=20
 
Retrieving the values as attributes is still more flexible because you =
can
then use them elsewhere in the workflow.
 
Unfortunately you can't use a container operation to directly fill in =
parts
of a string.=20
 
Another way to pass them across to SYSTEM.GENERICINSTANTIATE would be =
to use
an alternative programmed binding where you have a simple routine to =
build
the object key string from your input parameters before calling the =
task. =20
 
Regards,
        Jocelyn Dart=20
Consultant (SRM, EBP, Workflow)
and co-author of the book
"Practical Workflow for SAP"=20
SAP Australia
email: jocelyn.dart at sap.com=20
phone: +61 412 390 267
fax:   +61 2 9935 4880
 
 
 
 
 
-----Original Message-----
From: L=FCcking Claus [mailto:clucking at danfoss.com]
Sent: Wednesday, 23 April 2003 11:38 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: System.GenericInstantiate
 
 
Hi Jocelyn.
 
Is it correct that If I create a new (background) method, I will have =
matnr
and werks as import parameters for the method and the databasevalue =
that I
want to retrieve as exportparameter?
 
I just thought that by retrieving the values I need as attributes would =
be a
more flexible solution.
 
Is it impossible to create the reference to the object type as a string =
for
using System.genericinstantiate ?
 
Regards
 
Claus.
 
-----Original Message-----
From: Dart, Jocelyn [mailto:jocelyn.dart at sap.com]=20
Sent: 23. april 2003 15:19
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: System.GenericInstantiate
 
 
Hi Claus,=20
If you've already created a new object type why not add a method to=20
accept in matnr and werks and return an instance of ymarc?
 
Method System.genericinstantiate will show how to create and return an
object instance.
 
Regards,
        Jocelyn Dart=20
Consultant (SRM, EBP, Workflow)
and co-author of the book
"Practical Workflow for SAP"=20
SAP Australia
email: jocelyn.dart at sap.com=20
phone: +61 412 390 267
fax:   +61 2 9935 4880
 
 
 
 
-----Original Message-----
From: L=FCcking Claus [mailto:clucking at danfoss.com]
Sent: Wednesday, 23 April 2003 11:14 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: System.GenericInstantiate
 
 
Hi.
=20
I have created a new object type YMARC to get DB-values from MARC. =
There are
two key fields: Matnr and werks. Those fields are available in my =
workflow
as seperate containervalues, but I think it is necessary to convert the
values to a string to access the object type. The case is described in =
the
book under Tips and Tricks, but I need an idea to calculating the =
string in
a containeroperation or any other ideas ?
=20
Thanks,
=20
Claus L=FCcking
SAP Manager
=20
Danfoss Marine Systems A/S
Aaderupvej 41
DK-4700 N=E6stved
Phone: +45 5578 7261
Fax: +45 5578 7272
E-mail:  <mailto:clucking at danfoss.com> clucking at danfoss.com
=20