How To Fix UA_SM1043 - Compounded field &2 is missing for authorization field &1

SAP Error Message - Details

• Message type: E = Error

• Message class: UA_SM1 - Structure Maintenance

• Message number: 043

• Message text: Compounded field &2 is missing for authorization field &1

What causes this issue?

You want to include field &v1& as an authorization field. However, this
field is compounded with field &v2&.

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?

Also include field &v2& in the list of authorization fields and insert
it before field &v1&.

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 UA_SM1043 - Compounded field &2 is missing for authorization field &1 ?

  The SAP error message UA_SM1043 indicates that a compounded field is missing for an authorization field. This typically occurs in the context of authorization checks where a specific field is expected to be compounded with another field, but the necessary configuration or data is not present.
  Cause:
  
  Missing Configuration: The compounded field may not be defined in the authorization object or the relevant configuration settings.
  Authorization Object Issues: The authorization object may not be properly set up to include the necessary fields.
  Data Inconsistency: There may be inconsistencies in the data that prevent the system from recognizing the compounded field.
  User Role Issues: The user role may not have the necessary authorizations assigned, leading to the error when trying to access certain transactions or data.
  
  Solution:
  
  
  Check Authorization Objects: 
  
  Go to transaction code SU21 to check the authorization objects related to the error. Ensure that the compounded field is correctly defined.
  Verify that the authorization object includes both the authorization field and the compounded field.
  
  
  
  Review User Roles:
  
  Use transaction code PFCG to review the roles assigned to the user. Ensure that the roles include the necessary authorizations for the compounded field.
  If the role is missing the required authorization, you may need to add it and regenerate the profile.
  
  
  
  Maintain Compounded Fields:
  
  If you are an administrator, you may need to maintain the compounded fields in the authorization object. This can be done in transaction SU21 or by using the relevant customizing transactions.
  
  
  
  Check for Data Issues:
  
  Ensure that the data being accessed does not have any inconsistencies that could lead to the error. This may involve checking the underlying tables or data entries.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to the specific authorization object and fields involved. There may be specific guidance or known issues documented by SAP.
  
  
  
  Testing:
  
  After making changes, test the authorization by logging in with the affected user and attempting to perform the action that triggered the error.
  
  
  
  Related Information:
  
  
  Transaction Codes: 
  
  SU21 (Authorization Object Maintenance)
  PFCG (Role Maintenance)
  SU53 (Display Authorization Check)
  
  
  
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  
  
  Authorization Concept: Familiarize yourself with the SAP authorization concept, including how authorization objects, fields, and roles interact.
  
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP Basis or Security team for further assistance.