MEREP_RDB_S01_UPDATE SAP Function module - SAP Mobile: Update /SAPNEA/MBL101 from inttab

MEREP_RDB_S01_UPDATE is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name MEREP_RDB_S01_UPDATE into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: MEREP_RUNTIME_DB
Released Date: Not Released
Processing type: Normal fucntion module

Pattern for FM MEREP_RDB_S01_UPDATE - MEREP RDB S01 UPDATE

CALL FUNCTION 'MEREP_RDB_S01_UPDATE' "SAP Mobile: Update /SAPNEA/MBL101 from inttab
  EXPORTING
    scenario =                  " merep_scenario  SAP Mobile: Scenario ID
    mbl_id =                    " merep_mbl_id  ME Replica: ID of a mobile
    timestamp =                 " merep_updts   SAP Mobile: Time stamp for last update
  IMPORTING
    return =                    " bapireturn1   Return Parameter
  TABLES
    2_header =                  " merep_10100   SAP Mobile: Replica DB for Synchronization (Base)   Segmt
*   2_item =                    " merep_10100   SAP Mobile: Replica DB for Synchronization (Base)   Segmt
    .  "  MEREP_RDB_S01_UPDATE

ABAP code example for Function Module MEREP_RDB_S01_UPDATE

The ABAP code below is a full code listing to execute function module MEREP_RDB_S01_UPDATE including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
ld_return  
 
 TYPE BAPIRETURN1
,
it_2_header  
 
 TYPE STANDARD TABLE OF MEREP_10100,"TABLES PARAM
wa_2_header
 
 LIKE LINE OF it_2_header
,
it_2_item  
 
 TYPE STANDARD TABLE OF MEREP_10100,"TABLES PARAM
wa_2_item
 
 LIKE LINE OF it_2_item
.


DATA(ld_scenario) = 'Check type of data required'.

DATA(ld_mbl_id) = 'Check type of data required'.

DATA(ld_timestamp) = 'Check type of data required'.
 

"populate fields of struture and append to itab
append wa_2_header to it_2_header.
 

"populate fields of struture and append to itab
append wa_2_item to it_2_item.
.

CALL FUNCTION 'MEREP_RDB_S01_UPDATE'
  EXPORTING
    scenario =                   ld_scenario
    mbl_id =                     ld_mbl_id
    timestamp =                  ld_timestamp
  IMPORTING
    return =                     ld_return
  TABLES
    2_header =                   it_2_header
*   2_item =                     it_2_item
    .  "  MEREP_RDB_S01_UPDATE

IF SY-SUBRC EQ 0.
  "All OK
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_return
 
 TYPE BAPIRETURN1 ,
ld_scenario
 
 TYPE MEREP_SCENARIO ,
it_2_header
 
 TYPE STANDARD TABLE OF MEREP_10100 ,
wa_2_header
 
 LIKE LINE OF it_2_header,
ld_mbl_id
 
 TYPE MEREP_MBL_ID ,
it_2_item
 
 TYPE STANDARD TABLE OF MEREP_10100 ,
wa_2_item
 
 LIKE LINE OF it_2_item,
ld_timestamp
 
 TYPE MEREP_UPDTS .


ld_scenario = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_2_header to it_2_header.
ld_mbl_id = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_2_item to it_2_item.
ld_timestamp = 'Check type of data required'.