How To Fix >6013 - Correspondence record &1 has additional data of two categories

SAP Error Message - Details

• Message type: E = Error

• Message class: >6 - Purchasing Document

• Message number: 013

• Message text: Correspondence record &1 has additional data of two categories

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 >6013 - Correspondence record &1 has additional data of two categories ?

  The SAP error message 6013 indicates that there is an issue with a correspondence record that has additional data of two categories. This typically occurs in the context of SAP modules that handle correspondence, such as SAP Customer Relationship Management (CRM) or SAP Financial Accounting (FI).
  Cause:
  The error message is triggered when the system detects that a correspondence record is associated with more than one category of additional data. This can happen due to:
  
  Data Entry Errors: Incorrect or inconsistent data entry when creating or updating correspondence records.
  Configuration Issues: The system may not be properly configured to handle multiple categories of additional data for the correspondence record.
  Business Logic Violations: The business rules defined in the system may not allow for multiple categories of additional data for a single correspondence record.
  
  Solution:
  To resolve the error, you can take the following steps:
  
  
  Review the Correspondence Record: Check the specific correspondence record mentioned in the error message. Look for any inconsistencies or errors in the additional data categories assigned to it.
  
  
  Correct Data Entry: If you find that the record has been incorrectly populated with multiple categories, correct the data to ensure that only one category of additional data is associated with the record.
  
  
  Check Configuration: If the issue persists, review the configuration settings related to correspondence records in your SAP system. Ensure that the system is set up to handle the required categories of additional data correctly.
  
  
  Consult Documentation: Refer to SAP documentation or help resources for guidance on how to manage correspondence records and additional data categories.
  
  
  Contact SAP Support: If you are unable to resolve the issue through the above steps, consider reaching out to SAP support for assistance. They can provide more specific guidance based on your system configuration and the context of the error.
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes that deal with correspondence records, such as CRM_ORDER, FB03, or others depending on your specific SAP module.
  User Roles and Authorizations: Ensure that the user attempting to modify the correspondence record has the necessary authorizations to make changes.
  SAP Notes: Check for any SAP Notes related to error message 6013, as there may be patches or updates that address known issues.
  
  By following these steps, you should be able to identify the cause of the error and implement a solution to resolve it.