SAP HRFPM_GET_ADTKEY Function Module for









HRFPM_GET_ADTKEY is a standard hrfpm get adtkey 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 hrfpm get adtkey FM, simply by entering the name HRFPM_GET_ADTKEY into the relevant SAP transaction such as SE37 or SE38.

Function Group: HRFPM_ADT
Program Name: SAPLHRFPM_ADT
Main Program: SAPLHRFPM_ADT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function HRFPM_GET_ADTKEY 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 'HRFPM_GET_ADTKEY'"
EXPORTING
* PLVAR = "
* USE_IN_COMBOBOX = "
* FORCE_ADT_KEY_DERIVATION = ' ' "
* IV_ADD_STORED_VALUES = 'X' "
OTYPE = "
OBJID = "
SEL_DATE = "
* ISTAT = '1' "
* MGRP = "
* SGRP = "
* NO_MESSAGE = 'X' "
* SUBTY = "

IMPORTING
ADTKEY = "
EV_SGRP_USED = "
ES_ADTKEY_TO_STORED = "
ES_ADTKEY_STORED = "
TEXT = "
ABBRE = "
ADTKEY_T = "
ADTKEY_TO = "
TEXT_TO = "
ABBRE_TO = "
ADTKEY_T_TO = "
EV_MGRP_USED = "
.



IMPORTING Parameters details for HRFPM_GET_ADTKEY

PLVAR -

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

USE_IN_COMBOBOX -

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

FORCE_ADT_KEY_DERIVATION -

Data type: FLAG
Default: SPACE
Optional: Yes
Call by Reference: Yes

IV_ADD_STORED_VALUES -

Data type: FLAG
Default: 'X'
Optional: Yes
Call by Reference: No ( called with pass by value option)

OTYPE -

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

OBJID -

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

SEL_DATE -

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

ISTAT -

Data type: ISTAT_D
Default: '1'
Optional: Yes
Call by Reference: No ( called with pass by value option)

MGRP -

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

SGRP -

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

NO_MESSAGE -

Data type: FLAG
Default: 'X'
Optional: Yes
Call by Reference: Yes

SUBTY -

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

EXPORTING Parameters details for HRFPM_GET_ADTKEY

ADTKEY -

Data type: ADTKEY
Optional: No
Call by Reference: Yes

EV_SGRP_USED -

Data type: HRFPM_SGRP
Optional: No
Call by Reference: Yes

ES_ADTKEY_TO_STORED -

Data type: ADTINFO
Optional: No
Call by Reference: Yes

ES_ADTKEY_STORED -

Data type: ADTINFO
Optional: No
Call by Reference: Yes

TEXT -

Data type: ADTTEXT
Optional: No
Call by Reference: Yes

ABBRE -

Data type: ADTABBRE
Optional: No
Call by Reference: Yes

ADTKEY_T -

Data type: ADTKEY_T
Optional: No
Call by Reference: Yes

ADTKEY_TO -

Data type: ADTKEY
Optional: No
Call by Reference: Yes

TEXT_TO -

Data type: ADTTEXT
Optional: No
Call by Reference: Yes

ABBRE_TO -

Data type: ADTABBRE
Optional: No
Call by Reference: Yes

ADTKEY_T_TO -

Data type: ADTKEY_T
Optional: No
Call by Reference: Yes

EV_MGRP_USED -

Data type: HRFPM_MGRP
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for HRFPM_GET_ADTKEY 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_plvar  TYPE PLVAR, "   
lv_adtkey  TYPE ADTKEY, "   
lv_ev_sgrp_used  TYPE HRFPM_SGRP, "   
lv_use_in_combobox  TYPE FLAG, "   
lv_es_adtkey_to_stored  TYPE ADTINFO, "   
lv_force_adt_key_derivation  TYPE FLAG, "   SPACE
lv_es_adtkey_stored  TYPE ADTINFO, "   
lv_iv_add_stored_values  TYPE FLAG, "   'X'
lv_text  TYPE ADTTEXT, "   
lv_otype  TYPE OTYPE, "   
lv_abbre  TYPE ADTABBRE, "   
lv_objid  TYPE OBJEKTID, "   
lv_adtkey_t  TYPE ADTKEY_T, "   
lv_sel_date  TYPE SYDATUM, "   
lv_istat  TYPE ISTAT_D, "   '1'
lv_adtkey_to  TYPE ADTKEY, "   
lv_mgrp  TYPE HRFPM_MGRP, "   
lv_text_to  TYPE ADTTEXT, "   
lv_sgrp  TYPE HRFPM_SGRP, "   
lv_abbre_to  TYPE ADTABBRE, "   
lv_no_message  TYPE FLAG, "   'X'
lv_adtkey_t_to  TYPE ADTKEY_T, "   
lv_subty  TYPE SUBTY, "   
lv_ev_mgrp_used  TYPE HRFPM_MGRP. "   

  CALL FUNCTION 'HRFPM_GET_ADTKEY'  "
    EXPORTING
         PLVAR = lv_plvar
         USE_IN_COMBOBOX = lv_use_in_combobox
         FORCE_ADT_KEY_DERIVATION = lv_force_adt_key_derivation
         IV_ADD_STORED_VALUES = lv_iv_add_stored_values
         OTYPE = lv_otype
         OBJID = lv_objid
         SEL_DATE = lv_sel_date
         ISTAT = lv_istat
         MGRP = lv_mgrp
         SGRP = lv_sgrp
         NO_MESSAGE = lv_no_message
         SUBTY = lv_subty
    IMPORTING
         ADTKEY = lv_adtkey
         EV_SGRP_USED = lv_ev_sgrp_used
         ES_ADTKEY_TO_STORED = lv_es_adtkey_to_stored
         ES_ADTKEY_STORED = lv_es_adtkey_stored
         TEXT = lv_text
         ABBRE = lv_abbre
         ADTKEY_T = lv_adtkey_t
         ADTKEY_TO = lv_adtkey_to
         TEXT_TO = lv_text_to
         ABBRE_TO = lv_abbre_to
         ADTKEY_T_TO = lv_adtkey_t_to
         EV_MGRP_USED = lv_ev_mgrp_used
. " HRFPM_GET_ADTKEY




ABAP code using 7.40 inline data declarations to call FM HRFPM_GET_ADTKEY

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.

 
 
 
 
 
DATA(ld_force_adt_key_derivation) = ' '.
 
 
DATA(ld_iv_add_stored_values) = 'X'.
 
 
 
 
 
 
 
DATA(ld_istat) = '1'.
 
 
 
 
 
 
DATA(ld_no_message) = 'X'.
 
 
 
 


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!