SAP BKK_CLOSCTRL_LOOP_GET_LIMITS Function Module for Get Interval Limits
BKK_CLOSCTRL_LOOP_GET_LIMITS is a standard bkk closctrl loop get limits SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Get Interval Limits 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 bkk closctrl loop get limits FM, simply by entering the name BKK_CLOSCTRL_LOOP_GET_LIMITS into the relevant SAP transaction such as SE37 or SE38.
Function Group: FBMJ
Program Name: SAPLFBMJ
Main Program: SAPLFBMJ
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BKK_CLOSCTRL_LOOP_GET_LIMITS 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 'BKK_CLOSCTRL_LOOP_GET_LIMITS'"Get Interval Limits.
EXPORTING
I_PROGN = "
I_PROGDATE = "
I_PROGNO = "
I_APPLCATG = "
I_LOOPCNT1 = "
I_CURROBJNOMAX = "
I_XEMPTY_OCCURED = "
IMPORTING
E_OBJNOMIN = "
E_OBJNOMAX = "
E_XENDOFSEL = "
EXCEPTIONS
MISSING_FUNCTION = 1
IMPORTING Parameters details for BKK_CLOSCTRL_LOOP_GET_LIMITS
I_PROGN -
Data type: BKKD_PROGNOptional: No
Call by Reference: No ( called with pass by value option)
I_PROGDATE -
Data type: BKKD_PROGDATEOptional: No
Call by Reference: No ( called with pass by value option)
I_PROGNO -
Data type: BKKD_PROGNOOptional: No
Call by Reference: No ( called with pass by value option)
I_APPLCATG -
Data type: BKKD_APPLCATGOptional: No
Call by Reference: No ( called with pass by value option)
I_LOOPCNT1 -
Data type: BKKMDISPINTERV-LOOPCNT1Optional: No
Call by Reference: No ( called with pass by value option)
I_CURROBJNOMAX -
Data type: BKKD_OBJNOOptional: No
Call by Reference: No ( called with pass by value option)
I_XEMPTY_OCCURED -
Data type: BOOLE-BOOLEOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for BKK_CLOSCTRL_LOOP_GET_LIMITS
E_OBJNOMIN -
Data type: BKKD_OBJNOOptional: No
Call by Reference: No ( called with pass by value option)
E_OBJNOMAX -
Data type: BKKD_OBJNOOptional: No
Call by Reference: No ( called with pass by value option)
E_XENDOFSEL -
Data type: BOOLE-BOOLEOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
MISSING_FUNCTION -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for BKK_CLOSCTRL_LOOP_GET_LIMITS 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_i_progn | TYPE BKKD_PROGN, " | |||
| lv_e_objnomin | TYPE BKKD_OBJNO, " | |||
| lv_missing_function | TYPE BKKD_OBJNO, " | |||
| lv_e_objnomax | TYPE BKKD_OBJNO, " | |||
| lv_i_progdate | TYPE BKKD_PROGDATE, " | |||
| lv_i_progno | TYPE BKKD_PROGNO, " | |||
| lv_e_xendofsel | TYPE BOOLE-BOOLE, " | |||
| lv_i_applcatg | TYPE BKKD_APPLCATG, " | |||
| lv_i_loopcnt1 | TYPE BKKMDISPINTERV-LOOPCNT1, " | |||
| lv_i_currobjnomax | TYPE BKKD_OBJNO, " | |||
| lv_i_xempty_occured | TYPE BOOLE-BOOLE. " |
|   CALL FUNCTION 'BKK_CLOSCTRL_LOOP_GET_LIMITS' "Get Interval Limits |
| EXPORTING | ||
| I_PROGN | = lv_i_progn | |
| I_PROGDATE | = lv_i_progdate | |
| I_PROGNO | = lv_i_progno | |
| I_APPLCATG | = lv_i_applcatg | |
| I_LOOPCNT1 | = lv_i_loopcnt1 | |
| I_CURROBJNOMAX | = lv_i_currobjnomax | |
| I_XEMPTY_OCCURED | = lv_i_xempty_occured | |
| IMPORTING | ||
| E_OBJNOMIN | = lv_e_objnomin | |
| E_OBJNOMAX | = lv_e_objnomax | |
| E_XENDOFSEL | = lv_e_xendofsel | |
| EXCEPTIONS | ||
| MISSING_FUNCTION = 1 | ||
| . " BKK_CLOSCTRL_LOOP_GET_LIMITS | ||
ABAP code using 7.40 inline data declarations to call FM BKK_CLOSCTRL_LOOP_GET_LIMITS
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 BOOLE FROM BOOLE INTO @DATA(ld_e_xendofsel). | ||||
| "SELECT single LOOPCNT1 FROM BKKMDISPINTERV INTO @DATA(ld_i_loopcnt1). | ||||
| "SELECT single BOOLE FROM BOOLE INTO @DATA(ld_i_xempty_occured). | ||||
Search for further information about these or an SAP related objects