How To Fix HRPAYCH_ELM40067 - Fehler beim Signieren und Verschlüsseln: XML-Datei invalide (&1)

SAP Error Message - Details

• Message type: E = Error

• Message class: HRPAYCH_ELM40 - Messages for Withholding Tax

• Message number: 067

• Message text: Fehler beim Signieren und Verschlüsseln: XML-Datei invalide (&1)

Was verursacht dieses Problem?

Failed to encrypt or create the electronic signature, because the ELM
XML instance document to be signed or encrypted contains an error.

Systemantwort

Cannot perform the encryption or create the signature.
If this occurs when sending the ELM pay report, then the pay report
cannot be sent.

Wie behebe ich diesen Fehler?

The forgoing error message may contain information about the reason for
the error in the file.
This error typically occurs when the XML document is not well-formed
owing to errors during data acquisition or generation of the unsigned
and unencrypted instance document.
You can find additional information on the cause of this below, if the
error occurs when sending the report from within B2A Manager:
Check the invalid instance document for the report or download it. Then
have the instance document checked in an external validation tool to
validate whether it is well-formed.
You can access the unsigned and unencrypted instance document as
follows:
Go to the B2A process where the error occurred in B2A Manager:
Open the B2A process history.
Select the process step with the status/sub-status "<ZK>New</>"/"<ZK>Add
Report</>".
Click on <ZK>"</><PF>View</><ZK>"</>to access the pay report contents
<ZK><PF>.</></>
Click on "<PF>XML Preview</>" in the contents.
In the dialog box that opens, select whether you want to view the file
or download it.
Via a simulation run with the ELM data extractor ('RPLELMC0'):
Start the data extractor with the same parameters you used when creating
the B2A process (esp. Company, Year, Month, Domains) in simulation mode.
Click on<PF>"Pay Report"</>in the application log.
Then click on "<PF>XML Preview</>".
In the dialog box that opens, select whether you want to view the file
or download it.

Das System gibt eine Fehlermeldung aus und erlaubt Ihnen nicht, mit dieser Transaktion fortzufahren, bis der Fehler behoben ist.

The reasons for a non well-formed XML document can be as follows:
Caused by a program error during data acquisition
In this case, you usually need to load a patch over a SAP note or HR
support package. You may even be able to find the patch if it already
exists by performing a SAP reference search. Otherwise, please consult
SAP Support.
Owing to inconsistent master data or payroll results
In this case, you can redress the cause yourself by correcting the
master data and repeating the payroll run for the persons affected.
After making the correction, you should close the old B2A process in
both cases, and create a new B2A process with the data extractor. Trying
sending the message again afterwards using the new B2A process.
Advanced tips/hints for analyzing an inconsistent instance document:
The XML file view generated from within the SAP system usually displays
the XML with color highlighting and indents, provided that the
combination of operating system and front-end browser supports this and
it is well-formed. The display switches to single-color, non-indented
display, if the XML is not well-formed (regardless of the operating
system and front-end browser). After a correction attempt, this provides
you with advance indication in the XML preview in the data extractor of
whether the correction was successful, or whether an attempt to send it
has a chance of success.
A frequent cause of why the XML is not well-formed is the presence of
incomplete pairs of opening/closing XML tags (e.g. an opening XML tag
<(><<)> Correction >, which does not contain a corresponding closing XML
tag <(><<)> /Correction >), or incorrect parentheses (e.g. <(><<)> a
>... <(><<)> b >... <(><<)> /a >... <(><<)> /b> instead of <(><<)> a
>... <(><<)> b >... <(><<)> /b >... <(><<)> /a> or <(><<)>a >... <(><<)>
/a >... <(><<)> b >... <(><<)> /b >).
The name of the XML tag and its position within the XML document, and
the data before and after it, can provide conclusions on the cause of
the error or suggest terms that you can use in the SAP reference search.
If necessary, you can restrict the problem to a specific person by
looking for the first XML tag <(><<)> sd:EmployeeNumber > that appears
above the location of the error, and taking a closer look at the master
data/payment results and messages in the application log generated
during data extraction for that person.

Vorgehensweise für Systemadministratoren

If necessary, check whether the latest SAP notes/corrections in the ELM
environment (application component: 'PY-CH', software component:
'SAP_HRCCH', search term: ?ELM') are included in your SAP customer
system.

Fehlermeldungsextrakt aus SAP-System. Copyright SAP SE