How To Fix EK355 - No corresponding entry found in the correspondence container

SAP Error Message - Details

• Message type: E = Error

• Message class: EK - IS-U Accounts Receivable and Payable

• Message number: 355

• Message text: No corresponding entry found in the correspondence container

What causes this issue?

The system tried to read the correspondence container with the
following values:
Fieldname Fieldvalue
COTYP &V1&
ENTID&V4& &V2&
DATA&V4& &V3&
However no entry was found.

System Response

The system cannot print a returns notification.

How to fix this error?

Make sure that the value being searched for exists.

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 EK355 - No corresponding entry found in the correspondence container ?

  The SAP error message EK355 ("No corresponding entry found in the correspondence container") typically occurs in the context of purchasing documents, particularly when dealing with correspondence related to purchase orders, contracts, or other procurement-related activities. This error indicates that the system is unable to find a corresponding entry in the correspondence container for the document you are trying to process.
  Causes:
  
  Missing Correspondence Data: The correspondence data for the specific document may not have been created or may have been deleted.
  Incorrect Document Reference: The document you are trying to access may not have been properly linked to the correspondence container.
  Configuration Issues: There may be issues with the configuration settings related to the correspondence types or the document types in the system.
  Authorization Issues: The user may not have the necessary authorizations to access the correspondence data.
  
  Solutions:
  
  Check Correspondence Data: Verify if the correspondence data exists for the document in question. You can do this by navigating to the relevant transaction (e.g., ME23N for purchase orders) and checking the correspondence tab.
  Create Correspondence: If the correspondence data is missing, you may need to create it manually. This can often be done through the relevant transaction or by using the correspondence function in the purchasing module.
  Review Document Links: Ensure that the document is correctly linked to the correspondence container. This may involve checking the document type and ensuring it is set up to allow correspondence.
  Configuration Check: Review the configuration settings for correspondence types in the SAP Customizing Implementation Guide (IMG). Ensure that the necessary settings are in place for the document types you are working with.
  Authorization Check: Ensure that the user has the necessary authorizations to view and manage correspondence data. This may involve checking user roles and permissions in the system.
  Consult SAP Notes: Check for any relevant SAP Notes that may address this specific error. SAP frequently releases updates and patches that may resolve known issues.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as ME23N (Display Purchase Order), ME22N (Change Purchase Order), and ME21N (Create Purchase Order).
  SAP Documentation: Refer to SAP Help documentation for detailed information on managing correspondence in purchasing documents.
  Support: If the issue persists after trying the above solutions, consider reaching out to your SAP support team or consulting with SAP support for further assistance.
  
  By following these steps, you should be able to identify the cause of the EK355 error and implement a suitable solution.