Business object structure

The connector uses a BAPI-specific business object handler to map each business object attribute to a BAPI parameter. The connector, each business object, and each BAPI-specific business object handler are metadata-driven. The application-specific information provided in the metadata of each business object and business object handler allows you to add connector support for a new business object and its handler without modifying connector code. Instead:

Each BAPI-specific business object handler supports both single- and multiple-cardinality relationships between business objects.

A business object based on a BAPI can contain no more than two levels of hierarchy. Therefore, all BAPI simple parameters correspond to attributes of the top-level business object, and BAPI structure and table parameters correspond to child business objects.

Table 31. Correspondence between BAPIs and WebSphere Business Objects for SAP

BAPI Interface Parameter WebSphere Business Object for SAP
Simple field Attribute of the top-level business object
Structure Single-cardinality child business object
Table Multiple-cardinality child business objects
Note:
Importing and exporting parameters can be simple field or structure parameters.

Figure 25 illustrates the association between a business object and a BAPI. The figure illustrates a fragment of the sap_bapi_salesorder_createfromdat2 business object, which corresponds to the BAPI_SALESORDER_CREATEFROMDAT2 BAPI.

Figure 25. Mapping between a business object and a BAPI


Copyright IBM Corp. 1997, 2003