How To Fix SU2X220 - Unknown fixed values in authorization default values of object &

SU2X220 - Overview

• Message type: E = Error

• Message class: SU2X - Messages for Authorization Default Value Maintenance

• Message number: 220

• Message text: Unknown fixed values in authorization default values of object &

What causes this issue?

In the default values for the application, default values were stored
for the specified authorization object for at least one field that
cannot be maintained in the PFCG authorization maintenance or in the
default value maintenance.
For authorization fields for which the possible values are taken from
the fixed values of the corresponding domain, only the values defined
there can be used. You can use transaction SU21, SU20, and SE11 to
perform a detailed check.

System Response

This message indicates a potential problem in authorization
administration.

How to fix this error?

If the fixed values in the current authorization concept are still
relevant, you need to adjust the definition of the affected domain.
Otherwise, correct the default values accordingly.
Contact the responsible software vendor, if the affected application is
not a custom development object.

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 SU2X220 - Unknown fixed values in authorization default values of object & ?

  The SAP error message SU2X220 indicates that there are unknown fixed values in the authorization default values of a specific authorization object. This typically occurs when there are inconsistencies or missing entries in the authorization data for a user or role.
  
  Cause:
  
  Missing Authorization Values: The authorization object in question may have fixed values that are not defined in the system.
  Changes in Authorization Objects: If an authorization object has been modified (e.g., new fields added or existing fields changed) and the roles or profiles using it have not been updated accordingly, this error can occur.
  Transport Issues: If the authorization objects were transported from one system to another (e.g., from development to production) and the transport did not include all necessary data, this can lead to missing values.
  Custom Development: If there are custom authorization objects or modifications that are not properly maintained, it can lead to this error.
  
  
  Solution:
  
  Check Authorization Object: Identify the specific