Do you have any question about this error?
Message type: E = Error
Message class: CM_EHHSS_INC_REC -
Message number: 267
Message text: User defined text type &1 not recognized; it was not migrated
You want to migrate an incident that comprises attached documents. To
import the incident documents in the <LS>Environment, Health, and Safety
</> system, you must configure correct document type mapping values in
the Legacy System Migration Workbench (LSMW). However, the mapping
values for <LS>User defined text types</> in LSMW are either invalid or
missing. The valid mapping values are as follows:
<LB>01</>
Document types that are enabled and configured in Customizing.
<LB>02</>
Plain text document type.
<LB>03</>
URL addresses.
The system cannot migrate the documents with incorrect types related to
the particular incident.
Enter valid, user-defined text type values in LSMW.
Start LSMW and then choose <LS>Maintain Fixed Values, Translations,
User-Defined Routines.</>
Choose and edit <LS>User defined text types</>.
Choose the <LS>1:1 Translation Value </>tab and specify the mapping
values.
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.
CM_EHHSS_INC_REC267
- User defined text type &1 not recognized; it was not migrated ?The SAP error message CM_EHHSS_INC_REC267 indicates that a user-defined text type specified in your system is not recognized because it has not been migrated. This typically occurs in the context of the SAP Environment, Health, and Safety (EHS) module, particularly when dealing with incident records or similar data structures.
Cause:
- Migration Issues: The error often arises during data migration processes where custom text types were not properly migrated from a previous system or version.
- Configuration Problems: The user-defined text type may not be configured correctly in the system, or it may have been deleted or renamed.
- Data Inconsistency: There may be inconsistencies in the data where the system is trying to reference a text type that no longer exists.
Solution:
Check Configuration:
- Go to the configuration settings for user-defined text types in the EHS module.
- Ensure that the text type in question is defined and active in the system.
Data Migration:
- If you are in the process of migrating data, ensure that all necessary user-defined text types have been included in the migration plan.
- Review the migration logs to identify any issues that occurred during the migration of text types.
Create or Restore Text Type:
- If the text type is missing, you may need to create it again in the system.
- If it was renamed or modified, ensure that the references in your data are updated accordingly.
Consult Documentation:
- Review SAP documentation or notes related to the EHS module and user-defined text types for any specific instructions or known issues.
Contact SAP Support:
- If the issue persists after checking the above steps, consider reaching out to SAP support for assistance. They may provide patches or additional guidance based on your specific system configuration.
Related Information:
By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.
Get instant SAP help. Start your 7-day free trial now.
CM_EHHSS_INC_REC266
Import mapping node name for field name "&1" is missing
What causes this issue? You want to migrate the customer-specific enhancement data of an incident to the <LS>Environment, Health, and Safety<...
CM_EHHSS_INC_REC265
Damage type "&1" not valid for equipment type; damage was not imported
What causes this issue? You want to migrate an incident that comprises a damage type that applies to an asset of type <LS>Equipment</>. H...
CM_EHHSS_INC_REC268
Expenses of safety measure migrated to action type &1 subtype &2 title &3
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
CM_EHHSS_INC_REC269
Document "&1 &2" not determined; it was not migrated
What causes this issue? You want to migrate an incident that comprises attached documents. One or more than one DMS identifier of the attached docume...
Click on this link to search all SAP messages.