MEREP_UPLOAD_DATA_CREATE SAP Function module - SmartSync Create upload data

MEREP_UPLOAD_DATA_CREATE 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_UPLOAD_DATA_CREATE into the relevant SAP transaction such as SE37 or SE80.

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

Pattern for FM MEREP_UPLOAD_DATA_CREATE - MEREP UPLOAD DATA CREATE

CALL FUNCTION 'MEREP_UPLOAD_DATA_CREATE' "SmartSync Create upload data
  EXPORTING
    syncbo =                    " merep_scenario  SyncBO ID
    mbl_id =                    " merep_mbl_id  Mobile ID
    data =                      " merep_data_field_t  Smart Sync data field
  IMPORTING
    inbound_data =              " merep_t504    Table Type: MEREP_504
  EXCEPTIONS
    INVALID_SYNCBO = 1          "
    METADATA = 2                "
    SYNCBO_NOT_GENERATED = 3    "
    R3KEY_NOT_DEFINED = 4       "
    .  "  MEREP_UPLOAD_DATA_CREATE

ABAP code example for Function Module MEREP_UPLOAD_DATA_CREATE

The ABAP code below is a full code listing to execute function module MEREP_UPLOAD_DATA_CREATE 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_inbound_data  
 
 TYPE MEREP_T504
.


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

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

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

CALL FUNCTION 'MEREP_UPLOAD_DATA_CREATE'
  EXPORTING
    syncbo =                     ld_syncbo
    mbl_id =                     ld_mbl_id
    data =                       ld_data
  IMPORTING
    inbound_data =               ld_inbound_data
  EXCEPTIONS
    INVALID_SYNCBO =             1
    METADATA =                   2
    SYNCBO_NOT_GENERATED =       3
    R3KEY_NOT_DEFINED =          4
    .  "  MEREP_UPLOAD_DATA_CREATE

IF SY-SUBRC EQ 0.
  "All OK
ELSEIF SY-SUBRC EQ 1. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 2. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 3. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 4. "Exception
  "Add code for exception here
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_inbound_data
 
 TYPE MEREP_T504 ,
ld_syncbo
 
 TYPE MEREP_SCENARIO ,
ld_mbl_id
 
 TYPE MEREP_MBL_ID ,
ld_data
 
 TYPE MEREP_DATA_FIELD_T .


ld_syncbo = 'Check type of data required'.
ld_mbl_id = 'Check type of data required'.
ld_data = 'Check type of data required'.