SAP CUD0_OBJECTS_FROM_CLASS Function Module for NOTRANSL: Auflösung eines Klassenknotens
CUD0_OBJECTS_FROM_CLASS is a standard cud0 objects from class 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: Auflösung eines Klassenknotens 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 cud0 objects from class FM, simply by entering the name CUD0_OBJECTS_FROM_CLASS into the relevant SAP transaction such as SE37 or SE38.
Function Group: CUD0
Program Name: SAPLCUD0
Main Program: SAPLCUD0
Appliation area: M
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CUD0_OBJECTS_FROM_CLASS 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 'CUD0_OBJECTS_FROM_CLASS'"NOTRANSL: Auflösung eines Klassenknotens.
EXPORTING
CLASS = "Internal class number
CLASSTYPE = "Class type
OBJECTTYPE = "
* OBLIGATORY = 'X' "
* MULTI_OBJECTS_ALLOWED = ' ' "
DATE = "
PROPERTIES = "
* IV_SOLVE_CONFLICT = ' ' "
TABLES
OBJECTS = "List with the selected objects of the class
EXCEPTIONS
NO_SEARCH = 1 NO_OBJECT_FOUND = 2
Customer Function user exits
Below is a list of CUSTOMER FUNCTION exit user exits that are available within this program and maybe relevant for this FM.EXIT_SAPLCUD0_001 Configuration Decision to Load Configuration from External Source
EXIT_SAPLCUD0_002 Reaction Option to Conflicts When Finding Objects in Class Node
EXIT_SAPLCUD0_003 Time of Initialization for Variant Function Program Environment
IMPORTING Parameters details for CUD0_OBJECTS_FROM_CLASS
CLASS - Internal class number
Data type: KLAH-CLASSOptional: No
Call by Reference: Yes
CLASSTYPE - Class type
Data type: KLAH-KLARTOptional: No
Call by Reference: Yes
OBJECTTYPE -
Data type: TCLAO-OBTABOptional: No
Call by Reference: No ( called with pass by value option)
OBLIGATORY -
Data type: STPO-CLOBKDefault: 'X'
Optional: Yes
Call by Reference: Yes
MULTI_OBJECTS_ALLOWED -
Data type: STPO-CLMULDefault: SPACE
Optional: Yes
Call by Reference: Yes
DATE -
Data type: CABN-DATUVOptional: No
Call by Reference: Yes
PROPERTIES -
Data type: CULLT_PROPERTIESOptional: No
Call by Reference: Yes
IV_SOLVE_CONFLICT -
Data type: CDefault: SPACE
Optional: Yes
Call by Reference: Yes
TABLES Parameters details for CUD0_OBJECTS_FROM_CLASS
OBJECTS - List with the selected objects of the class
Data type: CKSSKOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
NO_SEARCH -
Data type:Optional: No
Call by Reference: Yes
NO_OBJECT_FOUND -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CUD0_OBJECTS_FROM_CLASS 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 | TYPE KLAH-CLASS, " | |||
| lt_objects | TYPE STANDARD TABLE OF CKSSK, " | |||
| lv_no_search | TYPE CKSSK, " | |||
| lv_classtype | TYPE KLAH-KLART, " | |||
| lv_no_object_found | TYPE KLAH, " | |||
| lv_objecttype | TYPE TCLAO-OBTAB, " | |||
| lv_obligatory | TYPE STPO-CLOBK, " 'X' | |||
| lv_multi_objects_allowed | TYPE STPO-CLMUL, " SPACE | |||
| lv_date | TYPE CABN-DATUV, " | |||
| lv_properties | TYPE CULLT_PROPERTIES, " | |||
| lv_iv_solve_conflict | TYPE C. " SPACE |
|   CALL FUNCTION 'CUD0_OBJECTS_FROM_CLASS' "NOTRANSL: Auflösung eines Klassenknotens |
| EXPORTING | ||
| CLASS | = lv_class | |
| CLASSTYPE | = lv_classtype | |
| OBJECTTYPE | = lv_objecttype | |
| OBLIGATORY | = lv_obligatory | |
| MULTI_OBJECTS_ALLOWED | = lv_multi_objects_allowed | |
| DATE | = lv_date | |
| PROPERTIES | = lv_properties | |
| IV_SOLVE_CONFLICT | = lv_iv_solve_conflict | |
| TABLES | ||
| OBJECTS | = lt_objects | |
| EXCEPTIONS | ||
| NO_SEARCH = 1 | ||
| NO_OBJECT_FOUND = 2 | ||
| . " CUD0_OBJECTS_FROM_CLASS | ||
ABAP code using 7.40 inline data declarations to call FM CUD0_OBJECTS_FROM_CLASS
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). | ||||
| "SELECT single KLART FROM KLAH INTO @DATA(ld_classtype). | ||||
| "SELECT single OBTAB FROM TCLAO INTO @DATA(ld_objecttype). | ||||
| "SELECT single CLOBK FROM STPO INTO @DATA(ld_obligatory). | ||||
| DATA(ld_obligatory) | = 'X'. | |||
| "SELECT single CLMUL FROM STPO INTO @DATA(ld_multi_objects_allowed). | ||||
| DATA(ld_multi_objects_allowed) | = ' '. | |||
| "SELECT single DATUV FROM CABN INTO @DATA(ld_date). | ||||
| DATA(ld_iv_solve_conflict) | = ' '. | |||
Search for further information about these or an SAP related objects