How To Fix ENHANCEMENT627 - There are still calls from customer subscreens for SAP enhancement &1

ENHANCEMENT627 - Overview

• Message type: E = Error

• Message class: ENHANCEMENT - SAP customer enhancement project messages

• Message number: 627

• Message text: There are still calls from customer subscreens for SAP enhancement &1

What causes this issue?

There are still calls of customer subscreens in the SAP enhancement &V1&
.

System Response

After migration of customer exits to BAdIs, subscreen calls - instead of
calls of customer subscreens of customer exits - are required.
To support you with this, we will show you on the next screen in which
screen customer subscreens are still called.

How to fix this error?

Place the cursor on the name of the screen and call the where-used
list..
Then you can change the subscreen calls at the where-used points.
Migration will be continued if you then leave the information screen for
migration of the subscreen calls in the application coding by pressing
the ENTER key or by clicing the Icon Copy @01@ . Otherwise migration
will be terminated.

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 ENHANCEMENT627 - There are still calls from customer subscreens for SAP enhancement &1 ?

  The SAP error message ENHANCEMENT627 indicates that there are still calls from customer subscreens for a specific SAP enhancement. This typically occurs when you are trying to deactivate or remove an enhancement (like a user exit or BAdI) that is still being referenced in the code, particularly in customer-specific modifications or enhancements.
  
  Cause:
  
  Active References: The enhancement you are trying to deactivate has active references in the form of customer subscreens or custom code that still calls it.
  Incomplete Cleanup: The enhancement may have been partially removed or deactivated, but some parts of the code still reference it.
  Custom Development: Custom developments or modifications may have been made that rely on the enhancement, and these need to be addressed before the enhancement can be safely removed.
  
  
  Solution:
  
  Identify References: Use transaction codes like SE80 (Object Navigator) or SE37 (Function Module) to search for references to the enhancement. Look for any custom code or subscreens that are