SAP KCK_COMMENT_ATTACHMENT_GET Function Module for
KCK_COMMENT_ATTACHMENT_GET is a standard kck comment attachment get 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 kck comment attachment get FM, simply by entering the name KCK_COMMENT_ATTACHMENT_GET into the relevant SAP transaction such as SE37 or SE38.
Function Group: KCCT
Program Name: SAPLKCCT
Main Program:
Appliation area: K
Release date: N/A
Mode(Normal, Remote etc): Remote-Enabled
Update:

Function KCK_COMMENT_ATTACHMENT_GET 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 'KCK_COMMENT_ATTACHMENT_GET'".
EXPORTING
I_ATTACHMENT_ID = "
IMPORTING
E_FILE_NAME = "
E_OBJ_TYPE = "
E_OBJ_DESCR = "
E_DOC_SIZE = "
TABLES
OBJECT_CONTENT = "
EXCEPTIONS
ATTACHMENT_NOT_EXIST = 1 OPERATION_NO_AUTHORIZATION = 2 PARAMETER_ERROR = 3 ENQUEUE_ERROR = 4
IMPORTING Parameters details for KCK_COMMENT_ATTACHMENT_GET
I_ATTACHMENT_ID -
Data type: SOATTLSTI1-ATTACH_IDOptional: No
Call by Reference: No ( called with pass by value option)
EXPORTING Parameters details for KCK_COMMENT_ATTACHMENT_GET
E_FILE_NAME -
Data type: CFFILE-FILENAMEOptional: No
Call by Reference: No ( called with pass by value option)
E_OBJ_TYPE -
Data type: SOFOLENTI1-OBJ_TYPEOptional: No
Call by Reference: No ( called with pass by value option)
E_OBJ_DESCR -
Data type: SOFOLENTI1-OBJ_DESCROptional: No
Call by Reference: No ( called with pass by value option)
E_DOC_SIZE -
Data type: SOFOLENTI1-DOC_SIZEOptional: No
Call by Reference: No ( called with pass by value option)
TABLES Parameters details for KCK_COMMENT_ATTACHMENT_GET
OBJECT_CONTENT -
Data type: SOLISTI1Optional: No
Call by Reference: No ( called with pass by value option)
EXCEPTIONS details
ATTACHMENT_NOT_EXIST -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
OPERATION_NO_AUTHORIZATION -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
PARAMETER_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
ENQUEUE_ERROR -
Data type:Optional: No
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for KCK_COMMENT_ATTACHMENT_GET 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_file_name | TYPE CFFILE-FILENAME, " | |||
| lt_object_content | TYPE STANDARD TABLE OF SOLISTI1, " | |||
| lv_i_attachment_id | TYPE SOATTLSTI1-ATTACH_ID, " | |||
| lv_attachment_not_exist | TYPE SOATTLSTI1, " | |||
| lv_e_obj_type | TYPE SOFOLENTI1-OBJ_TYPE, " | |||
| lv_operation_no_authorization | TYPE SOFOLENTI1, " | |||
| lv_e_obj_descr | TYPE SOFOLENTI1-OBJ_DESCR, " | |||
| lv_parameter_error | TYPE SOFOLENTI1, " | |||
| lv_e_doc_size | TYPE SOFOLENTI1-DOC_SIZE, " | |||
| lv_enqueue_error | TYPE SOFOLENTI1. " |
|   CALL FUNCTION 'KCK_COMMENT_ATTACHMENT_GET' " |
| EXPORTING | ||
| I_ATTACHMENT_ID | = lv_i_attachment_id | |
| IMPORTING | ||
| E_FILE_NAME | = lv_e_file_name | |
| E_OBJ_TYPE | = lv_e_obj_type | |
| E_OBJ_DESCR | = lv_e_obj_descr | |
| E_DOC_SIZE | = lv_e_doc_size | |
| TABLES | ||
| OBJECT_CONTENT | = lt_object_content | |
| EXCEPTIONS | ||
| ATTACHMENT_NOT_EXIST = 1 | ||
| OPERATION_NO_AUTHORIZATION = 2 | ||
| PARAMETER_ERROR = 3 | ||
| ENQUEUE_ERROR = 4 | ||
| . " KCK_COMMENT_ATTACHMENT_GET | ||
ABAP code using 7.40 inline data declarations to call FM KCK_COMMENT_ATTACHMENT_GET
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 FILENAME FROM CFFILE INTO @DATA(ld_e_file_name). | ||||
| "SELECT single ATTACH_ID FROM SOATTLSTI1 INTO @DATA(ld_i_attachment_id). | ||||
| "SELECT single OBJ_TYPE FROM SOFOLENTI1 INTO @DATA(ld_e_obj_type). | ||||
| "SELECT single OBJ_DESCR FROM SOFOLENTI1 INTO @DATA(ld_e_obj_descr). | ||||
| "SELECT single DOC_SIZE FROM SOFOLENTI1 INTO @DATA(ld_e_doc_size). | ||||
Search for further information about these or an SAP related objects