SAP HR_FR_DADSU_SPLIT_PERIODS Function Module for









HR_FR_DADSU_SPLIT_PERIODS is a standard hr fr dadsu split periods 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 dadsu split periods FM, simply by entering the name HR_FR_DADSU_SPLIT_PERIODS into the relevant SAP transaction such as SE37 or SE38.

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



Function HR_FR_DADSU_SPLIT_PERIODS 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_DADSU_SPLIT_PERIODS'"
EXPORTING
BEGDA = "
ENDDA = "
START_REASON = "
* START_REAS2 = "
END_REASON = "
* END_REAS2 = "
IS_ABSENCE = "

CHANGING
DADSU_PERIODS = "
.



IMPORTING Parameters details for HR_FR_DADSU_SPLIT_PERIODS

BEGDA -

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

ENDDA -

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

START_REASON -

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

START_REAS2 -

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

END_REASON -

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

END_REAS2 -

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

IS_ABSENCE -

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

CHANGING Parameters details for HR_FR_DADSU_SPLIT_PERIODS

DADSU_PERIODS -

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

Copy and paste ABAP code example for HR_FR_DADSU_SPLIT_PERIODS 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_begda  TYPE BEGDA, "   
lv_dadsu_periods  TYPE PFRDA_TAB_DADSU_ST41, "   
lv_endda  TYPE ENDDA, "   
lv_start_reason  TYPE PFRDA_CODE_MOTIF, "   
lv_start_reas2  TYPE PFRDA_CODE_MOTIF, "   
lv_end_reason  TYPE PFRDA_CODE_MOTIF, "   
lv_end_reas2  TYPE PFRDA_CODE_MOTIF, "   
lv_is_absence  TYPE BOOLE_D. "   

  CALL FUNCTION 'HR_FR_DADSU_SPLIT_PERIODS'  "
    EXPORTING
         BEGDA = lv_begda
         ENDDA = lv_endda
         START_REASON = lv_start_reason
         START_REAS2 = lv_start_reas2
         END_REASON = lv_end_reason
         END_REAS2 = lv_end_reas2
         IS_ABSENCE = lv_is_absence
    CHANGING
         DADSU_PERIODS = lv_dadsu_periods
. " HR_FR_DADSU_SPLIT_PERIODS




ABAP code using 7.40 inline data declarations to call FM HR_FR_DADSU_SPLIT_PERIODS

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.

 
 
 
 
 
 
 
 


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!