SAP CJDT_EVENT_PROCESSING Function Module for NOTRANSL: Message-Handling für Statusbearbeitung
CJDT_EVENT_PROCESSING is a standard cjdt event processing SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Message-Handling für Statusbearbeitung processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.
See here to view full function module documentation and code listing for cjdt event processing FM, simply by entering the name CJDT_EVENT_PROCESSING into the relevant SAP transaction such as SE37 or SE38.
Function Group: CJDT
Program Name: SAPLCJDT
Main Program: SAPLCJDT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CJDT_EVENT_PROCESSING pattern details
In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.CALL FUNCTION 'CJDT_EVENT_PROCESSING'"NOTRANSL: Message-Handling für Statusbearbeitung.
EXPORTING
* I_POPUP_IF_WARNING = ' ' "Generic Type
I_VRGNG = "Business Transaction
* OK_CODE = ' ' "Menu Painter: Function code
IMPORTING
OK_CODE = "Menu Painter: Function code
IMPORTING Parameters details for CJDT_EVENT_PROCESSING
I_POPUP_IF_WARNING - Generic Type
Data type: CDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
I_VRGNG - Business Transaction
Data type: TJ01-VRGNGOptional: No
Call by Reference: No ( called with pass by value option)
OK_CODE - Menu Painter: Function code
Data type: TC02-FCODEDefault: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CJDT_EVENT_PROCESSING
OK_CODE - Menu Painter: Function code
Data type: TC02-FCODEOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CJDT_EVENT_PROCESSING Function Module
The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.| DATA: | ||||
| lv_ok_code | TYPE TC02-FCODE, " | |||
| lv_i_popup_if_warning | TYPE C, " SPACE | |||
| lv_i_vrgng | TYPE TJ01-VRGNG, " | |||
| lv_ok_code | TYPE TC02-FCODE. " SPACE |
|   CALL FUNCTION 'CJDT_EVENT_PROCESSING' "NOTRANSL: Message-Handling für Statusbearbeitung |
| EXPORTING | ||
| I_POPUP_IF_WARNING | = lv_i_popup_if_warning | |
| I_VRGNG | = lv_i_vrgng | |
| OK_CODE | = lv_ok_code | |
| IMPORTING | ||
| OK_CODE | = lv_ok_code | |
| . " CJDT_EVENT_PROCESSING | ||
ABAP code using 7.40 inline data declarations to call FM CJDT_EVENT_PROCESSING
The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.| "SELECT single FCODE FROM TC02 INTO @DATA(ld_ok_code). | ||||
| DATA(ld_i_popup_if_warning) | = ' '. | |||
| "SELECT single VRGNG FROM TJ01 INTO @DATA(ld_i_vrgng). | ||||
| "SELECT single FCODE FROM TC02 INTO @DATA(ld_ok_code). | ||||
| DATA(ld_ok_code) | = ' '. | |||
Search for further information about these or an SAP related objects