SAP RSEC_DATE_CONVERT Function Module for Enhanced Date Conversion Exit









RSEC_DATE_CONVERT is a standard rsec date convert SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Enhanced Date Conversion Exit 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 rsec date convert FM, simply by entering the name RSEC_DATE_CONVERT into the relevant SAP transaction such as SE37 or SE38.

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



Function RSEC_DATE_CONVERT 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 'RSEC_DATE_CONVERT'"Enhanced Date Conversion Exit
EXPORTING
I_CHAVL_EXT = "

IMPORTING
E_CHAVL_INT = "

EXCEPTIONS
NO_INPUT_GIVEN = 1 INPUT_NOT_NUMERICAL = 2 CONVERSION_NOT_SUPPORTED = 3 DATE_NOT_CORRECT = 4 TIME_NOT_CORRECT = 5 INVALID_FORMAT = 6
.



IMPORTING Parameters details for RSEC_DATE_CONVERT

I_CHAVL_EXT -

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

EXPORTING Parameters details for RSEC_DATE_CONVERT

E_CHAVL_INT -

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

EXCEPTIONS details

NO_INPUT_GIVEN -

Data type:
Optional: No
Call by Reference: Yes

INPUT_NOT_NUMERICAL -

Data type:
Optional: No
Call by Reference: Yes

CONVERSION_NOT_SUPPORTED -

Data type:
Optional: No
Call by Reference: Yes

DATE_NOT_CORRECT -

Data type:
Optional: No
Call by Reference: Yes

TIME_NOT_CORRECT -

Data type:
Optional: No
Call by Reference: Yes

INVALID_FORMAT -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for RSEC_DATE_CONVERT 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_e_chavl_int  TYPE C, "   
lv_i_chavl_ext  TYPE C, "   
lv_no_input_given  TYPE C, "   
lv_input_not_numerical  TYPE C, "   
lv_conversion_not_supported  TYPE C, "   
lv_date_not_correct  TYPE C, "   
lv_time_not_correct  TYPE C, "   
lv_invalid_format  TYPE C. "   

  CALL FUNCTION 'RSEC_DATE_CONVERT'  "Enhanced Date Conversion Exit
    EXPORTING
         I_CHAVL_EXT = lv_i_chavl_ext
    IMPORTING
         E_CHAVL_INT = lv_e_chavl_int
    EXCEPTIONS
        NO_INPUT_GIVEN = 1
        INPUT_NOT_NUMERICAL = 2
        CONVERSION_NOT_SUPPORTED = 3
        DATE_NOT_CORRECT = 4
        TIME_NOT_CORRECT = 5
        INVALID_FORMAT = 6
. " RSEC_DATE_CONVERT




ABAP code using 7.40 inline data declarations to call FM RSEC_DATE_CONVERT

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.

 
 
 
 
 
 
 
 


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!