Unzip the archive and open result.html or index.html (later XPI Inspector releases).Ģ.1.Download the ZIP file to your local computer.Looking into the XPI Inspector trace file Repeat the procedure from Step 2 but select Example 71 - Elster instead of Example 50 - XI Channel.īoth Example 50 and Example 71 can be relevant for the troubleshooting. As soon as the error message appears, click on Stop to stop inspection of the tool.Start the XPI Inspector tool by clicking on Start button.The SOAP Receiver Communication channel, where the ERiC application is triggered which transfers data from the PI system to the Clearingstelle.The RFC Sender Communication Channel, which connects the FI system to the PI system.Select Example 50 - XI Channel and add the following channels.It's strongly recommended to use the latest XPI Inspector tool. All versions of the XPI Inspector older than 4.13 can cause some DB connections opened by the tool to stay active for a long time. A new window will up showing the version number and the SAP Note that can be used to download the tool. Open the URL Check the version of the XPI Inspector in the system.It's crucial to install the latest version of the XPI Inspector tool as from version 6.6 a new Elster related example is available. Install XPI Inspector tool by deploying the EAR file which you were given in an OSS incident. The best way to troubleshoot these kind of scenarios is to trace the error with the XPI Inspector tool ( SAP Note 1514898).
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |