How To Fix CM_EHHSS_INC_REC258 - Only preliminary data can be migrated for person ID &1

SAP Error Message - Details

• Message type: E = Error

• Message class: CM_EHHSS_INC_REC -

• Message number: 258

• Message text: Only preliminary data can be migrated for person ID &1

What causes this issue?

You want to migrate an incident that comprises a person entry with an
invalid ID. This happens when the person with the same ID does not exist
on the target system.

System Response

If you proceed with the migration, the system creates preliminary data
in the incident for this person in the target system.

How to fix this error?

Before you migrate the incident, you can create a person entry on the
target system that corresponds to the migrated one. Note that the new
person entry has a different ID. In this case, edit the import document
and replace the invalid ID with the new one.
Alternatively, after you migrate the incident, you can edit it and
manually select a person entry that corresponds to the preliminary
person data.

Procedure for System Administrators

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message CM_EHHSS_INC_REC258 - Only preliminary data can be migrated for person ID &1 ?

  The SAP error message CM_EHHSS_INC_REC258 indicates that only preliminary data can be migrated for a specific person ID. This error typically arises during the migration of employee data in the context of SAP's Employee Health and Safety (EHS) module or similar functionalities.
  Cause:
  The error usually occurs due to one of the following reasons:
  
  Incomplete Data: The person ID in question may not have complete or valid data in the source system, which prevents the migration of full records.
  Data Status: The data associated with the person ID may be in a status that only allows for preliminary data to be migrated. This could be due to the data being in a draft state or not fully approved.
  Configuration Issues: There may be configuration settings in the SAP system that restrict the migration of certain types of data for specific person IDs.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  
  Check Data Completeness:
  
  Verify that all necessary data for the person ID is complete and correctly entered in the source system. Ensure that there are no missing mandatory fields.
  
  
  
  Review Data Status:
  
  Check the status of the records associated with the person ID. If the records are in a draft or incomplete state, you may need to finalize or approve them before migration.
  
  
  
  Consult Migration Guidelines:
  
  Review the migration guidelines or documentation provided by SAP for the specific module you are working with. There may be specific requirements or steps that need to be followed.
  
  
  
  Adjust Configuration:
  
  If applicable, review the configuration settings in the SAP system to ensure that they allow for the migration of the required data types. You may need to consult with your SAP Basis or EHS configuration team.
  
  
  
  Use Migration Tools:
  
  If you are using SAP's migration tools (like LSMW or SAP S/4HANA Migration Cockpit), ensure that you are following the correct procedures and mappings for the data being migrated.
  
  
  
  Consult SAP Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP Support for further assistance. They may provide insights specific to your system configuration or data.
  
  
  
  Related Information:
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  Documentation: Review the official SAP documentation for the EHS module or the specific migration process you are using.
  Community Forums: Engage with SAP community forums or user groups where similar issues may have been discussed.
  
  By following these steps, you should be able to identify the root cause of the error and take appropriate action to resolve it.