RSB2_INBOUND_REQUESTS_GET SAP Function module - Determination of requests in a changelog

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

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

Pattern for FM RSB2_INBOUND_REQUESTS_GET - RSB2 INBOUND REQUESTS GET

CALL FUNCTION 'RSB2_INBOUND_REQUESTS_GET' "Determination of requests in a changelog
  EXPORTING
    i_dtanm =                   " rsddatatarget  Data target for transaction data (InfoCube or ODS object)
*   i_rlogsys =                 " rsrlogsys     Target System
*   i_request_out =             " rsrequid      Request ID
  TABLES
    e_t_request =               " rsbrequest    List of Request Numbers
  EXCEPTIONS
    NO_REQUESTS_FOUND = 1       "               No matching requests found
    FAILED = 2                  "
    .  "  RSB2_INBOUND_REQUESTS_GET

ABAP code example for Function Module RSB2_INBOUND_REQUESTS_GET

The ABAP code below is a full code listing to execute function module RSB2_INBOUND_REQUESTS_GET 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:
it_e_t_request  
 
 TYPE STANDARD TABLE OF RSBREQUEST,"TABLES PARAM
wa_e_t_request
 
 LIKE LINE OF it_e_t_request
.


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

DATA(ld_i_rlogsys) = 'some text here'.

DATA(ld_i_request_out) = 'some text here'.
 

"populate fields of struture and append to itab
append wa_e_t_request to it_e_t_request.
.

CALL FUNCTION 'RSB2_INBOUND_REQUESTS_GET'
  EXPORTING
    i_dtanm =                    ld_i_dtanm
*   i_rlogsys =                  ld_i_rlogsys
*   i_request_out =              ld_i_request_out
  TABLES
    e_t_request =                it_e_t_request
  EXCEPTIONS
    NO_REQUESTS_FOUND =          1
    FAILED =                     2
    .  "  RSB2_INBOUND_REQUESTS_GET

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
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_i_dtanm
 
 TYPE RSDDATATARGET ,
it_e_t_request
 
 TYPE STANDARD TABLE OF RSBREQUEST ,
wa_e_t_request
 
 LIKE LINE OF it_e_t_request,
ld_i_rlogsys
 
 TYPE RSRLOGSYS ,
ld_i_request_out
 
 TYPE RSREQUID .


ld_i_dtanm = 'some text here'. 

"populate fields of struture and append to itab
append wa_e_t_request to it_e_t_request.
ld_i_rlogsys = 'some text here'.
ld_i_request_out = 'some text here'.