
Correcting Severe Output Problems
A severe output problem means your output device printed something, but the result is illegible. The wrong character set may have been used (for example, Dingbats was printed instead of alphanumeric characters). Line breaks, page breaks, or the text layout may be incorrect. Uninterpreted printer command language statements may have been printed. Or the printer may print blank pages.
If a severe problem occurs, check for the following settings:
Choose Tools

The device definition for a Kyocera printer incorrectly specifies device type HPLJIIID (which is for a Hewlett-Packard LaserJet printer).
Many printers support multiple emulations; these printers are able to understand multiple printer languages. Emulations are switched either by an incoming print job or by way of the printer control panel. Example: a correctly-configured Hewlett-Packard LaserJet 4M printer can be switched between PostScript and PCL-5 emulations.
Do the following:
Choose Tools
If the printer default cannot be changed, can you change the R/3 output device definition to match the printer default?
You can specify that the R/3 System sets the printer to the correct emulation at the start of each output request. To do this, copy the R/3 device type. Then, in the INIT (printer initialization) action, enter the required print command to switch the emulation. Look in your printer manual for the command to enter. The R/3 System automatically restores the default emulation at the end of a print request.
For more information, see

You specify that your Hewlett-Packard printer starts in PCL-4 emulation mode (Hewlett-Packard LaserJet printer command language). However, the printer definition in the R/3 System specifies the device type POSTSCPT for the printer. This results in the following: The R/3 System sends PostScript code to a printer that is expecting commands in the PCL-4 language.
You can solve the problem in any of the following ways:
Using the WinCharSet parameter, you can specify the character set and font to be used with SWIN (device type) printers. Generally, the WinCharSet parameter should not be included in the WIN.INI file or, if included, it should be set to 0.
If all SWIN output requests are printed using the wrong character set (Dingbats, for example), check the WIN.INI file. If the parameter WinCharSet is included, remove it from the file.
For more information, see