A single implementation of the doVerbFor() method in
the Vision Connector Framework's business object handler initiates
all business object requests. The Vision business object handler
processes all of the business objects passed between the BAPI
module and the integration broker. In the BAPI module, a
BAPI-specific business object handler supports only one BAPI;
therefore, for each supported BAPI in the SAP R/3 application, you
must have an associated BAPI-specific business object handler.
The Vision business object handler uses the verb application-specific information of a business
object to invoke the appropriate BAPI-specific business object
handler. The BAPI parameter names and formats are hard-coded in the
BAPI-specific business object handler so that the business object
handler can make an RFC call to the appropriate BAPI.
- Note:
- When business object data is returned from SAP's Java Connector
(jCO) API, the BAPI module receives values for DATS and TIMS fields
in the following formats: YYYY-MM-DD (the hyphen is
included) for the DATS data element, and HH:mm:ss (the
colon is included) for the TIMS data element. The capitalized
HH denotes 24-hour time, and not 12-hour time. The BAPI
module does not change these formats.
Figure 24 illustrates business object
processing for the BAPI module.
Figure 24. Business object processing
for the BAPI module

Once invoked by the Vision business object handler, the
BAPI-specific business object handler executes in the following
manner:
- Receives the WebSphere business object for SAP from the Vision
business object handler.
- Populates the BAPI parameters with business object data.
- Executes a BAPI call using RFC and passes the BAPI parameters
to the SAP R/3 application. The business object handler waits for
the business object data to be returned.
- Receives the business object data (BAPI parameters).
- Converts the BAPI parameters back to WebSphere business object
data.
- Passes the business object to the Vision business object
handler and ultimately to the integration broker.
- Note:
- If a BAPI module has a Return Structure or Return Table, the
connector checks for the message types A (abort) and
E (error) to determine if the event processed
successfully. A message type A or E indicates
that the event failed to process. If a BAPI does not have a Return
Structure or Return Table, you must implement your own error
handling. When a message broker is the integration broker, events
that fail in the Connector Framework are moved to the fault queue;
events that fail in the message broker environment are handled by
the MQ message flow. When InterChange Server (ICS) is the
integration broker, you can resubmit failed events using WebSphere
InterChange Server System Manager (CSM).
