Hierarchy

⤷

⤷

Attribute
Message class | ![]() |
5C | |
Short Description | ![]() |
HR: Messages for Switzerland | |
Message Number | ![]() |
368 | |
Documentation status | ![]() |
||
Authorization check Error Message | |||
Changed On | ![]() |
20081217 |
Message Text
Help Document
Diagnosis
The recipient responded to your query with an error message (SOAP fault).
Most technical errors are responded to with a SOAP fault. This includes problems with transfer, decoding, or validation of a document that is not well formed. The SOAP fault transports error information within a SOAP message and comprises the following elements:
- Fault code element # Enables the fault to be classified
- Fault string element # Contains an explanation for the fault that can be read by users
- FaultActor element # Describes the part of the SOAP process where the error occurred
- Detail element # Additional information on fault
System Response
The B2A process is stopped. Your query (submitting the wage notification or querying the status) cannot be performed successfully.
Procedure
Read the following error messages for the individual elements of the error message. They contain any additional information on the cause of error and its correction.
If required, perform an interoperability check (go to the corresponding status) to exclude a problem with the content of the sent message.
If the problems are with the connection, contact the system administrator or check with the recipient whether there are (known) problems there with the ability to receive.
If the problems are with the content of the wage notification, depending on the type of problem, you have the following options:
- Correct master data or payroll results, end the current process by setting an error status, and generating a new corrected wage notification with the data extractor (report 'RPLELMC0').
- If XML was generated incorrectly, send a customer message to SAP.
Procedure for System Administration
The corresponding XML message can be downloaded via the display function of the B2A manager and analyzed. For more information, see the message monitor (transaction 'SXMB_MONI') of the connected PI. The problem could also be with the recipient.
History
Last changed on/by | ![]() |
20110809 | SAP |
SAP Release Created in |