How To Fix PB355 - You are not authorized to delete the relationship of P &1 using &2 to &3

PB355 - Overview

• Message type: E = Error

• Message class: PB - PD: Message IDs Org. Management

• Message number: 355

• Message text: You are not authorized to delete the relationship of P &1 using &2 to &3

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 PB355 - You are not authorized to delete the relationship of P &1 using &2 to &3 ?

  The SAP error message PB355 indicates that a user is attempting to delete a relationship between objects (such as personnel numbers, organizational units, etc.) but does not have the necessary authorization to perform this action. The message typically includes placeholders for the specific objects involved, represented by &1, &2, and &3.
  
  Cause:
  The primary cause of this error is a lack of appropriate authorization in the user's role or profile. In SAP, authorization checks are performed to ensure that users have the necessary permissions to perform specific actions, such as deleting relationships between objects.
  
  Solution:
  To resolve this issue, you can take the following steps:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after the error occurs to see the authorization check that failed. This will provide insight into which specific authorization object is missing.
  
  
  
  Review Role Assignments:
  
  Check the roles assigned to the user in transaction SU01 (User Maintenance). Ensure that the user has the necessary roles