‎2010 Jun 09 6:10 PM
Hi to everybody,
I'm developping an application to manage authorization requests.
I began it using BOR, for the reason that i'll manage different status creating them by SAP Workflow.
When I started with the application, we use the BOR FORMABSENC like an example, but while I were developping I found out several problems and I decided to create it with CLASS and SAP Work.
I would like to know what's the difference between BOR or Class, which of both options you recommend me and why you've decided on it.
I´m looking forward to a response soon.
Thank you.
Nicocer.
‎2010 Jun 09 8:19 PM
Objects defined in the BOR are basically a very old way of introducing OO concepts in ABAP. Classes defined via the class builder are a newer approach (but have now been around for quite some time) and represent also the way ahead.
If possible you should always stick to ABAP classes instead of BOR objects. However, there are still transactions where you can only reference BOR objects (historical reason, not everything has been converted to accept also the new ABAP OO classes, take for example IDoc workflows), but the general recommendation is to use BOR wrapper objects around ABAP classes in that case. The most compelling reason is the good tool support for ABAP classes and that support is much easier because you'll find more developers knowing ABAP classes than BOR objects in detail.
I strongly recommend the [blogs from workflow guru Jocelyn Dart|http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/u/4075] [original link is broken] [original link is broken];. They are an excellent starting point. A search on SDN will give you many more materials...
Oh, and by the way: I think your question probably would have been better in the forum, because your question seems to be focused on the workflow context (though I suspect they must have discussed this many of times)...
‎2010 Jun 09 8:19 PM
Objects defined in the BOR are basically a very old way of introducing OO concepts in ABAP. Classes defined via the class builder are a newer approach (but have now been around for quite some time) and represent also the way ahead.
If possible you should always stick to ABAP classes instead of BOR objects. However, there are still transactions where you can only reference BOR objects (historical reason, not everything has been converted to accept also the new ABAP OO classes, take for example IDoc workflows), but the general recommendation is to use BOR wrapper objects around ABAP classes in that case. The most compelling reason is the good tool support for ABAP classes and that support is much easier because you'll find more developers knowing ABAP classes than BOR objects in detail.
I strongly recommend the [blogs from workflow guru Jocelyn Dart|http://www.sdn.sap.com/irj/scn/weblogs?blog=/pub/u/4075] [original link is broken] [original link is broken];. They are an excellent starting point. A search on SDN will give you many more materials...
Oh, and by the way: I think your question probably would have been better in the forum, because your question seems to be focused on the workflow context (though I suspect they must have discussed this many of times)...
‎2010 Jun 10 3:28 AM
hello,
It is always good to adapt to object oriented approach for all sort of ABAP development. Using BOR is the conventional style of build. You will have better control on the program flow and design using OOABAP. Read some demo chapters available on internet of SAP press book "official abap programming guidelines" for your answer.
Thanks