Use SAPODA to generate business object definitions and business
object handlers for each RFC-enabled function that you want to
support. You can use the generated objects without any
modifications. However, you can manually edit these objects to
refine the functionality.
After the objects are generated, you must add the business
object definition and its corresponding BAPI-specific business
object handler to your WebSphere business integration system's
runtime environment.
- Use Business Object Designer to copy the business object
definition into your repository.
- Note:
- Alternatively, if InterChange Server (ICS) is the integration
broker, you can use the repos_copy command to load the
definition into the repository.
- Use a system command to copy the BAPI-specific business object
handler files to the following directory under the product
directory:
\connectors\SAP\bapi\client
The BAPI-specific business object handler files are:
- BAPI Name.java
- BAPI Name.class
For example, given the BAPI_SALESORDER_CREATEFROMDAT2
BAPI and a user-specified prefix of sap_, SAPODA generates
the following:
- sap_bapi_salesorder_createfromdat2 (business object
definition that includes all child business objects)
- Bapi_salesorder_createfromdat2.java
- Bapi_salesorder_createfromdat2.class
- Important:
- You can modify the name of the generated business object as
well as the name of its child business objects. To do so, you must
edit the definition as a text file rather than in Business Object
Designer. If you do change a business object's name, ensure that
you also modify all references to the names that you change. Also,
if you modify the names of the generated.class file for
the business object handler, you must maintain the changes for the
application-specific information for the associated business
object.
