SAP CUDB_SET_CONFLICT Function Module for NOTRANSL: Anlegen einer Konfliktmeldung zur DDB

Search SAP Function Modules

CUDB_SET_CONFLICT is a standard cudb set conflict SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for NOTRANSL: Anlegen einer Konfliktmeldung zur DDB 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 cudb set conflict FM, simply by entering the name CUDB_SET_CONFLICT into the relevant SAP transaction such as SE37 or SE38.

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

Function CUDB_SET_CONFLICT 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 'CUDB_SET_CONFLICT'"NOTRANSL: Anlegen einer Konfliktmeldung zur DDB
  EXPORTING
   KNTYPE =  "Knowledge area causing conflict message
   SEGM =  "Knowledge segment
   AUTHOR =  "Author
   TRIGGER =  "Facts that cause conflict

EXCEPTIONS
   INTERNAL_ERROR = 1 

.

IMPORTING Parameters details for CUDB_SET_CONFLICT

KNTYPE - Knowledge area causing conflict message

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

SEGM - Knowledge segment

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

AUTHOR - Author

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

TRIGGER - Facts that cause conflict

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

EXCEPTIONS details

INTERNAL_ERROR - Processing Errors

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

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

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