SAP CMS_API_BAPI_GUID_CONV_C32_R16 Function Module for Convert GUID: CHAR32 to RAW16
CMS_API_BAPI_GUID_CONV_C32_R16 is a standard cms api bapi guid conv c32 r16 SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Convert GUID: CHAR32 to RAW16 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 cms api bapi guid conv c32 r16 FM, simply by entering the name CMS_API_BAPI_GUID_CONV_C32_R16 into the relevant SAP transaction such as SE37 or SE38.
Function Group: CMS_API_BAPI_GENERAL
Program Name: SAPLCMS_API_BAPI_GENERAL
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function CMS_API_BAPI_GUID_CONV_C32_R16 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 'CMS_API_BAPI_GUID_CONV_C32_R16'"Convert GUID: CHAR32 to RAW16.
EXPORTING
I_GUID32 = "UUID in character form
IMPORTING
E_GUID16 = "UUID in X form (binary)
IMPORTING Parameters details for CMS_API_BAPI_GUID_CONV_C32_R16
I_GUID32 - UUID in character form
Data type: SYSUUID-COptional: No
Call by Reference: Yes
EXPORTING Parameters details for CMS_API_BAPI_GUID_CONV_C32_R16
E_GUID16 - UUID in X form (binary)
Data type: SYSUUID-XOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for CMS_API_BAPI_GUID_CONV_C32_R16 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_e_guid16 | TYPE SYSUUID-X, " | |||
| lv_i_guid32 | TYPE SYSUUID-C. " |
|   CALL FUNCTION 'CMS_API_BAPI_GUID_CONV_C32_R16' "Convert GUID: CHAR32 to RAW16 |
| EXPORTING | ||
| I_GUID32 | = lv_i_guid32 | |
| IMPORTING | ||
| E_GUID16 | = lv_e_guid16 | |
| . " CMS_API_BAPI_GUID_CONV_C32_R16 | ||
ABAP code using 7.40 inline data declarations to call FM CMS_API_BAPI_GUID_CONV_C32_R16
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 X FROM SYSUUID INTO @DATA(ld_e_guid16). | ||||
| "SELECT single C FROM SYSUUID INTO @DATA(ld_i_guid32). | ||||
Search for further information about these or an SAP related objects