How To Fix >6558 - No correspondence request was created for correspondence type &1

>6558 - Overview

• Message type: E = Error

• Message class: >6 - Purchasing Document

• Message number: 558

• Message text: No correspondence request was created for correspondence type &1

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 >6558 - No correspondence request was created for correspondence type &1 ?

  The SAP error message 6558 ("No correspondence request was created for correspondence type &1") typically occurs in the context of the SAP system when there is an attempt to generate correspondence (such as letters, notifications, etc.) but the system fails to create a request for the specified correspondence type.
  Causes:
  
  
  Missing Configuration: The correspondence type specified in the error message may not be properly configured in the system. This could include missing settings in the relevant customizing transactions.
  
  
  Incorrect Parameters: The parameters or data provided for generating the correspondence may be incorrect or incomplete, leading to the failure in creating the request.
  
  
  Authorization Issues: The user may not have the necessary authorizations to create correspondence requests for the specified type.
  
  
  System Errors: There could be underlying system issues or bugs that prevent the creation of correspondence requests.
  
  
  Business Logic: The business logic defined in the system may not allow for the creation of correspondence under certain