Table of Contents
Table of Contents
...
Error message: "Unable to fetch content after mapping" while saving a test case.
This message means that the logging settings for the configuration scenario are not set up correctly (AM step is not being logged). Please set the logging and stating parameters as per: PI Staging and Logging for outbound messages after mapping
Error message: "SAP PO outbound message after mapping not found" while running a SAP PO Outbound test case.
The messages are visible in SAP PO monitoring; however, int4 IFTT can't fetch them.
By default Int4 IFTT only searches messages which were pushed on SAP PO during the last 10 seconds. However, however the time is taken from the system on which the Int4 IFTT is installed (for example, Solution Manager). In case the timezones of Solution Manager and SAP PO are different, you need to increase the property - SRCHSRCH_TRS_O to make up for the time difference - difference Global Parameters
Error message: "Output message has same interface as input"
The error means , that inbound and outbound interfaces are the same. In order to To avoid this message add PISENREC , add PISENREC in Additional Parameters
Error message: "ABAP stack: function module SXMB_GET_MESSAGE_LIST returned execution error 5"
Error 5 stands for 'others' in function module signature. The most probable reason for the message is an unreachable RFC destination. In this case, you should ensure , that destination is properly maintained → maintained correctly → SAP PI ABAP stack configuration
...
When you have performed value mapping during Change Management configuration, and you are still getting this error, follow these steps:
Set alternative mapping:
And fill the table this way with your external service desk guid:
Error message: "XML element, Envelope missing in SOAP message header (SAP XI Extension)"
...
It is an SAP PI ABAP interface, and the following error occurs during test case creation of execution:
It seems that an incorrect message version is fetched for a message after execution. Check configuration settings per this article: SAP PI ABAP stack configuration
...
Error message: " Internal Error 500 error " when opening transaction SOAMANAGER on the sandbox system
In case Suppose Int4 IFTT is installed on a fresh new sandbox system. In that case, there is a high possibility , that web dynpro WebDynpro applications and soamanager SOAMANAGER are not activated. After soamanager SOAMANAGER activation in transaction SICF in the following path /default_host/sap/bc/webdynpro/sap/APPL_SOAP_MANAGEMENT you still get error error "Internal Error 500 " after after successful login in soamanagerSOA Manager.
In order to To solve this problem:
- Execute report rsicf
- rsicf_service_activation with
- with the option
- option WEB DYNPRO ABAP in order to
- to make sure that Webdynpro applications are going to
- will run properly. ( SAP Note 1088717).
- In transaction SICF transaction
- , activate the following path and all services below: /sap/bc/srt (SAP Note 1124553).
Error message: "SRT Framework exception: Service Ping ERROR: Error when calling SOAP Runtime functions: SRT Couldn't create Object: ("ICF error when creating HTTP client object by config for url" when creating ports via Int4 IFTT configuration wizard or manually in SOAMANAGER
In case Suppose Int4 IFTT is installed on a fresh new sandbox system. In that case, there is a high possibility , that you will get the above error message. The reason is that in transaction STRUST there is no valid certificate for SSL client SSL Client (AnnonymousAnonymous) in transaction STRUST.
In order to To solve this problem, please make sure that:
- In the RFC connection for your SAP PI/PO, you use a user with the necessary authorization
- Download the relevant certificate from your SAP PI/PO and then import it in transaction STRUST under SSL client SSL Client ( Annonymous
- Anonymous). Add it to the certificate and save it.
Error message: "Missing message: Party: Receiver: Int.: Ns:
You're running a test case on a new environment, and you see the message above:
In order to To solve this problem:
- Check if the SAP PO ICO configuration has this receiver configured on the landscape on which you're running the test case. Make sure
- Ensure the mapping did not fail for this test case on
- case on the landscape on which you're running the test case.
- Check if the logging and staging settings are using the Int4 IFTT recommended settings and are not changed in case of this ICO only.
Error message: "Parent message: X found for Y", "Hint: Check if the BI logging is set or disable looking for parent message by additional parameter PIIGPARENT"
You tried to create a test case from a an SAP PI/PO message that was created by splitting of the original message. The split was done as a scenario that contained multiple receivers.
The original message is stored as version BI. Due to the SAP recommendation, the BI processing is not staged, so the message before the split is not visible in monitoring.
In such a case, Int4 IFTT requires logging on the BI. It might be activated globally globally (check SAP PI/PO JAVA Stack Persistence or locally in ICO settings).
If you would like to create a test case just on the final receiver, then set additional parameter PIIGPARENT = X
...
Error message: "Message processing failed in SAP PO. No Succesors" while saving a test case.
An error like on the screenshot above pops up. However, although the message looks like it was processed correctly in Message Monitor on on the PI Java stack.
Solution: Please check if this is a classical ABAP stack scenario. And if so, configure the Automation Object accordingly, i.a. define an Automation Object additional parameter "PI: Landscape where interface exists on the ABAP stack" as in the example below:
Error message: "PIT connection not enabled’" while running test cases in "PIT mode".
An error like on this can happen if the PIT connection is not correctly registered (PI connection available it is set to false). Can you You can manually register it from the EJB Explorer using the registerPitConnection, as shown in the figure below.
Random HTTP 403 errors on CPI tenants with multiple nodes
When the SAP CPI (Cloud Platform Integration) has two or more tenant management or worker nodes enabled, you You may receive an "HTTP/1.1 403" authentication error when sending requests from IFTT to the SAP CPI (Cloud Platform Integration) when the CPI has two or more tenant management or worker nodes enabled.
This situation can happen during test case execution or trace activation.
Root The root cause is described in note 2950846 - the SAP kernel encodes the cookies' value of the cookies by default and this , which breaks the load balancing feature in the CPI.
To solve the issue set profile parameter ict/disable_cookie_urlencoding to 1 or 2 depending on kernel level, as described in the note 2681175.
Int4 IFTT report is not displayed correctly
Int4 IFTT result report is displayed in SAP HTML Viewer control which uses underlying uses the underlying Web browser on the current frontend. On Windows clients, it's Internet Explorer.
Internet Explorer is displaying Intranet pages in 'Compatibility view' mode by default. Depending on network settings Int4 IFTT report address might be recognized as an intranet page and displayed in compatibility view, which causes rendering issues.
The solution is to disable the compatibility view in Internet Explorer. This can be done in Tools > Compatibility View settings by unchecking 'Display intranet sites in Compatibility View.'.
Error message: "SoapFaultCode:5..."
For SAP PO scenarios, during test case creation or execution for a specific landscape, you get the following error message:
In that case, you need to check the communication user that is used for this landscape. The proper roles for the Int4 IFTT communication user must be assigned.
...
Error message: "Get logged message bytes - returned an exception"
In case you're using payload level restrictions, make sure the Int4 IFTT communication user used to connect to the respective SAP PO landscape has all the correct user roles "XiMdt.*."
Error message: "Error while sending message to middleware. HTTP error status: 500"
In case If you're using the PI/PO interface, please make sure ensure that Int4 IFTT channels in the BC_IFTT business component are Active and are Started.