SAP BRF_MAINTAIN_RULES Function Module for

Search SAP Function Modules

BRF_MAINTAIN_RULES is a standard brf maintain rules 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 rules FM, simply by entering the name BRF_MAINTAIN_RULES 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_RULES 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_RULES'"
  EXPORTING
*  IV_EDIT_MODE = '3' "BRF: Processing Type (Display, Change, Create ...)
*  IV_CALLED_FROM_WB = ' ' "
*  IV_APPLCLASS =  "BRF: Application Class
*  IV_EVENT =  "BRF: Event
*  IV_IMPORT_STATUS = 'A' "BRF: Import Status
*  IV_VERSION = 0 "BRF: Version
*  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

TABLES
*  ET_MESSAGE =  "BRF: Message

EXCEPTIONS
   MESSAGE_OCCURED = 1 

.

IMPORTING Parameters details for BRF_MAINTAIN_RULES

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_CALLED_FROM_WB -

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

IV_APPLCLASS - BRF: Application Class

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

IV_EVENT - BRF: Event

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

IV_IMPORT_STATUS - BRF: Import Status

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

IV_VERSION - BRF: Version

Data type: BRF_VERSION
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: SPACE
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for BRF_MAINTAIN_RULES

ET_MESSAGE - BRF: Message

Data type: BRF_MESSAGE
Optional: Yes
Call by Reference: Yes

EXCEPTIONS details

MESSAGE_OCCURED - Message Occurred in Processing

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for BRF_MAINTAIN_RULES 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.

ABAP code using 7.40 inline data declarations to call FM BRF_MAINTAIN_RULES

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