How To Fix /PLMB/AUTH_LOG017 - New object assignment (&4) deleted

SAP Error Message - Details

• Message type: E = Error

• Message class: /PLMB/AUTH_LOG -

• Message number: 017

• Message text: New object assignment (&4) deleted

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 /PLMB/AUTH_LOG017 - New object assignment (&4) deleted ?

  The SAP error message /PLMB/AUTH_LOG017 New object assignment (&4) deleted typically relates to authorization issues within the SAP PLM (Product Lifecycle Management) module. This error indicates that a new object assignment was deleted due to authorization checks failing.
  Cause:
  
  Authorization Issues: The user does not have the necessary authorizations to create or modify the object assignment in the PLM system.
  Object Locking: The object may be locked by another user or process, preventing the current user from making changes.
  Configuration Errors: There may be issues with the configuration of the authorization objects or roles assigned to the user.
  
  Solution:
  
  
  Check Authorizations:
  
  Verify that the user has the appropriate roles and authorizations to perform the action. This can be done by checking the user’s roles in transaction SU01 or PFCG.
  Ensure that the necessary authorization objects related to PLM are included in the user’s roles.
  
  
  
  Review Object Locking:
  
  Check if the object is locked by another user. You can use transaction SM12 to see if there are any locks on the object and who is holding them.
  
  
  
  Adjust Configuration:
  
  If the authorization objects are not correctly configured, you may need to adjust the settings in transaction PFCG to ensure that the necessary permissions are granted.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to the specific error message for any additional context or updates that may be relevant.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking authorizations and locks, consider reaching out to SAP support for further assistance, especially if this is a recurring issue.
  
  
  
  Related Information:
  
  
  Transaction Codes:
  
  SU01: User Maintenance
  PFCG: Role Maintenance
  SM12: Display and Delete Locks
  SU53: Display Authorization Check
  
  
  
  Authorization Objects: Familiarize yourself with the relevant authorization objects for PLM, which may include C_PLM_* objects.
  
  
  SAP Notes: Search for SAP Notes related to /PLMB/AUTH_LOG017 for any known issues or patches that may address the problem.
  
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.