SAP HR_READ_DU Function Module for









HR_READ_DU is a standard hr read du 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 read du FM, simply by entering the name HR_READ_DU into the relevant SAP transaction such as SE37 or SE38.

Function Group: HRD3
Program Name: SAPLHRD3
Main Program: SAPLHRD3
Appliation area: P
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:



Function HR_READ_DU 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_READ_DU'"
EXPORTING
KEY = "

IMPORTING
ANZAHL = "

TABLES
P_DIT = "

EXCEPTIONS
NO_NOTIF = 1 INCOMPLETE_KEY = 2 TARGET_NOT_FOUND = 3 S11S13_NOT_FOUND = 4 KNAPPSCHAFT = 5
.



IMPORTING Parameters details for HR_READ_DU

KEY -

Data type: HRD3KEY
Optional: No
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for HR_READ_DU

ANZAHL -

Data type: HRD3KEY-MNR
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for HR_READ_DU

P_DIT -

Data type: PC211
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

NO_NOTIF -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

INCOMPLETE_KEY -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

TARGET_NOT_FOUND -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

S11S13_NOT_FOUND -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

KNAPPSCHAFT -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for HR_READ_DU 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_key  TYPE HRD3KEY, "   
lt_p_dit  TYPE STANDARD TABLE OF PC211, "   
lv_anzahl  TYPE HRD3KEY-MNR, "   
lv_no_notif  TYPE HRD3KEY, "   
lv_incomplete_key  TYPE HRD3KEY, "   
lv_target_not_found  TYPE HRD3KEY, "   
lv_s11s13_not_found  TYPE HRD3KEY, "   
lv_knappschaft  TYPE HRD3KEY. "   

  CALL FUNCTION 'HR_READ_DU'  "
    EXPORTING
         KEY = lv_key
    IMPORTING
         ANZAHL = lv_anzahl
    TABLES
         P_DIT = lt_p_dit
    EXCEPTIONS
        NO_NOTIF = 1
        INCOMPLETE_KEY = 2
        TARGET_NOT_FOUND = 3
        S11S13_NOT_FOUND = 4
        KNAPPSCHAFT = 5
. " HR_READ_DU




ABAP code using 7.40 inline data declarations to call FM HR_READ_DU

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 MNR FROM HRD3KEY INTO @DATA(ld_anzahl).
 
 
 
 
 
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!