SAP CRM_DATES_GET_DESCRIPTION_CB Function Module for
CRM_DATES_GET_DESCRIPTION_CB is a standard crm dates get description cb SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used to perform a specific ABAP function and below is the pattern details, 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 dates get description cb FM, simply by entering the name CRM_DATES_GET_DESCRIPTION_CB into the relevant SAP transaction such as SE37 or SE38.
Function Group: CRM_DATES_CB
Program Name: SAPLCRM_DATES_CB
Main Program: SAPLCRM_DATES_CB
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CRM_DATES_GET_DESCRIPTION_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_DATES_GET_DESCRIPTION_CB'".
EXPORTING
* IV_PROCESS_TYPE = "Business Transaction Type
* IV_REF_GUID = "GUID of a CRM Order Object
* IV_REF_KIND = "Object Type
IS_LOGICAL_DATE_KEY = "Logical key in date definition
IMPORTING
EV_DESCRIPTION = "Descriptive Text
EXCEPTIONS
ERROR_OCCURRED = 1 DATETYPE_NOT_FOUND = 2
IMPORTING Parameters details for CRM_DATES_GET_DESCRIPTION_CB
IV_PROCESS_TYPE - Business Transaction Type
Data type: CRMT_PROCESS_TYPEOptional: Yes
Call by Reference: Yes
IV_REF_GUID - GUID of a CRM Order Object
Data type: CRMT_OBJECT_GUIDOptional: Yes
Call by Reference: Yes
IV_REF_KIND - Object Type
Data type: CRMT_OBJECT_KINDOptional: Yes
Call by Reference: Yes
IS_LOGICAL_DATE_KEY - Logical key in date definition
Data type: CRMT_DATE_LOGICAL_DATE_KEYOptional: No
Call by Reference: Yes
EXPORTING Parameters details for CRM_DATES_GET_DESCRIPTION_CB
EV_DESCRIPTION - Descriptive Text
Data type: TIMEDESCOptional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ERROR_OCCURRED -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
DATETYPE_NOT_FOUND -
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for CRM_DATES_GET_DESCRIPTION_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_error_occurred | TYPE STRING, " | |||
| lv_ev_description | TYPE TIMEDESC, " | |||
| lv_iv_process_type | TYPE CRMT_PROCESS_TYPE, " | |||
| lv_iv_ref_guid | TYPE CRMT_OBJECT_GUID, " | |||
| lv_datetype_not_found | TYPE CRMT_OBJECT_GUID, " | |||
| lv_iv_ref_kind | TYPE CRMT_OBJECT_KIND, " | |||
| lv_is_logical_date_key | TYPE CRMT_DATE_LOGICAL_DATE_KEY. " |
|   CALL FUNCTION 'CRM_DATES_GET_DESCRIPTION_CB' " |
| EXPORTING | ||
| IV_PROCESS_TYPE | = lv_iv_process_type | |
| IV_REF_GUID | = lv_iv_ref_guid | |
| IV_REF_KIND | = lv_iv_ref_kind | |
| IS_LOGICAL_DATE_KEY | = lv_is_logical_date_key | |
| IMPORTING | ||
| EV_DESCRIPTION | = lv_ev_description | |
| EXCEPTIONS | ||
| ERROR_OCCURRED = 1 | ||
| DATETYPE_NOT_FOUND = 2 | ||
| . " CRM_DATES_GET_DESCRIPTION_CB | ||
ABAP code using 7.40 inline data declarations to call FM CRM_DATES_GET_DESCRIPTION_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