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


SAP Error Message - Details

  • Message type: E = Error

  • Message class: FB - Batch Programs

  • Message number: 529

  • Message text: Correspondence type & has not been created

  • Show details Hide details
  • What causes this issue?

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

    System Response

    Cancellation of processing.

    How to fix this error?

    Please check the entries in the table &V2& with the general table
    display. First maintain the configurations for the requirements of
    the correspondence type &V1& available in the table or delete
    possibly incorrect correspondence requests with the deletion report.

    Error message extract from SAP system. Copyright SAP SE.


Smart SAP Assistant

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

    The SAP error message FB529 indicates that a correspondence type has not been created for the specified parameters. This error typically occurs in the context of financial accounting when trying to generate correspondence (such as account statements, reminders, etc.) for customers or vendors.

    Cause:

    1. Missing Correspondence Type: The most common cause is that the correspondence type specified in the transaction does not exist in the system.
    2. Configuration Issues: The correspondence type may not be properly configured in the system, or it may not be assigned to the relevant company code or account group.
    3. Authorization Issues: The user may not have the necessary authorizations to access or create the correspondence type.
    4. Incorrect Parameters: The parameters used in the transaction may be incorrect or incomplete, leading to the system not being able to find the corresponding correspondence type.

    Solution:

    1. Check Correspondence Type:

      • Go to the transaction code OB77 (for customer correspondence) or OB78 (for vendor correspondence).
      • Verify if the correspondence type you are trying to use is listed. If it is not, you will need to create it.
    2. Create Correspondence Type:

      • If the correspondence type does not exist, you can create it by using the transaction code OB77 or OB78.
      • Fill in the necessary details such as the correspondence type, description, and any other required fields.
    3. Assign Correspondence Type:

      • Ensure that the correspondence type is assigned to the relevant company code and account group. This can also be done in the same configuration transactions.
    4. Check User Authorizations:

      • Ensure that the user has the necessary authorizations to create or access the correspondence type. This may require checking with your SAP security team.
    5. Review Parameters:

      • Double-check the parameters you are using in the transaction to ensure they are correct and complete.

    Related Information:

    • Transaction Codes:
      • FB03: Display Document
      • FB70: Enter Customer Invoice
      • FB75: Enter Customer Credit Memo
      • OB77/OB78: Configuration for Correspondence Types
    • SAP Notes: Check for any relevant SAP Notes that may address specific issues related to correspondence types.
    • Documentation: Refer to SAP Help documentation for detailed information on configuring and using correspondence types in financial accounting.

    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 assistance.

    • Do you have any question about this error?


      Upgrade now to chat with this error.


Instant HelpGet instant SAP help. Start your 7-day free trial now.


Related SAP Error Messages

Click the links below to see the following related messages:

Click on this link to search all SAP messages.


Rating
ERPlingo simplifies finding the accurate answers to SAP message errors. I now use every week. A must have tool for anyone working with SAP! Highly recommended!
Rate 1
Kent Bettisworth
Executive SAP Consultant