SAP EXIT_SAPLCUD0_002 Function Module for Reaction Option to Conflicts When Finding Objects in Class Node









EXIT_SAPLCUD0_002 is a standard exit saplcud0 002 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Reaction Option to Conflicts When Finding Objects in Class Node 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 exit saplcud0 002 FM, simply by entering the name EXIT_SAPLCUD0_002 into the relevant SAP transaction such as SE37 or SE38.

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



Function EXIT_SAPLCUD0_002 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 'EXIT_SAPLCUD0_002'"Reaction Option to Conflicts When Finding Objects in Class Node
  EXPORTING
   CLASS_NAME =  "Class Name
   CLASS_TYPE =  "Class Type
   OBJECT_TYPE =  "Object Type
   DATE =  "
   OBLIGATORY =  "Object Required for Class Node
   MULTI_OBJECTS_ALLOWED =  "Multiple Objects Allowed for Class Node

TABLES
   SELECTION_CRITERIA =  "Value Selection (Entry)
   OBJECTS =  "Objects (Display)
   VALUES_OF_OBJECTS =  "Values for Objects (Display)
.



Related Function Modules

Below is a list of related SAP function modules this CUSTOMER FUNCTION exit / user exit is relevant for.
CUD0_CLASSIFICATION_AS_KB NOTRANSL: Klassifikation als Beziehungswissen darstellen
CUD0_CONFIGURATION_FROM_DB NOTRANSL: Lesen der Konfigurationsdaten einer Instanz
CUD0_CONFIGURATION_HAS_OBJECT NOTRANSL: Liefert zur CUOBJ die dazugehörende Objektinformation
CUD0_CONFIGURATION_INITIALIZER NOTRANSL: Konfiguration: Initialisierung
CUD0_CONFIGURATION_TO_DB NOTRANSL: Konfigurationsdaten zu einer Instanz sichern
CUD0_CONFIGURE_CHARACTERISTICS NOTRANSL: Konfiguration von Merkmalen
CUD0_CONFIGURE_OBJECT NOTRANSL: Konfiguration eines Objektes
CUD0_CUSTOM_CONFIG_INITIALIZER NOTRANSL: Aufruf des Customer Exit 003
CUD0_DDB_CONFIGURATION_FINISH NOTRANSL: Beendet die Konfiguration einer Instanz
CUD0_DDB_CONFIGURATION_INIT NOTRANSL: DDB: Zu einem konfigurierbaren Objekt wird die DDB aufgebaut
CUD0_DISPLAY_KNOWLEDGE NOTRANSL: Anzeige von Wissensdaten
CUD0_GET_CHARACTERISTICS NOTRANSL: Bereitstellung von Merkmalen und Werten für eine Instanz
CUD0_GET_IDDBI_INSTANCE NOTRANSL: Check bzw. Aufbau der IDDBI
CUD0_GET_SETTING_EXTERNAL_LOAD NOTRANSL: Konfiguration Entscheidung Laden Konfiguration aus externer Quel
CUD0_GET_VAL_FROM_INSTANCE NOTRANSL: Bereitstellung von Merkmalen und Werten für eine Instanz
CUD0_INIT_NUMBER_INSTANCE NOTRANSL: Initialisierung von NUMBER_INSTANCE
CUD0_IS_CONFIG_INITIALIZED NOTRANSL: Prüft, ob die Konfiguration bereits initialisiert ist
CUD0_KB_GET_MASTER_DATA NOTRANSL: Stellt der Konf.-DDB zu einem Objektmerkmal den Stammdatenwert z
CUD0_LOADING_KNOWLEDGEBASE NOTRANSL: Laden der Wissensbasis
CUD0_LOAD_INSTANCE NOTRANSL: Laden einer Konfiguration
CUD0_MAKE_INSTANCE_CL_SYSTEM Creates an Instance
CUD0_MAKE_NEW_CUOBJ_INSTANCE NOTRANSL: Vergibt eine neue cUOBJ-Instanz
CUD0_OBJECTS_FROM_CLASS NOTRANSL: Auflösung eines Klassenknotens
CUD0_OBJECT_HAS_MODEL NOTRANSL: Liefert zu einem Objekt das Konfigurationsmodell
CUD0_PROJ_ON_PURCH_MATNR_CLASS NOTRANSL: Projiziert die MMwerte in CUOBJ auf Klasse von purch_matnr (name
CUD0_PR_GET_AT_MSGS NOTRANSL: Restliche Präsentationsmeldungen einer Instanz
CUD0_PR_HAS_AT_MSGS NOTRANSL: Restliche Präsentationsmeldungen einer Instanz
CUD0_SET_OBJECT_AREA NOTRANSL: Übergabe der Objekte für die Objektmerkmale berücksichtigt werde
CUD0_SET_VAL_TO_INSTANCE NOTRANSL: Setzt Merkmale und Werte zu einer Instanz
CUD0_SOLVE_CLASS_NODE_CONFLICT NOTRANSL: Customer-Exit bei Konflikt Objektsuche Klassenknoten rufen
CUD0_STATUS_FROM_CONFIGURATION NOTRANSL: Statusinformation der vorliegenden Konfiguration

IMPORTING Parameters details for EXIT_SAPLCUD0_002

CLASS_NAME - Class Name

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

CLASS_TYPE - Class Type

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

OBJECT_TYPE - Object Type

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

DATE -

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

OBLIGATORY - Object Required for Class Node

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

MULTI_OBJECTS_ALLOWED - Multiple Objects Allowed for Class Node

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

TABLES Parameters details for EXIT_SAPLCUD0_002

SELECTION_CRITERIA - Value Selection (Entry)

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

OBJECTS - Objects (Display)

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

VALUES_OF_OBJECTS - Values for Objects (Display)

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

Copy and paste ABAP code example for EXIT_SAPLCUD0_002 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_class_name  TYPE KLAH-CLASS, "   
lt_selection_criteria  TYPE STANDARD TABLE OF COMW, "   
lt_objects  TYPE STANDARD TABLE OF CLOBJ, "   
lv_class_type  TYPE KLAH-KLART, "   
lv_object_type  TYPE TCLAO-OBTAB, "   
lt_values_of_objects  TYPE STANDARD TABLE OF AUSP, "   
lv_date  TYPE D, "   
lv_obligatory  TYPE STPO-CLOBK, "   
lv_multi_objects_allowed  TYPE STPO-CLMUL. "   

  CALL FUNCTION 'EXIT_SAPLCUD0_002'  "Reaction Option to Conflicts When Finding Objects in Class Node
    EXPORTING
         CLASS_NAME = lv_class_name
         CLASS_TYPE = lv_class_type
         OBJECT_TYPE = lv_object_type
         DATE = lv_date
         OBLIGATORY = lv_obligatory
         MULTI_OBJECTS_ALLOWED = lv_multi_objects_allowed
    TABLES
         SELECTION_CRITERIA = lt_selection_criteria
         OBJECTS = lt_objects
         VALUES_OF_OBJECTS = lt_values_of_objects
. " EXIT_SAPLCUD0_002




ABAP code using 7.40 inline data declarations to call FM EXIT_SAPLCUD0_002

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 CLASS FROM KLAH INTO @DATA(ld_class_name).
 
 
 
"SELECT single KLART FROM KLAH INTO @DATA(ld_class_type).
 
"SELECT single OBTAB FROM TCLAO INTO @DATA(ld_object_type).
 
 
 
"SELECT single CLOBK FROM STPO INTO @DATA(ld_obligatory).
 
"SELECT single CLMUL FROM STPO INTO @DATA(ld_multi_objects_allowed).
 


Search for further information about these or an SAP related objects



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!