How To Fix CRM_BSP_BF_MAX_ACCES006 - No recipient with "Send as = Original" selected

SAP Error Message - Details

• Message type: E = Error

• Message class: CRM_BSP_BF_MAX_ACCES - Output for Send Screen Model Access Class

• Message number: 006

• Message text: No recipient with "Send as = Original" selected

Self-Explanatory Message

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.

What else can you do?

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message CRM_BSP_BF_MAX_ACCES006 - No recipient with "Send as = Original" selected ?

  The SAP error message CRM_BSP_BF_MAX_ACCES006 typically occurs in the context of the SAP CRM (Customer Relationship Management) system when trying to send a document or communication (like an email) and the system cannot find a valid recipient with the "Send as = Original" option selected. This can happen in various scenarios, such as when sending emails from a business partner or when trying to send a document that requires a specific recipient configuration.
  Cause:
  
  Missing Recipient: The primary cause of this error is that there is no recipient defined in the system with the "Send as = Original" setting. This means that the system is looking for a specific type of recipient configuration that is not available.
  Incorrect Configuration: The recipient's settings may not be correctly configured in the system, leading to the inability to find a valid recipient.
  Business Partner Issues: The business partner may not have the necessary communication data (like email address) set up correctly.
  Document Type Restrictions: Certain document types may have restrictions on how they can be sent, and if the required recipient type is not available, this error can occur.
  
  Solution:
  
  
  Check Recipient Configuration:
  
  Go to the business partner master data and ensure that the recipient has the correct communication method set up (e.g., email).
  Verify that the recipient is marked with "Send as = Original" in the communication settings.
  
  
  
  Add Missing Recipients:
  
  If no recipient exists, you may need to add a new recipient with the appropriate settings. Ensure that the recipient has the necessary communication data filled out.
  
  
  
  Review Document Settings:
  
  Check the document type settings to ensure that they allow sending to the specified recipient type. Adjust the settings if necessary.
  
  
  
  Debugging:
  
  If you have access to the system, you can use transaction codes like SLG1 to check the application log for more detailed error messages that can provide additional context.
  
  
  
  Consult Documentation:
  
  Review SAP documentation or notes related to this error message for any specific recommendations or patches that may address the issue.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP support for further assistance. They may have additional insights or solutions based on the specific configuration of your system.
  
  
  
  Related Information:
  
  Business Partner Master Data: Ensure that the business partner's communication data is correctly maintained.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide updates.
  Transaction Codes: Familiarize yourself with transaction codes like BP (Business Partner), SOST (Send Requests), and SLG1 (Application Log) for troubleshooting.
  
  By following these steps, you should be able to identify and resolve the issue causing the error message CRM_BSP_BF_MAX_ACCES006.