SAP Function Modules

CNV_MBT_SUBPROTOCOL_READ SAP Function module - Read logs of an execution







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

Associated Function Group: CNV_MBT_PROTOCOL
Released Date: Not Released
Processing type: Normal fucntion module
Normal function module settings


Pattern for FM CNV_MBT_SUBPROTOCOL_READ - CNV MBT SUBPROTOCOL READ





CALL FUNCTION 'CNV_MBT_SUBPROTOCOL_READ' "Read logs of an execution
  EXPORTING
    i_session_id =              " cnv_mbt_session_id  MBT PCL: Session ID
    i_subact_id =               " cnv_mbt_subactivity  Unique ID for All Subactivities to Be Executed
    i_task_id =                 " cnv_mbt_taskid  Numeric Identifyer of Conversion or Migration Task
  IMPORTING
    et_messages =               " cnv_mbt_t_bal_s_msg  List of BAL_S_MSG messages
  EXCEPTIONS
    EXECUTION_NOT_FOUND = 1     "
    NO_LOG_EXISTS = 2           "
    RFC_PROBLEM = 3             "
    .  "  CNV_MBT_SUBPROTOCOL_READ

ABAP code example for Function Module CNV_MBT_SUBPROTOCOL_READ





The ABAP code below is a full code listing to execute function module CNV_MBT_SUBPROTOCOL_READ 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_et_messages  TYPE CNV_MBT_T_BAL_S_MSG .

DATA(ld_i_session_id) = 'Check type of data required'.
DATA(ld_i_subact_id) = 'Check type of data required'.
DATA(ld_i_task_id) = 'Check type of data required'. . CALL FUNCTION 'CNV_MBT_SUBPROTOCOL_READ' EXPORTING i_session_id = ld_i_session_id i_subact_id = ld_i_subact_id i_task_id = ld_i_task_id IMPORTING et_messages = ld_et_messages EXCEPTIONS EXECUTION_NOT_FOUND = 1 NO_LOG_EXISTS = 2 RFC_PROBLEM = 3 . " CNV_MBT_SUBPROTOCOL_READ
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 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_et_messages  TYPE CNV_MBT_T_BAL_S_MSG ,
ld_i_session_id  TYPE CNV_MBT_SESSION_ID ,
ld_i_subact_id  TYPE CNV_MBT_SUBACTIVITY ,
ld_i_task_id  TYPE CNV_MBT_TASKID .

ld_i_session_id = 'Check type of data required'.
ld_i_subact_id = 'Check type of data required'.
ld_i_task_id = 'Check type of data required'.

Contribute (Add Comments)

Please help keep this info upto date and use the comments section below to add useful hints, tips and information specific to this SAP function. This will then be available for you and other users to easily find by simply searching on the object name CNV_MBT_SUBPROTOCOL_READ or its description.