SAP CNV_MBT_L_PROTOCOL_OPEN_NEW Function Module for MBT PCL read existing log and transfer messages to new one

Search SAP Function Modules

CNV_MBT_L_PROTOCOL_OPEN_NEW is a standard cnv mbt l protocol open new 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 read existing log and transfer messages to new one 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 l protocol open new FM, simply by entering the name CNV_MBT_L_PROTOCOL_OPEN_NEW into the relevant SAP transaction such as SE37 or SE38.

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

Function CNV_MBT_L_PROTOCOL_OPEN_NEW 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_L_PROTOCOL_OPEN_NEW'"MBT PCL read existing log and transfer messages to new one
  EXPORTING
   PACKID =  "
   PHASE =  "
   ACTIVITY_ID =  "
   LOGNUMBER_OLD =  "

 IMPORTING
   LOGNUMBER =  "
   ER_LOGGER =  "ULV Logger

EXCEPTIONS
   INTERNAL_ERROR = 1    MODIFY_CENTRAL_STATE_MANAG_ERR = 2    RFC_FAILURE = 3 

.

IMPORTING Parameters details for CNV_MBT_L_PROTOCOL_OPEN_NEW

PACKID -

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

PHASE -

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

ACTIVITY_ID -

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

LOGNUMBER_OLD -

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

EXPORTING Parameters details for CNV_MBT_L_PROTOCOL_OPEN_NEW

LOGNUMBER -

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

ER_LOGGER - ULV Logger

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

EXCEPTIONS details

INTERNAL_ERROR -

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

MODIFY_CENTRAL_STATE_MANAG_ERR -

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

RFC_FAILURE -

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

Copy and paste ABAP code example for CNV_MBT_L_PROTOCOL_OPEN_NEW 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_L_PROTOCOL_OPEN_NEW

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