Show TOC

Object documentationBusiness Object Layer

 

The business object layer (BOL) and the generic interaction layer (GenIL) belong to the business layer.

  • Business object layer:

    The business object layer stores the data of the business objects together with a defined set of attributes and relationships during runtime of a CRM WebClient UI session.

  • Generic interaction layer:

    The generic interaction layer connects the BOL to the underlying business logic and database tables.

 

Different object types are used within the BOL. There are mainly three different types of objects:

  • Root objects:

    The superordinate object within a group of objects related to each other in a hierarchical structure. A root object is also an access object, meaning that it has an ID that can be used to determine both the attributes of the access object itself and those of its dependent objects.

  • Dependant objects:

    A dependent object is a special type of business object, whose attributes cannot be determined solely from the ID of this business object, but instead, only or together with the ID of the superior access object.

  • Search objects:

    Also called query services.

Root objects — like business partners and business transactions — are implemented as hierarchies of data dictionary structures. Each BOL object is displayed in a tree structure and has only one root node. The composition of BOL objects is generic, as the BOL data structures are usually including the structures of the underlying data model of the application. You can use the component workbench (transaction code BSP_WD_CMPWB, button “BOL Model”) to see how business objects are implemented in the BOL.

Accessing the Business Object Layer

The business object layer can be accessed using the component workbench (transaction code BSP_WD_CMPWD).

In the component workbench you can see how the BOL objects are implemented in the BOL.

The tree structure in the component workbench contains the root object, the attribute structure, methods and relations. Relations describe the relationship between two BOs that is assigned a unique, cross-component name.