SAP HR_SK_GET_PP_CHANGES Function Module for









HR_SK_GET_PP_CHANGES is a standard hr sk get pp changes 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 sk get pp changes FM, simply by entering the name HR_SK_GET_PP_CHANGES into the relevant SAP transaction such as SE37 or SE38.

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



Function HR_SK_GET_PP_CHANGES 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_SK_GET_PP_CHANGES'"
EXPORTING
PERNR = "
BEGDA = "
ENDDA = "
TXTYP = "
* BEGDA_ZMEN = 00000000 "
* ENDDA_ZMEN = 00000000 "

IMPORTING
HIRE = "
FIRE = "

TABLES
IT_PP_CHANGES = "
.



IMPORTING Parameters details for HR_SK_GET_PP_CHANGES

PERNR -

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

BEGDA -

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

ENDDA -

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

TXTYP -

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

BEGDA_ZMEN -

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

ENDDA_ZMEN -

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

EXPORTING Parameters details for HR_SK_GET_PP_CHANGES

HIRE -

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

FIRE -

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

TABLES Parameters details for HR_SK_GET_PP_CHANGES

IT_PP_CHANGES -

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

Copy and paste ABAP code example for HR_SK_GET_PP_CHANGES 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_hire  TYPE BEGDA, "   
lv_pernr  TYPE PERSNO, "   
lt_it_pp_changes  TYPE STANDARD TABLE OF PSK_PP, "   
lv_fire  TYPE ENDDA, "   
lv_begda  TYPE BEGDA, "   
lv_endda  TYPE ENDDA, "   
lv_txtyp  TYPE SORT_SUM, "   
lv_begda_zmen  TYPE BEGDA, "   00000000
lv_endda_zmen  TYPE ENDDA. "   00000000

  CALL FUNCTION 'HR_SK_GET_PP_CHANGES'  "
    EXPORTING
         PERNR = lv_pernr
         BEGDA = lv_begda
         ENDDA = lv_endda
         TXTYP = lv_txtyp
         BEGDA_ZMEN = lv_begda_zmen
         ENDDA_ZMEN = lv_endda_zmen
    IMPORTING
         HIRE = lv_hire
         FIRE = lv_fire
    TABLES
         IT_PP_CHANGES = lt_it_pp_changes
. " HR_SK_GET_PP_CHANGES




ABAP code using 7.40 inline data declarations to call FM HR_SK_GET_PP_CHANGES

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_begda_zmen) = 00000000.
 
DATA(ld_endda_zmen) = 00000000.
 


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!