How To Fix FSC1121 - Correspondence type &1 is not contained in correspondence variant &2

SAP Error Message - Details

• Message type: E = Error

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

• Message number: 121

• Message text: Correspondence type &1 is not contained in correspondence variant &2

What causes this issue?

In a program run, you want to create correspondence of
<DS:DE.COTYP_KK>correspondence type</> &V1&. In the
<DS:DE.COPRC_KK>correspondence variant</> &V2&, which is assigned to the
contract account, correspondence type &V1& is not entered.

System Response

The correspondence was not created.

How to fix this error?

If you want to include correspondence type &V1& in the correspondence
variant &V2&, change the system settings accordingly.
INCLUDE FICA_NA_F5 OBJECT DOKU ID TX

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message FSC1121 - Correspondence type &1 is not contained in correspondence variant &2 ?

  The SAP error message FSC1121 indicates that a specific correspondence type is not included in the defined correspondence variant. This error typically arises in the context of financial accounting or controlling processes where correspondence (such as letters, notifications, or reports) is generated based on certain variants.
  Cause:
  The error occurs when:
  
  The correspondence type specified in the transaction or process is not included in the configuration of the correspondence variant.
  There may be a mismatch between the correspondence type being used and the variant settings.
  The correspondence variant may not be properly configured or may have been changed or deleted.
  
  Solution:
  To resolve the FSC1121 error, you can follow these steps:
  
  
  Check Correspondence Variant Configuration:
  
  Go to the configuration settings for correspondence variants in SAP. This can typically be found in the SPRO transaction under Financial Accounting (FI) or the relevant module.
  Navigate to the section for defining correspondence variants and check if the correspondence type in question is included in the variant.
  
  
  
  Add Correspondence Type:
  
  If the correspondence type is missing, you can add it to the correspondence variant. Ensure that you have the necessary authorizations to make changes to the configuration.
  Save the changes and try to execute the process again.
  
  
  
  Verify Input Parameters:
  
  Ensure that the input parameters you are using in the transaction are correct and that you are referencing the correct correspondence type and variant.
  
  
  
  Consult Documentation:
  
  Review any relevant documentation or user manuals for your specific SAP implementation to understand how correspondence types and variants are configured.
  
  
  
  Check for Customizations:
  
  If your organization has custom developments or enhancements, check if there are any custom logic or configurations that might affect the correspondence types and variants.
  
  
  
  Contact Support:
  
  If you are unable to resolve the issue, consider reaching out to your SAP support team or consulting with an SAP expert who can provide further assistance.
  
  
  
  Related Information:
  
  Transaction Codes: You may need to use transaction codes like SPRO (for configuration), FB03 (to view documents), or others depending on the context of the correspondence.
  Documentation: SAP Help Portal and community forums can provide additional insights and examples related to correspondence types and variants.
  Testing: After making changes, conduct thorough testing to ensure that the correspondence generation works as expected without triggering the error.
  
  By following these steps, you should be able to identify the cause of the FSC1121 error and implement a solution to resolve it.