SAP BORCFG_OPT_FLAGS_GET Function Module for NOTRANSL: Übergabe der Optionsflags an die Optionsdynpros
BORCFG_OPT_FLAGS_GET is a standard borcfg opt flags get SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Übergabe der Optionsflags an die Optionsdynpros 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 borcfg opt flags get FM, simply by entering the name BORCFG_OPT_FLAGS_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: BORCFG
Program Name: SAPLBORCFG
Main Program: SAPLBORCFG
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function BORCFG_OPT_FLAGS_GET 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 'BORCFG_OPT_FLAGS_GET'"NOTRANSL: Übergabe der Optionsflags an die Optionsdynpros.
EXPORTING
* I_FLAG_SHPM_REG = 'I' "
* I_FLAG_SHPM_GR = 'I' "
* I_FLAG_RELEV_SHPM = 'I' "
* I_FLAG_DELV_REG = 'I' "
* I_FLAG_DELV_GR = 'I' "
* I_FLAG_DELV_SUBIT_AUTO = 'I' "
* I_FLAG_DOC_OBJ = 'I' "
* I_FLAG_MESSAGE_LEAVE_DOC = 'I' "
IMPORTING Parameters details for BORCFG_OPT_FLAGS_GET
I_FLAG_SHPM_REG -
Data type: CDefault: 'I'
Optional: Yes
Call by Reference: Yes
I_FLAG_SHPM_GR -
Data type: CDefault: 'I'
Optional: Yes
Call by Reference: Yes
I_FLAG_RELEV_SHPM -
Data type: CDefault: 'I'
Optional: Yes
Call by Reference: Yes
I_FLAG_DELV_REG -
Data type: CDefault: 'I'
Optional: Yes
Call by Reference: Yes
I_FLAG_DELV_GR -
Data type: CDefault: 'I'
Optional: Yes
Call by Reference: Yes
I_FLAG_DELV_SUBIT_AUTO -
Data type: CDefault: 'I'
Optional: Yes
Call by Reference: Yes
I_FLAG_DOC_OBJ -
Data type: CDefault: 'I'
Optional: Yes
Call by Reference: Yes
I_FLAG_MESSAGE_LEAVE_DOC -
Data type: CDefault: 'I'
Optional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for BORCFG_OPT_FLAGS_GET 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_flag_shpm_reg | TYPE C, " 'I' | |||
| lv_i_flag_shpm_gr | TYPE C, " 'I' | |||
| lv_i_flag_relev_shpm | TYPE C, " 'I' | |||
| lv_i_flag_delv_reg | TYPE C, " 'I' | |||
| lv_i_flag_delv_gr | TYPE C, " 'I' | |||
| lv_i_flag_delv_subit_auto | TYPE C, " 'I' | |||
| lv_i_flag_doc_obj | TYPE C, " 'I' | |||
| lv_i_flag_message_leave_doc | TYPE C. " 'I' |
|   CALL FUNCTION 'BORCFG_OPT_FLAGS_GET' "NOTRANSL: Übergabe der Optionsflags an die Optionsdynpros |
| EXPORTING | ||
| I_FLAG_SHPM_REG | = lv_i_flag_shpm_reg | |
| I_FLAG_SHPM_GR | = lv_i_flag_shpm_gr | |
| I_FLAG_RELEV_SHPM | = lv_i_flag_relev_shpm | |
| I_FLAG_DELV_REG | = lv_i_flag_delv_reg | |
| I_FLAG_DELV_GR | = lv_i_flag_delv_gr | |
| I_FLAG_DELV_SUBIT_AUTO | = lv_i_flag_delv_subit_auto | |
| I_FLAG_DOC_OBJ | = lv_i_flag_doc_obj | |
| I_FLAG_MESSAGE_LEAVE_DOC | = lv_i_flag_message_leave_doc | |
| . " BORCFG_OPT_FLAGS_GET | ||
ABAP code using 7.40 inline data declarations to call FM BORCFG_OPT_FLAGS_GET
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_i_flag_shpm_reg) | = 'I'. | |||
| DATA(ld_i_flag_shpm_gr) | = 'I'. | |||
| DATA(ld_i_flag_relev_shpm) | = 'I'. | |||
| DATA(ld_i_flag_delv_reg) | = 'I'. | |||
| DATA(ld_i_flag_delv_gr) | = 'I'. | |||
| DATA(ld_i_flag_delv_subit_auto) | = 'I'. | |||
| DATA(ld_i_flag_doc_obj) | = 'I'. | |||
| DATA(ld_i_flag_message_leave_doc) | = 'I'. | |||
Search for further information about these or an SAP related objects