BAPI

[Former Member]

Hi all,

Can any one let me know what are business objects and wat is BUS and how are they configured to API.

Thanks

ZAf

[Former Member]

generally we represent the business objects with BUS names.....

bus2032 represents business object for salesorder

BUS2075 represents business object for internalorder

BUS2005 represents business object for productionorder

BUS2004 represents business object for planned order.

in the each of the business object(each scenario like consider sales order) u will find number of the methods to create sales order(create bapi),to change sales order(change bapi), to get the details of sales order(get list bapi and get detail bapi)............

Business object technology and programming are based on the concept of business objects. Real objects, such as an employee or a sales order, can be represented as business objects in business application systems, such as the SAP Systems.

SAP business objects encapsulate SAP data and business processes while hiding the structure and implementation details of the underlying data.

Structure

To achieve this encapsulation, SAP business objects are created as entities with several layers.

At the core of an SAP business object is the kernel, which represents the object's inherent data.

The second layer, the integrity layer, represents the business logic of the object. It comprises the business rules for consistent embedding in the environment and the constraints regarding the values and domains that apply to the business object.

The third layer, the interface layer, describes the implementation and structure of the SAP business object, and defines the object's interface to the outside world.

The fourth and outermost layer of a business object is the access layer, which defines the technologies that can be used for external access to the object’s data, for example, COM/DCOM ((Component Object Model/Distributed Component Object Model). It specifies the technologies that enable object data to be accessed from external programs, for example, COM/DCOM (Component Object Model/Distributed Component Object Model).

As the graphic shows, the interface layer separates a business object's data and the applications and technologies that are used to access it. To the outside, SAP business objects reveal only their interface, which consists of a set of clearly defined methods. Applications can only access the business object data through the object's methods.

An application program wanting to access an SAP business object and its data, only needs the information required to execute the methods. Therefore, application programmers can work with SAP business objects and call their methods without having to know anything about the object's underlying implementation details.

The set of methods associated with a business object represents the object's behavior. When a method is executed on a business object, the method can change the object's internal state, that is, the object's data.

For example, one method that you can use on the business object Employee is to "check for the employee's existence".

In an SAP System, all SAP business object types and their methods are defined and described in the Business Object Repository (BOR).

Each individual business object belongs to a specific object class, depending on the nature and general characteristics of the object. These object classes are called object types. For example, the individual employees working in an organization are all part of the Employee object type.

The object types are descriptions of actual SAP business objects that can exist in an SAP System; that is, each SAP business object is a representation, or instance, of its object type. For example, the employee with the name Charlie Jones and the employee number 1234 is an instance of the Employee object type.

When writing object-oriented application programs, developers identify the object types that are to be used in their programs. At runtime, the application program accesses the specific instances of the defined object types.

If an application program uses an instance of a business object, the object instance responds only to the set of characteristics and methods defined for its own object type. SAP business object types are defined by the following:

Object type

The object type describes the features common to all instances of that object type. This includes information such as the unique name of the object type, its classification, and the data model.

Key Fields

The key fields determine the structure of an identifying key, which allows an application to access a specific instance of the object type. The object type Employee and the key field Employee.Number are examples of an object type and a corresponding key field.

Methods

A method is an activity that can be performed on a business object and that provides access to the object data. A method is defined by a name and a set of parameters and exceptions that can or must be provided by the calling program in order to use the method. BAPIs are examples of such methods.

Attributes

An attribute describes a specific property of a business object. For example, Employee.Name is an attribute of the Employee object type.

Events

An event signals that the status of a business object has changed.

Inheritance and Polymorphism

reward points if helpful