How To Fix EDOCUMENT164 - Not possible to create eDocuments for the selected documents

SAP Error Message - Details

• Message type: E = Error

• Message class: EDOCUMENT - eDocument: Messages

• Message number: 164

• Message text: Not possible to create eDocuments for the selected documents

What causes this issue?

In the selection screen of the eDocument Cockpit, you marked the <ZK>Not
Relevant </>flag. This flag includes in your selection any source
document, even those that the system determined as not relevant for the
creation of eDocuments.
In the output screen of the eDocument Cockpit, you tried to create
eDocuments for these source documents.

System Response

The system does not create eDocuments for these documents because they
are not configured as relevant for eDocuments.

How to fix this error?

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

Procedure for System Administrators

You can determine whether a source document is relevant for eDocument
creation by implementing the method IS_RELEVANT of BAdI EDOC_ADAPTOR.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message EDOCUMENT164 - Not possible to create eDocuments for the selected documents ?

  The SAP error message EDOCUMENT164 indicates that the system is unable to create electronic documents (eDocuments) for the selected documents. This error can arise due to various reasons, and understanding the cause is essential for finding a solution. Here are some common causes, potential solutions, and related information:
  Causes:
  
  Missing Configuration: The necessary configuration for eDocuments may not be set up correctly in the system.
  Document Status: The documents you are trying to process may not be in a valid status for eDocument creation (e.g., they might be incomplete or already processed).
  Authorization Issues: The user may not have the required authorizations to create eDocuments.
  Data Issues: There may be missing or incorrect data in the documents that prevent eDocument creation.
  Technical Issues: There could be technical problems, such as system errors or connectivity issues with external services.
  
  Solutions:
  
  
  Check Configuration:
  
  Ensure that the eDocument framework is properly configured in your SAP system. This includes checking the settings in transaction codes like SPRO (SAP Reference IMG) for eDocument-related configurations.
  
  
  
  Verify Document Status:
  
  Check the status of the documents you are trying to process. Ensure they are complete and in a state that allows for eDocument creation.
  
  
  
  Review Authorizations:
  
  Verify that the user attempting to create the eDocuments has the necessary authorizations. You can check this in transaction SU53 after the error occurs to see if there are any authorization issues.
  
  
  
  Data Validation:
  
  Review the data in the documents for any inconsistencies or missing information. Ensure that all required fields are filled out correctly.
  
  
  
  Check Logs and Messages:
  
  Look at the application logs (transaction SLG1) for any additional error messages or warnings that could provide more context about the issue.
  
  
  
  Consult SAP Notes:
  
  Search for relevant SAP Notes in the SAP Support Portal that may address this specific error or provide patches and updates.
  
  
  
  Technical Support:
  
  If the issue persists, consider reaching out to your SAP support team or consulting with SAP directly for further assistance.
  
  
  
  Related Information:
  
  SAP Documentation: Review the official SAP documentation for eDocuments to understand the requirements and configurations needed.
  Community Forums: Check SAP Community forums for similar issues and solutions shared by other users.
  Transaction Codes: Familiarize yourself with relevant transaction codes such as EDOC for eDocument processing and SICF for service activation if applicable.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.