SAP CCM_HAB_EV_OBJ_CREATE_FAILED Function Module for Saves objects which couldn't be instantiated in internal data
CCM_HAB_EV_OBJ_CREATE_FAILED is a standard ccm hab ev obj create failed SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Saves objects which couldn't be instantiated in internal data 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 ccm hab ev obj create failed FM, simply by entering the name CCM_HAB_EV_OBJ_CREATE_FAILED into the relevant SAP transaction such as SE37 or SE38.
Function Group: CCM2_HIDDEN_ACTION_BOX
Program Name: SAPLCCM2_HIDDEN_ACTION_BOX
Main Program: SAPLCCM2_HIDDEN_ACTION_BOX
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CCM_HAB_EV_OBJ_CREATE_FAILED 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 'CCM_HAB_EV_OBJ_CREATE_FAILED'"Saves objects which couldn't be instantiated in internal data.
EXPORTING
HANDLE = "
TABLES
T1 = "
IMPORTING Parameters details for CCM_HAB_EV_OBJ_CREATE_FAILED
HANDLE -
Data type: CIC0_HANDLEOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for CCM_HAB_EV_OBJ_CREATE_FAILED
T1 -
Data type: EWCPOBJOptional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CCM_HAB_EV_OBJ_CREATE_FAILED 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: | ||||
| lt_t1 | TYPE STANDARD TABLE OF EWCPOBJ, " | |||
| lv_handle | TYPE CIC0_HANDLE. " |
|   CALL FUNCTION 'CCM_HAB_EV_OBJ_CREATE_FAILED' "Saves objects which couldn't be instantiated in internal data |
| EXPORTING | ||
| HANDLE | = lv_handle | |
| TABLES | ||
| T1 | = lt_t1 | |
| . " CCM_HAB_EV_OBJ_CREATE_FAILED | ||
ABAP code using 7.40 inline data declarations to call FM CCM_HAB_EV_OBJ_CREATE_FAILED
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