SAP LIS_SSV_MODIFY_CONFIGURATION Function Module for
LIS_SSV_MODIFY_CONFIGURATION is a standard lis ssv modify configuration 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 lis ssv modify configuration FM, simply by entering the name LIS_SSV_MODIFY_CONFIGURATION into the relevant SAP transaction such as SE37 or SE38.
Function Group: LIS_UPD
Program Name: SAPLLIS_UPD
Main Program:
Appliation area: S
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function LIS_SSV_MODIFY_CONFIGURATION 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 'LIS_SSV_MODIFY_CONFIGURATION'".
EXPORTING
* IV_INSERT = ' ' "
* IT_COMDES = "LIS: Destination Table
* IT_COMDESC = "LIS: Distinct Landscapes
* IT_COMDESU = "LIS: Users for Generation
* IT_COMDESP = "LIS: User Profiles
* IT_DOMAIN = "LIS: Domain Attributes
* IT_DOMAINT = "LIS: Domain Short Texts
* IT_SYSTEM = "LIS: System Attributes
* IT_SYSTEMT = "LIS: System Short Texts
* IT_PARAM = "LIS: Additional Parameters for Systems
* IT_SYSCOM = "LIS: Additional Parameters for Systems
* IT_LOGSYS = "LIS: Logical Systems
* IT_PROD = "LIS: Calculated Product Versions
IMPORTING Parameters details for LIS_SSV_MODIFY_CONFIGURATION
IV_INSERT -
Data type: CDefault: ' '
Optional: Yes
Call by Reference: No ( called with pass by value option)
IT_COMDES - LIS: Destination Table
Data type: LISCOMDESSOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_COMDESC - LIS: Distinct Landscapes
Data type: LISCOMDESCSOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_COMDESU - LIS: Users for Generation
Data type: LISCOMDESUSOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_COMDESP - LIS: User Profiles
Data type: LISCOMDESPSOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_DOMAIN - LIS: Domain Attributes
Data type: LISDOMAINSOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_DOMAINT - LIS: Domain Short Texts
Data type: LISDOMAINTSOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_SYSTEM - LIS: System Attributes
Data type: LISSYSTEMSOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_SYSTEMT - LIS: System Short Texts
Data type: LISSYSTEMTSOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_PARAM - LIS: Additional Parameters for Systems
Data type: LISPARAMSSOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_SYSCOM - LIS: Additional Parameters for Systems
Data type: LISSYSCOMSOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_LOGSYS - LIS: Logical Systems
Data type: LISLOGSYSSOptional: Yes
Call by Reference: No ( called with pass by value option)
IT_PROD - LIS: Calculated Product Versions
Data type: LISPRODSOptional: Yes
Call by Reference: No ( called with pass by value option)
Copy and paste ABAP code example for LIS_SSV_MODIFY_CONFIGURATION 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_iv_insert | TYPE C, " ' ' | |||
| lv_it_comdes | TYPE LISCOMDESS, " | |||
| lv_it_comdesc | TYPE LISCOMDESCS, " | |||
| lv_it_comdesu | TYPE LISCOMDESUS, " | |||
| lv_it_comdesp | TYPE LISCOMDESPS, " | |||
| lv_it_domain | TYPE LISDOMAINS, " | |||
| lv_it_domaint | TYPE LISDOMAINTS, " | |||
| lv_it_system | TYPE LISSYSTEMS, " | |||
| lv_it_systemt | TYPE LISSYSTEMTS, " | |||
| lv_it_param | TYPE LISPARAMSS, " | |||
| lv_it_syscom | TYPE LISSYSCOMS, " | |||
| lv_it_logsys | TYPE LISLOGSYSS, " | |||
| lv_it_prod | TYPE LISPRODS. " |
|   CALL FUNCTION 'LIS_SSV_MODIFY_CONFIGURATION' " |
| EXPORTING | ||
| IV_INSERT | = lv_iv_insert | |
| IT_COMDES | = lv_it_comdes | |
| IT_COMDESC | = lv_it_comdesc | |
| IT_COMDESU | = lv_it_comdesu | |
| IT_COMDESP | = lv_it_comdesp | |
| IT_DOMAIN | = lv_it_domain | |
| IT_DOMAINT | = lv_it_domaint | |
| IT_SYSTEM | = lv_it_system | |
| IT_SYSTEMT | = lv_it_systemt | |
| IT_PARAM | = lv_it_param | |
| IT_SYSCOM | = lv_it_syscom | |
| IT_LOGSYS | = lv_it_logsys | |
| IT_PROD | = lv_it_prod | |
| . " LIS_SSV_MODIFY_CONFIGURATION | ||
ABAP code using 7.40 inline data declarations to call FM LIS_SSV_MODIFY_CONFIGURATION
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.| DATA(ld_iv_insert) | = ' '. | |||
Search for further information about these or an SAP related objects