SAP CRM_TIME_UNIT_CHECK_CB Function Module for Check Whether Time Unit Exists
CRM_TIME_UNIT_CHECK_CB is a standard crm time unit check cb SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Check Whether Time Unit Exists 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 crm time unit check cb FM, simply by entering the name CRM_TIME_UNIT_CHECK_CB into the relevant SAP transaction such as SE37 or SE38.
Function Group: CRM_SERVICE_I_CB
Program Name: SAPLCRM_SERVICE_I_CB
Main Program: SAPLCRM_SERVICE_I_CB
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CRM_TIME_UNIT_CHECK_CB 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 'CRM_TIME_UNIT_CHECK_CB'"Check Whether Time Unit Exists.
EXPORTING
IV_MSEHI = "Service Type
IMPORTING
ES_T006 = "Generated Table for View CRMV_SRV_TYPE
EXCEPTIONS
TIME_UNIT_NOT_FOUND = 1 NO_TIME_UNIT = 2 INPUT_ERROR = 3
IMPORTING Parameters details for CRM_TIME_UNIT_CHECK_CB
IV_MSEHI - Service Type
Data type: MSEHIOptional: No
Call by Reference: Yes
EXPORTING Parameters details for CRM_TIME_UNIT_CHECK_CB
ES_T006 - Generated Table for View CRMV_SRV_TYPE
Data type: T006Optional: No
Call by Reference: Yes
EXCEPTIONS details
TIME_UNIT_NOT_FOUND - Table Entry Was Not Found
Data type:Optional: No
Call by Reference: Yes
NO_TIME_UNIT - No Time Unit
Data type:Optional: No
Call by Reference: Yes
INPUT_ERROR - Import Interface Error
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for CRM_TIME_UNIT_CHECK_CB 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_es_t006 | TYPE T006, " | |||
| lv_iv_msehi | TYPE MSEHI, " | |||
| lv_time_unit_not_found | TYPE MSEHI, " | |||
| lv_no_time_unit | TYPE MSEHI, " | |||
| lv_input_error | TYPE MSEHI. " |
|   CALL FUNCTION 'CRM_TIME_UNIT_CHECK_CB' "Check Whether Time Unit Exists |
| EXPORTING | ||
| IV_MSEHI | = lv_iv_msehi | |
| IMPORTING | ||
| ES_T006 | = lv_es_t006 | |
| EXCEPTIONS | ||
| TIME_UNIT_NOT_FOUND = 1 | ||
| NO_TIME_UNIT = 2 | ||
| INPUT_ERROR = 3 | ||
| . " CRM_TIME_UNIT_CHECK_CB | ||
ABAP code using 7.40 inline data declarations to call FM CRM_TIME_UNIT_CHECK_CB
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