SAP INTERVAL_CONVERT Function Module for
INTERVAL_CONVERT is a standard interval convert 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 interval convert FM, simply by entering the name INTERVAL_CONVERT into the relevant SAP transaction such as SE37 or SE38.
Function Group: FMAB
Program Name: SAPLFMAB
Main Program: SAPLFMAB
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function INTERVAL_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 'INTERVAL_CONVERT'".
EXPORTING
INTERVAL_TO_MINMAX = "
CHANGING
INTERVALTYPE = "
MINBDGT = "
MAXBDGT = "
IMPORTING Parameters details for INTERVAL_CONVERT
INTERVAL_TO_MINMAX -
Data type: COptional: No
Call by Reference: Yes
CHANGING Parameters details for INTERVAL_CONVERT
INTERVALTYPE -
Data type: IFMUDRULESCR-INTERVALTYPEOptional: No
Call by Reference: Yes
MINBDGT -
Data type: FMUDRULE-MINBDGTOptional: No
Call by Reference: Yes
MAXBDGT -
Data type: FMUDRULE-MAXBDGTOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for INTERVAL_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_intervaltype | TYPE IFMUDRULESCR-INTERVALTYPE, " | |||
| lv_interval_to_minmax | TYPE C, " | |||
| lv_minbdgt | TYPE FMUDRULE-MINBDGT, " | |||
| lv_maxbdgt | TYPE FMUDRULE-MAXBDGT. " |
|   CALL FUNCTION 'INTERVAL_CONVERT' " |
| EXPORTING | ||
| INTERVAL_TO_MINMAX | = lv_interval_to_minmax | |
| CHANGING | ||
| INTERVALTYPE | = lv_intervaltype | |
| MINBDGT | = lv_minbdgt | |
| MAXBDGT | = lv_maxbdgt | |
| . " INTERVAL_CONVERT | ||
ABAP code using 7.40 inline data declarations to call FM INTERVAL_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.| "SELECT single INTERVALTYPE FROM IFMUDRULESCR INTO @DATA(ld_intervaltype). | ||||
| "SELECT single MINBDGT FROM FMUDRULE INTO @DATA(ld_minbdgt). | ||||
| "SELECT single MAXBDGT FROM FMUDRULE INTO @DATA(ld_maxbdgt). | ||||
Search for further information about these or an SAP related objects