How To Fix FB536 - Correspondence type & has not been created

SAP Error Message - Details

• Message type: E = Error

• Message class: FB - Batch Programs

• Message number: 536

• Message text: Correspondence type & has not been created

What causes this issue?

A correspondence request whose correspondence type &V1& has not
been created was selected.

System Response

Processing was continued

How to fix this error?

If you carried out a production run of the delete program, the
respective correspondence requests were deleted.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FB536 - Correspondence type & has not been created ?

  The SAP error message FB536 indicates that a correspondence type has not been created for a specific transaction or document. This error typically arises in the context of financial accounting, particularly when trying to generate correspondence (like invoices, statements, or reminders) for customers or vendors.
  Cause:
  
  Missing Correspondence Type: The primary cause of this error is that the correspondence type specified in the transaction does not exist in the system.
  Configuration Issues: The correspondence type may not have been configured properly in the system settings.
  Incorrect Document Type: The document type being processed may not be linked to a valid correspondence type.
  Authorization Issues: Sometimes, the user may not have the necessary authorizations to access or create the correspondence type.
  
  Solution:
  
  
  Create Correspondence Type:
  
  Go to the SAP transaction code OB77 (or the relevant configuration transaction).
  Check if the correspondence type exists. If it does not, you will need to create it.
  Define the correspondence type by specifying the necessary parameters (like output medium, form, etc.).
  
  
  
  Check Configuration:
  
  Ensure that the correspondence type is properly configured in the system.
  Verify that it is linked to the appropriate document types and accounts.
  
  
  
  Review Document Type:
  
  Check the document type you are working with to ensure it is compatible with the correspondence type you are trying to use.
  
  
  
  User Authorizations:
  
  Ensure that the user has the necessary authorizations to create or access the correspondence type.
  
  
  
  Testing:
  
  After making the necessary changes, test the process again to see if the error persists.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as FB03 (Display Document), FB70 (Invoice), and OB77 (Maintain Correspondence Types).
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  Documentation: Refer to SAP documentation for detailed guidance on configuring correspondence types and understanding their role in financial processes.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or refer to SAP community forums for additional insights.