SAP ICL_WRITE_TABLE_ENTRY_GUID Function Module for Write GUID of Table Entry









ICL_WRITE_TABLE_ENTRY_GUID is a standard icl write table entry guid SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Write GUID of Table Entry 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 icl write table entry guid FM, simply by entering the name ICL_WRITE_TABLE_ENTRY_GUID into the relevant SAP transaction such as SE37 or SE38.

Function Group: ICL_CLAIM_ASSIGN
Program Name: SAPLICL_CLAIM_ASSIGN
Main Program: SAPLICL_CLAIM_ASSIGN
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:



Function ICL_WRITE_TABLE_ENTRY_GUID 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 'ICL_WRITE_TABLE_ENTRY_GUID'"Write GUID of Table Entry
EXPORTING
IV_CLAIM = "Number of Claim
IV_TABLENAME = "Table Name of Link Source
IV_OBJECT = "
* IV_DATABASE = "Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')

IMPORTING
EV_GUID = "UUID of Source Entry of a Link

EXCEPTIONS
ENTRY_NOT_FOUND = 1
.



IMPORTING Parameters details for ICL_WRITE_TABLE_ENTRY_GUID

IV_CLAIM - Number of Claim

Data type: ICL_CLAIM
Optional: No
Call by Reference: Yes

IV_TABLENAME - Table Name of Link Source

Data type: ICL_SOURCE_TABNAME
Optional: No
Call by Reference: Yes

IV_OBJECT -

Data type: DATA
Optional: No
Call by Reference: Yes

IV_DATABASE - Data Element for BOOLE Domain: TRUE (='X') and FALSE (=' ')

Data type: BOOLE_D
Optional: Yes
Call by Reference: Yes

EXPORTING Parameters details for ICL_WRITE_TABLE_ENTRY_GUID

EV_GUID - UUID of Source Entry of a Link

Data type: ICL_SOURCE_GUID
Optional: No
Call by Reference: Yes

EXCEPTIONS details

ENTRY_NOT_FOUND - Entry not found

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for ICL_WRITE_TABLE_ENTRY_GUID 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_ev_guid  TYPE ICL_SOURCE_GUID, "   
lv_iv_claim  TYPE ICL_CLAIM, "   
lv_entry_not_found  TYPE ICL_CLAIM, "   
lv_iv_tablename  TYPE ICL_SOURCE_TABNAME, "   
lv_iv_object  TYPE DATA, "   
lv_iv_database  TYPE BOOLE_D. "   

  CALL FUNCTION 'ICL_WRITE_TABLE_ENTRY_GUID'  "Write GUID of Table Entry
    EXPORTING
         IV_CLAIM = lv_iv_claim
         IV_TABLENAME = lv_iv_tablename
         IV_OBJECT = lv_iv_object
         IV_DATABASE = lv_iv_database
    IMPORTING
         EV_GUID = lv_ev_guid
    EXCEPTIONS
        ENTRY_NOT_FOUND = 1
. " ICL_WRITE_TABLE_ENTRY_GUID




ABAP code using 7.40 inline data declarations to call FM ICL_WRITE_TABLE_ENTRY_GUID

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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!