SAP CNV_CMIS_GET_CONFLICTS_CONFIG Function Module for CMIS: get configuration table for conflicts
CNV_CMIS_GET_CONFLICTS_CONFIG is a standard cnv cmis get conflicts config SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for CMIS: get configuration table for conflicts 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 cmis get conflicts config FM, simply by entering the name CNV_CMIS_GET_CONFLICTS_CONFIG into the relevant SAP transaction such as SE37 or SE38.
Function Group: CNV_CMIS_M_10
Program Name: SAPLCNV_CMIS_M_10
Main Program: SAPLCNV_CMIS_M_10
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:
Function CNV_CMIS_GET_CONFLICTS_CONFIG 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_CMIS_GET_CONFLICTS_CONFIG'"CMIS: get configuration table for conflicts.
EXPORTING
IV_PACK = "Package Number to Specify CMIS and TDMS Packages
IMPORTING
ET_CONFIG_TAB = "CMIS: table type for CNVCMIS_CONFIG
IMPORTING Parameters details for CNV_CMIS_GET_CONFLICTS_CONFIG
IV_PACK - Package Number to Specify CMIS and TDMS Packages
Data type: CNVMBTPACK-PACKIDOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for CNV_CMIS_GET_CONFLICTS_CONFIG
ET_CONFIG_TAB - CMIS: table type for CNVCMIS_CONFIG
Data type: CNV_CMIS_CONFIG_TABOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CNV_CMIS_GET_CONFLICTS_CONFIG 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_iv_pack | TYPE CNVMBTPACK-PACKID, " | |||
lv_et_config_tab | TYPE CNV_CMIS_CONFIG_TAB. " |
  CALL FUNCTION 'CNV_CMIS_GET_CONFLICTS_CONFIG' "CMIS: get configuration table for conflicts |
EXPORTING | ||
IV_PACK | = lv_iv_pack | |
IMPORTING | ||
ET_CONFIG_TAB | = lv_et_config_tab | |
. " CNV_CMIS_GET_CONFLICTS_CONFIG |
ABAP code using 7.40 inline data declarations to call FM CNV_CMIS_GET_CONFLICTS_CONFIG
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 PACKID FROM CNVMBTPACK INTO @DATA(ld_iv_pack). | ||||
Search for further information about these or an SAP related objects