SAP CNV_INT_PROTOCOL_MWB_EXIT Function Module for Calls MWB exit

Search SAP Function Modules

CNV_INT_PROTOCOL_MWB_EXIT is a standard cnv int protocol mwb exit SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Calls MWB exit 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 int protocol mwb exit FM, simply by entering the name CNV_INT_PROTOCOL_MWB_EXIT into the relevant SAP transaction such as SE37 or SE38.

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

Function CNV_INT_PROTOCOL_MWB_EXIT 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_INT_PROTOCOL_MWB_EXIT'"Calls MWB exit
  EXPORTING
   MSGTY =  "Messages, message type
   MSGID =  "Messages, message class
   MSGNO =  "Messages, message number
   MSGV1 =  "
   MSGV2 =  "
   MSGV3 =  "
   MSGV4 =  "

.

IMPORTING Parameters details for CNV_INT_PROTOCOL_MWB_EXIT

MSGTY - Messages, message type

Data type: BALMI-MSGTY
Optional: No
Call by Reference: Yes

MSGID - Messages, message class

Data type: BALMI-MSGID
Optional: No
Call by Reference: Yes

MSGNO - Messages, message number

Data type: BALMI-MSGNO
Optional: No
Call by Reference: Yes

MSGV1 -

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

MSGV2 -

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

MSGV3 -

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

MSGV4 -

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

Copy and paste ABAP code example for CNV_INT_PROTOCOL_MWB_EXIT 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_INT_PROTOCOL_MWB_EXIT

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