MEREP_INBOX_MODIFICATION SAP Function module - Inbox Modification

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

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

Pattern for FM MEREP_INBOX_MODIFICATION - MEREP INBOX MODIFICATION

CALL FUNCTION 'MEREP_INBOX_MODIFICATION' "Inbox Modification
  EXPORTING
    i_inbox_wl =                " merep_505     SAP Mobile: Inbox/Outbox Worklist
  CHANGING
    inbox_data =                " merep_504     SAP Mobile: Inbox/Outbox Data
  EXCEPTIONS
    NOT_INBOX_DATA = 1          "
    NO_AVAILABLE_RECORD = 2     "
    SYSTEM = 3                  "
    ENQUEUE_FAIL = 4            "
    NOT_AVAILABLE_NOW = 5       "
    STATUS_NOT_VALID = 6        "
    .  "  MEREP_INBOX_MODIFICATION

ABAP code example for Function Module MEREP_INBOX_MODIFICATION

The ABAP code below is a full code listing to execute function module MEREP_INBOX_MODIFICATION 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_inbox_data) = 'Check type of data required'.

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

CALL FUNCTION 'MEREP_INBOX_MODIFICATION'
  EXPORTING
    i_inbox_wl =                 ld_i_inbox_wl
  CHANGING
    inbox_data =                 ld_inbox_data
  EXCEPTIONS
    NOT_INBOX_DATA =             1
    NO_AVAILABLE_RECORD =        2
    SYSTEM =                     3
    ENQUEUE_FAIL =               4
    NOT_AVAILABLE_NOW =          5
    STATUS_NOT_VALID =           6
    .  "  MEREP_INBOX_MODIFICATION

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
ELSEIF SY-SUBRC EQ 5. "Exception
  "Add code for exception here
ELSEIF SY-SUBRC EQ 6. "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_inbox_data
 
 TYPE MEREP_504 ,
ld_i_inbox_wl
 
 TYPE MEREP_505 .


ld_inbox_data = 'Check type of data required'.
ld_i_inbox_wl = 'Check type of data required'.