SAP HR_FR_TRACK_MODEL_CHANGES Function Module for









HR_FR_TRACK_MODEL_CHANGES is a standard hr fr track model 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 fr track model changes FM, simply by entering the name HR_FR_TRACK_MODEL_CHANGES into the relevant SAP transaction such as SE37 or SE38.

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



Function HR_FR_TRACK_MODEL_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_FR_TRACK_MODEL_CHANGES'"
EXPORTING
P_REGNO = "
P_BEGDA = "
P_ENDDA = "
* IV_PERNR = "
* IV_CHKDT = "
* IV_ADATE = "
* IV_VDATE = "
* IT_DECAL = "
* IV_ADDCT = ' ' "

IMPORTING
P_TAB_MODEL_CHANGES = "

CHANGING
* T_T5F1M = "
* T_T5F1F = "
* CT_P0001 = "
* CT_P0008 = "
* CT_P0016 = "
* CT_P0217 = "
* CT_WPBP = "
* CS_P0064 = "

EXCEPTIONS
INVALID_REGNO = 1 FEATURE_ERROR = 2
.



IMPORTING Parameters details for HR_FR_TRACK_MODEL_CHANGES

P_REGNO -

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

P_BEGDA -

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

P_ENDDA -

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

IV_PERNR -

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

IV_CHKDT -

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

IV_ADATE -

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

IV_VDATE -

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

IT_DECAL -

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

IV_ADDCT -

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

EXPORTING Parameters details for HR_FR_TRACK_MODEL_CHANGES

P_TAB_MODEL_CHANGES -

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

CHANGING Parameters details for HR_FR_TRACK_MODEL_CHANGES

T_T5F1M -

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

T_T5F1F -

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

CT_P0001 -

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

CT_P0008 -

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

CT_P0016 -

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

CT_P0217 -

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

CT_WPBP -

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

CS_P0064 -

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

EXCEPTIONS details

INVALID_REGNO -

Data type:
Optional: No
Call by Reference: Yes

FEATURE_ERROR -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for HR_FR_TRACK_MODEL_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_p_regno  TYPE PFRS0_TAB_REGNO, "   
lv_t_t5f1m  TYPE PFRS0_TAB_T5F1M, "   
lv_invalid_regno  TYPE PFRS0_TAB_T5F1M, "   
lv_p_tab_model_changes  TYPE PFRS0_TAB_MOD_CHANGES, "   
lv_p_begda  TYPE BEGDA, "   
lv_t_t5f1f  TYPE PFRS0_TAB_T5F1F, "   
lv_feature_error  TYPE PFRS0_TAB_T5F1F, "   
lv_p_endda  TYPE ENDDA, "   
lv_ct_p0001  TYPE P0001_TAB, "   
lv_ct_p0008  TYPE P0008_TAB, "   
lv_iv_pernr  TYPE PERNR_D, "   
lv_ct_p0016  TYPE P0016_TAB, "   
lv_iv_chkdt  TYPE CHKDT, "   
lv_ct_p0217  TYPE P0217_TAB, "   
lv_iv_adate  TYPE D, "   
lv_ct_wpbp  TYPE HRPAY99_WPBP, "   
lv_iv_vdate  TYPE D, "   
lv_cs_p0064  TYPE P0064, "   
lv_it_decal  TYPE PFRS0_TAB_DECAL, "   
lv_iv_addct  TYPE BOOLE_D. "   SPACE

  CALL FUNCTION 'HR_FR_TRACK_MODEL_CHANGES'  "
    EXPORTING
         P_REGNO = lv_p_regno
         P_BEGDA = lv_p_begda
         P_ENDDA = lv_p_endda
         IV_PERNR = lv_iv_pernr
         IV_CHKDT = lv_iv_chkdt
         IV_ADATE = lv_iv_adate
         IV_VDATE = lv_iv_vdate
         IT_DECAL = lv_it_decal
         IV_ADDCT = lv_iv_addct
    IMPORTING
         P_TAB_MODEL_CHANGES = lv_p_tab_model_changes
    CHANGING
         T_T5F1M = lv_t_t5f1m
         T_T5F1F = lv_t_t5f1f
         CT_P0001 = lv_ct_p0001
         CT_P0008 = lv_ct_p0008
         CT_P0016 = lv_ct_p0016
         CT_P0217 = lv_ct_p0217
         CT_WPBP = lv_ct_wpbp
         CS_P0064 = lv_cs_p0064
    EXCEPTIONS
        INVALID_REGNO = 1
        FEATURE_ERROR = 2
. " HR_FR_TRACK_MODEL_CHANGES




ABAP code using 7.40 inline data declarations to call FM HR_FR_TRACK_MODEL_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_iv_addct) = ' '.
 


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!