Do you have any question about this error?
Message type: E = Error
Message class: 25 - DDS: document distribution (DMS)
Message number: 070
Message text: Recipient & is not contained in any recipient list
Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.
To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.
Unfortunately, there isn't any extra information in this error notice.
First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).
Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.
You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.
25070
- Recipient & is not contained in any recipient list ?The SAP error message "25070 Recipient & is not contained in any recipient list" typically occurs in the context of SAP Business Workflow or when sending notifications via email or other communication methods. This error indicates that the specified recipient (denoted by "&") is not found in any of the defined recipient lists for the workflow or notification process.
Cause:
- Missing Recipient: The recipient specified in the workflow or notification is not included in the recipient list.
- Incorrect Recipient ID: The recipient ID may be incorrectly specified or may not exist in the system.
- Recipient List Configuration: The recipient list may not be properly configured or may not include the necessary users or groups.
- User Deactivation: The user account for the recipient may be inactive or locked.
Solution:
- Check Recipient ID: Verify that the recipient ID is correct and exists in the system. You can do this by checking the user master data in transaction
SU01
.- Update Recipient List: Ensure that the recipient is included in the appropriate recipient list. You can do this by:
- Navigating to the relevant workflow or notification configuration.
- Adding the recipient to the list if they are missing.
- Review Workflow Configuration: If this error occurs in a workflow, check the workflow definition to ensure that the recipient list is correctly set up and that the recipient is included.
- User Status: Check the status of the user account. If the user is inactive or locked, you may need to reactivate or unlock the account.
- Testing: After making changes, test the workflow or notification again to ensure that the error is resolved.
Related Information:
SWI1
(Work Item Selection) to analyze work items and their recipients, or SWDD
(Workflow Builder) to modify workflows.If the issue persists after following these steps, consider reaching out to your SAP Basis or Workflow team for further assistance, as they may have additional tools or insights to diagnose the problem.
Get instant SAP help. Start your 7-day free trial now.
25069
Error when bundling distribution order
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
25068
Error when distribution order was being checked
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
25071
Choose a recipient
Self-Explanatory Message Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of...
25072
Select a distribution list or an organizational unit
What causes this issue? The chosen recipient is not a distribution list or an organizational unit.System Response The system issues an error message...
Click on this link to search all SAP messages.