Hierarchy
SAP_HRCCH (Software Component) Sub component SAP_HRCCH of SAP_HR⤷
PA-PA-CH (Application Component) Switzerland⤷
PB02 (Package) HR Master Data: Switzerland 
Attribute
| Message class |  |
5C | |
| Short Description |  |
HR: Messages for Switzerland | |
| Message Number |  |
380 | |
| Documentation status | Space: object requires documentation |
||
| Authorization check Error Message | |||
| Changed On |  |
20081217 |
Message Text
Help Document
Diagnosis
The system received a response that was not classified as an error message. According to the guidelines for wage data transfer, responses that are not error messages must be signed by the sender (here: By the distributor to which you sent the message). The recipient must check the signature of the response and must not further process responses with an invalid signature in the usual way.
This is most likely to affect the verification of the correctness of the response signature.
This can be for the following reasons:
- The distributor has not signed the response, or has signed it with an invalid signature. You can determine whether the signature is missing entirely by displaying the corresponding XML file in the process data overview.
- The content of the response was forged or changed, either intentionally or unintentionally, on the way from the distributor to you.
- The distributor also coded the response
- The signature check does not work or is set up incorrectly (for example, is checked against the incorrect certificate, or an error message was incorrectly not identified as such).
- The PI disappeared between receipt of the response and the signature check, or can no longer be reached.
System Response
The received response is saved with the process data of the current step for further analysis. The data from the response must not be further processed in the usual way.
Procedure
You can view or download the received response as an XML file in the process data overview for further analysis. You can use the interoperability check to check whether all systems can be reached.
Depending on the cause, contact your system administrator, the distributor, or support.
You can repeat queries on the processing status of sent wage notifications (meaning a response with a valid signature and OrderID has already been received) by manually resetting the process to the "Query Status Again" step and restarting.
If you need to resend the wage notification and a 'jobkey' element is contained in the notification with the invalid signature in the XML display, check with the distributor whether the job should be stopped before it is resent or if you should indicate the new notification as a replacement notification.
To indicate the notification as a replacement notification, when recreating the notification enter the content of the "OrderID (ELM)" field from the notification context (select step 0 and the "Display" pushbutton) and the content of the 'ResponseID' field from the distributor's response (use XML file display and search function) in the data extractor's selection screen (report 'RPLELMC0').
Sending and receiving coded messages is currently only an optional wage standard option and is not supported. In this case, ask the distributor to send the responses uncoded. (Note: In the configuration, the PI enables the activation the coding/decoding in the same way as for the signature. This option may work, but it has not been certified and tested).
Procedure for System Administration
The signature check is performed by the PI. The cause can be further analyzed via the security logs and the message monitor. In particular, this means that it can be checked whether the signature check or the signature is incorrect.
For the signature check to work, the correct distributor's certificate must be imported into the key store and be configured for the corresponding integration scenario.
History
| Last changed on/by | |
20110809 | SAP |
| SAP Release Created in |
