Business Object Repository

A business object repository is a virtual space in which business objects are stored. Its purpose is to simplify the way developers work with business software applications.

A BOR is a central access point to all SAP business object types, their key fields and BAPI methods. It contains all the information that you need to integrate the correct object type definition and BAPI calls in an application program.

Object definition

The business object repository stores information on business objects. The repository includes information about business object types, key fields and methods. This information is useful for integrating the correct object type definition and BAPI calls in an application program.

BOR provides the following services:

It defines the implementation of business object types and the corresponding key fields, and provides BAPI methods for these types. It also records interface changes made to BAPIs and maintains previous interface versions for reconstructed interfaces.

In addition, the repository describes how the business object interacts with other objects and how to use the attributes of the object type.

Most data in a business object is stored in tables and can be accessed through attributes. Attributes can represent calculated values or be directly linked to a table field. Besides table fields, business objects can store references to external applications in a reference table. This allows a business object to be linked to other tables even if its own tables are deleted.

Object persistency

Objects in ABAP code are transient – they exist only within the internal session of the program. Data in objects (such as the attributes of classes) lives only until they are deleted by the Garbage Collector.

However, many applications need persistent data that can be accessed from other systems. This type of data is often stored in database tables, but also in files on application and presentation servers.

To solve this problem, business objects in Flow can notify interested listeners about important life cycle events, such as object creation, change or deletion. This notification mechanism enables extensions to register themselves at their host object in order to perform necessary cleanup or initialization actions on the underlying persistent state.

In addition, non-root objects (e.g., baskets) may have a unique ID that can be used to identify the object. Depending on how these entities are reached, this ID can be a UUID or an auto-generated sequence number in the database.

Object retrieval

The business object repository (BOR) is the central access point for all external applications to access SAP business objects and interface types and their BAPI methods. It defines and describes all the relevant details of these object types, including their key fields and BAPI calls.

BOR is a valuable source of information, and it is essential for all developers. Developing an application program requires knowing which SAP business object types to use, how to define them, and which BAPIs to call to integrate them with the SAP system.

This knowledge is best gained by reading the definition of the SAP business object types and their attributes, which you can find in the BOR browser. This is the best place to start when creating an SAP application program or using SAP Business Workflow, as it provides the most complete and up-to-date definitions for the SAP business object types and their functions.

Whenever the user needs to process a list of objects, they can use the iterator pipelet to retrieve them from the business object repository. It is important to note that iterators should not have any lookup logic for looking up the objects to be processed.

Object update

The Business Object Repository (BOR) is the central access point to SAP business objects types and their key fields and BAPI methods. The BOR also contains all the details you need for integrating object types and BAPI calls into your application program.

The BOR also allows you to create, modify or display an object in the business object repository. For this you need to know the name, ID or description of an object.

To do this, you can use the Business Object Repository Browser in the business object builder.

Alternatively, you can also use the Object Repository pane in UFT One.

This pane stores all associated shared object repositories for your application area, and you can modify, delete or prioritize these files.

Using the Object Repository pane, you can also define new shared object repositories for your application areas. After you create the repository, it is saved to a specific location in the ALM Test Resources module and associated with your application area.

Visit also at Tech In Journal for more qaulity tech information.