Modification Events in SAP Customizing Tables

Table Of Content

1. Introduction

2. Types of Modification Events

   • 2.1. Events Related to Data Saving and Deletion

   • 2.2. Events Related to Data Entry and Editing

   • 2.3. Events Related to Change Tracking and Authorization

   • 2.4. Events for Special Cases and Alternative Processes

   • 2.5. Events That Replace Standard SAP Routines

   • 2.6. Events Related to Internal Use and GUI

3. Creating a Modification Event from Scratch

   • Creating a Customizing Table

   • Enabling Maintenance View

   • Adding a Modification Event

   • Implementing ABAP Code

   • Testing and Validation

4. Conclusion and Best Practices

1. Introduction

In SAP systems, customizing tables allow users to manage system configurations. These tables are generally accessed through the SAP Implementation Guide (IMG) and are used to customize the operation of specific modules within the system.

Changes made to customizing tables must be controlled and traceable. To achieve this, SAP provides the Modification Events mechanism. Modification Events trigger specific actions when data is entered, modified, deleted, or when other special operations occur on customizing tables.

In this article, we will categorize and examine the different types of Modification Events, detailing their use cases. Additionally, we will provide ABAP code examples demonstrating how to implement these events.

2. Types of Modification Events

Modification Events can be categorized into six main groups:

2.1. Events Related to Data Saving and Deletion

Event Code	Description
01	Before saving the data in the database - Triggers before saving data. Used for data validation or additional checks.
02	After saving the data in the database - Triggers after saving data. Suitable for logging or trigger-based actions.
03	Before deleting the data displayed - Triggers before deleting a record. Can be used to cancel deletion.
04	After deleting the data displayed - Triggers after deleting a record. Can be used for logging or updating related data.

2.2. Events Related to Data Entry and Editing

Event Code	Description
05	Creating a new entry - Triggers when a new entry is created.
06	After completely performing the function 'Get original' - Triggers after the original data retrieval process is completed.
07	Before correcting the contents of a selected field - Triggers before modifying a selected field. Can be used for data validation.
08	After correcting the contents of a selected field - Triggers after updating a field.
09	After getting the original of an entry - Triggers after retrieving the original value of an entry.

2.3. Events Related to Change Tracking and Authorization

Event Code	Description
10	After creating the header entries for the change task (E071) - Triggers after adding header entries to the change task.
11	After changing a key entry for the change task (E071K) - Triggers when a key entry in a change task is modified.
12	After changing the key entries for the change task (E071K) - Triggers when key entries in a change task are modified.

2.4. Events for Special Cases and Alternative Processes

Event Code	Description
18	After checking whether the data has changed - Triggers after verifying whether data has changed.
19	After initializing global variables, field symbols, etc. - Triggers after initializing global variables and field symbols.
21	Fill hidden fields - Used to populate hidden fields.

2.5. Events That Replace Standard SAP Routines

Event Code	Description
AA	Instead of the standard data read routine
AB	Instead of the standard database change routine
AC	Instead of the standard 'Get original' routine

2.6. Events Related to Internal Use and GUI

Event Code	Description
ST	GUI menu main program name - Used for SAP GUI menu settings.
AI	Internal use only - Reserved for SAP's internal use.

3. Creating a Modification Event from Scratch

In this section, we will walk through the process of creating a Modification Event, using the 05 - Creating a new entry event as an example.

The following steps will guide you through creating a customizing table, adding it to a maintenance screen (SM30), integrating a Modification Event, and testing it.

Steps:

1. Create a customizing table using SE11

2. Convert the table into a maintenance view

3. Add a Modification Event

4. Write ABAP code to implement the 05 - Creating a new entry event

5. Test the setup and analyze the results

Create a customization table with SE11 T-Code.

Add fields and activate it. Click Utilities->Table Maintenance Generator.

Choose Function Group , maintenance type, screen settings and record routine and click Create button.

After creating process complete. you can check your customization table with SM30 T-Code.

You can change some field status.

You should open related screen. and double click screen number.

In this sample, We will change name column Input / Output Setting

After editing, you will not add any entries in the Name column.

We will create a event. SE11->Utilities->Table Maintenace Generator->Environment->Modification->Events

You should choose an event and write a form name. Then click editor button.

You can create new include.

You should add form endform block firstly with your form routine name.

We add event for after click enter button when adding new entries.

Write a customer codes and click enter. Event will run and get customer names.

4. Conclusion and Best Practices

• Before Save and Before Delete events should be used for data validation.

• After Save and After Delete events are useful for logging and trigger-based actions.

• AA-AH events should be used cautiously when replacing standard SAP read/write routines.

In this article, we explored the types of SAP Modification Events and their use cases. Selecting the appropriate event is crucial for maintaining data integrity, performance, and system stability in SAP projects.