SAP HR_DEUEV_CHECK_DSME Function Module for
HR_DEUEV_CHECK_DSME is a standard hr deuev check dsme SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 hr deuev check dsme FM, simply by entering the name HR_DEUEV_CHECK_DSME into the relevant SAP transaction such as SE37 or SE38.
Function Group: HRD3
Program Name: SAPLHRD3
Main Program: SAPLHRD3
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function HR_DEUEV_CHECK_DSME 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 'HR_DEUEV_CHECK_DSME'".
EXPORTING
I_KENNZST = "
IS_DSME = "
IMPORTING
ET_ERRORS = "
EXCEPTIONS
CHECK_FAILED = 1
IMPORTING Parameters details for HR_DEUEV_CHECK_DSME
I_KENNZST -
Data type: D3KENNZSTOptional: No
Call by Reference: Yes
IS_DSME -
Data type: PD3DSMEOptional: No
Call by Reference: Yes
EXPORTING Parameters details for HR_DEUEV_CHECK_DSME
ET_ERRORS -
Data type: P01_SYMSG_TABOptional: No
Call by Reference: Yes
EXCEPTIONS details
CHECK_FAILED -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for HR_DEUEV_CHECK_DSME 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_et_errors | TYPE P01_SYMSG_TAB, " | |||
| lv_i_kennzst | TYPE D3KENNZST, " | |||
| lv_check_failed | TYPE D3KENNZST, " | |||
| lv_is_dsme | TYPE PD3DSME. " |
|   CALL FUNCTION 'HR_DEUEV_CHECK_DSME' " |
| EXPORTING | ||
| I_KENNZST | = lv_i_kennzst | |
| IS_DSME | = lv_is_dsme | |
| IMPORTING | ||
| ET_ERRORS | = lv_et_errors | |
| EXCEPTIONS | ||
| CHECK_FAILED = 1 | ||
| . " HR_DEUEV_CHECK_DSME | ||
ABAP code using 7.40 inline data declarations to call FM HR_DEUEV_CHECK_DSME
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.Search for further information about these or an SAP related objects