Downtime Announcement: Please note the SAP Community Wiki will be unavailable due to a system upgrade on Thursday, September 24th between 6 and 7 AM CEST
Skip to end of metadata
Go to start of metadata

Enhancement Framework Class Enhancements Pre-exit, Post-exit and Overwrite-exit methods

(info) Class Enhancements (Klasse Verbesserungen) -

We can take the advantage of enhancing the global parameters and interface of a class with the help of the new enhancement framework to achieve the expected business functionality.

What things are possible when we can think of enhancing the features or functionality of a class?

→ Adding new methods to the existing ones.
→ Adding new, but optional global parameters to the existing method parameters.
→ Enhancing (Customer defined business functionality) the way the methods are triggered or executed with the help of Pre-exit, Post-exit and Overwrite methods respectively with customer logic.

The best way to utilize the functionality would be the combined use of enhancing the global parameters as well as applying the 'Pre-Post-Overwrite exit' methods. 

In Short,

(info)  Pre-exit methods -

Pre-exit methods are the enhanced methods which can be invoked at runtime before the original method code is supposed to be executed or triggered.

A pre-exit can be utilized for certain validations or passing some data from the pre-exit to the original method.

Note: In addition to the pre-exit some source code enhancements can be well used to adapt the changes from the enhanced 'pre-exit' method to the original method.

(info) Post-exit methods -

Post-exit methods are the enhanced methods which can be invoked at runtime after the original method code has been executed or triggered.

The post-exit can be used to add or enhance the data flowing from the original method and satisfy the custom business functionality.

(info) Overwrite-exit methods -

Overwrite-exit methods are the enhanced methods which act as a replacement at run time for the original method.

(lightbulb) Point to correlate -

If the things are observed closely then it reveals that the 'Pre-exit' and 'Post-exit' methods act like 'Enhancement-point' as in source code enhancements.
Also, the 'overwrite-exit' method acts like 'Enhancement-section'.

(warning) Note: This is the biggest function of the framework which knows what needs to be invoked for that particular 'Exit' method applied instead or along with the original code.
To understand these powerful techniques here is a practical demonstration of them by means of some basic scenarios.

(warning) Note: Here in this scenario the class used is in customer name space ('Z' class).

With respect to the scenario, three methods are used to demonstrate the functionalities of the three enhancement methods (Pre, Post and Overwrite Exit methods).

Access the class in 'Display' mode which needs to be enhanced.

These are three methods which need to be enhanced,

(plus) Scenario 1: Applying 'pre-exit' for enhancing method 'ZDAVE_METHOD_KNA1'.

Considering the first method 'ZDAVE_METHOD_KNA1', observe the global parameters

Check the source code for the original method,

This method can be called into an application (say) like a report program which will offer the standard functionality,

Execute the report, to check out the standard functionality

(tick) Test case I -

Observe the outcome,

(tick) Test case II -

Observe the outcome,

Now, we need to enhance this method. To access the enhancement mode,

As expected it is needed to create an implementation,
(warning) Note - It is suggested to create separate implementations for all the three 'Exit method' enhancements.

After selecting the implementation access the enhancement operation option for creating a 'Pre-exit' method enhancement.

Observe the post-exit created and click on that indication to navigate to enter the custom code.
In this case there are some validations and operations performed in this 'Pre-exit' method,

Activate the 'Pre-exit' method and call the 1st method 'ZDAVE_METHOD_KNA1' into the customer report program 'ZDAVE_KATEGORIEN_ENHC'.
Test the functionality achieved for different test cases,

As some validation for customer range was carried out, observe the 'Pre-exit' method has triggered

(tick) Observe the difference,

Another test case,

Validations are processed for the above test case,

(tick) Finally, observe the difference in the output of the report as the 'Pre-exit' method of the class 'ZDAVE_METHOD_KNA1' has been invoked or triggered.

(plus) Scenario 2: Applying 'post-exit' for enhancing method 'ZDAVE_METHOD_KNA2'.

Check the parameters for the method 'ZDAVE_METHOD_KNA2',

Original source code for method 'ZDAVE_METHOD_KNA2',

After calling the method in the application report program, execute the report
(tick) Test case I -

Observe the output,

(tick) Test case II -

Observe the output,

Access the 'Enhance' path (Enhancement Mode) 'Method' → 'Enhance'.

Create an Implementation for the method 'ZDAVE_METHOD_KNA2',

Create a 'Post-exit' method by accessing the path 'Enhancement operations' → 'Insert Post-method'

Observe the 'Post-exit' method created and navigate inside to write the enhancement code,

After the original method does its job the 'Post-exit' method will get invoked and it will allow to enhance the application by adding one more parameter which will be displayed by the application (here report program), here's the code.

Now, call the second method 'ZDAVE_METHOD_KNA2' in the report program,

Execute and enter the desired data,

(tick) Observe the difference,

(plus)   Scenario 3: Applying 'Overwrite-exit' method to the method 'ZDAVE_METHOD_KNA3',

Check the parameters of the method 'ZDAVE_METHOD_KNA3',

Observe the source code of the original method,

Call the method in the application report program and test it (Execute)

(tick) Test case I -

Output -

(tick) Test case II -

Output -

Now, to replace this functionality with the customer's functionality, we make use of 'Overwrite-exit' method
As usual access the path 'Method' →  'Enhance' to enable the enhancement mode.
Create an Implementation,

Add an 'Overwrite-method' accessing the path,

Observe that the method has been created and follow the indication to code the functionality which will replace the original one,

Observe the coding logic,

Activate and call the method in the application report program,

Now, its time to test the application,

(tick) First test case,

(tick) Observe that the overwrite-exit method has been triggered,

(tick) To confirm, observe the output,

(tick) Second, test case

(tick) Again, observe that the overwrite-exit method has been triggered,

(tick) Confirm with the output, (smile)

You can refer to the SAP documentation on Enhancing the Components of Classes or Interfaces

1 Comment

  1. Unknown User (106601wsx)

    This article is really great. Can you also tell me how to access the private attributes of the class in the overwrite-exit?