This section
describes problems that you may encounter when starting up or
running the RFC Server Module. It covers:
If the connector cannot register with the SAP application:
- Check that the SAP application is available.
- Check that you have properly set the standard and
connector-specific connector configuration properties.
Specifically, check the gwService,,
Hostname,,
RfcProgramId,,
and Modules,
properties. For more information, see "Configuring
the connector" and Appendix E,
"Troubleshooting the connector".
If your connector dies, check the following:
The following subsections provide suggestions for common event
handling problems.
If a subscribing business object is not being processed by the
RFC Server Module, then:
- Check that the vision connector framework is set to call the
RFC Server Module. The "Modules"
property must be set as follows: RfcServer.
- Check that the connector subscribes to the business
object.
- Check that the SAPODA-generated BAPI-specific business object
handler class file is in the \bapi\server directory. If
the class file is not in this directory, then the BAPI 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 BAPI business object handler name in the
business object verb application-specific information is correct.
For more information, see "Business object fails to
process".
- Check that the specified verb for your BAPI-specific business
object handler is correct for the type of processing you need.
Specifically, make sure that when you generated the business object
handler, you specified the appropriate verb to match the BAPI. For
more information, see
"Using generated business objects and business object
handlers"..
If a business object fails to process successfully:
- Check that the BAPI you are using has a return business object.
The RFC Server 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 RFC
Server 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. The I
parameter identifies the import parameter and the E parameter
identifies the export parameter. For more information, see "Business object fails to
process".
