SAP RV_MESSAGES_MAINTENANCE_MANY Function Module for NOTRANSL: Bearbeiten von Nachrichten aus Sammeltransaktionen









RV_MESSAGES_MAINTENANCE_MANY is a standard rv messages maintenance many 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: Bearbeiten von Nachrichten aus Sammeltransaktionen 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 rv messages maintenance many FM, simply by entering the name RV_MESSAGES_MAINTENANCE_MANY into the relevant SAP transaction such as SE37 or SE38.

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



Function RV_MESSAGES_MAINTENANCE_MANY 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 'RV_MESSAGES_MAINTENANCE_MANY'"NOTRANSL: Bearbeiten von Nachrichten aus Sammeltransaktionen
  EXPORTING
*  MIN_BILD = 'M' "Screen control
   MIN_CUA_TEXT =  "
   MIN_T185 =  "
   MIN_T185F =  "
   MIN_T185V =  "

 IMPORTING
   MEX_FCODE =  "
   MEX_T185F =  "
   MEX_T185V =  "

TABLES
   MTB_PART =  "
   MTB_XNAST =  "
   MTB_YNAST =  "
.




Customer Function user exits

Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.
EXIT_SAPLV61B_001 WFMC: Find Fax Number
EXIT_SAPLV61B_002 WFMC: Set Print Parameters

IMPORTING Parameters details for RV_MESSAGES_MAINTENANCE_MANY

MIN_BILD - Screen control

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

MIN_CUA_TEXT -

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

MIN_T185 -

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

MIN_T185F -

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

MIN_T185V -

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

EXPORTING Parameters details for RV_MESSAGES_MAINTENANCE_MANY

MEX_FCODE -

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

MEX_T185F -

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

MEX_T185V -

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

TABLES Parameters details for RV_MESSAGES_MAINTENANCE_MANY

MTB_PART -

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

MTB_XNAST -

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

MTB_YNAST -

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

Copy and paste ABAP code example for RV_MESSAGES_MAINTENANCE_MANY 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_min_bild  TYPE STRING, "   'M'
lt_mtb_part  TYPE STANDARD TABLE OF MSGPA, "   
lv_mex_fcode  TYPE MSGPA, "   
lv_mex_t185f  TYPE T185F, "   
lt_mtb_xnast  TYPE STANDARD TABLE OF VNAST, "   
lv_min_cua_text  TYPE VNAST, "   
lv_min_t185  TYPE VNAST, "   
lv_mex_t185v  TYPE T185V, "   
lt_mtb_ynast  TYPE STANDARD TABLE OF NAST, "   
lv_min_t185f  TYPE T185F, "   
lv_min_t185v  TYPE T185V. "   

  CALL FUNCTION 'RV_MESSAGES_MAINTENANCE_MANY'  "NOTRANSL: Bearbeiten von Nachrichten aus Sammeltransaktionen
    EXPORTING
         MIN_BILD = lv_min_bild
         MIN_CUA_TEXT = lv_min_cua_text
         MIN_T185 = lv_min_t185
         MIN_T185F = lv_min_t185f
         MIN_T185V = lv_min_t185v
    IMPORTING
         MEX_FCODE = lv_mex_fcode
         MEX_T185F = lv_mex_t185f
         MEX_T185V = lv_mex_t185v
    TABLES
         MTB_PART = lt_mtb_part
         MTB_XNAST = lt_mtb_xnast
         MTB_YNAST = lt_mtb_ynast
. " RV_MESSAGES_MAINTENANCE_MANY




ABAP code using 7.40 inline data declarations to call FM RV_MESSAGES_MAINTENANCE_MANY

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_min_bild) = 'M'.
 
 
 
 
 
 
 
 
 
 
 


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!