How To Fix UT058 - No Customizing request specified for import of the worklist &

UT058 - Overview

• Message type: E = Error

• Message class: UT - Logical transports

• Message number: 058

• Message text: No Customizing request specified for import of the worklist &

What causes this issue?

Selected objects of the worklist &V1& are to be imported into a logon
client for which recording is mandatory. However, no Workbench
Customizing request (valid for the user) for change recording is
assigned to the worklist. This means that changes made to the selected
Customizing objects by the Customizing import are not recorded.

System Response

The Customizing import of the worklist is not carried out.

How to fix this error?

Repeat the Customizing import, after you have assigned a valid
Customizing request for change recording to the worklist.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message UT058 - No Customizing request specified for import of the worklist & ?

  The SAP error message UT058, which states "No Customizing request specified for import of the worklist &," typically occurs when there is an issue with the transport request or customizing request related to the worklist in SAP. This error can arise in various scenarios, particularly when trying to import or manage worklists in the SAP system.
  
  Cause:
  
  
  Missing Transport Request: The error indicates that the system cannot find a transport request associated with the worklist you are trying to import. This could happen if the transport request was not created, was deleted, or was not properly released.
  
  
  Incorrect Configuration: There may be a configuration issue where the worklist is not correctly linked to a transport request.
  
  
  Authorization Issues: Sometimes, the user may not have the necessary authorizations to access or import the customizing request.
  
  
  System Configuration: The system might not be set up correctly to handle the worklist import process.
  
  
  
  Solution:
  
  
  Check Transport Request: Verify that the