Difference between Business object method and ABAP class methodsin atask

Wed Jun 20 04:44:36 EDT 2007

Hi

Where/what should be my starting point for looking at the OO workflow 
world as opposed to the historical BOR world.

Thanks

John

--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
This is a PRIVATE message. If you are not the intended recipient, please 
delete without copying and kindly advise us by e-mail of the mistake in 
delivery. NOTE: Regardless of content, this e-mail shall not operate to 
bind CSC to any order or other contract unless pursuant to explicit 
written agreement or government initiative expressly permitting the use of 
e-mail for such purpose.
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------

"Dart, Jocelyn" <jocelyn.dart at sap.com> 
Sent by: sap-wug-bounces at mit.edu
06/20/07 07:23 AM
Please respond to
"SAP Workflow Users' Group" <sap-wug at mit.edu>

To
"SAP Workflow Users' Group" <sap-wug at mit.edu>
cc

Subject
RE: Difference between Business object method and ABAP class    methodsin 
atask

Hi John, 

Actually having worked with both ABAP OO for Workflow and BOR my current 
opinion is - only use BOR for eventing if you are using - a standard 
workflow as-is or an event technique that doesn't support OO - like status 
management events. 

Otherwise stick with ABAP OO and link to the existing BOR using an 
attribute of type SIBFLPORB. 

Best of both worlds.  ABAP OO is soooooooooooooooo much easier to use for 
enhancements. 

Regards, 
Jocelyn Dart 
Senior Consultant 
SAP Australia Pty Ltd. 
Level 1/168 Walker St. 
North Sydney 
NSW, 2060 
Australia 
T   +61 412 390 267 
M   + 61 412 390 267 
E   jocelyn.dart at sap.com 
http://www.sap.com 
The information contained in or attached to this electronic transmission 
is confidential and may be legally privileged. It is intended only for the 
person or entity to which it is addressed. If you are not the intended 
recipient, you are hereby notified that any distribution, copying, review, 
retransmission, dissemination or other use of this electronic transmission 
or the information contained in it is strictly prohibited. If you have 
received this electronic transmission in error, please immediately contact 
the sender to arrange for the return of the original documents. 
Electronic transmission cannot be guaranteed to be secure and accordingly, 
the sender does not accept liability for any such data corruption, 
interception, unauthorized amendment, viruses, delays or the consequences 
thereof.
Any views expressed in this electronic transmission are those of the 
individual sender, except where the message states otherwise and the 
sender is authorized to state them to be the views of SAP AG or any of its 
subsidiaries. SAP AG, its subsidiaries, and their directors, officers and 
employees make no representation nor accept any liability for the accuracy 
or completeness of the views or information contained herein. Please be 
aware that the furnishing of any pricing information/ business proposal 
herein is indicative only, is subject to change and shall not be construed 
as an offer or as constituting a binding agreement on the part of SAP AG 
or any of its subsidiaries to enter into any relationship, unless 
otherwise expressly stated. 

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf 
Of John White
Sent: Wednesday, 20 June 2007 6:53 AM
To: SAP Workflow Users' Group
Subject: RE: Difference between Business object method and ABAP class 
methodsin atask

I don't know the answer, but here is what I found on SDN. My experience 
has only been with BOR object, creating new, and extending existing ones. 
Hope this helps!

BOR objects is the category that have been around for a long time, while 
CL is a (relatively) new possibility. You should use whatever is more 
practical in each case. For instance, if you are working with employees 
and everything you need is in BOR object BUS1065 it makes sense to use 
that BOR object. If you find a class that has everything you need it makes 
(even more) sense to use that.

If you have to create a completely new object type you should try to 
create a class instead of a new BOR object. If you simply need a little 
bit of additional functionality or a new virtual attribute, my 
recommendation would be to extend the object type that exists instead of 
trying to create a class that extends a BOR object. 

and,
ABAP CLASS
Template for objects in ABAP Objects. Defined using CLASS - ENDCLASS 
either globally in a class pool or locally in another ABAP program. The 
definition of a class is made up of a declaration section for the 
declaration of theclass components and animplementation section for the 
implementation of the methods.
BOR-OBJECT TYPES
mySAP Technology service and directory of all object types (business 
object types, organization object types and technical object types) in 
hierarchical order.
The object types are each assigned to a packet (and thus indirectly also 
to an application component).
Directory of all object types in hierarchical order.
The object types are each assigned a development class (and thus 
indirectly also to an application component).

From: sap-wug-bounces at mit.edu [mailto:sap-wug-bounces at mit.edu] On Behalf 
Of Albina Fernando
Sent: Monday, June 18, 2007 1:41 PM
To: sap-wug at mit.edu
Subject: Difference between Business object method and ABAP class methods 
in atask

Hi,

  Can anyone tell me the difference between using Business Object method 
and Class methods in the tasks of the Workflow. For eg. When creating a 
task we have 2 options. Either Assign a Business Object method or a ABAP 
Object class method. So I need to know the difference between the two. And 
also the advantages of using the two...
  Thanks a lot for all ur support.

Thanks
Albina

This email may contain confidential or privileged information for the 
intended recipient(s). If you are not the intended recipient, please do 
not use or disseminate the information, notify the sender and delete it 
from your system. Thanks

______________________________________________________________________

-- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --

This e-mail and any files transmitted with it may
contain privileged, confidential, or proprietary information
which may be protected from disclosure under law, and is
intended solely for the use of the individual, group, or entity
to whom this e-mail is addressed.  If you are not one of the
named recipients, please notify the sender by e-mail and
delete this message immediately from your computer.  Any
other use, retention, dissemination, forwarding, printing, or
copying of this e-mail is strictly prohibited.  Thank you for
your assistance.
_______________________________________________
SAP-WUG mailing list
SAP-WUG at mit.edu
http://mailman.mit.edu/mailman/listinfo/sap-wug

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.mit.edu/pipermail/sap-wug/attachments/20070620/f8f49b00/attachment.htm