How To Fix CNV_20200_CHECK352 - Securities account (CoCd &1 SecAcct &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: 352

• Message text: Securities account (CoCd &1 SecAcct &2) is not permitted

What causes this issue?

Securities account (company code &V1&, securities account &V2&) is not
permitted.
Only securities accounts 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 securities accounts.

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_CHECK352 - Securities account (CoCd &1 SecAcct &2) is not permitted ?

  The SAP error message CNV_20200_CHECK352 indicates that there is an issue with the securities account in the context of a conversion or migration process. This error typically arises during data migration activities, particularly when using the SAP S/4HANA Migration Cockpit or similar tools.
  Cause:
  The error message suggests that the specified securities account (identified by the company code and securities account number) is not permitted for the operation being performed. This could be due to several reasons:
  
  Invalid Configuration: The securities account may not be properly configured in the system.
  Missing Authorizations: The user executing the migration may not have the necessary authorizations to access or modify the specified securities account.
  Data Inconsistencies: There may be inconsistencies in the data being migrated, such as incorrect mappings or missing entries in the relevant tables.
  Business Rules: The securities account may not meet certain business rules or conditions defined in the system.
  
  Solution:
  To resolve the error, you can take the following steps:
  
  
  Check Configuration:
  
  Verify that the securities account is correctly configured in the system. Check the settings in the relevant configuration areas (e.g., Financial Accounting, Asset Accounting).
  Ensure that the securities account is active and valid for the specified company code.
  
  
  
  Review Authorizations:
  
  Ensure that the user executing the migration has the necessary authorizations to access and modify the securities account. You may need to consult with your SAP security team.
  
  
  
  Data Validation:
  
  Review the data being migrated for any inconsistencies. Ensure that the mappings for the securities account are correct and that all required fields are populated.
  Check for any missing entries in the relevant tables (e.g., T012, T012A) that may be causing the issue.
  
  
  
  Consult Documentation:
  
  Refer to the SAP documentation or notes related to the migration process you are using. There may be specific guidelines or prerequisites that need to be followed.
  
  
  
  Error Logs:
  
  Check the error logs for more detailed information about the error. This may provide additional context that can help in troubleshooting.
  
  
  
  Contact SAP Support:
  
  If the issue persists after checking the above points, consider reaching out to SAP Support for further assistance. Provide them with the error message details and any relevant logs.
  
  
  
  Related Information:
  
  Transaction Codes: You may want to use transaction codes like SE11 (Data Dictionary), SE16 (Data Browser), or SE37 (Function Module) to investigate the underlying data and configurations.
  SAP Notes: Search for relevant SAP Notes that may address this specific error or provide additional troubleshooting steps.
  Migration Cockpit: If you are using the SAP S/4HANA Migration Cockpit, ensure that you are following the correct steps and guidelines for the migration process.
  
  By following these steps, you should be able to identify the root cause of the error and implement a solution to resolve it.