How To Fix CNV_20200_CHECK356 - CJ business transaction (CoCd &1, CJ Tran.numb. &2) is not permitted


SAP Error Message - Details

  • Message type: E = Error

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

  • Message number: 356

  • Message text: CJ business transaction (CoCd &1, CJ Tran.numb. &2) is not permitted

  • Show details Hide details
  • What causes this issue?

    Cash journal business transaction (company code &V1&, cash journal
    transaction number &V2&) is not permitted.
    Only cash journal business transactions are permitted which are assigned
    to one of the participating company codes.

    System Response

    Error

    How to fix this error?

    Provide a suitable mapping for cash journal business transaction
    numbers.

    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_CHECK356 - CJ business transaction (CoCd &1, CJ Tran.numb. &2) is not permitted ?

    The SAP error message CNV_20200_CHECK356 indicates that a specific business transaction related to a project (CJ) is not permitted for the given company code (CoCd) and transaction number. This error typically arises during data migration or conversion processes, particularly when using SAP's Conversion Tools or during the execution of certain transactions in the Project System (PS) module.

    Cause:

    1. Invalid Transaction Type: The transaction type you are trying to process may not be allowed for the specified company code.
    2. Configuration Issues: There may be configuration settings in the Project System that restrict certain transactions for specific company codes.
    3. Data Migration Issues: If this error occurs during a data migration process, it could be due to incorrect mapping or transformation rules that do not align with the target system's configuration.
    4. Authorization Issues: The user executing the transaction may not have the necessary authorizations to perform the action for the specified project or company code.

    Solution:

    1. Check Configuration: Review the configuration settings for the Project System (PS) to ensure that the transaction type is permitted for the specified company code. This may involve checking the settings in transaction codes like OCN1 (Define Project Types) or OCN2 (Define Transaction Types).

    2. Review Transaction Type: Ensure that the transaction type you are trying to use is valid and allowed for the project and company code in question. You may need to consult with your SAP configuration team to verify this.

    3. Data Migration Review: If this error occurs during a data migration, review the mapping and transformation rules to ensure they are correctly set up. Make sure that the data being migrated adheres to the constraints of the target system.

    4. User Authorizations: Check the user authorizations to ensure that the user has the necessary permissions to execute the transaction. This can be done by reviewing the user's roles and authorizations in transaction SU53 or SU01.

    5. Consult Documentation: Refer to SAP documentation or notes related to the specific error message for additional insights or updates that may address the issue.

    6. Contact SAP Support: If the issue persists after checking the above points, consider reaching out to SAP support for further assistance, especially if this is part of a larger migration project.

    Related Information:

    • Transaction Codes: Familiarize yourself with relevant transaction codes such as CJ20N (Project Builder), CJ02 (Change Project), and OCN1/OCN2 for configuration.
    • SAP Notes: Search for SAP Notes related to the error message CNV_20200_CHECK356 for any known issues or patches.
    • Project System Documentation: Review the SAP Project System documentation for best practices and guidelines on managing project transactions.

    By following these steps, you should be able to identify the root cause of the error and implement a suitable solution.

    • 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's SAP support assistant is amazing. Saves me countless hours trying to solve complex SAP issues myself. It's a real game changer!
Rate 1
Thomas Michael
SAP Consultant, Author & Speaker