SAP MMPUR_CONF_GET_RULE_BY_NAME Function Module for NOTRANSL: Regelei









MMPUR_CONF_GET_RULE_BY_NAME is a standard mmpur conf get rule by name 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: Regelei 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 mmpur conf get rule by name FM, simply by entering the name MMPUR_CONF_GET_RULE_BY_NAME into the relevant SAP transaction such as SE37 or SE38.

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



Function MMPUR_CONF_GET_RULE_BY_NAME 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 'MMPUR_CONF_GET_RULE_BY_NAME'"NOTRANSL: Regelei
EXPORTING
IM_RULENAME = "

IMPORTING
EX_RULE = "View of MM Rule

EXCEPTIONS
CX_MMPUR_ROOT = 1
.



IMPORTING Parameters details for MMPUR_CONF_GET_RULE_BY_NAME

IM_RULENAME -

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

EXPORTING Parameters details for MMPUR_CONF_GET_RULE_BY_NAME

EX_RULE - View of MM Rule

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

EXCEPTIONS details

CX_MMPUR_ROOT - Exception Purchasing

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for MMPUR_CONF_GET_RULE_BY_NAME 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_ex_rule  TYPE IF_RULE_MM, "   
lv_im_rulename  TYPE STRING, "   
lv_cx_mmpur_root  TYPE STRING. "   

  CALL FUNCTION 'MMPUR_CONF_GET_RULE_BY_NAME'  "NOTRANSL: Regelei
    EXPORTING
         IM_RULENAME = lv_im_rulename
    IMPORTING
         EX_RULE = lv_ex_rule
    EXCEPTIONS
        CX_MMPUR_ROOT = 1
. " MMPUR_CONF_GET_RULE_BY_NAME




ABAP code using 7.40 inline data declarations to call FM MMPUR_CONF_GET_RULE_BY_NAME

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!