SAP HR_TMW_CALENDAR_SETTINGS Function Module for









HR_TMW_CALENDAR_SETTINGS is a standard hr tmw calendar settings 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 tmw calendar settings FM, simply by entering the name HR_TMW_CALENDAR_SETTINGS into the relevant SAP transaction such as SE37 or SE38.

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



Function HR_TMW_CALENDAR_SETTINGS 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_TMW_CALENDAR_SETTINGS'"
EXPORTING
* START_COLUMN = '3' "
* START_ROW = '1' "
VIEW = "

IMPORTING
FCODE = "

CHANGING
* VIEW_SETTINGS = "
* USER_SETTINGS = "
.



IMPORTING Parameters details for HR_TMW_CALENDAR_SETTINGS

START_COLUMN -

Data type: SYSCOLS
Default: '3'
Optional: Yes
Call by Reference: No ( called with pass by value option)

START_ROW -

Data type: SYSROWS
Default: '1'
Optional: Yes
Call by Reference: No ( called with pass by value option)

VIEW -

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

EXPORTING Parameters details for HR_TMW_CALENDAR_SETTINGS

FCODE -

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

CHANGING Parameters details for HR_TMW_CALENDAR_SETTINGS

VIEW_SETTINGS -

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

USER_SETTINGS -

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

Copy and paste ABAP code example for HR_TMW_CALENDAR_SETTINGS 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_fcode  TYPE UI_FUNC, "   
lv_start_column  TYPE SYSCOLS, "   '3'
lv_view_settings  TYPE PTM_S_VIEW_SETTINGS, "   
lv_start_row  TYPE SYSROWS, "   '1'
lv_user_settings  TYPE PTM_T_USER_SETTINGS, "   
lv_view  TYPE INT1. "   

  CALL FUNCTION 'HR_TMW_CALENDAR_SETTINGS'  "
    EXPORTING
         START_COLUMN = lv_start_column
         START_ROW = lv_start_row
         VIEW = lv_view
    IMPORTING
         FCODE = lv_fcode
    CHANGING
         VIEW_SETTINGS = lv_view_settings
         USER_SETTINGS = lv_user_settings
. " HR_TMW_CALENDAR_SETTINGS




ABAP code using 7.40 inline data declarations to call FM HR_TMW_CALENDAR_SETTINGS

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_start_column) = '3'.
 
 
DATA(ld_start_row) = '1'.
 
 
 


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!