How To Fix FSC1118 - Correspondence variant for &1 &2 is empty

SAP Error Message - Details

• Message type: E = Error

• Message class: FSC1 - FI-CA Extended: Message Class

• Message number: 118

• Message text: Correspondence variant for &1 &2 is empty

What causes this issue?

No correspondence variant is defined for the following master data
objects:
Business partner: &V1&
Contract account: &V2&

System Response

No correspondence was created.

How to fix this error?

If required, define a correspondence variant in the master data.

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FSC1118 - Correspondence variant for &1 &2 is empty ?

  The SAP error message FSC1118, which states "Correspondence variant for &1 &2 is empty," typically occurs in the context of financial accounting or controlling modules when the system is unable to find a correspondence variant for a specific object or transaction. This can happen in various scenarios, such as when generating correspondence documents or reports.
  Cause:
  
  Missing Correspondence Variant: The most common cause is that the correspondence variant specified for the given object (e.g., customer, vendor, or document type) is not defined or is empty in the system.
  Incorrect Configuration: The configuration settings for correspondence processing may not be set up correctly, leading to the absence of a valid correspondence variant.
  Data Entry Error: There may be a typo or incorrect entry in the transaction or configuration settings that leads to the system not being able to find the required variant.
  
  Solution:
  
  
  Check Correspondence Variants:
  
  Navigate to the relevant configuration settings in SAP (usually found under Financial Accounting or Controlling).
  Verify that the correspondence variant for the specified object (e.g., customer or vendor) is defined and not empty.
  If it is missing, create a new correspondence variant or assign an existing one.
  
  
  
  Configuration Settings:
  
  Go to the transaction code for maintaining correspondence variants (e.g., OBAL for account statements).
  Ensure that the necessary settings are in place for the specific document type or account group.
  
  
  
  Review Object Settings:
  
  Check the settings for the specific object (e.g., customer master data) to ensure that the correct correspondence variant is assigned.
  You can do this by using transaction codes like XD03 (Display Customer) or XK03 (Display Vendor) to review the master data.
  
  
  
  Consult Documentation:
  
  Refer to SAP documentation or help files for guidance on setting up correspondence variants and understanding their role in the system.
  
  
  
  Testing:
  
  After making changes, test the process again to ensure that the error message no longer appears.
  
  
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as OBAL, XD03, and XK03 for managing correspondence variants and master data.
  SAP Notes: Check SAP Notes for any known issues or patches related to this error message.
  User Roles and Authorizations: Ensure that the user has the necessary authorizations to view and modify correspondence variants.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or a functional consultant who specializes in the relevant module.