Do you have any question about this error?
Message type: E = Error
Message class: HRPAY99RU_RMS_DB - RMS DB: Messages for RMS persistence layer
Message number: 105
Message text: Record &1 already edited with different in-period date &2
You have requested an RMS record object with an in-period end date for
the key referenced in the error message, but there already exists a
record with unsaved changes with a different in-period end date. To
avoid data corruption, the system terminated the request.
System reports an error message.
In most cases, this message indicates that there is an error in record
processing by the report business logic. Contact your support or SAP
Support to resolve this issue.
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.
HRPAY99RU_RMS_DB105
- Record &1 already edited with different in-period date &2 ?The SAP error message
HRPAY99RU_RMS_DB105
indicates that there is a conflict with the editing of a record in the payroll system. Specifically, the message states that a record (identified by&1
) has already been edited with a different in-period date (&2
). This typically occurs in the context of payroll processing when multiple users or processes attempt to edit the same record simultaneously or when there are inconsistencies in the data being processed.Cause:
- Concurrent Editing: Another user or process has already edited the record for the specified period, leading to a conflict.
- Data Inconsistency: There may be inconsistencies in the payroll data, such as overlapping periods or incorrect date entries.
- System Configuration: The system may not be configured to handle certain scenarios, leading to conflicts in record editing.
Solution:
- Check for Concurrent Edits: Verify if another user is currently editing the same record. If so, coordinate with that user to resolve the conflict.
- Review Payroll Data: Check the payroll data for the employee associated with the record. Ensure that there are no overlapping periods or incorrect date entries.
- Reprocess the Record: If the record is locked due to a previous edit, you may need to wait until the other process is completed. Once it is free, you can attempt to edit the record again.
- Consult Logs: Review the system logs for any additional error messages or warnings that may provide more context about the issue.
- System Configuration: If this issue persists, consult with your SAP Basis or HR module administrator to review the system configuration and ensure it is set up correctly to handle payroll processing.
Related Information:
PA30
(Maintain HR Master Data) or PC00_MXX_CALC
(Payroll Calculation).If the issue continues after trying the above solutions, it may be beneficial to escalate the matter to your SAP support team for further investigation.
Get instant SAP help. Start your 7-day free trial now.
HRPAY99RU_RMS_DB104
Object with key &1 is to be read, but not found
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
HRPAY99RU_RMS_DB103
Object with key &1 is to be created, but exists in database
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
HRPAY99RU_RMS_DB120
* ABAP OS wrapping messages
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
HRPAY99RU_RMS_DB121
Object with key &1 not found in database
What causes this issue? You have requested an object with a specified key that is not present in the RMS ( <DS:GLOS.5CF3FCDB46F61ED681B30D9E90C5CC...
Click on this link to search all SAP messages.