SAP ICL_GOS_INSERT_DB Function Module for Note: Insert in DB
ICL_GOS_INSERT_DB is a standard icl gos insert db SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Note: Insert in DB 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 gos insert db FM, simply by entering the name ICL_GOS_INSERT_DB into the relevant SAP transaction such as SE37 or SE38.
Function Group: ICL_GOS_DB
Program Name: SAPLICL_GOS_DB
Main Program: SAPLICL_GOS_DB
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function ICL_GOS_INSERT_DB 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_GOS_INSERT_DB'"Note: Insert in DB.
EXPORTING
I_FOLDER_ID = "SAPoffice: Definition of an Object (Key Part)
I_OBJ_HD_CHANGE = "SAPoffice: object definition, change attributes
I_CLAIM_OBJ = "Object Relationship Service: BOR Object Identifier
* I_ICLPARTOCC = "Claim Participant Occurrence
I_OBJYR = "Object: Year from ID
I_OBJNO = "Object: Number from ID
* I_AUTHGRP = "User Group for Authorizations
CHANGING
C_ICLNOTE = "Claim Note
TABLES
T_OBJCONT = "SAPoffice: line, length 255
IMPORTING Parameters details for ICL_GOS_INSERT_DB
I_FOLDER_ID - SAPoffice: Definition of an Object (Key Part)
Data type: SOODKOptional: No
Call by Reference: No ( called with pass by value option)
I_OBJ_HD_CHANGE - SAPoffice: object definition, change attributes
Data type: SOOD1Optional: No
Call by Reference: No ( called with pass by value option)
I_CLAIM_OBJ - Object Relationship Service: BOR Object Identifier
Data type: BORIDENTOptional: No
Call by Reference: No ( called with pass by value option)
I_ICLPARTOCC - Claim Participant Occurrence
Data type: ICLPARTOCCOptional: Yes
Call by Reference: No ( called with pass by value option)
I_OBJYR - Object: Year from ID
Data type: SOODK-OBJYROptional: No
Call by Reference: No ( called with pass by value option)
I_OBJNO - Object: Number from ID
Data type: SOODK-OBJNOOptional: No
Call by Reference: No ( called with pass by value option)
I_AUTHGRP - User Group for Authorizations
Data type: ICL_AUTHGRPOptional: Yes
Call by Reference: No ( called with pass by value option)
CHANGING Parameters details for ICL_GOS_INSERT_DB
C_ICLNOTE - Claim Note
Data type: ICLNOTEOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for ICL_GOS_INSERT_DB
T_OBJCONT - SAPoffice: line, length 255
Data type: SOLIOptional: No
Call by Reference: Yes
Copy and paste ABAP code example for ICL_GOS_INSERT_DB 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_c_iclnote | TYPE ICLNOTE, " | |||
| lt_t_objcont | TYPE STANDARD TABLE OF SOLI, " | |||
| lv_i_folder_id | TYPE SOODK, " | |||
| lv_i_obj_hd_change | TYPE SOOD1, " | |||
| lv_i_claim_obj | TYPE BORIDENT, " | |||
| lv_i_iclpartocc | TYPE ICLPARTOCC, " | |||
| lv_i_objyr | TYPE SOODK-OBJYR, " | |||
| lv_i_objno | TYPE SOODK-OBJNO, " | |||
| lv_i_authgrp | TYPE ICL_AUTHGRP. " |
|   CALL FUNCTION 'ICL_GOS_INSERT_DB' "Note: Insert in DB |
| EXPORTING | ||
| I_FOLDER_ID | = lv_i_folder_id | |
| I_OBJ_HD_CHANGE | = lv_i_obj_hd_change | |
| I_CLAIM_OBJ | = lv_i_claim_obj | |
| I_ICLPARTOCC | = lv_i_iclpartocc | |
| I_OBJYR | = lv_i_objyr | |
| I_OBJNO | = lv_i_objno | |
| I_AUTHGRP | = lv_i_authgrp | |
| CHANGING | ||
| C_ICLNOTE | = lv_c_iclnote | |
| TABLES | ||
| T_OBJCONT | = lt_t_objcont | |
| . " ICL_GOS_INSERT_DB | ||
ABAP code using 7.40 inline data declarations to call FM ICL_GOS_INSERT_DB
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 OBJYR FROM SOODK INTO @DATA(ld_i_objyr). | ||||
| "SELECT single OBJNO FROM SOODK INTO @DATA(ld_i_objno). | ||||
Search for further information about these or an SAP related objects