How To Fix SO022 - Document sent

SAP Error Message - Details

• Message type: E = Error

• Message class: SO - SAPoffice: message texts

• Message number: 022

• Message text: Document sent

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 SO022 - Document sent ?

  The SAP error message SO022, which states "Document sent," typically indicates that a document (such as a sales order, invoice, or delivery note) has been successfully sent to the intended recipient, often via email or another communication method. This message is generally not an error but rather an informational message confirming that the document has been dispatched.
  Cause:
  
  The message SO022 is triggered when a document is processed and sent out of the SAP system. This could occur in various scenarios, such as:
  
  Sending an invoice to a customer.
  Dispatching a delivery note.
  Sending a sales order confirmation.
  
  
  
  Solution:
  Since SO022 is an informational message rather than an error, there is typically no action required unless you are expecting an issue with the document delivery. However, if you are facing issues related to document delivery, consider the following steps:
  
  
  Check Document Status: Verify that the document has been sent successfully and check the status in the relevant transaction (e.g., VA03 for sales orders, VF03 for invoices).
  
  
  Review Communication Settings: Ensure that the communication settings (e.g., email configuration) are correctly set up in the SAP system. This includes checking:
  
  Email addresses of recipients.
  SMTP settings in transaction SCOT.
  Output types and their configurations in transaction NACE.
  
  
  
  Check for Errors in Output Processing: If you are expecting an error but see SO022, check the output logs for any issues. You can do this in the relevant transaction (e.g., transaction VF03 for invoices) by checking the output conditions.
  
  
  Consult SAP Notes: If you suspect there is a deeper issue or if the message is accompanied by other errors, consult the SAP Support Portal for any relevant SAP Notes that might address your specific situation.
  
  
  Contact Support: If you continue to experience issues or have specific concerns about document delivery, consider reaching out to your SAP support team or consulting with SAP directly.
  
  
  Related Information:
  
  
  Transaction Codes: Familiarize yourself with relevant transaction codes for checking document statuses and output processing, such as:
  
  VA03 (Display Sales Order)
  VF03 (Display Billing Document)
  VL03N (Display Outbound Delivery)
  
  
  
  Output Determination: Understanding how output determination works in SAP can help troubleshoot issues related to document sending. This includes knowing how to configure output types and conditions.
  
  
  SAP Documentation: Refer to SAP Help documentation for detailed information on output processing and communication settings.
  
  
  In summary, SO022 is an informational message indicating successful document dispatch. If you encounter issues, focus on checking document statuses, communication settings, and output processing configurations.