Printing problem: device type?driver?

Hello friends.
There is a Smartfrom "Transfer Order label" that contains some plain text and also bar code (new bar code technology). Printers Epson LQ-1900KII are used.
While printing if the user selects LOCL printer (of device type SAPWIN, frontend printer), then in frontend, in Windows selects the proper "LQ-1900KII", the Label is printed correctly with bar code. So phisycally the printer can print the label correctly.
Now we need to create in SAP logical printer, that is assigned directly to the proper "LQ-1900KII". I tried the standard epson device type 'EPESCP', but it supplies only several font-sizes and doesn't supply new bar codes. So the label is printed, but the size of characters is incorrect and the bar code is not printed at all.
Do you have any ideas regarding which device type can I use? Or if I need to create a new one, than with wich driver?
Thank you.

Hi,
please look at this
[http://help.sap.com/saphelp_nw70/helpdata/EN/d9/4a956151ea11d189570000e829fbbd/content.htm]
New device type
[http://help.sap.com/saphelp_nw70/helpdata/EN/d9/4a956e51ea11d189570000e829fbbd/content.htm]
Regards,
Muralidhar

Similar Messages

Print Adobe PDF problem: Device type related?

Hi,
we have developed a number of adobe print forms and we face a problem. The problem is that not all types of printers can directly print (without first preview the pdf) the form.
We are using an output device with device type post2 (pdf1 works for some printers too) and access method F (Printing on Frontend computer) , but some printers work perfectly and others instead of the form, print out some postscript (or print) commands.
We can as well change our printers and get some postscipt printers but the problem is that we want to give access and print the forms some of our partners who logon to our system via VPN and we cannot "force" them to buy new printers.
Do you have any suggestion for this problem?
Thanx in advance
Kostas

the ABAP Backend is sending a ADS-document in an XML format to the ADS Server (JAVA), the ADS returns a "Parts" for the forms. A "parts" consist of an PDF file and a print file (PostScript, PCL or ZPL), which are placed in the Global Directory. All the conversion should take place within the ADS Server.
This "Parts" are then send as a PDF to the SAP Spooler.
For the printing of this PDF document in the SAP Spool System one of the Device types (POST2, HPLJ4, HP9500, PDF1, AZPL203, AZPL300) is taken into account which send the actual PDF to a physical printer.
What you see in SP01 are the "parts" of an ADS-document.
Report RSPO0020 (for troubleshooting ADS printing issues) is displaying the "Parts", send back from ADS to the backend System
The XDC file is the printer description in XML format, which the Adobe Document Services requires in order to create the "Parts" file. PDF documents can only be printed on printers of SAP device types for which there is an XDC file on the Adobe Document Server. Report RSPO0022 can be used to manage the mapping between the printer device type and the XDC file
Nesimi

Printer setting - Device type unsuitable for ADS documents - reg

Hai Expert
I am trying to generate print preview, From 16, I am getting error "Device type unsuitable for ADS documents"
guide me to where have to do corrections
Regards
Vincent

May be you should try the right forum:
pk

PDF Print: Using Device Type PDF1 to output SAPscript forms

Hi all,
I'm trying to create a e-mail with pdf attachment using the info from the note 323736.
I'm hable to send some mails with attachment, but I'm not hable to add the device type created in a smartform print and send automatically through e-mail.
It gives the following error:
"Device type PDF1 does not support page format DINA4."
Does anyone know the possible page formats or how to enalbe DINA4 as a possible format to send via PDF?
Any ideas?
Regards,
Pedro
Edited by: Pedro Taveira on Aug 6, 2009 4:53 PM

Hi Pedro,
Transaction SPAD, Click 'Full Administration' then the 'Devce Types' tab. Then display the device types.
Find your device type in the list and choose 'Formats', this will list the formats for this device type.
Regards,
Nick

Print Preview of smartform with device type EPESCP9

Hi all,
I have created a z smartform to print commercial invoice.
I am using dot matrix print Epson FX-2170 to print invoice.
For this printer the device type is EPESCP9.
So I created an output device having device type EPESCP9.
I have assigned the required Format type to the device type and the page format which is assigned in the smarform to the Format type.
But I am not getting any print preview of the invoice when I select this output device.
I am only able to get print preview when I select an ouput device having device type SAPWIN.
Please provide solution to get preview in device type EPESCP9.
Edited by: Vinod Iyer on Apr 24, 2008 6:08 PM

Hi,
1.I think You are assigned the Printer details in SPAD.
2.The page format and Printer settings are correctly done ,then it will come.But,the main problem is ,the page format is not supposed to match.Please check that page format in smrtform and Printer settings.
3.If posible see those settings in I18n also.
Regards,
Shiva.

ABAP list printing on device I2SWIN

Hello,
we have defined output device (printer) with device type I2SWIN for printing on users frontend computers via SAPlpd. Settings of I2SWIN device type is default:
SAPlpd/SAPWIN driver 3.0
Do not use printer driver for ABAP list print
Character set 1406 Printer I2SWIN ISO 8859-2 (MS Windows Latin-2)
We can print ABAP lists on this device. We define formats and set margins and orientation in this formats. But these settings are ignored during printing. If we change in I2SWIN setting Printer driver to "Printer driver for SWIN printing using SAPLP/Windows", then margins are accepted and printed, but there are wrong characters in print output (not in requested code page).
Could anybody help us how to set print to accept margins in ABAP lists and also have print output with good code page.
Thank you
Vaclav Jonas
Edited by: Vaclav Jonas on Apr 24, 2008 3:02 PM

O.K., we use margin settings according SAP Note 21738 and all works fine.

Printing problem with script barcode

hi ,
     i hav inserted a barcode for a particular window field. while giving print preview it is showing barcode.
     after taking print, it is not displaying the barcode.
   thank u all in advance,
balu.

Hello,
In general, if you want to print a barcode, somebody must draw the bars
of the barcode to get a correct print. So there are four possible ways to
print barcodes from SAP:
1. Print e.g. via a Barcode DIMM/SIMM
To use this way, the printer must be able to print barcodes by itself so it
needs e.g. a special barcode SIMM/DIMM module to print the barcodes.
ie: HP printers do not contain barcode fonts by default so a DIMM module
with the fonts must be installed. The print works as follows:
The SAP sends a simple printer escape sequence to the printer, which activates
the barcode printing in the printer. Then the SAP sends the barcode number and
finally it sends a printer escape sequence, which switches the printer back to
normal printing. So in this way the bars of the barcode are created in the printer
(and you only see a dummy barcode in the print preview).
Please see the following Note about the sequences for Jetcaps BarDIMM used
for printing barcodes on HP Laserjet printers:
45643 Barcode control sequences for JetCAPS/Jetmobile BarDIMM
The correct BarDIMM modules for different HP printer models can be seen on
the JetMobile website at the URL below:
http://www.jetmobile.com/products/SJ_BD.htm
2. Print via a barcode.dll
If your printer doesn't have a barcode DIMM, it cannot create the bars of
the barcode itself. So this must be done elsewhere. One possibility is that
you print via a Windows system, SAPSprint or SAPLPD, device type SAPWIN and
a barcode.dll.
ie: Your printer is connected to a Windows system that runs the SAPSprint or SAPLPD program
If you print via device type SAPWIN, the creation of the print data is done in the Windows.
So the Windows may create a graphic, which contains the bars of the barcode, and send this
graphic to the printer.
The job to create the barcode graphic is done by the barcode.dll. So it is only needed, if
you want to print this way please see the following note for more information:
14561 Printing barcodes via SAPLPD / Barcode DLL
3. New barcode technology
If your printer doesn't have a barcode DIMM and if you don't want to use a barcode.dll,
you may use the new barcode technology, which is described in the SAP notes 645158 and 430887.
However this is only possible when printing from Smartforms.
In this way SAP itself creates a picture, which contains the bars of the barcode. This picture
is sent to the printer. One important requirement when you print the barcode via a Smartform
is that you have at least release 46C.
4. Use of a barcode font
There are some font files (e.g. Windows TTF files), which contains bars instead of characters.
So if you use these font files, the bars of the barcode are printed instead of a text.
You may buy such a font file, install it under Windows and use it via device type SAPWIN
according to note 48803. Since release 46C these files can also be uploaded into the SAP and
used via other device types.
Hope this information helps you resolve the issue.
Regards,
David

Problem importing printer device type using RSTXSCRP

Hello,
Referring to sapnote 8928 I have extracted 6 printer device types that I wish to import into our dev box.
(note: I am trying this on our sandbox first).
However, the readme instructions for performing the import using RSTXSCRP are out of date or not complete for all SAP versions. For one they refer to a radio button that does not exist in our version of . (note: RSTXSCRP is also the ABAP called when doing the import from SPAD).
In addition, when attempting the import, I receive a popup box requesting a package. Since I have never used packages I am at a loss. There is no option to create a new one, as when I created transports back when I did ABAP.
I can save these as local objects, but they are then not transportable. I wish to be able to transport these through the landscape as they go to production. I really do not want to do a bunch of individual imports in every system, since I would need to do so for R3, BW, APO, etc.
So long into short: How do I import printer device types using either RSTXSCRP or SPAD and have them transportable?

Prabhu, Thank you, but this does not answer the question. It only repeats the information I already have.
How do I enter the package information when I do not have it, do not know how to get it or how to create a new one.
I have been out of directly working with SAP for a couple years and have only recently returned.
This is apparently such a basic thing it is not even in any of the documentation I can find.

Device Type SAPWIN giving problem

Dear Colleagues,
I need to print a cheque from different printers as they are in diffrent locations.For that i copied the device type SAPWIN Driver 3.0 to ZSAPWIN in SPAD as this is the generic driver for all types of printer.
Now my problem is that as i have the customised size of the cheque like 23 CM X 95 MM.It means that i need the height of the cheque of around 21 Lines Aprrox.
For that i need to code in the hexadecimal format in Printer Initialization in \e%SAPWIN% stream.
For that i need a code to set the page size/height so that the printer will take the page of that height and not pull the entire page and it should follow the SAPWIN Data protocol.
Thanks

Hi Siddharth,
Maybe what you can do is create a new page format like 'ZCHECK' whith the size as '23 CM X 95 MM'.
Assign this format in smartform or script you are creating.
After this you create a format type 'ZCHECK' in SPAD.
And then attach this format type 'ZCHECK' to locl printer i.e. ZSAPWIN.
Make sure that the page format and the format type are of same name.
It will start working if you follow this.
Hope this helps.I tried this for me and it worked.
Sushil

Which device type support Unicode printing ?

Hi all,
Do you know which cascading font device types support Customer-defined true type fonts ?
I use HP LaserJet printer. I've imported ZSWINCF device type in to SAP system and installed some true type fonts required for my report. It's able to print <b>Unicode </b>text in ABAP List but unable in SAPScript/Smartform printing.
I also try to use ZHPUTF8 or HPUTF8, and install these fonts. But i've problem in printing out.
Do you know how to resolve this problem ?
Thanks,
Best regards,

Hi
see this OSS notes may be useful
OSSNote:960341
Symptom
In some device types (e.g HPLJ4, HPLJ5) you experience non-uniform character spacing in the PDF document after the PDF conversion of SAPscript or Smart Forms documents, using HELVE or TIMES fonts. You want to know the reason.
Other terms
CONVERT_OTF, SAPscript, Smart Forms
Reason and Prerequisites
The problem is not due to an error in the PDF converter but due to the fact, that the printer font, underlying the device type (e.g. Univers or CG Times in PCL-5 device types), is not available for the PDF converter and is either not available in Adobe Reader. The PDF converter has to try to simulate the layout of the printer font by means of a font which is predefined in Adobe Reader. This is done by assigning the letter widths of the printer font to the font used in Adobe Reader.
The PDF file contains a table with letter widths, used by Adobe Reader in the output of text, for each used printer font (except PostScript fonts).
Example:
%Charwidth values from HP4300 HELVE 060 normal
/Widths
[ 278 333 500 633 633 1000 758 333 333 333 633...
Adobe reader converts this width table, by modifying the space between each character, so that the specified letter width (= space between the current and the next letter) is kept.
This 'Simulation' of printer fonts results in the sometimes visible irregular spaces in PDF.
The PDF converter always uses the Helvetica Adobe PostScript font for the display of HELVE and the Times Roman Adobe PostScript font for the display of TIMES. However, for these Adobe PostScript fonts, Adobe Reader often uses a Windows TrueType font, which differs slightly from the original PostScript font.
Solution
Workaround: Use the POST2 PostScript device type or the PDF1 PDF device type for the PDF conversion of documents in the Latin-1 character set. They both use the Adobe PostScript fonts Helvetica or Times Roman for the HELVE/TIMES printer fonts.
Header Data
Release Status: Released for Customer
Released on: 30.06.2006 12:44:06
Priority: Recommendations/additional info
Category: Consulting
Primary Component: BC-CCM-PRN Print and Output Management
Secondary Components: BC-SRV-SCR SAPscript
OSS Note: 776507
Symptom
Documents printed via SAPscript or SmartForms do not print with correct special characters, e.g. ### prints instead of Japanese or Russian characters. What to do?
Other terms
SAPscript, SmartForms, printing, device types, OTF
Reason and Prerequisites
Help required to choose proper fonts in a SAPscript or SmartForm
Solution
When using SAPscript or SmartForms to print (or email or fax) a form from a business application, many factors influence the outcome of the actual text within the form. All these factors must be checked in order to ensure a correct printout:
1) The language version of the form used to produce the printout.
Example: If you want to print a French invoice, you need to have a FR version of your SAPscript or SmartForms invoice form RVINVOICE01. And the application program must specify the corresponding language key (FR) when calling the SAPscript or SmartForms API.
2) The font selections specified in the form (possibly also in a SAPscript style or SmartStyle used in a form).
Example: In a SAPscript form or a SmartStyle you need to specify HELVE if you want to print German text in Helvetica (or similar) font. If you want to print Japanese text, HELVE is not a valid choice but you need to specify a Japanese font like JPMINCHO in your Japanese form.
3) The output character set of the device type
Every printer in transaction SPAD has a "device type" assigned. Device types used by the spooler for printing support only one single specific output character set. All text from the form has to be converted (using SAP's built-in character conversion mechanism) to this output character set.
A character set can typically support either a single language (e.g. Shift-JIS which supports only Japanese) or a set of languages (e.g. ISO 8859-1, which supports Western-European languages). It is possible that a given language (such as German) can be supported by several output character sets, e.g. you may use either ISO 8895-1 (Latin-1) or ISO 8859-2 (Latin-2) to represent German text. This is so because both character sets contain the special characters used in German.
Example: HPLJ4000 is a HP LaserJet device type supporting the ISO 8859-1 (Latin-1) character set. ISO 8859-1 can be used to represent e.g. Dutch, English, French, German, Spanish, Swedish but NOT Russian or Japanese.
As a consequence, it is ok to use HPLJ4000 to print English, German French etc. but not for Japanese or Russian.
4) The set of available printer fonts for a given device type
When formatting a document, SAPscript and SmartForms perform an automatic mapping of the font definitions in the form (e.g. "HELVE 14 point bold") and the available printer fonts of the device type. A replacement printer font is chosen, should the specified font selection not be available in the device type. Now this replacement can be problematic if a language-specific font, such as Chinese CNSONG, is specified in a form and it gets replaced by a font which does not support this language, e.g. COURIER.
To solve this problem, font families in SE73 have language attribute assigned, e.g. some fonts are characterized as being suitable only for certain languages. And when a replacement has to be chosen because the original font from the form is not available in the device type, a replacement font is chosen which has the same language attributes.
If no fonts for the language in question exist in the device type, the resulting font will not be able to print the special characters and you will see "wrong" output characters in the printout.
Note on SAPscript/SmartForms Print Preview:
The OTF Print Preview available in Windows GUI (e.g. from transaction SP01) will sometimes not show the "wrong" characters which appear on the final printout. Here is the reason: since the Print Preview runs in Windows environment, it will use Windows fonts to represent the actual printer fonts. A Windows font typically has more available characters (i.e. covers more character sets) than are actually available in a printer's resident font.
A typical example where the Print Preview will differ from the printout is here: if you have a Chinese PCL5 printer such as CNHPLJ4 and use the Western Latin font COURIER in your document, the print preview will show you Chinese characters if you (by accident) tried to format Chinese characters in COURIER font. This is because Windows will automatically choose a font that can output Chinese characters (which is actually not Courier). But when you print the job on an actual PCL5 printer with resident Western and Chinese fonts, the Courier font will not print any Chinese characters but Western special characters instead, because the printer's resident Courier font does not include Chinese characters.
Rule of thumb: all Asian device types (e.g. CNHPLJ4, JPHPLJ4, JPPOST, KPHPLJ4) support not only Asian fonts but also COURIER, HELVE and TIMES fonts. But these Latin fonts can only be used to print English text, not Chinese/Japanese/Korean characters.
Which fonts are suitable for a given language?
Language(s):            Font family to use in a form:
Latin-1 (Western Europe/Americas) *******
DE,EN,FR,ES,NL,SV       COURIER, HELVE, TIMES
                        (LETGOTH, LNPRINT)
Latin-2 (Central Europe) ****************
PL, CZ                  COURIER, HELVE, TIMES
ISO 8859-4 (Baltic) *********************
ET, LT, LV              COURIER, HELVE, TIMES
ISO 8859-5 (Cyrillic) *******************
BG, RU, SR, UK          COURCYR, HELVCYR, TIMECYR
ISO 8859-7 (Greek) **********************
EL                      COUR_I7, HELV_I7, TIME_I7
ISO 8859-8 (Hebrew) *********************
HE                      COURIER, HELVE, TIMES
ISO 8859-9 (Turkish) ********************
TR                      COURIER, HELVE, TIMES
Simplified Chinese **********************
ZH                      CNHEI, CNKAI, CNSONG
Japanese ********************************
JA                      JPMINCHO, DBMINCHO, DBGOTHIC
Korean **********************************
KP                      KPBATANG, KPDODUM, KPGULIM
                        KPGUNGSE, KPSAMMUL
Traditional Chinese *********************
ZF                      TWDPHEI, TWMING, TWSONG
Thai ************************************
TH                      THANGSAN, THDRAFT, THVIJIT
Arabic (Unicode systems only) ***********
AR                      ANDALE_J
Verify your output by examining the OTF data
When analysing printing problems of this type, be sure to check the OTF data which gets produced by SAPscript or SmartForms. OTF or "Output Text Format" is the intermediate page-description format generated from SAPscript or SmartForms. OTF will contain the final printer font names and character set/language identifiers which help to solve the problem. OTF will even name the form and the language of the form used to create the output.
The easiest way to do this is to create a spool request from your application, run transaction SP01, use menu
Goto->Display Requests->Settings
and choose
Display Mode: Raw
Now display your spool request. If this is a SAPscript or SmartForms spool request, you will see OTF data. Each line represents one OTF command, every command starts with a 2-character cmd identifier and possibly some cmd parameters follow.
Here is an excerpt from a sample OTF file where we highlight the most interesting commands:
//XHPLJ8000    0700 00000000001
IN04EALEXTEST_ZEBRA
IN05%PAGE1
OPDINA4 P 144 240 1683811906000010000100001
IN06%WINDOW2
MT0024401289
CP11000000E
FCHELVE 120 00109XSF100SF101110000067E X
UL +0000000000000
SW00067
CT00000000
ST0453037Dieses SF hat Stil ALEXTEST_ZEBRA mit
The 1st line with the // (Control) command reveals the device type usedto print: HPLJ8000
//XHPLJ8000    0700 00000000001
The 2nd line (IN = Info command) shows the name and (internal 1-char)language key of the form:
IN04EALEXTEST_ZEBRA
In this case it is the English (E = EN) SmartForm ALEXTEST_ZEBRA
The OP-line (OP = Open Page) gives the page format used in the form, it is DINA4 Portrait orientation:
OPDINA4 P 144 240 1683811906000010000100001
The CP (CodePage) cmd shows the SAP system codepage used to code the text and the active language. In our case it is codepage 1100 and language E = EN = English.
CP11000000E
Finally, the FC-cmd (Font Call) lists a printer font selected within SmartForms. Please note that every SmartForm has a designated default SmartStyle under "Form Attributes->Output Options". In addition, every text node can have a SmartStyle attached (which will override the definitions from the default style for the text). In our case the resulting printer font that was selected is HELVE 12.0 pt bold-off, italic-off.
FCHELVE   120 00109XSF100SF101110000067E X
Header Data
Release Status: Released for Customer
Released on: 22.08.2005 09:57:20
Priority: Recommendations/additional info
Category: Customizing
Primary Component: BC-CCM-PRN Print and Output Management
Secondary Components: BC-SRV-SCR SAPscript
BC-SRV-SSF Smart Forms
<b>Reward points for useful Answers</b>
Regards
Anji

URGENT: Smartform - Attaching Font to Device Type and Printing

Hello Smarform Gurus,
I have uploaded CORPOS font to SAP and using in SMARTFORMS. Whenever the PDF is called for invoice, it should print immediately.
When I open the smartform and then print, the printout is coming fine with CORPOS font.
Problem: When Invoice is created and PDF is called immediately, the prinout is not coming properly. It's because the printer device type KYOFS150 we are using does not support CORPOS. Pls let me know the options we have. We have also referred to SAP note 12462.
Thanks in advance,
Abhishek

Hi
U need to update the printer device type KYOFS150 or use another one supports that font
Max

Printing a new format page in Matrix Printer with the SAPWIN Device Type...

Hi,
The requierements is to print Identification Material Labels with an Epson DFX-8500 printer. The label font is TIMES 34, therefore the Printer Device Type is SAPWIN. The real throuble is that label size (Format Page) doesn't exist.
I created a New Format Page but when a print the Materlal Label (SAPSCRIPT), the SPAD configuration isn't recognized. I need an Height of 432 PT (Like INCH6 because the paper is continuous form) isn't recognized.
Could somebody help me???
Alexis Sánchez N.
SAP ABAP Development Consultant
<< removed >>
Valencia, Venezuela
Edited by: Rob Burbank on May 25, 2010 3:56 PM

Hi all,
I solved myself... This is the way...
I have an Epson Matrix Printer (Epson DFX-8500)
In SAP, I created the Epson DFX-8500 Printer with the device type SAPWIN. This printer have some attributes in windows operational system (Windows XP). One of this attributes is the default paper size (Letter).
To change this, you have to do what the SAP Note 163136 (Creating new paper size for Windows NT-2000-XP-2003) says:
Solution
Note: This note is based on Note Q157172 from the Microsoft Knowledge Base.
You create a new paper size this way in Windows NT:
1. Choose 'Control Panel' and double-click 'Printer'.
2. Select 'Server Properties' in the 'File' menu.
3. Select the 'Create A New Form' check box on the 'Forms' tab page.
4. Enter the settings for the new paper size.
NOTE : If you set up your own customized paper size, the margins
cannot exceed the settings of the installed printer. The print area
must correspond to the margin settings of the printer driver used.
5. Save the paper size.
Proceed as follows to use the new paper size as the default format:
1. Select 'Printer' in the 'Control Panel'.
2. Click the right mouse button to select the required printer and select
'Document defaults'.
3. Select the new paper size in the 'Paper Size' selection box (on the
'Advanced' tab page).
4. Click OK.
5. Again with the right mouse button click the required printer and
select 'Attributes'.
6. Open the 'Device Settings' tab page and select the paper tray from
which you should print. Then select the new paper size.
NOTE: New paper sizes are stored on the computer on which they were
created. If you create a new paper size for a shared printer, you must
create the new paper size on the printer's print server.
NOTE : In Windows XP, there is an error in this procedure that can be
corrected with Note Q838298 from the Microsoft Knowledge Base.
I hope it helps you...
Alexis Sánchez N.
SAP ABAP Development Consultant
Valencia, Venezuela

WFMC_PREPARE_SMART_FORM - device type problem

Hi,
I have created the logical destination "ZMAIL" to send a mail for vendor address.
It's working fine in ME21N/ME22N. if we go to ME9F then it's goes to print it's not sending a mail.
I'm using the FM "WFMC_PREPARE_SMART_FORM".
In ME21N/ME22N, pe_device value is 'MAIL'
In ME9F, pe_device valie is 'PRINTER.' (It's wrong)
On what basis, This function module select the device type. how to change it.
Thanks with Regards,
Vallamuthu M

Hi,
Try to check the FM logic for ME9F execution, i can see that there is a call to one FM ADDR_GET_NEXT_COMM_TYPE to get the communication type based on the TCODE (different Communication Strategy's can be defined in SAP). And then based on the communication type your Communiation device can be determined in another FM - CONVERT_COMM_TYPE_DATA.
Hope it can help you to understand the problem.
Br..
Dwaraka

ZHANWIN device type does not print Korean characters

Hi All,
We are trying to print smart forms containing Chinese,Taiwanese and Korean characters from our ECC 6.0
As per SAP Note 1038413 - Unicode SAPWIN device type for CJK fon, we used the device type ZHANWIN to print smart forms for these characters.
But with this device type we are unable to print smart forms with Korean characters. But as per the note, it has to support Korean characters too.
Please help with this issue.
Thanks and Regards,
Subashree

Hi Subashree,
it is likely that the problem with ZHANWIN is related to the font used in the form. if you want to print Korean characters via ZHANWIN, you need to specify a Korean font like KPBATANG for the Korean characters in the form. Then this will be mapped to a suitable windows font in windows. If you chosse e.g font COURIER , it is mapped to windosw font Courier New which does nto contain the Korean characters.
For SWINCF or SWINCFCK the font in SAP is not so impertant. The mapping of the characters in windows is based on the Unicode character range. So as Nils said, SWINCFCK should work regardless of the font in the SAP form.
Regards,
Aidan

Device type for printer types

Hello,
Could you please tell me the device type for these 2 SAP printer types:
HP Color Laserjet CP1515n
Triumph adler DC 2218
I searched for these, but without any success.
Thank you for your help in advance,
Noemi

Hi,
You can refer to the SAP note 8928 and solve your problem.
Good luck
Tao

Printing problem: device type?driver?

Similar Messages

Maybe you are looking for