SAP CNV_MBT_PROTOCOL_TRANSFER_CHK Function Module for Check if all logs were transferred successful
CNV_MBT_PROTOCOL_TRANSFER_CHK is a standard cnv mbt protocol transfer chk SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check if all logs were transferred successful 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 transfer chk FM, simply by entering the name CNV_MBT_PROTOCOL_TRANSFER_CHK 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: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CNV_MBT_PROTOCOL_TRANSFER_CHK 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_TRANSFER_CHK'"Check if all logs were transferred successful.
EXPORTING
* PACKID = "Package Number to Specify CMIS and TDMS Packages
EXCEPTIONS
RFC_PROBLEMS = 1
IMPORTING Parameters details for CNV_MBT_PROTOCOL_TRANSFER_CHK
PACKID - Package Number to Specify CMIS and TDMS Packages
Data type: CNV_MBT_PACKIDOptional: Yes
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
RFC_PROBLEMS -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CNV_MBT_PROTOCOL_TRANSFER_CHK 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.| DATA: | ||||
| lv_packid | TYPE CNV_MBT_PACKID, " | |||
| lv_rfc_problems | TYPE CNV_MBT_PACKID. " |
|   CALL FUNCTION 'CNV_MBT_PROTOCOL_TRANSFER_CHK' "Check if all logs were transferred successful |
| EXPORTING | ||
| PACKID | = lv_packid | |
| EXCEPTIONS | ||
| RFC_PROBLEMS = 1 | ||
| . " CNV_MBT_PROTOCOL_TRANSFER_CHK | ||
ABAP code using 7.40 inline data declarations to call FM CNV_MBT_PROTOCOL_TRANSFER_CHK
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