This section describes problems that you may encounter when running the BAPI
Module.
The following subsections provide suggestions for common request process
handling problems.
If a subscribing business object is not being processed by the BAPI Module,
then:
- Check that the vision connector framework is set to call the BAPI
Module. The Modules property must be set as follows:
Bapi.
- Check that the connector subscribes to the business object.
- Check that any custom business object handler files are in the
\bapi\client directory. If the class file is not in this
directory, then the custom business object handler is not invoked to process
the business object. For more information, see Using generated business objects and business object handlers..
- Check that the custom business object handler name in the business object
verb application-specific information is correct. For more information,
see Business object application-specific information..
- Ensure that when you generated the custom business object handler, you
specified the appropriate verb to match the BAPI.
If a business object fails to process successfully:
- Check that the BAPI you are using has a return business object. The
BAPI Module looks in the return business object for messages with the key
e (error) or a (abort). If the module finds one
of these keys, then it notes that the event has failed. If the BAPI
does not have a return business object, make sure you implement your own error
handling.
- Use transaction SE37 to test the BAPI associated with the failed
event. This should enable you to reproduce the failure.
If this does not work, then you may have a problem in the conversion from
internal formats to external formats. Check that you are specifying
values in the correct format. For example, for dates, SAP's
internal format is YYYYMMDD and you may be specifying the format
MMDDYYYY. This causes the BAPI to fail, because the specified format is
not understood.
- Check that the application-specific information of each attribute is
correct. If these values are not correct, then the BAPI Module does not
populate the object correctly before sending it back to the SAP
application.
- Check that the I and E parameters are specified properly. Remember
that I identifies the import parameter and E identifies
the export parameter. For more information, see "Business object fails to process".
The BAPI Module includes a dummy implementation of the
pollForEvents() method. The connector appears to be polling
because it returns a polling message. The BAPI Module does not support
polling, so ignore these messages.
If you want to implement polling for the BAPI Module, you must use the
polling capabilities in the ABAP Extension Module. For more
information, see Overview of the ABAP Extension Module..
