 |
| ||||||||
When sending a transaction from Ariba to ERP or S/4 HANA via SAP Integration Suite, Managed Gateway for Spend Management and SAP Business Network, the following error is triggered in Transaction Tracker:
Fault response received from: ANXXXXXXXXXXX-T for:ANXXXXXXXXXXX-T with Status: FAILED and ErrorResponse:XXXX Suggested Action : Please contact support with ErrorCode:CIG-PLT-00676.
The cause and resolution depend on the actual error response you see next to ErrorResponse: message. Follow resolutions below according to your ErrorResponse details.
Error 1: Fault response received from: ANXXXXXXXXXXX for:XXXXX with Status:FAILED and ErrorResponse:Service Unavailable. There is no SAP Cloud Connector (SCC) connected to your subaccount matching the requested tunnel for subaccount "a8f3ed22c" and SCC location ID "XXXXX". Check the configuration on SCC and cloud side... Suggested Action : Please contact support with ErrorCode:CIG-PLT-00676.
- Solution to follow: 3294218 - Managed Gateway for Spend&Network transactions are failing with "Error: There is no SAP Cloud Connector (SCC) connected to your subaccount
Error 2: Fault response received from: ANXXXXXXXXXXX for:XXXXX with Status:FAILED and ErrorResponse:Bad Gateway. Invalid server certificate.. Suggested Action : Please contact support with ErrorCode:CIG-PLT-00676.
- Solution to follow: 3156901 - 502: Bad Gateway. Invalid Server certificate when connecting with Cloud Connector to an on-premise SAP system.
Error 3: Fault response received from: ANXXXXXXXXXXX for:XXXXX with Status:FAILED and ErrorResponse:Bad Gateway. Unable to open connection to backend system.. Suggested Action : Please contact support with ErrorCode:CIG-PLT-00676.
- Solution to follow: 3218619 - Unable to open connection to backend system: Connection refused: no further information
Error 4: Fault response received from: ANXXXXXXXXXXX for:XXXXX with Status:FAILED and ErrorResponse:Error reading XMLStreamReader: Unexpected character 'j' (code 106) in prolog; expected '<' at [row,col {unknown-source}]: [1,1].. Suggested Action : Please contact support with ErrorCode:CIG-PLT-00676.
- Solution to follow: In above case there is an error response but not in XML format. Most common issue could be related to SAP Cloud Connector. We recommend checking cloud connector trace logs for more details. Related common issue KBAs below:
- In case no errors in cloud connector logs, enabling Payload Trace option temporarily under SAP Cloud Connector > Logs and Traces and reproducing issue could provide complete details of this error response. Trace file format: traffic_trace_XXXXX_hana.ondemand.com.trc. Note: Switch off Payload trace after collecting the required details as it could slow down cloud connector performance.
Error 5: Fault response received from: ANXXXXXXXXXXX for:XXXXX with Status:FAILED and ErrorResponse: .. Suggested Action : Please contact support with ErrorCode:CIG-PLT-00676.
- Solution to follow: In above case the error response content is empty i.e. null. Reason could be destination or ERP application encountered application error or dump. In such cases check in ERP SRT_MONI, SRT_LOG, SLG1, ST22, SMICM logs and for Purchase Requisition transactions capturing SRT_UTIL trace during timestamp when transaction flow towards ERP failed in Managed Gateway for Spend&Network portal Transaction Tracker. If any middlebox like web dispatcher etc. check relevant logs.
SAP Integration Suite Managed Gateway > Managed Gateway - Platform > Managed Gateway - Buy side Connectivity
SAP Integration Suite Managed Gateway > Managed Gateway - Portal