Supported data operations on BAPI business objects, WebSphere Adapter for SAP Software

The operation of a BAPI business object is the name of the BAPI call that an adapter issues on the SAP server during outbound processing. The BAPI method determines the operation associated with it. The adapter uses the application-specific information (ASI) inside the business object definition to implement the operation.

BAPIs and BAPI work unit

Operations of a business object are invoked by the component that makes calls to SAP through the adapter. The SAP JCo APIs are used to make the call to the SAP system.

The following table defines operations that the adapter supports for BAPIs and BAPI work unit.

Note: The definitions listed in the table are the expected uses for the operations. The action taken in the SAP application is based on the meaning of the BAPI itself.

Table 1. Supported operations: BAPI business objects
Operation	Definition
Create	The top-level business object and all contained children are created.
Update	The top-level business object is modified. This operation can include adding and deleting child objects.
Delete	The top-level business object and any contained children are deleted.
Retrieve	The top-level business object and any contained children are retrieved.
Execute	The top-level business object and any contained children is executed. Note: This operation is available only if the Generate BAPIs within Wrappers check box is not selected. If the Configure Wrapper Business Object for Selected BAPI check box is selected, then other operations, such as Create, Update, Delete, and Retrieve are available.

For an operation that is not supported, the adapter logs the appropriate error and produces a ResourceException.

Result sets

The following table defines the operation that the adapter supports for BAPI result sets.

Table 2. Supported operation: BAPI result sets
Operation	Definition
RetrieveAll	All the matching records for the BAPI result set are retrieved.

The adapter uses the metadata information from the wrapper business object to find the operation associated with the received RFC-enabled function name. The adapter uses the application-specific information (ASI) inside the business object definition to implement the operation. After the adapter determines the operation, it sets it on the business object before sending it to the endpoint.