Business object delegation

[Dart, Jocelyn]

Hi Arpad,=20
It's possible you don't really need two delegates - but can just use =
your
other subtype directly.=20
Especially if it is used in a separate workflow, you could simply use =
the
subtype as the object=20
of the new workflow.  =20
=20
If you want to use a parent event to trigger your workflow, or you only =
want
to use your subtype
in certain steps of your workflow, you can add a workflow container =
element
referring to your subtype,
and use a step linked to a task based on SYSTEM.GENERICINSTANTIATE =
method to
convert from one object type to the other.=20
Then you would have both object types available in your workflow and =
could
use whichever one suits the situation best.=20
=20
It's quite legitimate to have true subtypes that aren't delegates - =
e.g..
representing special cases in the child object type and
the more generic situation at the parent level.=20
=20
You only really need to use delegation where you want to extend the =
provided
SAP business object for the generic situation to your
own business object for the generic situation.=20
=20
E.g. You might delegate BUS1001 representing materials to your own =
ZMATERIAL
object type representing materials,=20
but if you want a ZRAWMAT object type representing "raw" materials that
would be a subtype of BUS1001 but not delegated,=20
and ZRAWMAT would simply be used directly in your tasks or workflows.=20
=20
Hope that helps.=20
Regards,
=09
Jocelyn Dart=20
Consultant (EBP, BBP, Ecommerce, Internet Transaction Server, Workflow) =
 
SAP Australia
Email  <mailto:jocelyn.dart at sap.com> jocelyn.dart at sap.com
Tel: +61 412 390 267
Fax: +61 2 9935 4880
 
-----Original Message-----
From: de Valensart Schoenmaeckers, Patrick
[mailto:deValensartSchoenmaeckers.Patrick at pmintl.ch]
Sent: Tuesday, 12 March 2002 8:28 PM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Business object delegation
 
 
It looks quite natural that you cannot do this : if you had for example =
the
same virtual attribute (=3Dsame names) in your two subtypes, but with a
different code. How would the system react when you would call that
attribute from the main object type?
=20
A workaround for this could be :
1. Create all attributes and methods in the same subtype, but use them =
only
for one project, and use a naming convention that shows clearly which
project they are related to (e.g. if you want to have the same kind of
attribute for both projects, you would have to create it twice with a
different name).
=20
or
=20
2. Make a subtype of a subtype (e.g. bus2081 delegates to zbus2081, and
zbus2081 delegates to ybus2081). I have not tried this, but I do not =
see any
reason why it would not work.
=20
Kind regards,
=20
Patrick
---------------------------------------------------------=20
Patrick de Valensart=20
Information Services=20
Philip Morris S.p.A.=20
Via Salandra, 18, 00187 Roma, Italy=20
---------------------------------------------------------=20
 
-----Original Message-----
From: Vincze =C1rp=E1d [mailto:Arpad.Vincze at itelligence.hu]
Sent: Tuesday, March 12, 2002 10:09 AM
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Business object delegation
 
 
 
        Hello,=20
 
 
 
        Let us say I would like create a business object subtype, like=20
 
              image      ->  zimage  or=20
      bus2081  ->  zbus2081.=20
 
        I can create as many subobject as I would, but I can delegate only
one.=20
I don't understand why?=20
 
        Sometimes it would be appreciated if I can use separate sub object
(different project can work separately). I can create it but at the end =
I
can delegate only one.
 
 
        Any idea?=20
 
        Regards:=20
 
             Arpad=20
 
 
Vincze =C1rp=E1d=20
itelligence Hungary Kft.=20
H-1138 Budapest, V=E1ci =FAt 141=20
Tel.:   (+36 1) 452 3822=20
Fax:    (+36 1) 452 3839=20
Mobil:   (+36 20) 9 533 578=20
arpad.vincze at itelligence.hu=20
 
 
 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20020313/6fa9747d/attachment.htm