SAP TIMEZONE2 Function Module for Timezone Miniap
TIMEZONE2 is a standard timezone2 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Timezone Miniap processing and below is the pattern details for this FM, 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 timezone2 FM, simply by entering the name TIMEZONE2 into the relevant SAP transaction such as SE37 or SE38.
Function Group: HR_US_MINIAPP
Program Name: SAPLHR_US_MINIAPP
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function TIMEZONE2 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 'TIMEZONE2'"Timezone Miniap.
EXPORTING
* CUR_CITY = 'WALLDORF' "
* CUR_TIME = SY-UZEIT "
IMPORTING
OUT_TIME = "
IMPORTING Parameters details for TIMEZONE2
CUR_CITY -
Data type: PA0006-ORT01Default: 'WALLDORF'
Optional: No
Call by Reference: No ( called with pass by value option)
CUR_TIME -
Data type: SY-UNAMEDefault: SY-UZEIT
Optional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for TIMEZONE2
OUT_TIME -
Data type: SY-UNAMEOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for TIMEZONE2 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_cur_city | TYPE PA0006-ORT01, " 'WALLDORF' | |||
| lv_out_time | TYPE SY-UNAME, " | |||
| lv_cur_time | TYPE SY-UNAME. " SY-UZEIT |
|   CALL FUNCTION 'TIMEZONE2' "Timezone Miniap |
| EXPORTING | ||
| CUR_CITY | = lv_cur_city | |
| CUR_TIME | = lv_cur_time | |
| IMPORTING | ||
| OUT_TIME | = lv_out_time | |
| . " TIMEZONE2 | ||
ABAP code using 7.40 inline data declarations to call FM TIMEZONE2
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 ORT01 FROM PA0006 INTO @DATA(ld_cur_city). | ||||
| DATA(ld_cur_city) | = 'WALLDORF'. | |||
| "SELECT single UNAME FROM SY INTO @DATA(ld_out_time). | ||||
| "SELECT single UNAME FROM SY INTO @DATA(ld_cur_time). | ||||
| DATA(ld_cur_time) | = SY-UZEIT. | |||
Search for further information about these or an SAP related objects