SAP CNV_CHECK_CONVERSION_OBJECT Function Module for Check JEST object
CNV_CHECK_CONVERSION_OBJECT is a standard cnv check conversion object 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 JEST object 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 check conversion object FM, simply by entering the name CNV_CHECK_CONVERSION_OBJECT into the relevant SAP transaction such as SE37 or SE38.
Function Group: CNV_TDMS_DF_JEST
Program Name: SAPLCNV_TDMS_DF_JEST
Main Program: SAPLCNV_TDMS_DF_JEST
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function CNV_CHECK_CONVERSION_OBJECT 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_CHECK_CONVERSION_OBJECT'"Check JEST object.
EXPORTING
MTID = "Identification of MBT Mass Transfer
IMPORTING
COBJ_EXIST = "Single-character flag
IMPORTING Parameters details for CNV_CHECK_CONVERSION_OBJECT
MTID - Identification of MBT Mass Transfer
Data type: CNVMBTSUBPROJECT-MTIDOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CNV_CHECK_CONVERSION_OBJECT
COBJ_EXIST - Single-character flag
Data type: CHAR1Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CNV_CHECK_CONVERSION_OBJECT 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_mtid | TYPE CNVMBTSUBPROJECT-MTID, " | |||
| lv_cobj_exist | TYPE CHAR1. " |
|   CALL FUNCTION 'CNV_CHECK_CONVERSION_OBJECT' "Check JEST object |
| EXPORTING | ||
| MTID | = lv_mtid | |
| IMPORTING | ||
| COBJ_EXIST | = lv_cobj_exist | |
| . " CNV_CHECK_CONVERSION_OBJECT | ||
ABAP code using 7.40 inline data declarations to call FM CNV_CHECK_CONVERSION_OBJECT
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 MTID FROM CNVMBTSUBPROJECT INTO @DATA(ld_mtid). | ||||
Search for further information about these or an SAP related objects