Transport & Freight Management API

AEB Transport & Freight Management API Hub

Welcome to the AEB Transport & Freight Management API hub. You'll find comprehensive guides and documentation to help you start working with AEBs T&F services as quickly as possible. Let's jump right in!

Get Started    Guides

SAP connection trouble shooting (Document Service)

You had issues with establishing a connection from your SAP to our data center?
You should check the following prerequisites:

  • When accessing the AEB data center, an HTTPS service must be running (you can access the list of services using transaction SMICM).
  • When creating via SOAMANGER and using HTTPS, the certificates must be loaded into the SSL-CLIENT (Anonymous) node. (Transaction STRUST)
  • The SAPCRYPTOLIB or COMMON Crypto DLL must be installed and active in the version according to the system requirements. (Transaction STRUST)
  • In most cases, errors when calling the Web service are logged in the ICM log. You can open this log in transaction SMICM. (Alternatively, you can open the file "dev.icm" in transaction ST11).

Issue/Error

Solution

"GET_BUSINESS_SYSTEM_ERROR An error occurred when determining the business system (SLD_API_EXCEPTION)"

Check the logical port in transaction LPCONFIG. Is it created and linked to the correct HTTP connection? No standard port must be defined for the proxy class.

Only a green tick appears in the connection test in the SM59 for an SSL connection.

The service for HTTPS is not running.

HTTPIO_PLG_CANCELED

There is probably no service available for the required process (HTTP or HTTPs) or these are not active.
Also to be checked: Is the connection in the SM59 really of type G? Are all PSEs in the STRUST below the SSL client green?

'Create failed: Argument not found'

The problem could be related to the service port - is there the correct port, for example 443', or is there a typing error (e.g. space)?
There may also be something wrong with the SSL client stored in the destination. Check it in the STRUST - is this SSL client in 'green' status? Are the AEB certificates also installed there?

'ICM_HTTP_SSL_ERROR'

The problem may be related to the SSL certificates. Are all required certificates installed in the STRUST? Has the ICM been restarted to reload them?
The correct SSL certificate list must still be entered in the connection.
A fixed IP address has been entered in the destination. For connections to the AEB computer center, the host must be rz3.aeb.de.

  • 'ICM_CONNECTION_FAILED' and in log file dev.icm the error 'NIECONN_REFUSED' occurs.

The name resolution for the host address "rz3.aeb.de" does not work because DNS is not set correctly.
The problem could also be related to the fact that a proxy is required to connect to external websites. If this is the case, the proxy parameters must be stored in the SM59 destination.

'ICM_HTTP_CONNECTION_FAILED' and in log file dev.icm the error 'NIECONN_REFUSED' occurs.

This may be because the destination forgot to activate SSL. The correct SSL client certificate must also be selected there.

The firewall may block the connection to the target system. It is possible that the port of the target system is not released.

ICM_HTTP_CONNECTION_FAILED' always occurs.

Several possible causes. The problem could be related to the port entered in the SM59. Is the correct HTTPS port 443 or the correct HTTP port of the target system stored there? Or is a proxy required for connections?

ICM_HTTP_CONNECTION_FAILED' occurs sporadically only

The error ICM_HTTP_CONNECTION_FAILED means that no connection could be established between SAP and the target system. If this message occurs only sporadically, it may be a problem at the TCP level of the server on which the AEB solution is running.
Microsoft documents a parameter in the registry for Windows to release TCP connections after a certain waiting time: https://technet.microsoft.com/en-us/library/cc938217.aspx
Since the value is usually set to 120 seconds, reducing the waiting time can solve the problem.

Translated with www.DeepL.com/Translator

'ICM_HTTP_TIMEOUT'.

It may be due to the proxy used, the SSL certificates must be known there. The proxy must not hold obsolete certificates. If so, remove them from the certificate memory. Even if a decryption of the SSL connection can lead to the error.

Unsupported xstream found: (HTTP Code 200 : OK)

One possible cause is incorrect SSL settings in the connection or the logical port.

SOAP:1.007 SRT: Unsupported xstream found: (HTTP Code 404 : Not Found)

An incorrect path prefix is entered in the destination or logical port.

SOAP:1.023: SRT: Processing error in Internet Communication Frame-work: ("ICF Error when receiving the response: ICM_HTTP_CONNECTION_BROKEN")

This error means that the already established connection has been interrupted. This is most likely due to the fact that there are short interruptions in the network / Internet connection. This may also occur if the password of the connection user is wrong.

ICF Error when receiving the re-sponse: ICM_HTTP_CONNECTION_FAILED

Error pattern: There are repeated interruptions. In between, however, many calls also work. The ICM log contains the error message NIECONN_REFUSED for the affected user, but with the IP address of the proxy server. This user has no authorization to establish an external connection via the proxy.

SOAP:1.013 SRT: ASSERT failed: field is initial

See SAP Note 921347.

SOAP:1.008 SRT: Couldn't create Object: ICF error when creating HTTP client object by config for URL

The password of the connection user is incorrectly stored in the SM59 or in the SOAMANAGER.

##The AEB solution runs in the AEB data center and the connection user does not have the role I_BUSINESSFACADE in the AEB solution.

SOAP:1036 SRT: HTTP-Code 415: ("Unsupported 22Media Type")

In SOAMANGER SOAP 1.2 is set to 1.1 instead of SOAP 1.1.

SOAP:1.007 SRT: Unsupported xstream found: (HTTP Code 404 : Not Found)

An incorrect path prefix is entered in the destination or logical port.

There are some known errors and solutions:

Updated 7 days ago

SAP connection trouble shooting (Document Service)


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.