How To Fix CP243 - No authorization to delete task list type & status & usage & plant &

SAP Error Message - Details

• Message type: E = Error

• Message class: CP - Task list messages: Core data

• Message number: 243

• Message text: No authorization to delete task list type & status & usage & plant &

What causes this issue?

In Customizing the <GL:task list type>task list type</> the extended
authority check for deletion has been activated in the general control
parameters.
You need special authorization for deletion.
This authorization has not been assigned to your user master record.

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

INCLUDE NA_BER OBJECT DOKU ID TX
INCLUDE NA_SYSVW_HINW OBJECT DOKU ID TX
During deletion the authority object C_ROUT the activity <ls>06</> is
checked.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message CP243 - No authorization to delete task list type & status & usage & plant & ?

  The SAP error message CP243 indicates that a user does not have the necessary authorization to delete a task list of a specific type, status, usage, and plant. This error typically arises in the context of SAP's Production Planning (PP) or Plant Maintenance (PM) modules, where task lists are used for various planning and maintenance activities.
  
  Cause:
  The error is caused by insufficient authorization in the user's role or profile to perform the delete operation on the specified task list. The task list could be of various types, such as routing, maintenance task lists, etc., and the user may not have the required permissions to delete it.
  
  Solution:
  To resolve this issue, you can take the following steps:
  
  
  Check User Authorizations:
  
  Use transaction code SU53 immediately after encountering the error to see which authorization object is missing.
  Review the authorization logs to identify the specific authorization object that is causing the issue.
  
  
  
  Modify User Roles:
  
  If you have the