SAP TZ_TIMEFIELD_INPUT Function Module for









TZ_TIMEFIELD_INPUT is a standard tz timefield input 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 tz timefield input FM, simply by entering the name TZ_TIMEFIELD_INPUT into the relevant SAP transaction such as SE37 or SE38.

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



Function TZ_TIMEFIELD_INPUT 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 'TZ_TIMEFIELD_INPUT'"
EXPORTING
* IF_IO_FROM = "
* IF_IO_TO = "
* IS_FORMAT = "
* IF_USER_DATE = 'X' "
* IF_USER_TIME = 'X' "
* IF_USER_TIMEZONE = 'X' "
* IF_DEFAULT_DATE = "
* IF_DEFAULT_TIME = "
* IF_DEFAULT_TIMEZONE = "Default Time Zone

IMPORTING
ET_FROM_MESSAGES = "
EF_FROM_TIME = "From Time Stamp
EF_FROM_TIMEZONE = "
EF_TO_TIME = "To Time Stamp
EF_TO_TIMEZONE = "
ET_TO_MESSAGES = "
EF_FROM_ERROR = "
EF_TO_ERROR = "

EXCEPTIONS
ERROR_OCCURRED = 1
.



IMPORTING Parameters details for TZ_TIMEFIELD_INPUT

IF_IO_FROM -

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

IF_IO_TO -

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

IS_FORMAT -

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

IF_USER_DATE -

Data type: XFLAG
Default: 'X'
Optional: No
Call by Reference: Yes

IF_USER_TIME -

Data type: XFLAG
Default: 'X'
Optional: No
Call by Reference: Yes

IF_USER_TIMEZONE -

Data type: XFLAG
Default: 'X'
Optional: No
Call by Reference: Yes

IF_DEFAULT_DATE -

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

IF_DEFAULT_TIME -

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

IF_DEFAULT_TIMEZONE - Default Time Zone

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

EXPORTING Parameters details for TZ_TIMEFIELD_INPUT

ET_FROM_MESSAGES -

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

EF_FROM_TIME - From Time Stamp

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

EF_FROM_TIMEZONE -

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

EF_TO_TIME - To Time Stamp

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

EF_TO_TIMEZONE -

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

ET_TO_MESSAGES -

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

EF_FROM_ERROR -

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

EF_TO_ERROR -

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

EXCEPTIONS details

ERROR_OCCURRED -

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

Copy and paste ABAP code example for TZ_TIMEFIELD_INPUT 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_if_io_from  TYPE TZTF_IO_FIELD, "   
lv_error_occurred  TYPE TZTF_IO_FIELD, "   
lv_et_from_messages  TYPE TZT_MESSAGE, "   
lv_if_io_to  TYPE TZTF_IO_FIELD, "   
lv_ef_from_time  TYPE TIMESTAMP, "   
lv_is_format  TYPE TZTF_FORMAT, "   
lv_ef_from_timezone  TYPE TIMEZONE, "   
lv_ef_to_time  TYPE TIMESTAMP, "   
lv_if_user_date  TYPE XFLAG, "   'X'
lv_if_user_time  TYPE XFLAG, "   'X'
lv_ef_to_timezone  TYPE TIMEZONE, "   
lv_et_to_messages  TYPE TZT_MESSAGE, "   
lv_if_user_timezone  TYPE XFLAG, "   'X'
lv_ef_from_error  TYPE XFLAG, "   
lv_if_default_date  TYPE D, "   
lv_ef_to_error  TYPE XFLAG, "   
lv_if_default_time  TYPE T, "   
lv_if_default_timezone  TYPE TIMEZONE. "   

  CALL FUNCTION 'TZ_TIMEFIELD_INPUT'  "
    EXPORTING
         IF_IO_FROM = lv_if_io_from
         IF_IO_TO = lv_if_io_to
         IS_FORMAT = lv_is_format
         IF_USER_DATE = lv_if_user_date
         IF_USER_TIME = lv_if_user_time
         IF_USER_TIMEZONE = lv_if_user_timezone
         IF_DEFAULT_DATE = lv_if_default_date
         IF_DEFAULT_TIME = lv_if_default_time
         IF_DEFAULT_TIMEZONE = lv_if_default_timezone
    IMPORTING
         ET_FROM_MESSAGES = lv_et_from_messages
         EF_FROM_TIME = lv_ef_from_time
         EF_FROM_TIMEZONE = lv_ef_from_timezone
         EF_TO_TIME = lv_ef_to_time
         EF_TO_TIMEZONE = lv_ef_to_timezone
         ET_TO_MESSAGES = lv_et_to_messages
         EF_FROM_ERROR = lv_ef_from_error
         EF_TO_ERROR = lv_ef_to_error
    EXCEPTIONS
        ERROR_OCCURRED = 1
. " TZ_TIMEFIELD_INPUT




ABAP code using 7.40 inline data declarations to call FM TZ_TIMEFIELD_INPUT

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_if_user_date) = 'X'.
 
DATA(ld_if_user_time) = 'X'.
 
 
 
DATA(ld_if_user_timezone) = 'X'.
 
 
 
 
 
 


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!