Business object structure

The connector uses an RFC Server-specific business object handler to map each business object attribute to an RFC-enabled function's parameter. The connector, each business object, and each RFC Server-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 RFC Server-specific business object handler supports both single- and multiple-cardinality relationships between business objects.

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

Table 31. Correspondence between RFC-enabled functions and business objects
RFC-enabled function 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 57 illustrates the association between a WebSphere business object and an RFC-enabled function, in this instance, a BAPI. The figure illustrates a fragment of a user-defined sap_bapi_po_create business object, which corresponds to the BAPI_PO_CREATE BAPI.

Figure 57. Mapping between a business object and a BAPI

Copyright IBM Corporation 1997, 2004. All Rights Reserved.