SAP ICLE_ACT_CNV_DB2GUI_SINGLE Function Module for Convert DB Structure to GUI Structure (Activity Log)
ICLE_ACT_CNV_DB2GUI_SINGLE is a standard icle act cnv db2gui single 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 DB Structure to GUI Structure (Activity Log) 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 icle act cnv db2gui single FM, simply by entering the name ICLE_ACT_CNV_DB2GUI_SINGLE into the relevant SAP transaction such as SE37 or SE38.
Function Group: ICLE_CMC_EXT
Program Name: SAPLICLE_CMC_EXT
Main Program: SAPLICLE_CMC_EXT
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ICLE_ACT_CNV_DB2GUI_SINGLE 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 'ICLE_ACT_CNV_DB2GUI_SINGLE'"Convert DB Structure to GUI Structure (Activity Log).
EXPORTING
IS_DB = "Claim Activity
IMPORTING
ES_GUI = "Screen Fields for Activities
IMPORTING Parameters details for ICLE_ACT_CNV_DB2GUI_SINGLE
IS_DB - Claim Activity
Data type: ICLEACTIVITYOptional: No
Call by Reference: Yes
EXPORTING Parameters details for ICLE_ACT_CNV_DB2GUI_SINGLE
ES_GUI - Screen Fields for Activities
Data type: ICLE_ACTIVITY_EXTOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for ICLE_ACT_CNV_DB2GUI_SINGLE 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_is_db | TYPE ICLEACTIVITY, " | |||
| lv_es_gui | TYPE ICLE_ACTIVITY_EXT. " |
|   CALL FUNCTION 'ICLE_ACT_CNV_DB2GUI_SINGLE' "Convert DB Structure to GUI Structure (Activity Log) |
| EXPORTING | ||
| IS_DB | = lv_is_db | |
| IMPORTING | ||
| ES_GUI | = lv_es_gui | |
| . " ICLE_ACT_CNV_DB2GUI_SINGLE | ||
ABAP code using 7.40 inline data declarations to call FM ICLE_ACT_CNV_DB2GUI_SINGLE
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