How To Fix RP079 - No write authorization for & & for & &

SAP Error Message - Details

• Message type: E = Error

• Message class: RP - Error Messages for Infotype Module Pools

• Message number: 079

• Message text: No write authorization for & & for & &

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 RP079 - No write authorization for & & for & & ?

  The SAP error message RP079 "No write authorization for & & for & &" typically indicates that a user is attempting to perform an action that requires write authorization for a specific object or data set, but they do not have the necessary permissions. This error is commonly encountered in the context of HR (Human Resources) modules, particularly when dealing with personnel data.
  Cause:
  
  Lack of Authorization: The user does not have the required authorization to modify the specified data. This could be due to missing roles or authorizations in their user profile.
  Authorization Object: The specific authorization object that governs the write access for the data in question is not assigned to the user.
  Data Locking: The data might be locked by another user or process, preventing write access.
  Incorrect Configuration: There may be issues with the configuration of the authorization profiles or roles in the system.
  
  Solution:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after the error occurs to check the authorization check that failed. This will provide insight into which specific authorization is missing.
  Review the user’s roles and authorizations in transaction SU01 or PFCG to ensure they have the necessary permissions.
  
  
  
  Modify Roles:
  
  If the user lacks the required authorization, you may need to modify their roles or create a new role that includes the necessary authorizations.
  Ensure that the relevant authorization objects (e.g., P_ORGIN, P_PERNR) are included in the user’s roles.
  
  
  
  Consult with Security Team:
  
  If you do not have the necessary access to modify roles, consult with your SAP security team or administrator to request the required authorizations.
  
  
  
  Check Data Locking:
  
  Verify if the data is locked by another user. You can use transaction SM12 to check for locks on the relevant data.
  
  
  
  Testing:
  
  After making changes to authorizations, have the user log out and log back in to ensure that the new authorizations take effect.
  
  
  
  Related Information:
  
  Authorization Objects: Familiarize yourself with the relevant authorization objects that control access to HR data, such as:
  
  P_ORGIN: Personnel Administration
  P_PERNR: Personnel Number
  
  
  Transaction Codes:
  
  SU53: Display Authorization Check
  SU01: User Maintenance
  PFCG: Role Maintenance
  SM12: Display and Delete Locks
  
  
  Documentation: Refer to SAP documentation or your organization’s internal guidelines for managing user authorizations and roles.
  
  By following these steps, you should be able to identify the cause of the RP079 error and implement a solution to resolve it.