RPY_BMEV_MULTI_UPDATE_31 SAP Function module - Update Events

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

Associated Function Group: SIBU
Released Date: Not Released
Processing type: Remote-Enabled

Pattern for FM RPY_BMEV_MULTI_UPDATE_31 - RPY BMEV MULTI UPDATE 31

CALL FUNCTION 'RPY_BMEV_MULTI_UPDATE_31' "Update Events
  EXPORTING
*   language = SY-LANGU         " sy-langu      Masterlanguage
    cico_request_no =           " rpybmgf-cico_reqno  Check-In-Check-Out-Request-Number
  IMPORTING
    error_occured =             " rpygsgf-err_exist  Error occured and is listed in Table 'ERRORS'
    processing_status =         " rpygsgf-proc_stat  Processing Status of operation
  TABLES
    events =                    " rpybm0331     Events
    errors =                    " rpybmer31     Errors that occured
    .  "  RPY_BMEV_MULTI_UPDATE_31

ABAP code example for Function Module RPY_BMEV_MULTI_UPDATE_31

The ABAP code below is a full code listing to execute function module RPY_BMEV_MULTI_UPDATE_31 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_error_occured  
 
 TYPE RPYGSGF-ERR_EXIST
,
ld_processing_status  
 
 TYPE RPYGSGF-PROC_STAT
,
it_events  
 
 TYPE STANDARD TABLE OF RPYBM0331,"TABLES PARAM
wa_events
 
 LIKE LINE OF it_events
,
it_errors  
 
 TYPE STANDARD TABLE OF RPYBMER31,"TABLES PARAM
wa_errors
 
 LIKE LINE OF it_errors
.


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


DATA(ld_cico_request_no) = some text here
 

"populate fields of struture and append to itab
append wa_events to it_events.
 

"populate fields of struture and append to itab
append wa_errors to it_errors.
.

CALL FUNCTION 'RPY_BMEV_MULTI_UPDATE_31'
  EXPORTING
*   language =                   ld_language
    cico_request_no =            ld_cico_request_no
  IMPORTING
    error_occured =              ld_error_occured
    processing_status =          ld_processing_status
  TABLES
    events =                     it_events
    errors =                     it_errors
    .  "  RPY_BMEV_MULTI_UPDATE_31

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_error_occured
 
 TYPE RPYGSGF-ERR_EXIST ,
ld_language
 
 TYPE SY-LANGU ,
it_events
 
 TYPE STANDARD TABLE OF RPYBM0331 ,
wa_events
 
 LIKE LINE OF it_events,
ld_processing_status
 
 TYPE RPYGSGF-PROC_STAT ,
ld_cico_request_no
 
 TYPE RPYBMGF-CICO_REQNO ,
it_errors
 
 TYPE STANDARD TABLE OF RPYBMER31 ,
wa_errors
 
 LIKE LINE OF it_errors.


ld_language = 'Check type of data required'. 

"populate fields of struture and append to itab
append wa_events to it_events.

ld_cico_request_no = some text here 

"populate fields of struture and append to itab
append wa_errors to it_errors.

SAP Documentation for FM RPY_BMEV_MULTI_UPDATE_31