SAP MEREP_RTN_UPDATE Function Module for Prepare Return Messages for Structure ID RTN









MEREP_RTN_UPDATE is a standard merep rtn update SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Prepare Return Messages for Structure ID RTN 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 merep rtn update FM, simply by entering the name MEREP_RTN_UPDATE into the relevant SAP transaction such as SE37 or SE38.

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



Function MEREP_RTN_UPDATE 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 'MEREP_RTN_UPDATE'"Prepare Return Messages for Structure ID RTN
  EXPORTING
   COMMON_RTN =  "SAP Mobile: Bapireturn common (old/new)
   INBOX_RECORD =  "SAP Mobile: Inbox/Outbox Data
   HANDLER_WORKLIST =  "SAP Mobile: Inbox/Outbox Worklist
   UPLOAD_SYNCWL =  "SAP Mobile: Synchronizer Worklist
   RUNNUM =  "SAP Mobile: Run Number
   SCENARIO_CONTROL =  "SAP Mobile: Synchronizer Control Record
   SYNC_KEY =  "SAP Mobile: Synchronization key
*  RETURN =  "Return parameter
*  SYNC_GENERIC =  "Synchronizer Generic Parameters

 IMPORTING
   SENDER_WORKLIST =  "SAP Mobile: Inbox/Outbox Worklist

TABLES
   I_METADATA =  "SAP Mobile: Metadata structure for scenario
*  I_OUTBOX_DATA =  "SAP Mobile: Inbox/Outbox Data
.



IMPORTING Parameters details for MEREP_RTN_UPDATE

COMMON_RTN - SAP Mobile: Bapireturn common (old/new)

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

INBOX_RECORD - SAP Mobile: Inbox/Outbox Data

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

HANDLER_WORKLIST - SAP Mobile: Inbox/Outbox Worklist

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

UPLOAD_SYNCWL - SAP Mobile: Synchronizer Worklist

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

RUNNUM - SAP Mobile: Run Number

Data type: MEREP_601-RUNNUM
Optional: No
Call by Reference: Yes

SCENARIO_CONTROL - SAP Mobile: Synchronizer Control Record

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

SYNC_KEY - SAP Mobile: Synchronization key

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

RETURN - Return parameter

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

SYNC_GENERIC - Synchronizer Generic Parameters

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

EXPORTING Parameters details for MEREP_RTN_UPDATE

SENDER_WORKLIST - SAP Mobile: Inbox/Outbox Worklist

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

TABLES Parameters details for MEREP_RTN_UPDATE

I_METADATA - SAP Mobile: Metadata structure for scenario

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

I_OUTBOX_DATA - SAP Mobile: Inbox/Outbox Data

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

Copy and paste ABAP code example for MEREP_RTN_UPDATE 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_common_rtn  TYPE MEREP_BAPIRETURN, "   
lt_i_metadata  TYPE STANDARD TABLE OF MEREP_SCEN_METADATA, "   
lv_sender_worklist  TYPE MEREP_505, "   
lv_inbox_record  TYPE MEREP_504, "   
lt_i_outbox_data  TYPE STANDARD TABLE OF MEREP_504, "   
lv_handler_worklist  TYPE MEREP_505, "   
lv_upload_syncwl  TYPE MEREP_506, "   
lv_runnum  TYPE MEREP_601-RUNNUM, "   
lv_scenario_control  TYPE MEREP_409, "   
lv_sync_key  TYPE MEREP_SYNC_KEY, "   
lv_return  TYPE BAPIRETURN1, "   
lv_sync_generic  TYPE MEREP_SYNC_GENERIC. "   

  CALL FUNCTION 'MEREP_RTN_UPDATE'  "Prepare Return Messages for Structure ID RTN
    EXPORTING
         COMMON_RTN = lv_common_rtn
         INBOX_RECORD = lv_inbox_record
         HANDLER_WORKLIST = lv_handler_worklist
         UPLOAD_SYNCWL = lv_upload_syncwl
         RUNNUM = lv_runnum
         SCENARIO_CONTROL = lv_scenario_control
         SYNC_KEY = lv_sync_key
         RETURN = lv_return
         SYNC_GENERIC = lv_sync_generic
    IMPORTING
         SENDER_WORKLIST = lv_sender_worklist
    TABLES
         I_METADATA = lt_i_metadata
         I_OUTBOX_DATA = lt_i_outbox_data
. " MEREP_RTN_UPDATE




ABAP code using 7.40 inline data declarations to call FM MEREP_RTN_UPDATE

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.

 
 
 
 
 
 
 
"SELECT single RUNNUM FROM MEREP_601 INTO @DATA(ld_runnum).
 
 
 
 
 


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!