Troubleshooting

Testing Proxy Calls

You can test a proxy call in ABAP proxy generation in the menu Proxy → Test Interface.

Troubleshooting

There are two categories of errors, namely those that occur during generation and those that occur at runtime. The proxy generation function must be able to access the interface description in the Integration Repository to be able to generate proxies. To send a message at runtime involves a whole series of Exchange Infrastructure components. If a transfer problem occurs, it is either because configuration is not yet complete or the Exchange Infrastructure is not yet fully established (Integration Server not recognized, for example). Compared with errors that occur during generation, runtime errors are more difficult to localize.

The following table summarizes the different types of error and their possible cause:

Type of Error	Possible Causes
Unable to generate a proxy	Server for the Integration Repository not loaded or not entered (check by choosing Goto → Test Connection in transaction SPROXY). The WSDL that was read from the Integration Repository contains errors or is not supported by proxy generation.
Unable to send a message to a receiver	A transferal error can have many causes, for example: The Integration Server address is not recognized by the proxy runtime No inbound interface could be assigned to the outbound interface during interface determination. Interface determination has possibly not been configured. The name of the sender or receiver system could not be found in the Integration Directory or the corresponding server could not be reached You have not configured the Integration Server correctly It is beyond the scope of this documentation to describe the configuration of the entire infrastructure. See the Configuration Guide for more information. There is a monitor for message processing in the Integration Engine. See: Administrative Tasks .

Type of Error

Possible Causes

Unable to generate a proxy

Server for the Integration Repository not loaded or not entered (check by choosing Goto → Test Connection in transaction SPROXY).
The WSDL that was read from the Integration Repository contains errors or is not supported by proxy generation.

Unable to send a message to a receiver

A transferal error can have many causes, for example:

The Integration Server address is not recognized by the proxy runtime

No inbound interface could be assigned to the outbound interface during interface determination. Interface determination has possibly not been configured.

The name of the sender or receiver system could not be found in the Integration Directory or the corresponding server could not be reached

You have not configured the Integration Server correctly

It is beyond the scope of this documentation to describe the configuration of the entire infrastructure. See the Configuration Guide for more information. There is a monitor for message processing in the Integration Engine. See: Administrative Tasks .