Subtypes

[Gun> <Celine]

Thank you for your answer. But unfortunately I tried it also ! I =
searched OSS Notes but there is nothing about it !
 
-----Original Message-----
From: Pokraka, Michael [mailto:michael.pokraka at kcc.com]=20
Sent: 04 Ekim 2002 Cuma 16:02
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Subtypes
 
 
Sorry, just realized I wasn't finished with my last mail.
The main point I was getting to was that you should use the supertype - =
i.e. BUS2032 in your workflow. Delegation means that all ZBUS2032's =
extras will be available to BUS2032.
 
The event you should be using/looking out for is thus BUS2032.ZCREATED
 
The other advantage to using BUS2032 in your workflows is that it will =
happily work with any SAP-standard task/role/ABAP/whatever that expects =
a BUS2032 object.
 
A last hint, use SWEL for tracing event problems.
 
Cheers
Mike
 
 
 
 
-----Original Message-----
From: Pokraka, Michael [mailto:michael.pokraka at kcc.com]
Sent: 04 October 2002 13:45
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Subtypes
 
 
First, I'd just like to clarify something - you say you created the =
subtype by copying BUS2032???? There is a difference to creating a copy =
and a subtype - a subtype _inherits_ the supertype's functionality.
 
Onto your question, the idea behind delegation is kind of the opposite =
to inheritance. Inheritance is where the functionality of a supertype is =
used by a subtype, e.g. ZBUS2032.CREATE doesn't really exist, but merely =
points to and executes BUS2032.CREATE. Delegation is the opposite, it =
makes a subtype's method/attributes visible and available as if they =
were available in the supertype. Thus we can use BUS2032.ZCUSTOMMETHOD. =
This gets around the fact that we cannot edit SAP objects directly. Note =
that an object can only be delegated to ONE subtype.
 
HTH
Mike
 
-----Original Message-----
From: <Gun> <Celine> [mailto:gulsenu at kocsistem.com.tr]
Sent: 04 October 2002 13:27
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Subtypes
 
 
Yess. But it didn'nt work :((
 
-----Original Message-----
From: Shane Burns [mailto:Shane.Burns at boimail.com]
Sent: 04 Ekim 2002 Cuma 15:12
To: SAP-WUG at MITVMA.MIT.EDU
Subject: Re: Subtypes
 
 
Hello,
have you delegated the subtypes using the system wide delegation?
 
 
 
 
 
                    Sent by: SAP                To:
SAP-WUG at MITVMA.MIT.EDU
                    Workflow                    cc:
                    <Owner-SAP-WUG at MITVM        Subject:     Subtypes
                    A.MIT.EDU>
 
 
                    04/10/2002 13:01
                    Please respond to
                    SAP Workflow Users'
                    Group
 
 
 
 
 
Hi Workflowers !
 I'm new in WF and confused with subtypes.
WF subtypes which created by us (exp: ZBUS2032) does not work properly. =
We created new subtypes via copying the SAP objects and defined =
ZCREATED, ZCHANGED vs.. events. We should set some restrictions for the =
new object via transaction SWEC for the different scenarios. When we =
used the subtypes in the workflow, events are not triggered. As soon as =
we use the origional SAP objects in the same wf, triggering is working. =
Heeelp !
 
 
 
 
 
 
********************************************************************
This email and any files transmitted with it are confidential and =
intended solely for the use of the individual or entity to whom they are =
addressed. If you have received this email in error please notify us =
immediately at MailMonitor at isismail.ie and delete this E-mail from your =
system. Thank you. It is possible for data transmitted by email to be =
deliberately or accidentally corrupted or intercepted. For this reason, =
where the communication is by email, the Bank of Ireland Group does not =
accept any responsibility for any breach of confidence which may arise =
through the use of this medium. This footnote also confirms that this =
email message has been swept  for the presence of known computer =
viruses.
********************************************************************
 
-------------------------------------------------------------------------=
---
--
This e-mail is intended for the use of the addressee(s) only and may =
contain privileged, confidential, or proprietary information that is =
exempt from disclosure under law.  If you have received this message in =
error, please inform us promptly by reply e-mail, then delete the e-mail =
and destroy any
printed copy.   Thank you.
 
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D
=3D=3D
 
-------------------------------------------------------------------------=
---
--
This e-mail is intended for the use of the addressee(s) only and may =
contain privileged, confidential, or proprietary information that is =
exempt from disclosure under law.  If you have received this message in =
error, please inform us promptly by reply e-mail, then delete the e-mail =
and destroy any
printed copy.   Thank you.
 
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D
=3D=3D
 
-------------------------------------------------------------------------=
-----
This e-mail is intended for the use of the addressee(s) only and may =
contain privileged, confidential, or proprietary information that is =
exempt from disclosure under law.  If you have received this message in =
error, please inform us promptly by reply e-mail, then delete the e-mail =
and destroy any printed copy.   Thank you.
 
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D