CNV_MBT_CHECK_CONFLICT_READ SAP Function module - Return conflicts for a specified conversion object or package

CNV_MBT_CHECK_CONFLICT_READ is a standard SAP function module available within R/3 SAP systems depending on your version and release level. Below is the pattern details for this FM showing its interface including any import and export parameters, exceptions etc as well as any documentation contributions (Comments) specific to the object.

See here to view full function module documentation and code listing, simply by entering the name CNV_MBT_CHECK_CONFLICT_READ into the relevant SAP transaction such as SE37 or SE80.

Associated Function Group: CNV_MBT_CHECK
Released Date: Not Released
Processing type: Remote-Enabled

Pattern for FM CNV_MBT_CHECK_CONFLICT_READ - CNV MBT CHECK CONFLICT READ

CALL FUNCTION 'CNV_MBT_CHECK_CONFLICT_READ' "Return conflicts for a specified conversion object or package
  EXPORTING
    packid =                    " cnvmbtpack-packid  Package Number to Specify CMIS and TDMS Packages
*   convobject =                " cnvmbtconvobjects  Structure for Conversion objects
*   strucname =                 " cnvmbttables-strucname  Structure Name
*   fieldname =                 " cnvmbtforkey-fieldname  Field Name
*   conflict_type =             " cnvmbtconflicts-conflict_type  Conflict between sender and receiver structure
*   only_not_solved =           " cnvmbtconflicts-solved  conflict solved?
*   only_solved =               " cnvmbtconflicts-solved  conflict solved?
  TABLES
    et_cnvmbtconflicts =        " cnvmbtconflicts  Conflicts between sender and receiver system
    .  "  CNV_MBT_CHECK_CONFLICT_READ

ABAP code example for Function Module CNV_MBT_CHECK_CONFLICT_READ

The ABAP code below is a full code listing to execute function module CNV_MBT_CHECK_CONFLICT_READ including all data declarations. The code uses 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 original method of declaring data variables up front. 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).

DATA:
it_et_cnvmbtconflicts  
 
 TYPE STANDARD TABLE OF CNVMBTCONFLICTS,"TABLES PARAM
wa_et_cnvmbtconflicts
 
 LIKE LINE OF it_et_cnvmbtconflicts
.

 

SELECT single PACKID 
  FROM CNVMBTPACK 
  INTO @DATA(ld_packid).


DATA(ld_convobject) = 'Check type of data required'.
 

SELECT single STRUCNAME 
  FROM CNVMBTTABLES 
  INTO @DATA(ld_strucname).

 

SELECT single FIELDNAME 
  FROM CNVMBTFORKEY 
  INTO @DATA(ld_fieldname).

 

SELECT single CONFLICT_TYPE 
  FROM CNVMBTCONFLICTS 
  INTO @DATA(ld_conflict_type).

 

SELECT single SOLVED 
  FROM CNVMBTCONFLICTS 
  INTO @DATA(ld_only_not_solved).

 

SELECT single SOLVED 
  FROM CNVMBTCONFLICTS 
  INTO @DATA(ld_only_solved).

 

"populate fields of struture and append to itab
append wa_et_cnvmbtconflicts to it_et_cnvmbtconflicts.
.

CALL FUNCTION 'CNV_MBT_CHECK_CONFLICT_READ'
  EXPORTING
    packid =                     ld_packid
*   convobject =                 ld_convobject
*   strucname =                  ld_strucname
*   fieldname =                  ld_fieldname
*   conflict_type =              ld_conflict_type
*   only_not_solved =            ld_only_not_solved
*   only_solved =                ld_only_solved
  TABLES
    et_cnvmbtconflicts =         it_et_cnvmbtconflicts
    .  "  CNV_MBT_CHECK_CONFLICT_READ

IF SY-SUBRC EQ 0.
  "All OK
ENDIF.

ABAP code to compare 7.40 inline data declaration with original syntax

The below ABAP code uses the older none in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. It may also be useful if you are using an older version of SAP as some of the newer syntax above, such as the @DATA is not available until 4.70 EHP 8.

DATA:

ld_packid
 
 TYPE CNVMBTPACK-PACKID ,
it_et_cnvmbtconflicts
 
 TYPE STANDARD TABLE OF CNVMBTCONFLICTS ,
wa_et_cnvmbtconflicts
 
 LIKE LINE OF it_et_cnvmbtconflicts,
ld_convobject
 
 TYPE CNVMBTCONVOBJECTS ,
ld_strucname
 
 TYPE CNVMBTTABLES-STRUCNAME ,
ld_fieldname
 
 TYPE CNVMBTFORKEY-FIELDNAME ,
ld_conflict_type
 
 TYPE CNVMBTCONFLICTS-CONFLICT_TYPE ,
ld_only_not_solved
 
 TYPE CNVMBTCONFLICTS-SOLVED ,
ld_only_solved
 
 TYPE CNVMBTCONFLICTS-SOLVED .



SELECT single PACKID 
  FROM CNVMBTPACK 
  INTO ld_packid.
 

"populate fields of struture and append to itab
append wa_et_cnvmbtconflicts to it_et_cnvmbtconflicts.
ld_convobject = 'Check type of data required'.

SELECT single STRUCNAME 
  FROM CNVMBTTABLES 
  INTO ld_strucname.


SELECT single FIELDNAME 
  FROM CNVMBTFORKEY 
  INTO ld_fieldname.


SELECT single CONFLICT_TYPE 
  FROM CNVMBTCONFLICTS 
  INTO ld_conflict_type.


SELECT single SOLVED 
  FROM CNVMBTCONFLICTS 
  INTO ld_only_not_solved.


SELECT single SOLVED 
  FROM CNVMBTCONFLICTS 
  INTO ld_only_solved.