SAP POSS_UIDEV_OPTCFG_SAVE Function Module for Save selected options
POSS_UIDEV_OPTCFG_SAVE is a standard poss uidev optcfg save SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Save selected options 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 poss uidev optcfg save FM, simply by entering the name POSS_UIDEV_OPTCFG_SAVE into the relevant SAP transaction such as SE37 or SE38.
Function Group: RSPOPOSS
Program Name: SAPLRSPOPOSS
Main Program: SAPLRSPOPOSS
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function POSS_UIDEV_OPTCFG_SAVE 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 'POSS_UIDEV_OPTCFG_SAVE'"Save selected options.
EXPORTING
PRINTERNAME = "Spool: Long device names
EXCEPTIONS
INVALID_PRINTER = 1
IMPORTING Parameters details for POSS_UIDEV_OPTCFG_SAVE
PRINTERNAME - Spool: Long device names
Data type: RSPOLNAMEOptional: No
Call by Reference: Yes
EXCEPTIONS details
INVALID_PRINTER - Printer does not exist (shortname?)
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for POSS_UIDEV_OPTCFG_SAVE 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_printername | TYPE RSPOLNAME, " | |||
| lv_invalid_printer | TYPE RSPOLNAME. " |
|   CALL FUNCTION 'POSS_UIDEV_OPTCFG_SAVE' "Save selected options |
| EXPORTING | ||
| PRINTERNAME | = lv_printername | |
| EXCEPTIONS | ||
| INVALID_PRINTER = 1 | ||
| . " POSS_UIDEV_OPTCFG_SAVE | ||
ABAP code using 7.40 inline data declarations to call FM POSS_UIDEV_OPTCFG_SAVE
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