How To Fix CNV_20200_CHECK313 - Merge of house bank account ID's in tables PAYR and PCEC


SAP Error Message - Details

  • Message type: E = Error

  • Message class: CNV_20200_CHECK - Messages for check functions (company code merge)

  • Message number: 313

  • Message text: Merge of house bank account ID's in tables PAYR and PCEC

  • Show details Hide details
  • What causes this issue?

    Merge of house bank account ID's.
    This may cause duplicate table keys in tables PAYR or PCEC.

    System Response

    Error

    How to fix this error?

    The business processes must be analyzed for these conflicts.
    In order to avoid duplicate table keys in tables PAYR and PCEC and to
    avoid a loss of information regarding their associated checks and lots
    these house bank account ID's must be renamed.
    Provide a suitable mapping.

    Procedure for System Administrators

    The system issues an error message and will not allow you to continue with this transaction until the error is resolved.


    Error message extract from SAP system. Copyright SAP SE.


Smart SAP Assistant

  • What is the cause and solution for SAP error message CNV_20200_CHECK313 - Merge of house bank account ID's in tables PAYR and PCEC ?

    The SAP error message CNV_20200_CHECK313 typically occurs during the data migration process, particularly when merging house bank account IDs in the context of financial data. This error is part of the SAP Conversion and Migration tools, often encountered during the SAP S/4HANA migration or data transfer processes.

    Cause:

    The error message indicates that there is an inconsistency or conflict in the house bank account IDs between the tables PAYR (Payment Transactions) and PCEC (Payment Clearing). This can happen due to:

    1. Duplicate Entries: There may be duplicate house bank account IDs in the source data that are being merged.
    2. Inconsistent Data: The data in the two tables may not align correctly, leading to issues when trying to merge them.
    3. Missing Mapping: If there is no proper mapping defined for the house bank accounts during the migration, it can lead to this error.

    Solution:

    To resolve the CNV_20200_CHECK313 error, you can follow these steps:

    1. Check for Duplicates: Review the entries in both the PAYR and PCEC tables to identify any duplicate house bank account IDs. You can use SQL queries or SAP transaction codes to extract this data.

    2. Data Consistency: Ensure that the data in both tables is consistent. This may involve checking for discrepancies in account IDs, names, or other related fields.

    3. Mapping Configuration: If you are using a mapping table for house bank accounts, ensure that it is correctly configured. Each house bank account ID in the source data should have a corresponding entry in the mapping table.

    4. Data Cleansing: Cleanse the data before migration. This may involve removing duplicates, correcting inconsistencies, and ensuring that all necessary mappings are in place.

    5. Re-run the Migration: After making the necessary corrections, re-run the migration process to see if the error persists.

    6. Consult Documentation: Refer to SAP's official documentation or notes related to the CNV_20200_CHECK313 error for any specific guidelines or updates.

    Related Information:

    • SAP Notes: Check for any relevant SAP Notes that may provide additional insights or solutions for this specific error.
    • Transaction Codes: Familiarize yourself with transaction codes like SE11 (Data Dictionary), SE16 (Data Browser), and others that can help you analyze the data in the relevant tables.
    • SAP Community: Engage with the SAP Community forums where other users may have encountered similar issues and can share their solutions.

    If the problem persists after following these steps, it may be beneficial to consult with an SAP expert or your organization's SAP support team for further 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