How To Fix ENHANCEMENT568 - Customer subscreen calls exist that are not yet migrated

ENHANCEMENT568 - Overview

• Message type: E = Error

• Message class: ENHANCEMENT - SAP customer enhancement project messages

• Message number: 568

• Message text: Customer subscreen calls exist that are not yet migrated

What causes this issue?

During SMOD migration, you must also migrate all customer subscreen
calls of a customer exit (see documentation). If you have not yet done
this, you cannot continue with the migration process.

System Response

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

How to fix this error?

Migrate all customer subscreen calls of the customer exit.

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message ENHANCEMENT568 - Customer subscreen calls exist that are not yet migrated ?

  The SAP error message "ENHANCEMENT568 Customer subscreen calls exist that are not yet migrated" typically arises during the migration of custom enhancements or modifications in SAP systems, particularly when transitioning to newer versions or when implementing SAP S/4HANA. This message indicates that there are custom subscreen calls that have not been updated or migrated to the new enhancement framework.
  
  Cause:
  
  Legacy Customizations: The error is often caused by legacy custom enhancements that were implemented using older methods (like user exits or custom subscreens) that are not compatible with the new enhancement framework.
  Migration Issues: During the migration process, the system checks for existing custom enhancements and identifies those that have not been properly migrated to the new structure.
  Incompatibility with New Framework: The new enhancement framework in SAP S/4HANA may not support certain types of custom subscreen calls, leading to this error.
  
  
  Solution:
  
  Identify Custom Enhancements: Use transaction codes like SE80 (Object Navigator) or SE37 (Function