Do you have any question about this error?
Message type: E = Error
Message class: HRPAYAT_3670 - Insured Person Notif. Infotype 3670 (SI Notif. Suppl. A)
Message number: 029
Message text: 'Deregistration' (record type M4) is not allowed.
An attempt was made to report changes to the first SI record (IT0044) to
ELDA using 'Deregistration' (record type M4).
A 'Cancel Registration' (record type S3) should be transferred here.
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
HRPAYAT_3670029
- 'Deregistration' (record type M4) is not allowed. ?The SAP error message HRPAYAT_3670029, which states that "Deregistration" (record type M4) is not allowed, typically occurs in the context of payroll processing in the SAP Human Capital Management (HCM) module, particularly in relation to Austrian payroll.
Cause:
This error usually arises when there is an attempt to deregister an employee from a payroll or social security system using an M4 record type, but the system does not allow this action under the current circumstances. Common causes include:
- Incorrect Record Type: The M4 record type is specifically used for deregistration, and if the employee's status or the timing of the deregistration is not appropriate, the system will throw this error.
- Employee Status: The employee may not be in a status that allows for deregistration (e.g., they may still be active or have not completed the necessary exit procedures).
- Timing Issues: The deregistration may be attempted outside of the allowed time frame (e.g., trying to deregister an employee for a period that has already been processed).
- Missing Data: Required data for the deregistration process may be missing or incorrect.
Solution:
To resolve this error, consider the following steps:
Check Employee Status: Ensure that the employee is in a status that allows for deregistration. If the employee is still active, you may need to change their status to inactive or terminated before attempting to deregister.
Review Record Type: Verify that you are using the correct record type for the action you are trying to perform. If you need to perform a different action (like a registration or change), ensure you are using the appropriate record type.
Timing Verification: Confirm that the deregistration is being processed within the correct time frame. If the payroll period has already been closed, you may need to reopen it or process the deregistration in the next period.
Data Completeness: Check that all required fields and data for the deregistration process are filled out correctly. This includes ensuring that all necessary infotypes are completed.
Consult Documentation: Refer to SAP documentation or notes related to payroll processing in Austria for any specific requirements or restrictions regarding deregistration.
Contact Support: If the issue persists after checking the above points, consider reaching out to your SAP support team or consulting with an SAP HCM expert for further assistance.
Related Information:
By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.
Get instant SAP help. Start your 7-day free trial now.
HRPAYAT_3670028
Please specify the correct registration reason.
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
HRPAYAT_3670027
A data record already exists for &1 &2
What causes this issue? You want to create a new infotype record.System Response The SAP system returns the following error message: A data record a...
HRPAYAT_3670030
Fields ADAT0 (&1) and BVAB0 (&2) must be identical
What causes this issue? You want to perform a registration for the <ZK>company pension plan</> without a social insurance contribution pe...
HRPAYAT_3670031
Pensioner and deceased (&1) must not be identical
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.