SAP MEREP_RDB_T01_UPDATE Function Module for SAP Mobile: Update /SAPNEA/MBL207
MEREP_RDB_T01_UPDATE is a standard merep rdb t01 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 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 FM, simply by entering the name MEREP_RDB_T01_UPDATE 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: 1
Function MEREP_RDB_T01_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_RDB_T01_UPDATE'"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 = "SAP Mobile: Replica DB for Timed 2 Way Sync
I_ITEM = "SAP Mobile: Replica DB for Timed 2 Way Sync
* I_HEADER_RDB = "SAP Mobile: Replica DB for Timed 2 Way Sync
* I_ITEM_RDB = "SAP Mobile: Replica DB for Timed 2 Way Sync
* I_MBL_RDB = "SAP Mobile: Mobile Sync Key Control Table
* I_RDB_H_CUR = "SAP Mobile: Replica DB for Timed 2 Way Sync
* I_RDB_P_CUR = "SAP Mobile: Replica DB for Timed 2 Way Sync
* E_HEADER = "SAP Mobile: Replica DB for Timed 2 Way Sync
* E_ITEM = "SAP Mobile: Replica DB for Timed 2 Way Sync
IMPORTING Parameters details for MEREP_RDB_T01_UPDATE
SCENARIO - SAP Mobile: Scenario ID
Data type: MEREP_SCENARIOOptional: No
Call by Reference: No ( called with pass by value option)
MBL_ID - ME Replica: ID of a mobile
Data type: MEREP_MBL_IDOptional: Yes
Call by Reference: No ( called with pass by value option)
TIMESTAMP - SAP Mobile: Time stamp for last update
Data type: MEREP_UPDTSOptional: Yes
Call by Reference: No ( called with pass by value option)
BOTH - Single-character flag
Data type: CHAR1Optional: Yes
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for MEREP_RDB_T01_UPDATE
I_HEADER - SAP Mobile: Replica DB for Timed 2 Way Sync
Data type: MEREP_207Optional: No
Call by Reference: Yes
I_ITEM - SAP Mobile: Replica DB for Timed 2 Way Sync
Data type: MEREP_207Optional: No
Call by Reference: Yes
I_HEADER_RDB - SAP Mobile: Replica DB for Timed 2 Way Sync
Data type: MEREP_207Optional: Yes
Call by Reference: Yes
I_ITEM_RDB - SAP Mobile: Replica DB for Timed 2 Way Sync
Data type: MEREP_207Optional: Yes
Call by Reference: Yes
I_MBL_RDB - SAP Mobile: Mobile Sync Key Control Table
Data type: MEREP_10700Optional: Yes
Call by Reference: Yes
I_RDB_H_CUR - SAP Mobile: Replica DB for Timed 2 Way Sync
Data type: MEREP_207Optional: Yes
Call by Reference: Yes
I_RDB_P_CUR - SAP Mobile: Replica DB for Timed 2 Way Sync
Data type: MEREP_207Optional: Yes
Call by Reference: Yes
E_HEADER - SAP Mobile: Replica DB for Timed 2 Way Sync
Data type: MEREP_207Optional: Yes
Call by Reference: Yes
E_ITEM - SAP Mobile: Replica DB for Timed 2 Way Sync
Data type: MEREP_207Optional: Yes
Call by Reference: Yes
Copy and paste ABAP code example for MEREP_RDB_T01_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: | ||||
| lt_i_header | TYPE STANDARD TABLE OF MEREP_207, " | |||
| lv_scenario | TYPE MEREP_SCENARIO, " | |||
| lt_i_item | TYPE STANDARD TABLE OF MEREP_207, " | |||
| lv_mbl_id | TYPE MEREP_MBL_ID, " | |||
| lv_timestamp | TYPE MEREP_UPDTS, " | |||
| lt_i_header_rdb | TYPE STANDARD TABLE OF MEREP_207, " | |||
| lv_both | TYPE CHAR1, " | |||
| lt_i_item_rdb | TYPE STANDARD TABLE OF MEREP_207, " | |||
| lt_i_mbl_rdb | TYPE STANDARD TABLE OF MEREP_10700, " | |||
| lt_i_rdb_h_cur | TYPE STANDARD TABLE OF MEREP_207, " | |||
| lt_i_rdb_p_cur | TYPE STANDARD TABLE OF MEREP_207, " | |||
| lt_e_header | TYPE STANDARD TABLE OF MEREP_207, " | |||
| lt_e_item | TYPE STANDARD TABLE OF MEREP_207. " |
| CALL FUNCTION 'MEREP_RDB_T01_UPDATE' "SAP Mobile: Update /SAPNEA/MBL207 |
| EXPORTING | ||
| SCENARIO | = lv_scenario | |
| MBL_ID | = lv_mbl_id | |
| TIMESTAMP | = lv_timestamp | |
| BOTH | = lv_both | |
| TABLES | ||
| I_HEADER | = lt_i_header | |
| I_ITEM | = lt_i_item | |
| I_HEADER_RDB | = lt_i_header_rdb | |
| I_ITEM_RDB | = lt_i_item_rdb | |
| I_MBL_RDB | = lt_i_mbl_rdb | |
| I_RDB_H_CUR | = lt_i_rdb_h_cur | |
| I_RDB_P_CUR | = lt_i_rdb_p_cur | |
| E_HEADER | = lt_e_header | |
| E_ITEM | = lt_e_item | |
| . " MEREP_RDB_T01_UPDATE | ||
ABAP code using 7.40 inline data declarations to call FM MEREP_RDB_T01_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.Search for further information about these or an SAP related objects