SAP RULE_MONIDEF_WRITE Function Module for









RULE_MONIDEF_WRITE is a standard rule monidef write 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 rule monidef write FM, simply by entering the name RULE_MONIDEF_WRITE into the relevant SAP transaction such as SE37 or SE38.

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



Function RULE_MONIDEF_WRITE 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 'RULE_MONIDEF_WRITE'"
EXPORTING
MONITOR_GUID = "

CHANGING
MONIDEF = "Monitor definition

EXCEPTIONS
MONITOR_SPECIFICATION_MISSING = 1 MONIDEF_MISSING = 2 MONIDEF_CONVERT_ERROR = 3 CANT_WRITE_MONIDEF_TO_DB = 4 MONITOR_DOES_NOT_EXIST = 5 MONITOR_CONVERT_ERROR = 6
.



IMPORTING Parameters details for RULE_MONIDEF_WRITE

MONITOR_GUID -

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

CHANGING Parameters details for RULE_MONIDEF_WRITE

MONIDEF - Monitor definition

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

EXCEPTIONS details

MONITOR_SPECIFICATION_MISSING -

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

MONIDEF_MISSING -

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

MONIDEF_CONVERT_ERROR -

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

CANT_WRITE_MONIDEF_TO_DB -

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

MONITOR_DOES_NOT_EXIST -

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

MONITOR_CONVERT_ERROR -

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

Copy and paste ABAP code example for RULE_MONIDEF_WRITE 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_monidef  TYPE ALMDEFTBL, "   
lv_monitor_guid  TYPE SYSUUID_C, "   
lv_monitor_specification_missing  TYPE SYSUUID_C, "   
lv_monidef_missing  TYPE SYSUUID_C, "   
lv_monidef_convert_error  TYPE SYSUUID_C, "   
lv_cant_write_monidef_to_db  TYPE SYSUUID_C, "   
lv_monitor_does_not_exist  TYPE SYSUUID_C, "   
lv_monitor_convert_error  TYPE SYSUUID_C. "   

  CALL FUNCTION 'RULE_MONIDEF_WRITE'  "
    EXPORTING
         MONITOR_GUID = lv_monitor_guid
    CHANGING
         MONIDEF = lv_monidef
    EXCEPTIONS
        MONITOR_SPECIFICATION_MISSING = 1
        MONIDEF_MISSING = 2
        MONIDEF_CONVERT_ERROR = 3
        CANT_WRITE_MONIDEF_TO_DB = 4
        MONITOR_DOES_NOT_EXIST = 5
        MONITOR_CONVERT_ERROR = 6
. " RULE_MONIDEF_WRITE




ABAP code using 7.40 inline data declarations to call FM RULE_MONIDEF_WRITE

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!