Use SAPODA to generate RFC-enabled function-specific business object definitions and RFC Server-specific business object handlers for each RFC-enabled function you want to support. You can use the generated files with minimal modifications.
The only edit you must make is specifying the name of the destination collaboration in the verb application-specific information of the server verb.
After the business object definition and its corresponding RFC Server-specific business object handler are generated, you must add the business object definition to your WebSphere business integration system's runtime environment.
\connectors\SAP\bapi\server
The RFC Server-specific business object handler files are:
For example, given the BAPI_PO_CREATE RFC-enabled function and a user-specified prefix of sap_, SAPODA generates the following:
The following are tips and tricks for developing business objects and RFC Server-specific business object handlers.
Most RFC-enabled functions use the same name for the return object. When SAPODA generates a business object definition, it creates a child business object to represent this return object. If multiple business object definitions contain an identically named child business object, you can add the definition for child business object into the repository only once.
To enable multiple business objects to contain the return business object, you must modify the name of the return business object to be unique for each business object.
To rename the return business object, modify the definition of each business object definition that contains it. The definition of the child business object is contained in the same definition file as its parent.
To rename the child, do the following:
SAPODA interprets all RFC-enabled function interface parameters and, for each one, it creates a corresponding WebSphere business object attribute or child business object. To increase performance of business object processing, remove all unrequired attributes and business objects from the business object definition.
To increase performance of business object processing, you can also remove all unrequired importing and exporting table parameter values from the application-specific information.
After definition generation, you can use Business Object Designer to manually edit the business object definition if you require other changes. However, be careful that you remove only attributes that you absolutely will not be using.
SAPODA uses the name of the RFC-enabled function module to name the generated business object. You can use a text editor to modify a business object's name.
To change a generated business object's name:
Table parameters can be both importing and exporting parameters. If you do not require importing or exporting of values for a table parameter, you can remove it from the application-specific information.
For example, for a create operation, if you do not need to return the table data from the SAP application after the create operation has completed, you can remove the exporting parameter value (such as Etable name).
For a retrieve operation, you do not need to specify any importing table parameters. Therefore, you can remove the importing parameter value (such as Itable name).
For example, to remove the ETable_7 exporting parameter in Figure 30, you would do the following:
ITable_7:
ITable_7:
IField_14: