SAP MEREP_RDB_T01_GET_SINGLE Function Module for Read One TOP Block









MEREP_RDB_T01_GET_SINGLE is a standard merep rdb t01 get single SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read One TOP Block 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 get single FM, simply by entering the name MEREP_RDB_T01_GET_SINGLE 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_GET_SINGLE 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_GET_SINGLE'"Read One TOP Block
EXPORTING
SCENARIO = "SAP Mobile: Scenario ID
SYNC_KEY = "Synchronization Key
* SYNC_GENERIC = "

IMPORTING
HEADER = "Replica DB for Timed 2-Way Sync

TABLES
* E_ITEM = "SAP Mobile: Replica DB for Timed 2 Way Sync
.



IMPORTING Parameters details for MEREP_RDB_T01_GET_SINGLE

SCENARIO - SAP Mobile: Scenario ID

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

SYNC_KEY - Synchronization Key

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

SYNC_GENERIC -

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

EXPORTING Parameters details for MEREP_RDB_T01_GET_SINGLE

HEADER - Replica DB for Timed 2-Way Sync

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

TABLES Parameters details for MEREP_RDB_T01_GET_SINGLE

E_ITEM - SAP Mobile: Replica DB for Timed 2 Way Sync

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

Copy and paste ABAP code example for MEREP_RDB_T01_GET_SINGLE 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_e_item  TYPE STANDARD TABLE OF MEREP_207, "   
lv_header  TYPE MEREP_207, "   
lv_scenario  TYPE MEREP_SCENARIO, "   
lv_sync_key  TYPE MEREP_SYNC_KEY, "   
lv_sync_generic  TYPE MEREP_SYNC_GENERIC. "   

  CALL FUNCTION 'MEREP_RDB_T01_GET_SINGLE'  "Read One TOP Block
    EXPORTING
         SCENARIO = lv_scenario
         SYNC_KEY = lv_sync_key
         SYNC_GENERIC = lv_sync_generic
    IMPORTING
         HEADER = lv_header
    TABLES
         E_ITEM = lt_e_item
. " MEREP_RDB_T01_GET_SINGLE




ABAP code using 7.40 inline data declarations to call FM MEREP_RDB_T01_GET_SINGLE

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!