SAP BORCFG_FILTER_SAVE Function Module for NOTRANSL: String vom EXIDV-Dynpro









BORCFG_FILTER_SAVE is a standard borcfg filter save 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: String vom EXIDV-Dynpro 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 filter save FM, simply by entering the name BORCFG_FILTER_SAVE 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_FILTER_SAVE 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_FILTER_SAVE'"NOTRANSL: String vom EXIDV-Dynpro
EXPORTING
IO_FILTER = "DE-EN-LANG-SWITCH-NO-TRANSLATION
IO_DIALOG_CFG = "Dialog Configuration Goods Receipt Automotive
.



IMPORTING Parameters details for BORCFG_FILTER_SAVE

IO_FILTER - DE-EN-LANG-SWITCH-NO-TRANSLATION

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

IO_DIALOG_CFG - Dialog Configuration Goods Receipt Automotive

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

Copy and paste ABAP code example for BORCFG_FILTER_SAVE 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_io_filter  TYPE CL_BORGR_DIALOG_FILTER, "   
lv_io_dialog_cfg  TYPE CL_BORGR_DIALOG_CFG. "   

  CALL FUNCTION 'BORCFG_FILTER_SAVE'  "NOTRANSL: String vom EXIDV-Dynpro
    EXPORTING
         IO_FILTER = lv_io_filter
         IO_DIALOG_CFG = lv_io_dialog_cfg
. " BORCFG_FILTER_SAVE




ABAP code using 7.40 inline data declarations to call FM BORCFG_FILTER_SAVE

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!