How To Fix HRDSYS712 - &1 objects with original system <> &2 found in table SMODILOG

SAP Error Message - Details

• Message type: E = Error

• Message class: HRDSYS - Messages for HR documentation system

• Message number: 712

• Message text: &1 objects with original system <> &2 found in table SMODILOG

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message HRDSYS712 - &1 objects with original system <> &2 found in table SMODILOG ?

  The SAP error message HRDSYS712 indicates that there are inconsistencies in the data related to the system landscape, specifically concerning the objects logged in the table SMODILOG. This error typically arises in the context of SAP HR (Human Resources) systems when there are discrepancies between the original system and the current system.
  Cause:
  The error message HRDSYS712 occurs when the system detects that there are objects in the SMODILOG table that were created or modified in a different original system than the one currently being used. This can happen due to various reasons, such as:
  
  Transport Issues: Objects may have been transported from one system to another without proper alignment of the original system information.
  System Copy or Migration: If a system copy or migration was performed, the original system identifiers may not match.
  Manual Changes: Manual changes to the configuration or data that do not align with the original system settings.
  
  Solution:
  To resolve the HRDSYS712 error, you can follow these steps:
  
  
  Identify the Objects: Use the error message details to identify the specific objects that are causing the issue. The message will typically include the object names and the original system identifiers.
  
  
  Check the Original System: Verify the original system from which the objects were transported. Ensure that the system identifiers are correct and consistent.
  
  
  Adjust the SMODILOG Table: If you have determined that the objects are indeed from a different original system and should not be there, you may need to clean up the SMODILOG table. This can involve:
  
  Deleting the inconsistent entries.
  Updating the entries to reflect the correct original system if applicable.
  
  
  
  Re-transport Objects: If necessary, re-transport the objects from the correct original system to ensure that they are aligned with the current system.
  
  
  Consult Documentation: Refer to SAP Notes or documentation related to HRDSYS712 for any specific recommendations or patches that may address this issue.
  
  
  Testing: After making changes, ensure to test the system thoroughly to confirm that the issue has been resolved and that no new issues have arisen.
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may provide additional insights or solutions for this specific error message.
  System Landscape: Ensure that your system landscape is well-documented and that all transports are managed properly to avoid such inconsistencies in the future.
  Backup: Always take a backup of the relevant tables or data before making any changes to avoid data loss.
  
  If the issue persists after following these steps, it may be beneficial to consult with SAP support or a qualified SAP consultant for further assistance.