HRMSS_PMU_GET_REC_TRAIN_NAME SAP Function module

HRMSS_PMU_GET_REC_TRAIN_NAME 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 HRMSS_PMU_GET_REC_TRAIN_NAME into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: HRMSS_PROFILEMATCHUP
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM HRMSS_PMU_GET_REC_TRAIN_NAME - HRMSS PMU GET REC TRAIN NAME

CALL FUNCTION 'HRMSS_PMU_GET_REC_TRAIN_NAME' "
  EXPORTING
    colname =                   " twpc_col-colname  Column Name
    key_date =                  " objec-begda   Start Date
    begda =                     " objec-begda   Start Date
    endda =                     " objec-endda   End Date
    langu =                     " sy-langu      Language Key for Current Text Environment
  IMPORTING
    coltype =                   " hrwpc_s_coltype-coltype  Column Type
  TABLES
    key_objects =               " hrwpc_s_keyobjec  Work Area for Database PCH
*   key_structure =             " hrwpc_s_keystruc  Structure Information for Database PCH
    column_content =            " hrwpc_s_keycolcont  Column Contents with Object Key
*   sort_column_content =       " hrwpc_s_sortcolcont  Column Content: Sortable
    .  "  HRMSS_PMU_GET_REC_TRAIN_NAME

ABAP code example for Function Module HRMSS_PMU_GET_REC_TRAIN_NAME

The ABAP code below is a full code listing to execute function module HRMSS_PMU_GET_REC_TRAIN_NAME 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_coltype  
 
 TYPE HRWPC_S_COLTYPE-COLTYPE
,
it_key_objects  
 
 TYPE STANDARD TABLE OF HRWPC_S_KEYOBJEC,"TABLES PARAM
wa_key_objects
 
 LIKE LINE OF it_key_objects
,
it_key_structure  
 
 TYPE STANDARD TABLE OF HRWPC_S_KEYSTRUC,"TABLES PARAM
wa_key_structure
 
 LIKE LINE OF it_key_structure
,
it_column_content  
 
 TYPE STANDARD TABLE OF HRWPC_S_KEYCOLCONT,"TABLES PARAM
wa_column_content
 
 LIKE LINE OF it_column_content
,
it_sort_column_content  
 
 TYPE STANDARD TABLE OF HRWPC_S_SORTCOLCONT,"TABLES PARAM
wa_sort_column_content
 
 LIKE LINE OF it_sort_column_content
.

 

SELECT single COLNAME 
  FROM TWPC_COL 
  INTO @DATA(ld_colname).



DATA(ld_key_date) = 20210129


DATA(ld_begda) = 20210129


DATA(ld_endda) = 20210129

DATA(ld_langu) = 'Check type of data required'.
 

"populate fields of struture and append to itab
append wa_key_objects to it_key_objects.
 

"populate fields of struture and append to itab
append wa_key_structure to it_key_structure.
 

"populate fields of struture and append to itab
append wa_column_content to it_column_content.
 

"populate fields of struture and append to itab
append wa_sort_column_content to it_sort_column_content.
.

CALL FUNCTION 'HRMSS_PMU_GET_REC_TRAIN_NAME'
  EXPORTING
    colname =                    ld_colname
    key_date =                   ld_key_date
    begda =                      ld_begda
    endda =                      ld_endda
    langu =                      ld_langu
  IMPORTING
    coltype =                    ld_coltype
  TABLES
    key_objects =                it_key_objects
*   key_structure =              it_key_structure
    column_content =             it_column_content
*   sort_column_content =        it_sort_column_content
    .  "  HRMSS_PMU_GET_REC_TRAIN_NAME

IF SY-SUBRC EQ 0.
  "All OK
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_coltype
 
 TYPE HRWPC_S_COLTYPE-COLTYPE ,
ld_colname
 
 TYPE TWPC_COL-COLNAME ,
it_key_objects
 
 TYPE STANDARD TABLE OF HRWPC_S_KEYOBJEC ,
wa_key_objects
 
 LIKE LINE OF it_key_objects,
ld_key_date
 
 TYPE OBJEC-BEGDA ,
it_key_structure
 
 TYPE STANDARD TABLE OF HRWPC_S_KEYSTRUC ,
wa_key_structure
 
 LIKE LINE OF it_key_structure,
ld_begda
 
 TYPE OBJEC-BEGDA ,
it_column_content
 
 TYPE STANDARD TABLE OF HRWPC_S_KEYCOLCONT ,
wa_column_content
 
 LIKE LINE OF it_column_content,
ld_endda
 
 TYPE OBJEC-ENDDA ,
it_sort_column_content
 
 TYPE STANDARD TABLE OF HRWPC_S_SORTCOLCONT ,
wa_sort_column_content
 
 LIKE LINE OF it_sort_column_content,
ld_langu
 
 TYPE SY-LANGU .



SELECT single COLNAME 
  FROM TWPC_COL 
  INTO ld_colname.
 

"populate fields of struture and append to itab
append wa_key_objects to it_key_objects.

ld_key_date = 20210129 

"populate fields of struture and append to itab
append wa_key_structure to it_key_structure.

ld_begda = 20210129 

"populate fields of struture and append to itab
append wa_column_content to it_column_content.

ld_endda = 20210129 

"populate fields of struture and append to itab
append wa_sort_column_content to it_sort_column_content.
ld_langu = 'Check type of data required'.