How To Fix EDOCUMENT_PT_INV001 - Sending not possible; digital signature for &1 &2 &3 is missing

SAP Error Message - Details

• Message type: E = Error

• Message class: EDOCUMENT_PT_INV - eInvoice Portugal: Messages

• Message number: 001

• Message text: Sending not possible; digital signature for &1 &2 &3 is missing

What causes this issue?

The invoice has not been digitally signed. However, this is a
prerequisite for submitting the invoice.

System Response

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

How to fix this error?

Sign the invoice before submitting the eDocument. For example, for FI
invoices use the report SIPT_INTERVAL_SIGN_FI.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message EDOCUMENT_PT_INV001 - Sending not possible; digital signature for &1 &2 &3 is missing ?

  The SAP error message "EDOCUMENT_PT_INV001 Sending not possible; digital signature for &1 &2 &3 is missing" typically occurs in the context of electronic invoicing or document processing where a digital signature is required for the document to be sent or processed. Here’s a breakdown of the cause, potential solutions, and related information:
  Cause:
  
  
  Missing Digital Signature: The error indicates that the digital signature required for the specified document (represented by placeholders &1, &2, &3) is missing. This could be due to:
  
  The document not being signed before sending.
  Configuration issues in the electronic document processing settings.
  The digital certificate used for signing is not available or has expired.
  
  
  
  Configuration Issues: There may be issues with the configuration of the electronic invoicing or document processing settings in SAP, which could prevent the system from generating or attaching the digital signature.
  
  
  Authorization Issues: The user or system may not have the necessary authorizations to access the digital signature or the signing process.
  
  
  Solution:
  
  
  Check Digital Signature Configuration:
  
  Ensure that the digital signature settings are correctly configured in the SAP system. This includes checking the settings in transaction codes like SICF, STRUST, or SICF for the relevant services.
  Verify that the digital certificate used for signing is correctly installed and valid.
  
  
  
  Sign the Document:
  
  If the document is not signed, ensure that the signing process is executed before attempting to send the document. This may involve using specific transaction codes or programs to sign the document.
  
  
  
  Review Authorizations:
  
  Check the user roles and authorizations to ensure that the user has the necessary permissions to access and use the digital signature.
  
  
  
  Check for System Updates:
  
  Ensure that your SAP system is up to date with the latest patches and updates, as there may be bug fixes or enhancements related to electronic document processing.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or notes related to electronic invoicing and digital signatures for specific guidance on configuration and troubleshooting.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP support for further assistance, providing them with the error details and any relevant logs.
  
  
  
  Related Information:
  
  SAP Notes: Search for relevant SAP Notes that may address this specific error or provide guidance on digital signatures in electronic invoicing.
  Transaction Codes: Familiarize yourself with transaction codes related to electronic documents, such as FB60 (Enter Incoming Invoices), FB70 (Enter Outgoing Invoices), and others that may be relevant to your process.
  Digital Signature Management: Understand how digital signatures are managed in your organization, including the lifecycle of digital certificates and the signing process.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.