SAP HR_WRITE_D3 Function Module for









HR_WRITE_D3 is a standard hr write d3 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 write d3 FM, simply by entering the name HR_WRITE_D3 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): Normal Function Module
Update:



Function HR_WRITE_D3 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_WRITE_D3'"
  EXPORTING
*  IT_HIST =  "

TABLES
   DSAP =  "
*  DBEU =  "
*  DBKS =  "
*  DBKV =  "
*  FLAG =  "
*  DELETE =  "
   DSME =  "
*  DBME =  "
*  DBNA =  "
*  DBAN =  "
*  DBGB =  "
*  DBSO =  "
*  DBUV =  "
*  DBUV_DAT =  "

EXCEPTIONS
   DUPLICATE_KEY = 1    MISSING_ENTRY = 2    MISSING_DSME = 3
.



IMPORTING Parameters details for HR_WRITE_D3

IT_HIST -

Data type: HRD3_T_HIST
Optional: Yes
Call by Reference: Yes

TABLES Parameters details for HR_WRITE_D3

DSAP -

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

DBEU -

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

DBKS -

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

DBKV -

Data type: PD3DBKV
Optional: Yes
Call by Reference: Yes

FLAG -

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

DELETE -

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

DSME -

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

DBME -

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

DBNA -

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

DBAN -

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

DBGB -

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

DBSO -

Data type: HRDESV_DS_S_DBSO_D3
Optional: Yes
Call by Reference: Yes

DBUV -

Data type: PD3DBUV
Optional: Yes
Call by Reference: Yes

DBUV_DAT -

Data type: PD3DBUV_DAT
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

DUPLICATE_KEY -

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

MISSING_ENTRY -

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

MISSING_DSME -

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

Copy and paste ABAP code example for HR_WRITE_D3 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:
lt_dsap  TYPE STANDARD TABLE OF PD3DSAP, "   
lv_it_hist  TYPE HRD3_T_HIST, "   
lv_duplicate_key  TYPE HRD3_T_HIST, "   
lt_dbeu  TYPE STANDARD TABLE OF PD3DBEU, "   
lt_dbks  TYPE STANDARD TABLE OF PD3DBKS, "   
lt_dbkv  TYPE STANDARD TABLE OF PD3DBKV, "   
lt_flag  TYPE STANDARD TABLE OF PD3FLAG, "   
lt_delete  TYPE STANDARD TABLE OF HRD3KEY, "   
lt_dsme  TYPE STANDARD TABLE OF PD3DSME, "   
lv_missing_entry  TYPE PD3DSME, "   
lt_dbme  TYPE STANDARD TABLE OF PD3DBME, "   
lv_missing_dsme  TYPE PD3DBME, "   
lt_dbna  TYPE STANDARD TABLE OF PD3DBNA, "   
lt_dban  TYPE STANDARD TABLE OF PD3DBAN, "   
lt_dbgb  TYPE STANDARD TABLE OF PD3DBGB, "   
lt_dbso  TYPE STANDARD TABLE OF HRDESV_DS_S_DBSO_D3, "   
lt_dbuv  TYPE STANDARD TABLE OF PD3DBUV, "   
lt_dbuv_dat  TYPE STANDARD TABLE OF PD3DBUV_DAT. "   

  CALL FUNCTION 'HR_WRITE_D3'  "
    EXPORTING
         IT_HIST = lv_it_hist
    TABLES
         DSAP = lt_dsap
         DBEU = lt_dbeu
         DBKS = lt_dbks
         DBKV = lt_dbkv
         FLAG = lt_flag
         DELETE = lt_delete
         DSME = lt_dsme
         DBME = lt_dbme
         DBNA = lt_dbna
         DBAN = lt_dban
         DBGB = lt_dbgb
         DBSO = lt_dbso
         DBUV = lt_dbuv
         DBUV_DAT = lt_dbuv_dat
    EXCEPTIONS
        DUPLICATE_KEY = 1
        MISSING_ENTRY = 2
        MISSING_DSME = 3
. " HR_WRITE_D3




ABAP code using 7.40 inline data declarations to call FM HR_WRITE_D3

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



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!