Skip to Content


The key driver for this new development was a reduction of ABAP coding for the extraction in the application system of up to 100 percent. As the new extraction is customizing-based, no extraction function modules are required anymore.

Definition of Extraction Fields

In the first step, the Business Process Type has to be chosen from the table.

Choose Business Process Type

Now you can define the extraction fields. The fields are grouped by the Business Process Type. This means that you can reuse an extraction field for different scenarios as long as it uses the same Business Process Type.

New fields for extraction

In the next step the data source of the field is defined. Different options for data extraction exist. 


  • Take over Application Table value  

Value from Application Table

The structure or table is defined in addition to the field name the value should be extracted from.


  • Concatenate values from different fields

Concatenate Fields

It is possible to concatenate values. Therefore you have to create two or more entries and choose Concatenate with Previous value as field type in the second entry.


  • Read from related application tables

Related Application Tables

In this example you can see how you can read from related tables. You choose Key for Further Table Access as field type. Then you define the source field – in this example it is LIFNR from the Purchase Order Header table. This field is used to access the table LFA1. Any possible logical operator is available (equal, not equal etc.). In the next screen the field ADRNR is extracted from table LFA1. This field is used to read from table ADR6, where e-mail addresses are stored. On the last screen, the value is assigned to the field.
In the example above it in general is possible to find more than one e-mail address. In this case you can choose All Entries, which extracts all addresses using indexed parameters. It is also possible to choose Last Entry or First Entry.


Assigning Fields to Application Object Type 

After defining all fields, you assign the parameters to your Application Object Type. In addition, you define whether the parameter shall be a Control, Info or Query parameter or a Tracking ID.

Overview assigning fields to Application Object

Detailed view of an example parameter. As you can see, you can define a parameter as Control Parameter as well as a Tracking ID.

Detail View


Define Expected Events 

It is also possible to define Expected Events with this customizing. In the following you can find an example of two Expected Events:

Example Expected Events

First you define the expected event name and field to which the date and time shall be stored.
In the extraction field you enter a parameter which you have defined before. In the example the parameter contains the date. As no time is available, it is defined as a constant. The parameter is concatenated as you can see on the following screen:

Example Date and Time

In case the expected event date and time shall be calculated based on a offset, you use the field Offset in Days. If for example the expected date should be five days later than the extracted date, you would enter five in the field.
Factory calendars are used to consider weekends and public holidays. Either you use a standard calendar or you can define which calendar to use in the customizing.

Expected Event calculated using offset


Event Types

In the last step we will see an example of how to use the extraction customizing for Event Messages.
In the first step, the relevant Event Type has to be chosen from the table. Please be aware that as a prerequisite, you have to define this in the customizing of Define Event Types.

Insert Event Type

This is an example to send an event message. Actual date, time and Tracking ID are taken over from extraction fields.

Settings to Send an Event Message

Within the customizing you define all required data for an Event Message. If you want to add several parameters within one Event Message, you have to increase the row number.



With this new customizing, it is now possible to set up SAP Event Management scenarios without requiring any function module. Furthermore, it is possible to combine this customizing with function modules – so you can use the new customizing for easy extraction and function modules for special cases.
In addition, it is much easier for the customer to add attributes after the implementation project is finished and the implementation consultants are out of reach.

To report this post you need to login first.


You must be Logged on to comment or reply to a post.

  1. Former Member

    Thanks Berthold for this great blog posting. It was really helpful for me to do some quick prototypes and demonstrations without having to tap my development resources!


Leave a Reply