SAP HR_HU_GET_SZEMNAP Function Module for
HR_HU_GET_SZEMNAP is a standard hr hu get szemnap 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 hu get szemnap FM, simply by entering the name HR_HU_GET_SZEMNAP into the relevant SAP transaction such as SE37 or SE38.
Function Group: 0PH2
Program Name: SAPL0PH2
Main Program: SAPL0PH2
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:
Function HR_HU_GET_SZEMNAP 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_HU_GET_SZEMNAP'".
EXPORTING
IV_PERNR = "
* IV_PERIOD = '999912' "
* IV_T5H4X = "
TABLES
EV_PCL1_PC = "
IMPORTING Parameters details for HR_HU_GET_SZEMNAP
IV_PERNR -
Data type: PERSNOOptional: No
Call by Reference: Yes
IV_PERIOD -
Data type: IPERIDefault: '999912'
Optional: Yes
Call by Reference: Yes
IV_T5H4X -
Data type: FLAGOptional: Yes
Call by Reference: Yes
TABLES Parameters details for HR_HU_GET_SZEMNAP
EV_PCL1_PC -
Data type: P21_PCL1_PCOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for HR_HU_GET_SZEMNAP 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_iv_pernr | TYPE PERSNO, " | |||
lt_ev_pcl1_pc | TYPE STANDARD TABLE OF P21_PCL1_PC, " | |||
lv_iv_period | TYPE IPERI, " '999912' | |||
lv_iv_t5h4x | TYPE FLAG. " |
  CALL FUNCTION 'HR_HU_GET_SZEMNAP' " |
EXPORTING | ||
IV_PERNR | = lv_iv_pernr | |
IV_PERIOD | = lv_iv_period | |
IV_T5H4X | = lv_iv_t5h4x | |
TABLES | ||
EV_PCL1_PC | = lt_ev_pcl1_pc | |
. " HR_HU_GET_SZEMNAP |
ABAP code using 7.40 inline data declarations to call FM HR_HU_GET_SZEMNAP
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_iv_period) | = '999912'. | |||
Search for further information about these or an SAP related objects