How To Fix SRM_GENERIC_SP115 - Class attribute SRM_CONT_TYPE for LOIO class &4 is not set

SAP Error Message - Details

• Message type: E = Error

• Message class: SRM_GENERIC_SP - SRM: Generic Service Provider

• Message number: 115

• Message text: Class attribute SRM_CONT_TYPE for LOIO class &4 is not set

What causes this issue?

The content model is not maintained correctly. The LOIO class &v4& must
contain the class property SRM_CONT_TYPE as a value that can only be
filled once. This is not the case.

System Response

No documents can be created because the content model is not correct.

How to fix this error?

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

Procedure for System Administrators

You need to correct the content model &v4& accordingly. Permitted
values for SRM_CONT_TYPE are "2" or "3" for two-level (version only, no
variants) or three-level content models.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message SRM_GENERIC_SP115 - Class attribute SRM_CONT_TYPE for LOIO class &4 is not set ?

  The SAP error message "SRM_GENERIC_SP115 Class attribute SRM_CONT_TYPE for LOIO class &4 is not set" typically occurs in the context of SAP Supplier Relationship Management (SRM) when there is an issue with the classification of a business object, particularly when dealing with the lifecycle of objects in the system.
  
  Cause:
  
  Missing Configuration: The error indicates that the attribute SRM_CONT_TYPE for the specified LOIO (Logical Object Identifier) class is not set. This usually means that the system is expecting a certain classification or type for the object, but it has not been defined in the system configuration.
  Incorrect Object Type: The object being processed may not have the correct type assigned, or the type may not be recognized by the system.
  Data Inconsistency: There may be inconsistencies in the data or configuration that lead to the system being unable to determine the correct classification for the object.
  
  
  Solution:
  
  
  Check Configuration: 
  
  Go to the transaction code SPRO and