SAP SLS_COM_SET_COMMENT Function Module for Import Comment
SLS_COM_SET_COMMENT is a standard sls com set comment SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Import Comment 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 sls com set comment FM, simply by entering the name SLS_COM_SET_COMMENT into the relevant SAP transaction such as SE37 or SE38.
Function Group: SLS1
Program Name: SAPLSLS1
Main Program:
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function SLS_COM_SET_COMMENT 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 'SLS_COM_SET_COMMENT'"Import Comment.
EXPORTING
P_EVID = "PAW - Event ID
P_NO_TEM = "PAW - Event either from TEM or not
TABLES
* P_CEVENT = "PAW - PERSON / EVENT / TEST
* P_CXET = "Aggregate Results
* P_CPET = "Result for Item
* P_CRITEM = "Result for Item Multiple Choice
EXCEPTIONS
NO_EVENT_FOUND = 1 NO_TESTID_FOUND = 2 NO_XET_FOUND = 3 NO_PET_FOUND = 4 NO_ITEM_FOUND = 5 WRONG_PARAMETER = 6 SYSTEM_FAILURE = 7
IMPORTING Parameters details for SLS_COM_SET_COMMENT
P_EVID - PAW - Event ID
Data type: SLS_EVENT-EVIDOptional: No
Call by Reference: Yes
P_NO_TEM - PAW - Event either from TEM or not
Data type: SLS_EVENT-NO_TEMOptional: No
Call by Reference: Yes
TABLES Parameters details for SLS_COM_SET_COMMENT
P_CEVENT - PAW - PERSON / EVENT / TEST
Data type: SLS_SCEVEOptional: Yes
Call by Reference: Yes
P_CXET - Aggregate Results
Data type: SLS_SCXETOptional: Yes
Call by Reference: Yes
P_CPET - Result for Item
Data type: SLS_SCPETOptional: Yes
Call by Reference: Yes
P_CRITEM - Result for Item Multiple Choice
Data type: SLS_SCRITEOptional: Yes
Call by Reference: Yes
EXCEPTIONS details
NO_EVENT_FOUND - Event don't exists
Data type:Optional: No
Call by Reference: Yes
NO_TESTID_FOUND - Testid don't exists
Data type:Optional: No
Call by Reference: Yes
NO_XET_FOUND - Event / test (XET) don't exists
Data type:Optional: No
Call by Reference: Yes
NO_PET_FOUND - Event / test / participant (PET) don't exists
Data type:Optional: No
Call by Reference: Yes
NO_ITEM_FOUND - Itemid don't exists
Data type:Optional: No
Call by Reference: Yes
WRONG_PARAMETER - Transfer parameter don't exists
Data type:Optional: No
Call by Reference: Yes
SYSTEM_FAILURE - System failure
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for SLS_COM_SET_COMMENT 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_p_evid | TYPE SLS_EVENT-EVID, " | |||
| lt_p_cevent | TYPE STANDARD TABLE OF SLS_SCEVE, " | |||
| lv_no_event_found | TYPE SLS_SCEVE, " | |||
| lt_p_cxet | TYPE STANDARD TABLE OF SLS_SCXET, " | |||
| lv_p_no_tem | TYPE SLS_EVENT-NO_TEM, " | |||
| lv_no_testid_found | TYPE SLS_EVENT, " | |||
| lt_p_cpet | TYPE STANDARD TABLE OF SLS_SCPET, " | |||
| lv_no_xet_found | TYPE SLS_SCPET, " | |||
| lt_p_critem | TYPE STANDARD TABLE OF SLS_SCRITE, " | |||
| lv_no_pet_found | TYPE SLS_SCRITE, " | |||
| lv_no_item_found | TYPE SLS_SCRITE, " | |||
| lv_wrong_parameter | TYPE SLS_SCRITE, " | |||
| lv_system_failure | TYPE SLS_SCRITE. " |
|   CALL FUNCTION 'SLS_COM_SET_COMMENT' "Import Comment |
| EXPORTING | ||
| P_EVID | = lv_p_evid | |
| P_NO_TEM | = lv_p_no_tem | |
| TABLES | ||
| P_CEVENT | = lt_p_cevent | |
| P_CXET | = lt_p_cxet | |
| P_CPET | = lt_p_cpet | |
| P_CRITEM | = lt_p_critem | |
| EXCEPTIONS | ||
| NO_EVENT_FOUND = 1 | ||
| NO_TESTID_FOUND = 2 | ||
| NO_XET_FOUND = 3 | ||
| NO_PET_FOUND = 4 | ||
| NO_ITEM_FOUND = 5 | ||
| WRONG_PARAMETER = 6 | ||
| SYSTEM_FAILURE = 7 | ||
| . " SLS_COM_SET_COMMENT | ||
ABAP code using 7.40 inline data declarations to call FM SLS_COM_SET_COMMENT
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 EVID FROM SLS_EVENT INTO @DATA(ld_p_evid). | ||||
| "SELECT single NO_TEM FROM SLS_EVENT INTO @DATA(ld_p_no_tem). | ||||
Search for further information about these or an SAP related objects