cancel
Showing results for 
Search instead for 
Did you mean: 

BOR - what is it good for?

0 Kudos

Hello Gurus,

from time to time I stumble over BOR.

I've learned that you need it to develop workflows, from a developer's view I don't understand what's the benefit.

Where is a need for using this BOR-thing? Is there a chance to define an own BOR-thing that anyone can use?

Is it true, that these BOR-methods are separated from the ABAP-OO?

Even this BOR-Editor is strange!

Any suggestions,

thanks

Juergen

to the link droppers: i've read

are there other useful links?

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Business objects are used for workflow and for records management (the two places where i have met them).

They are unfortunately different from proper ABAP objects and behave like half objects /half procedural code.

For most of your work, they actually work well apart from the annoying difference from ABAP OO.

Espen

Answers (2)

Answers (2)

shaheryar_hashmi
Explorer
0 Kudos

Hello,

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, PO Workflows, PR 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.

Former Member
0 Kudos

This link would have been useful, rather than the one you posted.

http://help.sap.com/saphelp_47x200/helpdata/en/7e/5e11c24a1611d1894c0000e829fbbd/frameset.htm

Regards,

Subramanian V.