1845770 - Error Returned by Check Connection in Communication Arrangement Really Means Communication Problem between SAP Cloud for Travel and Expense System and Integrated Backend System?

SAP Knowledge Base Article - Public

1845770 - Error Returned by Check Connection in Communication Arrangement Really Means Communication Problem between SAP Cloud for Travel and Expense System and Integrated Backend System?

Symptom

You, as a system administrator, want to use Check Connection in a Communication Arrangement to see if the communication between SAP Cloud for Travel and Expense system and integrated backend system (such as SAP ERP system) works. But you may find the transferred document (such as IDoc) can be successfully sent from SAP Cloud for Travel and Expense system and received by backend system even Check Connection returns some error.

Reproducing the Issue

  1. Go to the Application and User Management work center.
  2. Select the Communication Arrangements view.
  3. Select one arrangement, such as SAP ERP Financials Using IDoc.
  4. Select the Edit button.
  5. Choose the Technical Data tab.
  6. Select the Edit Advanced Settings.
  7. Select the Outbound tab.
  8. Select the Check Connection button.

The system may return some error, such as:

Error accessing service; Service ping ERROR: Not Acceptable (406)

But if you post an expense report to backend ERP system, you may find the system correctly receive the corresponding IDoc. 

Cause

You have to make sure how your system landscape is configured. Some customers use middleware in between SAP Cloud for Travel and Expense system and backend ERP system, such as Microsoft BizTalk or Software AG WebMethods. Check Connection feature for Outbound in Communication Arrangement is only valid for SAP ERP system directly connecting to SAP Cloud for Travel and Expense system or SAP PI server as middleware. For the non-SAP third party middleware between SAP Cloud for Travel and Expense system and SAP ERP system, the returned ping status and/or message may not relate to correct or wrong Communication Arrangement configuration. It is always better to get a successful ping, but this is not a must. The error message of the ping does not mean the message flow cannot go through successfully from SAP Cloud for Travel and Expense system to ERP system.

Keywords

KBA , SRD-CC , Cross Components , How To

Product

SAP Cloud for Travel and Expense 1308 ; SAP Cloud for Travel and Expense 1311 ; SAP Travel OnDemand 1305