SAP Basis Tech Supports

Symptom
The device type wizard in transaction SPAD is suggesting to use a device type, which is not yet available in your system.
The device type (or device driver or code page) is attached to the Printer Vendor Wizard Note (a list of all Printer Vendor Wizard Notes is shown in note 1097990) or the Printer Vendor Wizard Note is pointing to a download area at the printer vendors website.
You want to install the device type / ABAP PDL / code page.
Other terms
PVP, SAP Printer Vendor Program
Solution
Installing Devcie types:
The current procedure to install device types is described in note 6427.
If the device type is developed by an SAP Printer Vendor program gold member, please select the package SPOO when being asked for the package assignment.Installing device drivers:
(Only for label printers using the ABAP plugin method described in note 1097563; drivers for Postscript, PCL, Prescribe, ZPL and ESC/Page are implemented in the SAP kernel)
(For the minimum release,support packages and corrections required to use device drivers read note 1097563).
The procedure to install device drivers is to import the transport files provided by the printer vendor into your main development system via transaction STMS.
Here is an example from a system with SAP_BASIS 6.20 SP 64:
/nstms
–> Menue Overview
–> Imports (F5)
–> Double click on the import queue you want to use
–> Menue Extras
–> Other requests
–> Add
–> Use F4 to select the transport request with the given number
–> Enter
–> Yes
–> Mark the row showing the request
–> Menue Request
–> Import
–> Target client: 000 / Date: Immediate / Execution: Synchronous / Options: check “Leave Transport request in Queue for later import”
–> Enter
–> Import is running.
Please ignore all import warnings. An example of ignorable import warnings is shown in attachment STMS_import_log.htm.
After importing the class and table entries run the attached report Z_ABAP_PDL_ADJUST_TADIR and change the package from TEST_PVP* to an own package so that you will be able to transport the class. Also adjust the orginal system to be your central development system in which you imported the device driver class.
IMPORTANT:SAP recommends to define at least 2 spool work processes on instances that are to convert spool requests via device drivers developed by partner companies.Installing Code Pages:
Please use report RSCP0025 to import the code page definitions and code page segments into your system.