How To Fix WZ321 - RFC destination WORKFLOW_LOCAL_... contains errors

SAP Error Message - Details

• Message type: E = Error

• Message class: WZ - Workflow: Model objects

• Message number: 321

• Message text: RFC destination WORKFLOW_LOCAL_... contains errors

What causes this issue?

A report is to be scheduled which is run by the user entered in
WORKFLOW_LOCAL_ccc (ccc is replaced by the current client). An error
occurred while reading the user for this RFC destination.
There are a number of possible causes:

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

The RFC destination WORKFLOW_LOCAL_ccc is not available
No user is entered for the RFC destination WORKFLOW_LOCAL_ccc

System Response

The report could not be scheduled.

How to fix this error?

Correct the RFC destination WORKFLOW_LOCAL_ccc by executing
<DS:TRAN.SWU3>automatic customizing</>.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message WZ321 - RFC destination WORKFLOW_LOCAL_... contains errors ?

  The SAP error message:
  WZ321 RFC destination WORKFLOWLOCAL... contains errors
  typically occurs in the context of SAP Workflow when the system tries to communicate via an RFC destination named WORKFLOW_LOCAL_... (often WORKFLOW_LOCAL or similar), and that RFC destination is not properly configured or has errors.
  
  Cause
  
  The RFC destination WORKFLOW_LOCAL (or similar) is used by the SAP Workflow runtime to call local functions or to communicate internally.
  This RFC destination is either:
  Not maintained/configured correctly.
  Has invalid parameters (e.g., wrong target system, missing user, incorrect logon data).
  The destination is inactive or has connection errors.
  
  
  Sometimes, this error appears after system upgrades, transport imports, or changes in the workflow configuration.
  The error indicates that the workflow runtime cannot use the RFC destination to execute tasks or communicate internally.
  
  
  Solution
  
  
  Check the RFC Destination:
  
  Go to transaction SM59.
  Look for the RFC destination named WORKFLOW_LOCAL (or the exact name mentioned in the error).
  Test the connection by selecting the destination and clicking Test Connection.
  If the test