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 fails, check the error message for details.
  
  
  
  Correct the RFC Destination Configuration:
  
  The WORKFLOW_LOCAL RFC destination should be of type 3 (ABAP Connection).
  It should point to the local system (the same system where the workflow runs).
  The target system should be the same as the current system (check system ID and client).
  The logon data should be valid (usually a trusted system or a user with appropriate authorizations).
  If the destination is missing, create it with the above parameters.
  
  
  
  Check User Authorizations:
  
  The user configured in the RFC destination must have the necessary authorizations to execute workflows.
  Usually, the user should have the S_RFC authorization object with appropriate values.
  
  
  
  Restart Workflow Runtime (if needed):
  
  Sometimes, after fixing the RFC destination, you may need to restart the workflow runtime or relevant work processes.
  Use transaction SWU3 to check workflow configuration and fix inconsistencies.
  Use transaction SWI1 or SWI2_FREQ to monitor workflow errors.
  
  
  
  Check for Transport or Upgrade Issues:
  
  If the error appeared after a system upgrade or transport, verify that all workflow-related transports were imported correctly.
  Run SWU3 to check and fix workflow configuration.
  
  
  
  
  Related Information
  
  Transaction SM59: Manage and test RFC destinations.
  Transaction SWU3: Workflow Customizing and consistency check.
  SAP Note references (example):
  
  SAP Note 108850 - "RFC destination WORKFLOW_LOCAL contains errors"
  SAP Note 109011 - "Workflow: RFC destination WORKFLOW_LOCAL missing or incorrect"
  
  
  Workflow runtime uses WORKFLOW_LOCAL RFC destination to call local functions internally.
  Incorrect configuration of this RFC destination can cause workflow tasks to fail or not start.
  
  
  Summary
  
  
  
  Aspect
  Details
  
  
  
  
  Cause
  RFC destination WORKFLOW_LOCAL is missing, incorrectly configured, or inactive.
  
  
  Solution
  Check and correct RFC destination in SM59; ensure it points to local system with valid logon data; test connection; run SWU3 to fix workflow config.
  
  
  Related
  Transactions: SM59, SWU3; SAP Notes 108850, 109011; Workflow runtime depends on this RFC.
  
  
  
  
  If you fix the RFC destination WORKFLOW_LOCAL as described, the error message WZ321 should be resolved.