BM_QUESTION_TRANSPORT SAP Function module

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

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

Pattern for FM BM_QUESTION_TRANSPORT - BM QUESTION TRANSPORT

CALL FUNCTION 'BM_QUESTION_TRANSPORT' "
  EXPORTING
    i_question_id =             " sqadb01-queid  Unique question ID
*   i_corr_insert = SPACE       " c
*   i_transport_type = 'K'      " c
*   i_params = SPACE            " bmtrparam     Transport Control Parameters
* TABLES
*   i_devclasses =              " bmseldevcl    Range for DEVCLASS
* CHANGING
*   object_list =               " strobjlist    Sorted Table of Interfaces for Objects in CTS
*   key_list =                  " strkeylist    Table with Key Entries of Requests/Tasks
*   transport_order =           " trkorr        Request/Task
*   messages =                  " bmmsgtab      Messages
    .  "  BM_QUESTION_TRANSPORT

ABAP code example for Function Module BM_QUESTION_TRANSPORT

The ABAP code below is a full code listing to execute function module BM_QUESTION_TRANSPORT 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_i_devclasses  
 
 TYPE STANDARD TABLE OF BMSELDEVCL,"TABLES PARAM
wa_i_devclasses
 
 LIKE LINE OF it_i_devclasses
.


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

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

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

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

SELECT single QUEID 
  FROM SQADB01 
  INTO @DATA(ld_i_question_id).


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

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

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

"populate fields of struture and append to itab
append wa_i_devclasses to it_i_devclasses.
.

CALL FUNCTION 'BM_QUESTION_TRANSPORT'
  EXPORTING
    i_question_id =              ld_i_question_id
*   i_corr_insert =              ld_i_corr_insert
*   i_transport_type =           ld_i_transport_type
*   i_params =                   ld_i_params
* TABLES
*   i_devclasses =               it_i_devclasses
* CHANGING
*   object_list =                ld_object_list
*   key_list =                   ld_key_list
*   transport_order =            ld_transport_order
*   messages =                   ld_messages
    .  "  BM_QUESTION_TRANSPORT

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_object_list
 
 TYPE STROBJLIST ,
ld_i_question_id
 
 TYPE SQADB01-QUEID ,
it_i_devclasses
 
 TYPE STANDARD TABLE OF BMSELDEVCL ,
wa_i_devclasses
 
 LIKE LINE OF it_i_devclasses,
ld_key_list
 
 TYPE STRKEYLIST ,
ld_i_corr_insert
 
 TYPE C ,
ld_transport_order
 
 TYPE TRKORR ,
ld_i_transport_type
 
 TYPE C ,
ld_messages
 
 TYPE BMMSGTAB ,
ld_i_params
 
 TYPE BMTRPARAM .


ld_object_list = 'Check type of data required'.

SELECT single QUEID 
  FROM SQADB01 
  INTO ld_i_question_id.
 

"populate fields of struture and append to itab
append wa_i_devclasses to it_i_devclasses.
ld_key_list = 'Check type of data required'.
ld_i_corr_insert = 'Check type of data required'.
ld_transport_order = 'Check type of data required'.
ld_i_transport_type = 'Check type of data required'.
ld_messages = 'Check type of data required'.
ld_i_params = 'Check type of data required'.