How To Fix SPROJECT347 - You are not authorized to write documentation

SPROJECT347 - Overview

• Message type: E = Error

• Message class: SPROJECT - General Project Management Messages

• Message number: 347

• Message text: You are not authorized to write documentation

What causes this issue?

You are not authorized for the action. You need the value <ZH>76</> for
the field <ZH>ACTVT</> in the authorization object <ZH>S_PROJECT</> to
edit documents in the current project.

System Response

The selected action is cancelled.

How to fix this error?

Get the necessary authorization or get support from colleagues with
sufficient authorization.

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 SPROJECT347 - You are not authorized to write documentation ?

  The SAP error message SPROJECT347, which states "You are not authorized to write documentation," typically occurs when a user attempts to create or modify documentation in the SAP system but lacks the necessary authorizations.
  
  Cause:
  The primary cause of this error is insufficient authorization in the user's role or profile. In SAP, access to various functions, including writing documentation, is controlled by authorization objects. If the user does not have the appropriate permissions assigned, they will encounter this error.
  
  Solution:
  To resolve this issue, you can take the following steps:
  
  
  Check User Roles and Authorizations:
  
  Verify the roles assigned to the user encountering the error. This can be done by navigating to the user management transaction (e.g., SU01) and checking the roles assigned to the user.
  Look for roles that include the necessary authorizations for writing documentation.
  
  
  
  Review Authorization Objects:
  
  The specific authorization object related to documentation writing may vary depending on the context (e.g., project documentation, technical documentation).