Skip to end of metadata
Go to start of metadata

1. Collecting XPI Inspector traces

The best way to troubleshoot these kind of scenarios is to trace the error with the XPI Inspector tool (SAP Note 1514898).

  1. Install XPI Inspector tool by deploying the EAR file which you were given in an OSS incident. 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.
  2. Open the URL http://<host>:<port>/xpi_inspector.
    Check the version of the XPI Inspector in the system. Open the URL http://<host>:<port>/xpi_inspector and click on "About". A new window will up showing the version number and the SAP Note that can be used to download the 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. It's strongly recommended to use the latest XPI Inspector tool. Currently 7.0 is the newest version.
  3. Select Example 50 - XI Channel and add the following channels.
    1. The RFC Sender Communication Channel, which connects the HR system to the PI system.
    2. The SOAP Receiver Communication channel, where the ERiC application is triggered which transfers data from the PI system to the Clearingstelle.
  4. Start the XPI Inspector tool by clicking on Start button.
  5. Login to HCM system, and open TCODE SE38. Enter report RPUTX7D0 and press F8.
  6. Select the scenario that you'd like to troubleshoot, i.e.
  7. Start the XPI Inspector tool by clicking on Start button.
  8. Run the report in HCM system.
  9. As soon as the error message appears, click on Stop to stop inspection of the tool.
  10. Repeat the procedure from Step 2 but select Example 71 - Elster instead of Example 50 - XI Channel.

2. Looking into the XPI Inspector trace file

  1. Download the ZIP file to your local computer.
  2. Unzip the archive and open result.html or index.html (later XPI Inspector releases).

2.1. Check the used URL in the SOAP receiver channel

As explained in SAP Note 2745249 - Implementation of ELSTER modules using the ERiC libraries, the target URL for the SOAP receiver channels must be changed to: http://[NW_Java_Server_HTTP_host]:[NW_Java_Server_HTTP_port]/ELSTER/elster-echo 

This is needed because with the introduction of ERiC application, the actual data sending is carried by the ERiC application and by the SOAP receiver channel anymore, which is why to SOAP receiver must point to the own host. 

Any reference to the old URLs like below is incorrect and will cause message processing failure:

http://62.157.211.58/Elster2/EMS --> http://datenannahme1.elster.de/Elster2/EMS
http://62.157.211.59/Elster2/EMS --> http://datenannahme2.elster.de/Elster2/EMS
http://80.157.84.22/Elster2/EMS --> http://datenannahme3.elster.de/Elster2/EMS
http://80.157.84.22/Elster2/EMS --> http://datenannahme4.elster.de/Elster2/EMS

2.2. Checking the Module Sequence

The SOAP Receiver Communication Channel must have the same Module and Module Parameter settings. In the XPI Inspector trace file, click on the name of one of the SOAP Receiver Communication Channels. The sequence of the Modules must look like this:

1. sap.com/com.sap.fin.xi.elster/ElsterHCMSendModule
2. sap.com/com.sap.aii.af.soapadapter/XISOAPAdapterBean
3. sap.com/com.sap.fin.xi.elster/ElsterHCMReceiveResponseModule

If the used modules and their order is not exactly the same as above, it can lead to message processing errors highlighted in KBA 2887677 - Elster ERiC errors - got unexpected document type:DOC_TYPE_UNKNOWN. The usage of sap.com/com.sap.fin.xi.elster/ElsterHCMConvertRFCToElster or AF_Modules/XMLAnonymizerBean is deprecated and should be removed.

3. Check the ERiC application logs

The ERiC application is collecting logs in the folder /usr/sap/<systemID>/<instanceID>/j2ee/os_libs/eric in the file called eric.log. This log file can reveal any validation, connection errors. The default log level is INFO but this can be increased so that the whole processing by the ERiC application is logged. There are two ways to increase it the log level.

3.1. Increase the ERiC application's log level in a channel

Open the Integration Builder of your PI/PO system and navigate to the SOAP receiver channel. In the receiver SOAP channel configuration go to the Module tab and set the module parameter with parameter name "log.detailed" and parameter value "true" for module "sap.com/com.sap.fin.xi.elster/ElsterHCMSendModule"

3.2. Increase the ERiC application's log level at application level

Open NWA → Configuration → Infrastructure → Java System Properties → Applications → fi~elster_appl → Change the log.detailed property from false to true. The property is online changeable.


  • No labels