Do you have any question about this error?
Stop googling SAP errors. Use our Free Essentials plan instead - no credit card needed. Start Now →
Message type: E = Error
Message class: SWF_RUN - Workflow Runtime System
Message number: 679
Message text: tRFC created with destination &1
The work item was not registered for execution. The following parameters
were used:
Name,,Value
RFC Destination,,&V1&
RFC Type,,&V2&
The system issues an error message and will not allow you to continue with this transaction until the error is resolved.
Error message extract from SAP system. Copyright SAP SE.
SWF_RUN679
- tRFC created with destination &1 ?The SAP error message SWF_RUN679 indicates that a transactional RFC (tRFC) has been created with a specific destination, but there is an issue that needs to be addressed. This error typically arises in the context of workflow or background processing where a tRFC call is made to another system or client.
Cause:
- Destination Issues: The destination specified in the error message may not be correctly configured or may be inactive. This can happen if the RFC destination is not set up properly in transaction
SM59
.- Network Issues: There may be network connectivity problems between the SAP systems involved.
- Authorization Issues: The user or service account making the tRFC call may not have the necessary authorizations to execute the function in the target system.
- System Configuration: The target system may not be configured to accept tRFC calls, or there may be issues with the target system itself (e.g., it is down or not reachable).
- Data Issues: The data being sent via tRFC may be invalid or not conforming to the expected format.
Solution:
Check RFC Destination:
- Go to transaction
SM59
and verify the configuration of the RFC destination mentioned in the error message.- Ensure that the destination is active and correctly configured (e.g., correct IP address, port, and connection type).
Test Connection:
- Use the "Connection Test" feature in
SM59
to check if the connection to the target system is working properly.Review Authorizations:
- Ensure that the user or service account has the necessary authorizations to perform the tRFC call in the target system.
Check Network Connectivity:
- Verify that there are no network issues preventing communication between the two systems. This may involve checking firewalls, VPNs, or other network configurations.
Monitor tRFC Queue:
- Use transaction
SM58
to monitor the tRFC queue. Check for any entries that may indicate issues with the tRFC calls and take appropriate action (e.g., reprocessing failed entries).Review Logs:
- Check the application logs (transaction
SLG1
) for any additional error messages or details that may provide more context about the issue.Consult Documentation:
- Refer to SAP documentation or support notes related to tRFC and workflow processing for any specific guidance or known issues.
Related Information:
If the issue persists after following these steps, it may be necessary to engage SAP support for further assistance.
Get instant SAP help. Sign up for our Free Essentials Plan.
SWF_RUN678
Method &1 is locked against execution (reason: &2)
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
SWF_RUN677
Work item returned
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
SWF_RUN680
Exit class '&1' activated
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
SWF_RUN681
Constructor class '&1' is active
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
Click on this link to search all SAP messages.