SAP CNV_MBT_CR_INTERFACE_TEMPLATE Function Module for Template for the checking rule function module interface

Search SAP Function Modules

CNV_MBT_CR_INTERFACE_TEMPLATE is a standard cnv mbt cr interface template SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Template for the checking rule function module interface 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 cr interface template FM, simply by entering the name CNV_MBT_CR_INTERFACE_TEMPLATE into the relevant SAP transaction such as SE37 or SE38.

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

Function CNV_MBT_CR_INTERFACE_TEMPLATE 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_CR_INTERFACE_TEMPLATE'"Template for the checking rule function module interface
  EXPORTING
*  IP_PACKID =  "Package Number to Specify CMIS and TDMS Packages
   IP_VARIANT =  "Checking rule variant
   IP_CNVMBTCR =  "Checking rule function modules
*  IP_TEST =  "If set than the variant values will be checked
*  IP_STATUS =  "If set than with status management

 IMPORTING
   RETURN_CODE =  "Return value, return value after ABAP statements

TABLES
   T_CNVMBTCRVAL =  "Values used for the checking rules in the CR function mod.
   RETURN_TABLE =  "Return parameter

EXCEPTIONS
   NO_FUNCTION_MODULE_NAME = 1    NO_CHECKING_RULE_FOUND = 2    NO_VARIANT = 3    NO_GLOBAL_PARAMETER = 4    ERROR_READ_GP = 5 

.

IMPORTING Parameters details for CNV_MBT_CR_INTERFACE_TEMPLATE

IP_PACKID - Package Number to Specify CMIS and TDMS Packages

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

IP_VARIANT - Checking rule variant

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

IP_CNVMBTCR - Checking rule function modules

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

IP_TEST - If set than the variant values will be checked

Data type: C
Optional: Yes
Call by Reference: Yes

IP_STATUS - If set than with status management

Data type: C
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for CNV_MBT_CR_INTERFACE_TEMPLATE

RETURN_CODE - Return value, return value after ABAP statements

Data type: SY-SUBRC
Optional: No
Call by Reference: Yes

TABLES Parameters details for CNV_MBT_CR_INTERFACE_TEMPLATE

T_CNVMBTCRVAL - Values used for the checking rules in the CR function mod.

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

RETURN_TABLE - Return parameter

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

EXCEPTIONS details

NO_FUNCTION_MODULE_NAME - Function module name not found

Data type:
Optional: No
Call by Reference: Yes

NO_CHECKING_RULE_FOUND - Checking rule not found

Data type:
Optional: No
Call by Reference: Yes

NO_VARIANT - No Checking Rule variant found

Data type:
Optional: No
Call by Reference: Yes

NO_GLOBAL_PARAMETER - Specified Global Parameter not found

Data type:
Optional: No
Call by Reference: Yes

ERROR_READ_GP - Error while reading the Global Parameters

Data type:
Optional: No
Call by Reference: Yes

Copy and paste ABAP code example for CNV_MBT_CR_INTERFACE_TEMPLATE 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_CR_INTERFACE_TEMPLATE

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