How To Fix 5A749 - Infotype 0105 could not be deleted. No authorization.

SAP Error Message - Details

• Message type: E = Error

• Message class: 5A - Basis Personnel Management

• Message number: 749

• Message text: Infotype 0105 could not be deleted. No authorization.

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

Smart SAP Assistant

• What is the cause and solution for SAP error message 5A749 - Infotype 0105 could not be deleted. No authorization. ?

  The SAP error message 5A749 indicates that there is an authorization issue preventing the deletion of an infotype (in this case, Infotype 0105, which is related to "Communication" data in the HR module). This error typically arises when a user attempts to delete or modify data in the system without having the necessary permissions.
  Cause:
  
  Lack of Authorization: The user does not have the required authorization to delete the specific infotype. This could be due to missing roles or authorizations in their user profile.
  Authorization Object: The authorization check is likely failing on an authorization object related to HR data management, such as P_ORGIN (Personnel Administration) or P_PERNR (Personnel Number).
  Infotype Locking: The infotype might be locked for editing or deletion due to other processes or transactions being active.
  
  Solution:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after the error occurs to see which authorization check failed. This will provide insight into what specific authorization is missing.
  Review the user’s roles and authorizations in transaction SU01 (User Maintenance) or PFCG (Role Maintenance) to ensure they have the necessary permissions for Infotype 0105.
  
  
  
  Modify User Roles:
  
  If the user lacks the necessary authorizations, a security administrator or someone with the appropriate permissions should update the user’s roles to include the required authorizations for managing Infotype 0105.
  
  
  
  Consult with Security Team:
  
  If you are not able to resolve the issue, consult with your SAP security team or administrator. They can analyze the authorization objects and make the necessary adjustments.
  
  
  
  Check for Locks:
  
  Ensure that the infotype is not locked by another user or process. You can check for locks using transaction SM12.
  
  
  
  Testing:
  
  After making changes to authorizations, have the user log out and log back in, then attempt the deletion again to see if the issue is resolved.
  
  
  
  Related Information:
  
  Infotype 0105: This infotype is used to store communication data such as email addresses, phone numbers, etc. It is important for maintaining employee contact information.
  Authorization Objects: Familiarize yourself with relevant authorization objects like P_ORGIN, P_PERNR, and others that pertain to personnel administration.
  SAP Notes: Check SAP Notes for any known issues or updates related to authorization errors in HR infotypes.
  
  By following these steps, you should be able to identify and resolve the authorization issue causing the error message 5A749.