SAP BRF_MAINTAIN_GENERIC Function Module for









BRF_MAINTAIN_GENERIC is a standard brf maintain generic 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 brf maintain generic FM, simply by entering the name BRF_MAINTAIN_GENERIC into the relevant SAP transaction such as SE37 or SE38.

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



Function BRF_MAINTAIN_GENERIC 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 'BRF_MAINTAIN_GENERIC'"
  EXPORTING
   IO_MAINTENANCE =  "BRF: Maintenance
   IS_HEADER =  "
*  IV_EDIT_MODE = 3 "BRF: Processing Type (Display, Change, Create ...)
*  IV_LANGU = SY-LANGU "SAP R/3 System, Current Language
*  IV_SKIP_ENTRY_SCREEN = ' ' "Skip Initial Screen if Possible
*  IV_RETURN_IF_ERROR = ' ' "Change/Display: Cancel Processing if Nothing Found
*  IV_WB_MODE = '~' "Called in Workbench Mode
*  IV_CALLED_FROM_WB =  "Call from Workbench

TABLES
*  ET_MESSAGE =  "BRF: Message
.



IMPORTING Parameters details for BRF_MAINTAIN_GENERIC

IO_MAINTENANCE - BRF: Maintenance

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

IS_HEADER -

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

IV_EDIT_MODE - BRF: Processing Type (Display, Change, Create ...)

Data type: BRF_EDIT_MODE
Default: 3
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_LANGU - SAP R/3 System, Current Language

Data type: SYLANGU
Default: SY-LANGU
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_SKIP_ENTRY_SCREEN - Skip Initial Screen if Possible

Data type: BRF_BOOLE_D
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_RETURN_IF_ERROR - Change/Display: Cancel Processing if Nothing Found

Data type: BRF_BOOLE_D
Default: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_WB_MODE - Called in Workbench Mode

Data type: BRF_BOOLE_D
Default: '~'
Optional: Yes
Call by Reference: No ( called with pass by value option)

IV_CALLED_FROM_WB - Call from Workbench

Data type: BRF_BOOLE_D
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for BRF_MAINTAIN_GENERIC

ET_MESSAGE - BRF: Message

Data type: BRF_MESSAGE
Optional: Yes
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for BRF_MAINTAIN_GENERIC 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:
lt_et_message  TYPE STANDARD TABLE OF BRF_MESSAGE, "   
lv_io_maintenance  TYPE IF_MAINTENANCE_BRF, "   
lv_is_header  TYPE ANY, "   
lv_iv_edit_mode  TYPE BRF_EDIT_MODE, "   3
lv_iv_langu  TYPE SYLANGU, "   SY-LANGU
lv_iv_skip_entry_screen  TYPE BRF_BOOLE_D, "   SPACE
lv_iv_return_if_error  TYPE BRF_BOOLE_D, "   SPACE
lv_iv_wb_mode  TYPE BRF_BOOLE_D, "   '~'
lv_iv_called_from_wb  TYPE BRF_BOOLE_D. "   

  CALL FUNCTION 'BRF_MAINTAIN_GENERIC'  "
    EXPORTING
         IO_MAINTENANCE = lv_io_maintenance
         IS_HEADER = lv_is_header
         IV_EDIT_MODE = lv_iv_edit_mode
         IV_LANGU = lv_iv_langu
         IV_SKIP_ENTRY_SCREEN = lv_iv_skip_entry_screen
         IV_RETURN_IF_ERROR = lv_iv_return_if_error
         IV_WB_MODE = lv_iv_wb_mode
         IV_CALLED_FROM_WB = lv_iv_called_from_wb
    TABLES
         ET_MESSAGE = lt_et_message
. " BRF_MAINTAIN_GENERIC




ABAP code using 7.40 inline data declarations to call FM BRF_MAINTAIN_GENERIC

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_iv_edit_mode) = 3.
 
DATA(ld_iv_langu) = SY-LANGU.
 
DATA(ld_iv_skip_entry_screen) = ' '.
 
DATA(ld_iv_return_if_error) = ' '.
 
DATA(ld_iv_wb_mode) = '~'.
 
 


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!