SAP POSS_UIPT_NEW_DEVTYPE Function Module for Device type changed
POSS_UIPT_NEW_DEVTYPE is a standard poss uipt new devtype SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Device type changed 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 uipt new devtype FM, simply by entering the name POSS_UIPT_NEW_DEVTYPE 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_UIPT_NEW_DEVTYPE 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_UIPT_NEW_DEVTYPE'"Device type changed.
EXPORTING
PRINTERNAME = "Spool: Long device names
NEW_DEVTYPE = "Spool: Device type name
EXCEPTIONS
PRINTER_NO_OPTIONS = 1
IMPORTING Parameters details for POSS_UIPT_NEW_DEVTYPE
PRINTERNAME - Spool: Long device names
Data type: RSPOLNAMEOptional: No
Call by Reference: Yes
NEW_DEVTYPE - Spool: Device type name
Data type: RSPOPTYPEOptional: No
Call by Reference: Yes
EXCEPTIONS details
PRINTER_NO_OPTIONS - Printer has no options
Data type:Optional: No
Call by Reference: Yes
Copy and paste ABAP code example for POSS_UIPT_NEW_DEVTYPE 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_printer_no_options | TYPE RSPOLNAME, " | |||
| lv_new_devtype | TYPE RSPOPTYPE. " |
|   CALL FUNCTION 'POSS_UIPT_NEW_DEVTYPE' "Device type changed |
| EXPORTING | ||
| PRINTERNAME | = lv_printername | |
| NEW_DEVTYPE | = lv_new_devtype | |
| EXCEPTIONS | ||
| PRINTER_NO_OPTIONS = 1 | ||
| . " POSS_UIPT_NEW_DEVTYPE | ||
ABAP code using 7.40 inline data declarations to call FM POSS_UIPT_NEW_DEVTYPE
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