SAP HR_PROPOSE_TIMES_FROM_DWS Function Module for









HR_PROPOSE_TIMES_FROM_DWS is a standard hr propose times from dws 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 propose times from dws FM, simply by entering the name HR_PROPOSE_TIMES_FROM_DWS into the relevant SAP transaction such as SE37 or SE38.

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



Function HR_PROPOSE_TIMES_FROM_DWS 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_PROPOSE_TIMES_FROM_DWS'"
EXPORTING
STDAZ = "
VTKEN_IMP = "
DAYGEN = "
* INFOTYPE = 2001 "

IMPORTING
BEGUZ_EXP = "
ENDUZ_EXP = "
VTKEN_EXP = "
STDAZ_EXP = "
MESSAGE_OCCURED = "

TABLES
DAYINT = "
I2001 = "
I2002 = "
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLPTWS_001 User Exit for Generating Monthly Work Schedule

IMPORTING Parameters details for HR_PROPOSE_TIMES_FROM_DWS

STDAZ -

Data type: P2001-STDAZ
Optional: No
Call by Reference: No ( called with pass by value option)

VTKEN_IMP -

Data type: P2001-VTKEN
Optional: No
Call by Reference: No ( called with pass by value option)

DAYGEN -

Data type: PWSDAYGEN
Optional: No
Call by Reference: No ( called with pass by value option)

INFOTYPE -

Data type: PSKEY-INFTY
Default: 2001
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for HR_PROPOSE_TIMES_FROM_DWS

BEGUZ_EXP -

Data type: P2001-BEGUZ
Optional: No
Call by Reference: No ( called with pass by value option)

ENDUZ_EXP -

Data type: P2001-ENDUZ
Optional: No
Call by Reference: No ( called with pass by value option)

VTKEN_EXP -

Data type: P2001-VTKEN
Optional: No
Call by Reference: No ( called with pass by value option)

STDAZ_EXP -

Data type: P2001-STDAZ
Optional: No
Call by Reference: No ( called with pass by value option)

MESSAGE_OCCURED -

Data type: C
Optional: No
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for HR_PROPOSE_TIMES_FROM_DWS

DAYINT -

Data type: PWSDAYINT
Optional: No
Call by Reference: No ( called with pass by value option)

I2001 -

Data type: P2001
Optional: No
Call by Reference: No ( called with pass by value option)

I2002 -

Data type: P2002
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for HR_PROPOSE_TIMES_FROM_DWS 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_stdaz  TYPE P2001-STDAZ, "   
lt_dayint  TYPE STANDARD TABLE OF PWSDAYINT, "   
lv_beguz_exp  TYPE P2001-BEGUZ, "   
lt_i2001  TYPE STANDARD TABLE OF P2001, "   
lv_enduz_exp  TYPE P2001-ENDUZ, "   
lv_vtken_imp  TYPE P2001-VTKEN, "   
lt_i2002  TYPE STANDARD TABLE OF P2002, "   
lv_daygen  TYPE PWSDAYGEN, "   
lv_vtken_exp  TYPE P2001-VTKEN, "   
lv_infotype  TYPE PSKEY-INFTY, "   2001
lv_stdaz_exp  TYPE P2001-STDAZ, "   
lv_message_occured  TYPE C. "   

  CALL FUNCTION 'HR_PROPOSE_TIMES_FROM_DWS'  "
    EXPORTING
         STDAZ = lv_stdaz
         VTKEN_IMP = lv_vtken_imp
         DAYGEN = lv_daygen
         INFOTYPE = lv_infotype
    IMPORTING
         BEGUZ_EXP = lv_beguz_exp
         ENDUZ_EXP = lv_enduz_exp
         VTKEN_EXP = lv_vtken_exp
         STDAZ_EXP = lv_stdaz_exp
         MESSAGE_OCCURED = lv_message_occured
    TABLES
         DAYINT = lt_dayint
         I2001 = lt_i2001
         I2002 = lt_i2002
. " HR_PROPOSE_TIMES_FROM_DWS




ABAP code using 7.40 inline data declarations to call FM HR_PROPOSE_TIMES_FROM_DWS

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.

"SELECT single STDAZ FROM P2001 INTO @DATA(ld_stdaz).
 
 
"SELECT single BEGUZ FROM P2001 INTO @DATA(ld_beguz_exp).
 
 
"SELECT single ENDUZ FROM P2001 INTO @DATA(ld_enduz_exp).
 
"SELECT single VTKEN FROM P2001 INTO @DATA(ld_vtken_imp).
 
 
 
"SELECT single VTKEN FROM P2001 INTO @DATA(ld_vtken_exp).
 
"SELECT single INFTY FROM PSKEY INTO @DATA(ld_infotype).
DATA(ld_infotype) = 2001.
 
"SELECT single STDAZ FROM P2001 INTO @DATA(ld_stdaz_exp).
 
 


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!