How To Fix SCPR426 - The forbidden field &1 in table/view &2 is removed from the BC Set

SCPR426 - Overview

• Message type: E = Error

• Message class: SCPR - BC Sets

• Message number: 426

• Message text: The forbidden field &1 in table/view &2 is removed from the BC Set

What causes this issue?

The field '&V1&' (field name '&V3&') of table/view '&V2&', was put in
the BC Set by a previous create procedure.
Field '&V1&' cannot remain in the BC Set, for one of the following
reasons:
There are dependencies between the table/view '&V2&' and other
tables/views, which prevent the field '&V1&' being put in the BC Set.
Its output length is more as 255 characters
It is of type 'STRING' or 'RAWSTRING'
<ZH>Note:</>
If this field remains in the BC Set (i.e. it is not changed and saved),
the system ignores it, so the BC Set field values are incomplete, and
the create/activate BC Sets transactions could be cancelled. In this
case, report the error to SAP.

System Response

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

How to fix this error?

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message SCPR426 - The forbidden field &1 in table/view &2 is removed from the BC Set ?

  The SAP error message SCPR426 indicates that a specific field in a table or view has been removed from a Business Configuration Set (BC Set). This typically occurs during the configuration of a system where certain fields are not allowed to be included in the BC Set due to restrictions or changes in the data model.
  
  Cause:
  
  Field Restrictions: The field in question may be marked as "forbidden" for inclusion in BC Sets. This can happen if the field is not intended to be configurable or if it is a system field that should not be modified.
  Changes in Data Model: Updates or changes in the underlying data model or business logic may lead to certain fields being deprecated or removed from the configuration options.
  Version Compatibility: If you are working with different versions of SAP or have recently upgraded, certain fields may have been removed or altered in the new version.
  
  
  Solution:
  
  Review the Field: