How To Fix S_CUS_IMG_ACTIVITY133 - Table &1 contains forbidden key field '&2' of type String

SAP Error Message - Details

• Message type: E = Error

• Message class: S_CUS_IMG_ACTIVITY - IMG Activity

• Message number: 133

• Message text: Table &1 contains forbidden key field '&2' of type String

What causes this issue?

The table/view &V1& contains key fields of type 'STRING' or 'XSTRING'.

System Response

You cannot use the object in BC Sets, because BC Sets do not support
fields of type 'STRING'. If these fields are in the table/view key, as
in this case, they cannot be put in BC Sets.

How to fix this error?

This is not a table/view design error. Key fields can be of type
'STRING'/'XSTRING', but restrictions in the BC Set technology prevent
this table/view being used in BC Sets.
The SAP developer responsible must change the design of the table/view
in the Data Dictionary. Replace the field with one which is not of type
'STRING' or 'XSTRING'. If a maintenance dialog has been generated for
the table/view, regenerate it with the transaction SE54.
<ZH>Note:</>
Test the BC Set functionality, to ensure that the entries are correct.
Create a BC Set for the object.
Check whether the data has been recorded completely in the BC Set
(SCPR3).
Change an entry in the object (SPRO or SM30/34).
Activate the BC Set (SCPR20).
Check whether the values put in the BC Set have been written correctly
into the table/view.

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 S_CUS_IMG_ACTIVITY133 - Table &1 contains forbidden key field '&2' of type String ?

  The SAP error message S_CUS_IMG_ACTIVITY133 indicates that there is an issue with a configuration or customization activity in the SAP system. Specifically, it points out that a table (denoted as &1 in the error message) contains a forbidden key field (denoted as &2) of type String. This typically occurs when you are trying to create or modify a configuration that includes a key field that is not allowed in the context of the activity you are performing.
  
  Cause:
  
  Forbidden Key Field: The key field specified in the error message is not permitted for the particular table or activity you are working with. This could be due to system restrictions or design rules that prevent certain data types from being used as key fields.
  Configuration Error: There may be a misconfiguration in the customizing settings or an attempt to use a field that is not defined correctly in the data dictionary.
  Data Dictionary Constraints: The