SAP CNV_MBT_PROTOCOL_TRANSFER Function Module for MBT PCL transfer local log to PCL system and create new central log









CNV_MBT_PROTOCOL_TRANSFER is a standard cnv mbt protocol transfer SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for MBT PCL transfer local log to PCL system and create new central log 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 FM, simply by entering the name CNV_MBT_PROTOCOL_TRANSFER 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 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'"MBT PCL transfer local log to PCL system and create new central log
EXPORTING
* IM_EXTNUMBER = "
IM_LOGNUMBER = "
* DESTINATION_ID = "
* IM_SCENARIO = "MBT PCL: Scenario
* IM_SESSIONID = "MBT PCL: Session ID

IMPORTING
EX_LOGNUMBER = "

EXCEPTIONS
NO_LOG_FOUND = 1 INVALID_CALL = 2 CONNECTION_FAILURE = 3 INTERNAL_ERROR = 4
.



IMPORTING Parameters details for CNV_MBT_PROTOCOL_TRANSFER

IM_EXTNUMBER -

Data type: BALHDR-EXTNUMBER
Optional: Yes
Call by Reference: No ( called with pass by value option)

IM_LOGNUMBER -

Data type: BALHDR-LOGNUMBER
Optional: No
Call by Reference: No ( called with pass by value option)

DESTINATION_ID -

Data type: CNVMBTDEST-DESTINATION_ID
Optional: Yes
Call by Reference: No ( called with pass by value option)

IM_SCENARIO - MBT PCL: Scenario

Data type: CNVMBTPACK-SCENARIO
Optional: Yes
Call by Reference: No ( called with pass by value option)

IM_SESSIONID - MBT PCL: Session ID

Data type: CNVMBTSTATE-SESSION_ID
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXPORTING Parameters details for CNV_MBT_PROTOCOL_TRANSFER

EX_LOGNUMBER -

Data type: BALHDR-LOGNUMBER
Optional: No
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

NO_LOG_FOUND -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

INVALID_CALL -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

CONNECTION_FAILURE -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

INTERNAL_ERROR -

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for CNV_MBT_PROTOCOL_TRANSFER 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_ex_lognumber  TYPE BALHDR-LOGNUMBER, "   
lv_im_extnumber  TYPE BALHDR-EXTNUMBER, "   
lv_no_log_found  TYPE BALHDR, "   
lv_im_lognumber  TYPE BALHDR-LOGNUMBER, "   
lv_invalid_call  TYPE BALHDR, "   
lv_destination_id  TYPE CNVMBTDEST-DESTINATION_ID, "   
lv_connection_failure  TYPE CNVMBTDEST, "   
lv_im_scenario  TYPE CNVMBTPACK-SCENARIO, "   
lv_internal_error  TYPE CNVMBTPACK, "   
lv_im_sessionid  TYPE CNVMBTSTATE-SESSION_ID. "   

  CALL FUNCTION 'CNV_MBT_PROTOCOL_TRANSFER'  "MBT PCL transfer local log to PCL system and create new central log
    EXPORTING
         IM_EXTNUMBER = lv_im_extnumber
         IM_LOGNUMBER = lv_im_lognumber
         DESTINATION_ID = lv_destination_id
         IM_SCENARIO = lv_im_scenario
         IM_SESSIONID = lv_im_sessionid
    IMPORTING
         EX_LOGNUMBER = lv_ex_lognumber
    EXCEPTIONS
        NO_LOG_FOUND = 1
        INVALID_CALL = 2
        CONNECTION_FAILURE = 3
        INTERNAL_ERROR = 4
. " CNV_MBT_PROTOCOL_TRANSFER




ABAP code using 7.40 inline data declarations to call FM CNV_MBT_PROTOCOL_TRANSFER

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.

"SELECT single LOGNUMBER FROM BALHDR INTO @DATA(ld_ex_lognumber).
 
"SELECT single EXTNUMBER FROM BALHDR INTO @DATA(ld_im_extnumber).
 
 
"SELECT single LOGNUMBER FROM BALHDR INTO @DATA(ld_im_lognumber).
 
 
"SELECT single DESTINATION_ID FROM CNVMBTDEST INTO @DATA(ld_destination_id).
 
 
"SELECT single SCENARIO FROM CNVMBTPACK INTO @DATA(ld_im_scenario).
 
 
"SELECT single SESSION_ID FROM CNVMBTSTATE INTO @DATA(ld_im_sessionid).
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!