SAP ABAP Message Class E4 Message Number 202 (Enhancements will not be copied)
Hierarchy
☛ SAP_BASIS (Software Component) SAP Basis Component
   ⤷ BC-DWB-UTL-BRR (Application Component) Repository Browser
     ⤷ SEU (Package) ABAP Workbench
Attribute
Message class E4  
Short Description Program maintenance functions within development system    
Message Number 202  
Documentation status       Space: object requires documentation
Authorization check Error Message      
Changed On 20130531   
Message Text
Enhancements will not be copied
Help Document

Diagnosis

An object (program, function module, method, or class) that contains enhancement implementations is being copied. These enhancement implementations are not contained in the target object. Since enhancements are always bound to the corresponding compilation unit, or bound when the INCLUDE BOUND addition is used, they are not included in the copy action.

The "ENHANCEMENT-POINT" and "ENHANCEMENT-SECTION / END-ENHANCEMENT-SECTION" statements contained in the source object are commented out in the target object. The coding between "ENHANCEMENT-SECTION" and "END-ENHANCEMENT-SECTION" is copied because it is always run through when there is no implementation.

System Response

Procedure

If these enhancement implementations are required for the program flow, the following solution options are available:

  1. If the coding is to be run through, whatever the case, you can insert the coding of the enhancement implementation directly at the same position within the target program or replace the coding that is between the statements "ENHANCEMENT-SECTION" and "END-ENHANCED-SECTION" by it.
  2. All enhancements are copied. So that the system can execute the correct coding in connection with the current switch setting, it determines the respective switch setting (for example, using the function module SFW_GET_SW_STATUS) and branches to the executing coding through additional IF conditions.
    Here it should be noted that appends that are possibly switched off could cause syntax errors. This solution cannot be used in such cases.
  3. You create your own enhancement options and implementations. If there are different switches in the original, the implementations must be created in different packages. A separate new switch is assigned to each package, and this switch is, in turn, is bound to the business function of the original switch.

For more information on this topic, refer to Note 1677260.

Procedure for System Administration

History
Last changed on/by 20130531  SAP 
SAP Release Created in