How To Fix LSO_CORRESPONDENCE504 - Correspondence request &1 was not found; output will be cancelled

SAP Error Message - Details

• Message type: E = Error

• Message class: LSO_CORRESPONDENCE - Correspondence Messages

• Message number: 504

• Message text: Correspondence request &1 was not found; output will be cancelled

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 LSO_CORRESPONDENCE504 - Correspondence request &1 was not found; output will be cancelled ?

  The SAP error message LSO_CORRESPONDENCE504 indicates that a correspondence request (identified by the number &1) could not be found, leading to the cancellation of the output. This error typically occurs in the context of SAP Learning Solution (LSO) when trying to generate or process correspondence outputs, such as notifications or confirmations related to training events.
  Causes:
  
  Non-existent Correspondence Request: The specified correspondence request number does not exist in the system. This could be due to a typo or because the request was never created.
  Deletion of Request: The correspondence request may have been deleted or not saved properly.
  Authorization Issues: The user may not have the necessary authorizations to access the correspondence request.
  Configuration Issues: There may be issues with the configuration of the correspondence types or output settings in the SAP system.
  Data Inconsistencies: There could be inconsistencies in the data that prevent the system from locating the correspondence request.
  
  Solutions:
  
  Verify the Request Number: Check the correspondence request number for accuracy. Ensure that it is correctly entered and exists in the system.
  Check for Deletion: Investigate whether the correspondence request was deleted or if it was never created. You can do this by checking the relevant tables or transaction codes related to correspondence.
  Review Authorizations: Ensure that the user has the necessary authorizations to access and process correspondence requests. This may involve checking user roles and permissions.
  Configuration Check: Review the configuration settings for correspondence types and output processing in the SAP LSO module. Ensure that all necessary settings are correctly configured.
  Consult Logs: Check the application logs or system logs for any additional error messages or warnings that may provide more context about the issue.
  Recreate the Request: If the correspondence request is indeed missing, you may need to recreate it or trigger the process that generates it again.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as LSO_CORR for managing correspondence requests or SOST for monitoring output requests.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message. SAP frequently updates its knowledge base with solutions for common problems.
  Documentation: Review the SAP Help Portal or documentation specific to SAP Learning Solution for more detailed information on correspondence processing.
  
  If the issue persists after trying the above solutions, it may be beneficial to consult with your SAP support team or reach out to SAP support for further assistance.