SAP CNV_MBT_PROTOCOL_READ Function Module for Read logs of an execution

Search SAP Function Modules

CNV_MBT_PROTOCOL_READ is a standard cnv mbt protocol read SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Read logs of an execution processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.

See here to view full function module documentation and code listing for cnv mbt protocol read FM, simply by entering the name CNV_MBT_PROTOCOL_READ into the relevant SAP transaction such as SE37 or SE38.

Function Group: CNV_MBT_PROTOCOL
Program Name: SAPLCNV_MBT_PROTOCOL
Main Program: SAPLCNV_MBT_PROTOCOL
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CNV_MBT_PROTOCOL_READ pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.

CALL FUNCTION 'CNV_MBT_PROTOCOL_READ'"Read logs of an execution
  EXPORTING
   I_PACKID =  "Package Number to Specify CMIS and TDMS Packages
   I_PHASE =  "Phase of the Migration Project
   I_ACTIVITY_ID =  "Unique ID for all activities to be executed
   I_EXEC_NUM =  "Counters For Execution of Specified Activity

 IMPORTING
   ET_MESSAGES =  "List of BAL_S_MSG messages

EXCEPTIONS
   EXECUTION_NOT_FOUND = 1    NO_LOG_EXISTS = 2    RFC_PROBLEM = 3 

.

IMPORTING Parameters details for CNV_MBT_PROTOCOL_READ

I_PACKID - Package Number to Specify CMIS and TDMS Packages

Data type: CNV_MBT_PACKID
Optional: No
Call by Reference: Yes

I_PHASE - Phase of the Migration Project

Data type: CNV_MBT_PHASE
Optional: No
Call by Reference: Yes

I_ACTIVITY_ID - Unique ID for all activities to be executed

Data type: CNV_MBT_ACTIVITY
Optional: No
Call by Reference: Yes

I_EXEC_NUM - Counters For Execution of Specified Activity

Data type: CNV_MBT_EXEC_NUM
Optional: No
Call by Reference: Yes

EXPORTING Parameters details for CNV_MBT_PROTOCOL_READ

ET_MESSAGES - List of BAL_S_MSG messages

Data type: CNV_MBT_T_BAL_S_MSG
Optional: No
Call by Reference: Yes

EXCEPTIONS details

EXECUTION_NOT_FOUND -

Data type:
Optional: No
Call by Reference: Yes

NO_LOG_EXISTS -

Data type:
Optional: No
Call by Reference: Yes

RFC_PROBLEM -

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CNV_MBT_PROTOCOL_READ Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than 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 newer method of declaring data variables on the fly. 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), which i why i have stuck to the origianl for this example.

ABAP code using 7.40 inline data declarations to call FM CNV_MBT_PROTOCOL_READ

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

Search for further information about these or an SAP related objects