K_HR_ACTIVITYTYPE_GETDETAIL SAP Function module

K_HR_ACTIVITYTYPE_GETDETAIL is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name K_HR_ACTIVITYTYPE_GETDETAIL into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: KMA6HR
Released Date: Not Released
Processing type: Remote-Enabled

Pattern for FM K_HR_ACTIVITYTYPE_GETDETAIL - K HR ACTIVITYTYPE GETDETAIL

CALL FUNCTION 'K_HR_ACTIVITYTYPE_GETDETAIL' "
  EXPORTING
    co_area =                   " csla_hr-co_area
    activitytype =              " csla_hr-activitytype
*   read_date = SY-DATUM        " csla_hr-date_from
*   language = SY-LANGU         " csla_hr-langu
*   bypassing_buffer = SPACE    " csks_hr1-flag
*   fill_buffer = 'X'           " csks_hr1-flag
  IMPORTING
    activitytype_detail =       " csla_core
  EXCEPTIONS
    NOT_FOUND = 1               "
    .  "  K_HR_ACTIVITYTYPE_GETDETAIL

ABAP code example for Function Module K_HR_ACTIVITYTYPE_GETDETAIL

The ABAP code below is a full code listing to execute function module K_HR_ACTIVITYTYPE_GETDETAIL including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_activitytype_detail  
 
 TYPE CSLA_CORE
.



DATA(ld_co_area) = some text here


DATA(ld_activitytype) = some text here


DATA(ld_read_date) = 20210129


DATA(ld_language) = Check type of data required


DATA(ld_bypassing_buffer) = some text here


DATA(ld_fill_buffer) = some text here
.

CALL FUNCTION 'K_HR_ACTIVITYTYPE_GETDETAIL'
  EXPORTING
    co_area =                    ld_co_area
    activitytype =               ld_activitytype
*   read_date =                  ld_read_date
*   language =                   ld_language
*   bypassing_buffer =           ld_bypassing_buffer
*   fill_buffer =                ld_fill_buffer
  IMPORTING
    activitytype_detail =        ld_activitytype_detail
  EXCEPTIONS
    NOT_FOUND =                  1
    .  "  K_HR_ACTIVITYTYPE_GETDETAIL

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_activitytype_detail
 
 TYPE CSLA_CORE ,
ld_co_area
 
 TYPE CSLA_HR-CO_AREA ,
ld_activitytype
 
 TYPE CSLA_HR-ACTIVITYTYPE ,
ld_read_date
 
 TYPE CSLA_HR-DATE_FROM ,
ld_language
 
 TYPE CSLA_HR-LANGU ,
ld_bypassing_buffer
 
 TYPE CSKS_HR1-FLAG ,
ld_fill_buffer
 
 TYPE CSKS_HR1-FLAG .



ld_co_area = some text here

ld_activitytype = some text here

ld_read_date = 20210129

ld_language = Check type of data required

ld_bypassing_buffer = some text here

ld_fill_buffer = some text here