SAP MEREP_RDB_T01_UPDATE_1 Function Module for SAP Mobile: Update /SAPNEA/MBL207









MEREP_RDB_T01_UPDATE_1 is a standard merep rdb t01 update 1 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for SAP Mobile: Update /SAPNEA/MBL207 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 rdb t01 update 1 FM, simply by entering the name MEREP_RDB_T01_UPDATE_1 into the relevant SAP transaction such as SE37 or SE38.

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



Function MEREP_RDB_T01_UPDATE_1 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_RDB_T01_UPDATE_1'"SAP Mobile: Update /SAPNEA/MBL207
  EXPORTING
   SCENARIO =  "SAP Mobile: Scenario ID
*  MBL_ID =  "ME Replica: ID of a mobile
*  TIMESTAMP =  "SAP Mobile: Time stamp for last update
*  BOTH =  "Single-character flag

TABLES
   I_HEADER_STR =  "Holds data from merep_207
   I_ITEM_STR =  "Holds data from merep_207
*  I_HEADERSTR_RDB =  "Holds data from merep_207
*  I_ITEMSTR_RDB =  "Holds data from merep_207
*  I_MBL_RDB =  "Mobile Sync Key Control Table
*  I_RDBSTR_H_CUR =  "Holds data from merep_207
*  I_RDBSTR_P_CUR =  "Holds data from merep_207

EXCEPTIONS
   UPDATE_ERROR = 1    NUMBER_ASSIGN_ERROR = 2
.



IMPORTING Parameters details for MEREP_RDB_T01_UPDATE_1

SCENARIO - SAP Mobile: Scenario ID

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

MBL_ID - ME Replica: ID of a mobile

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

TIMESTAMP - SAP Mobile: Time stamp for last update

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

BOTH - Single-character flag

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

TABLES Parameters details for MEREP_RDB_T01_UPDATE_1

I_HEADER_STR - Holds data from merep_207

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

I_ITEM_STR - Holds data from merep_207

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

I_HEADERSTR_RDB - Holds data from merep_207

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

I_ITEMSTR_RDB - Holds data from merep_207

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

I_MBL_RDB - Mobile Sync Key Control Table

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

I_RDBSTR_H_CUR - Holds data from merep_207

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

I_RDBSTR_P_CUR - Holds data from merep_207

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

EXCEPTIONS details

UPDATE_ERROR -

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

NUMBER_ASSIGN_ERROR -

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

Copy and paste ABAP code example for MEREP_RDB_T01_UPDATE_1 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_scenario  TYPE MEREP_SCENARIO, "   
lt_i_header_str  TYPE STANDARD TABLE OF MEREP_T207STRUCT, "   
lv_update_error  TYPE MEREP_T207STRUCT, "   
lv_mbl_id  TYPE MEREP_MBL_ID, "   
lt_i_item_str  TYPE STANDARD TABLE OF MEREP_T207STRUCT, "   
lv_number_assign_error  TYPE MEREP_T207STRUCT, "   
lv_timestamp  TYPE MEREP_UPDTS, "   
lt_i_headerstr_rdb  TYPE STANDARD TABLE OF MEREP_T207STRUCT, "   
lv_both  TYPE CHAR1, "   
lt_i_itemstr_rdb  TYPE STANDARD TABLE OF MEREP_T207STRUCT, "   
lt_i_mbl_rdb  TYPE STANDARD TABLE OF MEREP_10700, "   
lt_i_rdbstr_h_cur  TYPE STANDARD TABLE OF MEREP_T207STRUCT, "   
lt_i_rdbstr_p_cur  TYPE STANDARD TABLE OF MEREP_T207STRUCT. "   

  CALL FUNCTION 'MEREP_RDB_T01_UPDATE_1'  "SAP Mobile: Update /SAPNEA/MBL207
    EXPORTING
         SCENARIO = lv_scenario
         MBL_ID = lv_mbl_id
         TIMESTAMP = lv_timestamp
         BOTH = lv_both
    TABLES
         I_HEADER_STR = lt_i_header_str
         I_ITEM_STR = lt_i_item_str
         I_HEADERSTR_RDB = lt_i_headerstr_rdb
         I_ITEMSTR_RDB = lt_i_itemstr_rdb
         I_MBL_RDB = lt_i_mbl_rdb
         I_RDBSTR_H_CUR = lt_i_rdbstr_h_cur
         I_RDBSTR_P_CUR = lt_i_rdbstr_p_cur
    EXCEPTIONS
        UPDATE_ERROR = 1
        NUMBER_ASSIGN_ERROR = 2
. " MEREP_RDB_T01_UPDATE_1




ABAP code using 7.40 inline data declarations to call FM MEREP_RDB_T01_UPDATE_1

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!