SAP CEI4_RUNTIME_OBJECT_CREATE Function Module for NOTRANSL: Prüft, ob zur Klassenart und Klasse Laufzeitobjekte möglich sind
CEI4_RUNTIME_OBJECT_CREATE is a standard cei4 runtime object create 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: Prüft, ob zur Klassenart und Klasse Laufzeitobjekte möglich sind 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 cei4 runtime object create FM, simply by entering the name CEI4_RUNTIME_OBJECT_CREATE into the relevant SAP transaction such as SE37 or SE38.
Function Group: CEI4
Program Name: SAPLCEI4
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CEI4_RUNTIME_OBJECT_CREATE 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 'CEI4_RUNTIME_OBJECT_CREATE'"NOTRANSL: Prüft, ob zur Klassenart und Klasse Laufzeitobjekte möglich sind.
EXPORTING
CLASS_TYPE = "
OBJECT_ID = "
OBJECT = "
IMPORTING Parameters details for CEI4_RUNTIME_OBJECT_CREATE
CLASS_TYPE -
Data type: CUCO-KLARTOptional: No
Call by Reference: No ( called with pass by value option)
OBJECT_ID -
Data type: CUCO-OBTABOptional: No
Call by Reference: No ( called with pass by value option)
OBJECT -
Data type: CUCO-OBJEKOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CEI4_RUNTIME_OBJECT_CREATE 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 | TYPE CUCO-KLART, " | |||
| lv_object_id | TYPE CUCO-OBTAB, " | |||
| lv_object | TYPE CUCO-OBJEK. " |
|   CALL FUNCTION 'CEI4_RUNTIME_OBJECT_CREATE' "NOTRANSL: Prüft, ob zur Klassenart und Klasse Laufzeitobjekte möglich sind |
| EXPORTING | ||
| CLASS_TYPE | = lv_class_type | |
| OBJECT_ID | = lv_object_id | |
| OBJECT | = lv_object | |
| . " CEI4_RUNTIME_OBJECT_CREATE | ||
ABAP code using 7.40 inline data declarations to call FM CEI4_RUNTIME_OBJECT_CREATE
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 KLART FROM CUCO INTO @DATA(ld_class_type). | ||||
| "SELECT single OBTAB FROM CUCO INTO @DATA(ld_object_id). | ||||
| "SELECT single OBJEK FROM CUCO INTO @DATA(ld_object). | ||||
Search for further information about these or an SAP related objects