SAP CONVERT_TIME_INPUT Function Module for Convert a time from external to internal format









CONVERT_TIME_INPUT is a standard convert time input SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Convert a time from external to internal format 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 convert time input FM, simply by entering the name CONVERT_TIME_INPUT into the relevant SAP transaction such as SE37 or SE38.

Function Group: SCON
Program Name: SAPLSCON
Main Program:
Appliation area: *
Release date: 07-Aug-1995
Mode(Normal, Remote etc): Normal Function Module
Update:



Function CONVERT_TIME_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 'CONVERT_TIME_INPUT'"Convert a time from external to internal format
EXPORTING
INPUT = "Formatted time entry
* PLAUSIBILITY_CHECK = 'X' "Make plausibility check

IMPORTING
OUTPUT = "Output time as database field

EXCEPTIONS
PLAUSIBILITY_CHECK_FAILED = 1 WRONG_FORMAT_IN_INPUT = 2
.



IMPORTING Parameters details for CONVERT_TIME_INPUT

INPUT - Formatted time entry

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

PLAUSIBILITY_CHECK - Make plausibility check

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

EXPORTING Parameters details for CONVERT_TIME_INPUT

OUTPUT - Output time as database field

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

EXCEPTIONS details

PLAUSIBILITY_CHECK_FAILED - Plausibility check error

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

WRONG_FORMAT_IN_INPUT - Time in INPUT has incorrect format

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

Copy and paste ABAP code example for CONVERT_TIME_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_input  TYPE STRING, "   
lv_output  TYPE SY-UZEIT, "   
lv_plausibility_check_failed  TYPE SY, "   
lv_plausibility_check  TYPE SY, "   'X'
lv_wrong_format_in_input  TYPE SY. "   

  CALL FUNCTION 'CONVERT_TIME_INPUT'  "Convert a time from external to internal format
    EXPORTING
         INPUT = lv_input
         PLAUSIBILITY_CHECK = lv_plausibility_check
    IMPORTING
         OUTPUT = lv_output
    EXCEPTIONS
        PLAUSIBILITY_CHECK_FAILED = 1
        WRONG_FORMAT_IN_INPUT = 2
. " CONVERT_TIME_INPUT




ABAP code using 7.40 inline data declarations to call FM CONVERT_TIME_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.

 
"SELECT single UZEIT FROM SY INTO @DATA(ld_output).
 
 
DATA(ld_plausibility_check) = '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!