As-built in smartforms
Hello!
I create a report with materials in smartforms. Those of materials that are connected with as-built I can't unload into my report. Other works good.
How can I solve this problem?
Regards,
Alexander.
Hi Alexander,
Could you elaborate Beriefly?
Similar Messages
-
BAR CODES in smartforms - conversion problems to PDF
Hello,
I have a problem. Have a look at the following points and see what I have done:
1. I generated several different system bar codes using SM73
2. I added those system bar codes to a smartformstyle
3. and built a smartform using smartformstyle of system-bar codes.
4. then I made some examples of bar codes in the smartform as text.
5. next I sent this smartform via email as an pdf attachment using smartform mail functionality.
6. shocking - all bar codes in the pdf-file are not readable. You can see that there is a barcode placed, but all barcodes looks like the same.
Has somebody got a idea on what is going on here?
I already had a look at OSS Notes 430887 and 645158.
Greetings
danielHi,
Please can you have a look at Sap OSS Note 197177.
Regards,
Sudheer. -
How to find which Smartform it display
Dear Experts,
I display print preview in t-code VA23 to show my quotation report ,
and this report built by smartform ,
How could I find which smartform form it use?
Thanks a lot in advanced.
YacoaTransaction NACE -> Select Application V1 -> Click Output Type -> Select your output type from the list -> Click on Process routines, you will see the smartform that is assigned to your output type
To see which output type is assigned to your Form, in VA23/VA22, click on Extras -> Output -> Header -> Edit. You will then see list of output types triggered, one of which will be for the printing through smartform -
Hi,
In my company we both have internal and external certificates associated with users who has been on either internal or external course.
The internal certificates are generated in the SAP while the external are given to the persons after ended course.
We are looking at the best way of having these certificates uploaded to the backend and tied to the P-object. Does any of you have expierence with this? What is SAP best practice on this area?
We are looking at either, Archive Link, DMS or Record Management - please advice or share your expierence
Best regards
JakobHi Jakob,
We built a custom infotype to allow the administrator to define which certificate should be associated with a particular course type. Our certificates are built as SMARTFORMs, and we also provide a custom page in LSO which allows learners to view/print their certificates on their own. Certificates appear as PDF files, and we have logic to automatically populate the SMARTFORMS with the appropriate information (e.g. course title, date, instructor name (if classroom training), company logo, etc.). We also included logic in producing the certificate based on delivery method; for example, if the training was classroom based, it would include the location, but ignore this information if the delivery method is location independent (e.g. WBT or Virtual Training).
Hope this helps.
Gary -
Printing barcode in HP laser jet through smartform
Hi folks,
can i print barcode in HP laser jet P3005 PCL6 by using smartform???
plz advice.
regards
smitaYes, you can.. I guess, HP laser jet P3005 series PCL6 can print bar codes.
I am attaching the list of BARCODE supported printers
List of device types in SAP Releases 4.6x/6.xx/NW04/NW04s
OSS NOTE : 8928
Installation of new device types ********************
Many device types are appended as a zip-attachment to this note.
README.TXT contains information about these device types and codepages.
README_UPLOAD.TXT contains information on how to import the device
types.
PRINTER DRIVERS AND DEVICE TYPES:
In R/3, a distinction is made between "printer driver" and "device type". The device type consists of all the attributes defined for an output device. For correct access, these must be made known in the R/3 system. They cover aspects such as control commands for font selection, page size, character set selection, character set used and so on. One of these attributes is the printer driver to be used by SAPscript (R/3 forms processor) for this particular printer.
If your printer is not specified in the list below, ask the manufacturer if the printer is compatible with one of the defined printers or if it can be used with another emulation (for example, Postscript).
If the printer is not compatible or cannot be operated using an emulation, you must create a new device type (if the printer is not compatible). To print from SAPscript, you must choose one of the existing printer drivers.
At present, there are five SAPscript printer drivers. They include:
for HP-PCL5 (for example, HP Laserjet 3,4,5,6 series)
for PostScript printers (PS level 2)
for PRESCRIBE (for example, Kyocera FS-1500)
for device types SWIN/SAPWIN/xxSWIN/xxSAPWIN
for all other models.
The last driver is known as the "standard driver". It cannot provide absolutely precise positioning on the paper and does not support proportional fonts. Printer drivers are relevant for forms output with SAPscript. For the output of ABAP lists special printer drivers are only used as of Release 4.5A. They are anchored in the C kernel and are developed and maintained exclusively by SAP.
In the spool environment, device types refer not only to printers but also other output devices, for example, fax machines. Device types support specific printers or printer models. Device type definitions are stored completely in tables and can be individually adapted, modified or enhanced. If SAP performs such an adjustment for a customer, it constitutes a consulting service, and is generally charged seperately. On the other hand, the list of device types, above all in conjunction with SAP's hardware partners, is continually expanded.
COMPATIBLE PRINTERS:
Some printer models have been so successful on the market that many OEM products, clones and compatibles are also listed. You can often use compatible printers with R/3 by entering the printer definition of the original. Since complete compatibility is extremely rare, SAP can offer no assurances regarding the usability of compatible printers. This also applies to follow-up models made by the original producer.
LIST OF PRINTERS:
This is the list of device types supplied by SAP in different Releases. Most of these device types use "Western European" or "North American" character sets. Some device types in newer Releases however, also support other character sets and language areas such as Russian or Czech.
The device types named in this list are supported in the standard R/3 System as of the release mentioned.
If an OCR-A font (prerequisite for check printing) or an OCR-B font is supported in the R/3 device types, this is indicated. However, this generally requires additional font cassettes or firmware for the printer involved, since few printers have an OCR-A font "built in." For additional information about this, contact the printer manufacturer.
Check related notes attached for addition information on printer supportin R/3.
Related notes:
Note 135894 contains information on printing labels on special label printers.
Note 05196 contains information on printing bar codes with SAPscript
Note 94233 contains information on printing MICR font with SAPscript
Note 62178 contains information on device types for the Japanese version of the R/3 System.
Note 77891 contains information on device types for IBM-SCS printers on the IBM AS/400 hardware platform.
Note 98477 informs you on device types for printers by the manufacturer PSi.
Note 107938 contains information on device types for printers by the producer Tally.
Note 141719 contains information on device types for printers from the producer Printronix.
Note 141914 contains information on device types for printers from the producer Lexmark.
Note 153879 contains information on compatible printer models of producer EPSON.
Note 154494 contains information on compatible printer models of producer Genicom.
Note 199166 contains information on device types for printers from the producer Hewlett Packard.
Note 214187 contains information on device types for printers from the producer Océ.
Note 398236 contains information on device types for printers from the producer Sharp.
Note 408189 contains information on device types for printers from the producer Konica Minolta.
Note 436609 contains information on device types for printers from the producer Xerox.
Note 458047 contains information on device types for printers from the producer Ricoh.
Note 485240 contains information on device types for printers from the producer SAVIN.
Note 485244 contains information on device types for printers from the producer NRG.
Note 516687 contains information on device types for printers from the producer Lanier.
Note 516669 contains information on device types for printers from the producer Gestetner.
Note 878109 contains information on device types for printers from the producer Danka.
ASCIIPRI
Generic device type for line printers that can be used in urgent cases where no customized printer definition exists for a line printer. It contains no printer-specific control commands, but merely CARRIAGE RETURN, NEWLINE and FORMFEED commands. It uses the standard 7 bit ASCII character set (USASCII).
COMPU960
Device type for BULL line printers COMPUPRINT 4/66, as well as COMPUPRINT 960. Character set used: IBM 2 German.
DECLA75P
Device type for the DEC line printer DEC LA75 Plus.
DECLN07
Device type for the DEC laser printers LN07 and DECLaser 1100.
HP256X
Device type for all Hewlett-Packard line printers in the HP256... series. Based on the HP manual describing the HP256X series, OCR-A is included in this printer definition, but the printer needs an additional firmware/font cassette.
HP2930
Device type for Hewlett-Packard's HP2930 line printer.
HPDJ500
Device type for Hewlett-Packard's DeskJet 500 ink jet printer.
HPLJIIID
Device type for Hewlett-Packard's LaserJet IIIP, III, IIID and IIIsi printers, as well as the HP LaserJet 4 series. OCR-A and OCR-B are included in the printer definition, but the printer needs an additional firmware/font cassette. The "HP LaserJet barcodes & More Font Cartridge" is needed for this. Barcode printing from R/3 is not supported.
HPLJSTND
Generic device type for printers that have an HP LaserJet emulation but cannot be operated via the definitions HPLJ4, HPLJIIID or HPLJ_II.
HPLJ_II
Device type for the Hewlett-Packard LaserJet II laser printer series. OCR-A and OCR-B are included in the printer definition, but the printer needs an additional firmware/font cassette. The "HP LaserJet barcodes & More Font Cartridge" is needed for this. Barcode printing from R/3 is not supported.
KYOF1000
Device type for the Kyocera F-1000 laser printer. OCR fonts are not supported. Bar code printing is supported.
KYOF1200
Device type for the Kyocera laser printers F-1200 and F-1200S. OCR fonts are not supported. Barcode printing is supported.
MT600
Device type for the Mannesmann-Tally line printer MT600. Character set used: US-ASCII (that is no German umlauts).
MT600GER
Device type for the Mannesmann-Tally line printer MT600. Character set used: German. OCR-A and OCR-B (German standard) are included in the printer definition; the printer must be upgraded with these fonts.
MT600NDA
Device type for the Mannesmann-Tally line printer MT600. Character set used: Norwegian / Danish. OCR-A and OCR-B (German standard) are included in the printer definition; the printer must be upgraded with these fonts.
OKI341
Device type for the OKI Microline 3410 line printer.
POSTSCPT
Device type which is used for pure PostScript printers. Barcode printing from R/3 is not supported.
S4440XTG
Device type for the SEL Alcatel line printer 4440XT. Character set used: German.
SAPWIN
Generic device type for printers linked (or also fax devices) to PCs running under MS Windows 3.1, Windows 95 or Windows NT by means of the R/3 program SAPLPD. Windows printer drivers are used and the character set is ISO 8859-1. Barcode printing from R/3 is possible with the additional installation of a third-party DLL (see Note 25344), but is not supported in the standard system. OCR-A and OCR-B fonts are possible with an appropriate TrueType font (see also Note 48803).
Important Note:
As of Release 3.0E, you can use SAPWIN to:
Print proportional fonts and lines/boxes in SAPscript
Print black and white as well as color TIFF graphics (with the 32-bit SAPlpd on Windows 95 and Windows NT only).
See Note 39031.
SWIN
Generic device type for printing/faxing using MS Windows with SAPlpd. It is available as of Release 3.1H. Device type SWIN differs from SAPWIN in the layout of X_... formats for ABAP/4 list printing. The font size and line spacing were adjusted, particularly for color list printing.
In addition, SAPWIN contains an expanded list of SAPscript printer fonts for current releases, for example, Greek and Russian.
SNI4009
Device type for the Siemens-Nixdorf SNI 4009 line printer.
SNI4010
Device type for the Siemens-Nixdorf SNI 4010 line printer. OCR-A is included in the printer definition, but the printer needs an additional firmware/font cassette.
SNI9014
Device type for the Siemens-Nixdorf SNI 9014/12 line printer. OCR-A and OCR-B are included in the printer definition. The 9014/12 has OCR-A and OCR-B font installed as a default.
SNIZD13
Device type for the Siemens-Nixdorf SNI ZD13 line printer. OCR-A is included in the printer definition. The ZD13 has OCR-A font installed as a default.
CIP1000
Device type for C.ITOH line printers CI-1000 and CI-500. The IBM Proprinter II/XL emulation and IBM character set 2 (multilingual) are used.
EPESCP
Device type for all 24 or 48 element EPSON printers that use the control language ESC/P. Character set IBM 437 is used. OCR-A/OCR-B are included in the printer definition. However, some printers also require an additional firmware/font cassette.
EPESCP2
Device type for EPSON printers that use the control language ESC/P2. The character set IBM 850 (multilingual) is used. OCR-A/OCR-B are included in the printer definition. However, some printers also require an additional firmware/font cassette.
EPESCP9
Device type for all 9-pin dot matrix EPSON printers that use the control language ESC/P. The standard ASCII character set is used with some additional international characters.
EPLQ550
Device type for the EPSON LQ-55 dot matrix printer. OCR-A/OCR-B are included in the printer definition. However, the printer needs an additional firmware/font cassette.
HP2300
Device type for the Hewlett-Packard 2300 line printer series. OCR-A/OCR-B are included in the printer definition. However, the printer needs an additional firmware/font cassette.
HPLJ4
Device type for all printers in Hewlett-Packard's LaserJet 4 series (this includes LaserJet 4/4m, 4Plus/4mPlus, 4V/4mV, 4si). OCR-A/OCR-B are included in the printer definition. However, the printer needs an additional firmware/font cassette. The "HP LASERJET barcodes & MORE FONT CARTRIDGE" or a SIMM module is required. Barcode printing from R/3 with HP LaserJet 4 Series printers requires SIMM module "JetCAPS Intelligent Barcode SIMM" and is supported.
IBM239X
Device type for the IBM 238X/239X Plus line printer series from Lexmark. This includes the types IBM 2380 Plus, IBM 2381 Plus, IBM 2390 Plus, IBM 2391 Plus. The IBM emulation and character set IBM 850 are used.
IBM4226
Device type for the IBM 4226 line printers from Lexmark. The IBM emulation and the character set IBM 850 are used.
IBM4232
Device type for the IBM 4232-302 line printer from IBM. The 4202 emulation and the character set IBM 2 are used. OCR-A/OCR-B are included and supported. Barcode printing is not supported.
IBM6408
Device type for the IBM 6408-A00 line printer from IBM. The PropPrinter III XL emulation and the character set IBM 850/IBM 2 are used. OCR-A/OCR-B are included and supported. Barcode printing is not supported.
IBMAFP
Device type for IBM's external SAP2AFP converter. The R/3 spool output is converted to AFPDS format and passed to IBM AFP software. IBMAFP can only be used in conjunction with spool-exit (access method Z when defining the device type). Selection of printers directly connected to R/3 is not possible. IBMAFP must be used for 240 pel AFP printers.
Character set is ISO 8859-1 (Latin 1). OCR-A and OCR-B are supported, as well as barcodes.
IBMAFP is for use on R/3 UNIX and Windows NT platforms.
IBMEFP is the proper device type for AS/400 R/3 Platforms and uses the EBCDIC character set.
IBMAFP3
Device type for IBM's external SAP2AFP converter that converts the R/3 spool output to an AFPDS format and sends it to IBM AFP software.IBMAFP3 can be used only in conjunction with spool-exit (access method Z when defining the device type). Selection of printers connected via R/3 is not possible. IBMAFP3 must be used for 300 pel AFP printers.
Character set is ISO 8859-1 (Latin 1). OCR-A and OCR-B are supported, as well as barcodes.
IBMAFP3 is for use on UNIX and Windows NT platforms.
IBMEFP3 is the proper device type for AS/400 R/3 Platforms and uses the EBCDIC character set.
IBMSCS
Device Type IBMSCS supports the "basic IBMSNA Character String" data stream for printers that are connected under IBM OS/400. IBMSCS is only supported for the use under SAP R/3 on hardware platforms IBM AS/400.
LX4039
Device type for the Lexmark laser printer series 4039. OCR-A/OCR-B are included in the printer definition. However, the printer requires an additional firmware/typeface cassette. "HP LASERJET barcodes & MORE FONT CARTRIDGE" is required. Barcode printing from R/3 is not supported.
KYOFS150
Device type for the Kyocera laser printer FS-1500, FS-3500, FS-1550+. OCR fonts are not supported. Barcode printing is supported.
NECP30
Device type for the NEC matrix printers P20/P30. The character set used is IBM codepage 850 (multilingual).
NECP72
Device type for the NEC matrix printers P62/P72. The NEC Pinwriter level 2 emulation and the character set IBM codepage 850 (multilingual) are used. OCR-A/OCR-B are included in the printer definition. However, the printer requires an additional firmware/font cassette.
NECPW
Device type for the NEC 48-pin Pinwriter P5XL, P9XL, P6/P7, P6plus/P7plus, P2200, P2plus, P60/P70, P90, P20/P30, P22Q/P32Q, P42/P52, P62/P72. The character set IBM codepage 850 (multilingual) is used.
SNI4011
Device type for the 24-pin version of the SNI 4011 dot matrix printer. The EPSON LQ-850+ emulation and character set IBM codepage 850 (multilingual) are used. OCR-A/OCR-B are included in the printer definition. The printer has these fonts built in.
SNI20XX8
Device type for the Siemens-Nixdorf 2050-8, 2075-8 and 2090-8 laser printers (HP-LaserJet emulation). For operation with R/3, you need to obtain a special font diskette for the printer from SNI. This contains the fonts required, including OCR-A and OCR-B. Barcode printing from R/3 is not supported.
MT2033
Device type for the Mannesmann-Tally T2033 matrix printer. Uses MTPL+IBM Proprinter emulation and IBM codepage II for the character set. OCR-A/OCR-B are included in the printer definition. These fonts are built into the printer at the factory.
MT2045
Device type for the Mannesmann-Tally T2045 matrix printer. Uses MTPL+IBM Proprinter emulation and IBM codepage II for the character set. OCR-A/OCR-B are included in the printer definition. These fonts are built into the printer at the factory.
DEVICE TYPES NEW TO RELEASE 3.1G:
HPDJ660
Device type for the color inkjet printer Hewlett-Packard DeskJet 660C. Lists are printed in color. OCR-A, OCR-B and barcode printing from R/3 are not supported.
HPDJ850
Device type for the color inkjet printer Hewlett-Packard DeskJet 850C. Lists are printed in color. OCR-A, OCR-B and barcode printing from R/3 are not supported.
HPLJ5SI
Device type for Hewlett-Packard's LaserJet 5Si. OCR-A/OCR-B are included in the printer definition. However, the printer needs an additional firmware. The "HP LASERJET barcodes & MORE FONT CARTRIDGE" or a SIMM module is required. Barcode printing from R/3 with HP LaserJet 5Si requires and supports SIMM module "JetCAPS Intelligent Barcode SIMM".
MT6045
Device type for the Mannesmam-Tally T6045 dot matrix printer. Uses MT660 emulation and character set Latin-1. OCR-A/OCR-B are included in the printer definition. These fonts are built into the printer at the factory.
Important note: For use with R/3 the printer's standard character set must be set to Latin-1.
NEW DEVICE TYPES IN RELEASE 3.1H:
MT691
Device type for the Mannesmann-Tally T691 dot matrix printer. Uses MT660 emulation and character set Latin-1. OCR-A/OCR-B are included in the printer definitions. These fonts are built into the printer at the factory.
NEW DEVICE TYPES IN RELEASE 3.1I:
SAPWIN5
Device type for printing cyrillic characters (character set ISO 8859-5, for example Russian) with SAPlpd/Microsoft Windows. This device type works exclusively with the Russian Windows 95 or NT 4.0 (not with Windows 3.1). To use it, a 32 bit version of the SAPlpd with a number 4.00 or higher is required.
DEVICE TYPES IN RELEASE 4.0A:
HPLJ5
Device type for all printers of the Hewlett-Packard LaserJet 5 printer series (LaserJet 5/5m, 5P/5MP, 5C) except for HP LaserJet 5 SI. OCR-A/OCR-B are included in the printer definitions. However, the printer needs an additional firmware/font cassettes. The "HP LASERJET BarCodes & MORE FONT CARTRIDGE" or a SIMM module is required. Barcode printing from R/3 with printers of the HP LaserJet 5 series requires and supports SIMM module "JetCAPS Intelligent Barcode SIMM".
Important note: HPLJ5 uses new 4.0A features (scalable fonts under PCL-5) and can only be used in Release 4.0A and higher releases!
I2HP4
Device type for Eastern Europe for all printer of the Hewlett Packard LaserJet 4 printer series (for example, LaserJet 4/4m, 4Plus/4mPlus, 4V/4mV, 4Si). Uses character set "ISO 8859/2" (Latin 2). OCR-A/OCR-B are included in the printer definitions, however, the printer requires additional firmware/font diskette. The "HP LASERJET BarCodes & MORE FONT CARTRIDGE" or a respective SIMM module is required. For the barcode print from R/3 with printer of the HP LaserJet 4 series the SIMM module "JetCAPS Intelligent Barcode SIMM" is required and supported.
I2SWIN
Device type for Eastern Europe for printing under Microsoft Windows via a 32 bit SAPlpd. I2SWIN uses the character set ISO 8859/2 (Latin 2). To use I2SWIN, the following preconditions are required:
SAPlpd 32 bit version, from 4.00
Microsoft Windows NT 4.0 or eastern European Win95 (Latin 2 version)
R/3 Release 3.0E or higher
Important note: Microsoft Windows 3.1 (SAPlpd 16 bit) is NOT supported!
I7SWIN
Device type for Greece for printing under Microsoft Windows via SAPlpd 32 bit. I7SWIN uses character set "ISO 8859/7" (Greek). Requirements for operation of I7SWIN are:
SAPlpd 32 bit as of Version 4.00
MS Windows NT 4.0 or Greek Windows 95
R/3 Release 3.0E or newer
Important note: MS Windows 3.1 (SAPlpd 16 bit) is not supported!
NEW DEVICE TYPES IN RELEASE 4.5A:
HPLJ4000
Device type for the Hewlett Packard LaserJet 4000 printer and
related models such as LaserJet 5000, 8000, 8100 and 8150.
HPLJ4000 uses character set "ISO 8859/1" (Latin 1). For the barcode print from R/3 with HP LaserJet 4000, the DIMM module "JetCAPS Intelligent Barcode DIMM" is required and supported. In addition to the barcodes this DIMM module contains the OCR-A and OCR-B fonts that are supported by HPLJ4000.
Device type HPLJ4000 offers improved output of ABAP print lists by using a special PCL-5-printer drivers and can therefore only be used in Releases as of 4.5A.
I9HP4
Device type for Turkey for all printers of the Hewlett-Packard LaserJet 4 printer series (among others LaserJet 4/4m, 4Plus/4mPlus, 4V/4mV, 4Si). I9HP4 uses character set "ISO 8859/9" (Latin 5). OCR-A/ OCR-B are contained in the device type, however, the printer needs extra firmware or an extra font cartridge. The "HP LASERJET BarCodes & MORE FONT CARTRIDGE" or a corresponding SIMM module is needed for this. The SIMM module "JetCAPS Intelligent Barcode SIMM" is a requirement for printing barcodes from R/3 with printers of the HP LaserJet 4 series and is supported.
KYOFS170
Device type for the Kyocera laser printer FS-1700. OCR fonts are not supported. Barcode printing is supported.
Device type KYOFS170 offers improved output of ABAP print lists by using a special PRESCRIBE-II-printer driver and can therefore only be used in Releases as of 4.5A.
POST2
New device type for PostScript-level-2-printer which can be used alternatively to POSTSCPT. Barcode printing and OCR printing from R/3 is not supported.
Device type POST2 offers an improved output of ABAP print lists by using a special PostScript-L2-printer driver and can therefore only be used in Releases as of 4.5A.
NEW DEVICE TYPES IN RELEASE 4.6A:
IXLINK
Device type for the external XLink/SAP translator of Xerox, which translates R/3 SAPGOF data to Xerox format and transfers data to the Xerox production printer. IXLINK can only be used if the XLink/SAP translator is being used. You cannot access printers, which are connected via R/3!
OCR-A and OCR-B fonts as well as bar codes are supported.
NEW DEVICE TYPES IN RELEASE 4.6C:
HPLJ8000
Device type for Hewlett Packard LaserJet 8000, 8000N, 8000DN printers. HPLJ8000 uses character set "ISO 8859/1" (Latin 1). For the barcode print from R/3 with HP LaserJet 4000, the DIMM module "JetCAPS Intelligent Barcode DIMM" is required and supported. In addition to the barcodes this DIMM module contains the OCR-A and OCR-B fonts that are supported by HPLJ4000.
Device type HPLJ8000 offers improved output of ABAP print lists by using a special PCL-5-printer driver and can therefore only be used in Releases as of 4.5A.
HPLJ1100
Device type for Hewlett Packard LaserJet 1100 printer. HPLJ1100 uses character set "ISO 8859/1" (Latin 1). OCR-A/B as well as barcode print from R/3 are not supported.
Device type HPLJ1100 can only be used in Releases as of 4.6C.
I9SWIN
Device type for Turkey und printing with MS Windows via SAPlpd 32 bit. I9SWIN uses character set "ISO 8859/9" (Latin 5). Preconditions for using I9SWIN:
SAPlpd 32 bit as of version 4.00
MS Windows NT 4.0 or Turkish Windows 95 (Latin 5 Version)
R/3 Release 3.0E or newer
Important note: MS Windows 3.1 (SAPlpd 16 bit) is not supported!
IBMNP
Device type for laser printer IBM InfoPrint 20 as well as the IBM Network Printer 12, 17, 24, IBM InfoPrint 32, InfoPrint 40. OCR- and MICR fonts are supported by the device type. The printer needs an additional module for these fonts. "Barcode-, MICR and OCR A+B SIMM for IBM Network Printers" is required. Read Note 133660 also. Bar code printing from R/3 is not supported.
Important note: IBMNP uses new 4.0A features (scaleable font under PCL-5) and can only be used in maintenance level 4.0A and higher.
NEW DEVICE TYPES IN RELEASE 6.10:
IBMIP12
Device type for laser printer IBM InfoPrint 12. IBMIP12 uses character set ISO 8859-1 (Latin 1). Bar code and OCR-font printing from SAP is not supported. This device type is compatible with all SAP releases from 4.0A.
IBMIP21
Device type for laser printer IBM InfoPrint 21. IBMIP21 uses character set ISO 8859-1 (Latin 1). Bar code and OCR-font printing from SAP is not supported. This device type is compatible with all SAP releases from 4.0A.
IBMIP32
Device type for laser printers IBM InfoPrint 32 and InfoPrint 40. IBMIP32 uses character set ISO 8859-1 (Latin 1). Bar code and OCR-font printing from SAP is not supported. This device type is compatible with all SAP releases from 4.0A.
IBMIP2K
Device type for production laser printer IBM InfoPrint 2000 with PCL-5 emulation. IBMIP2K uses character set ISO 8859-1 (Latin 1). Bar code and OCR-font printing from SAP is not supported. This device type is compatible with all SAP releases from 4.0A.
IBMIP60
Device type for laser printer IBM InfoPrint 60. IBMIP60 uses character set ISO 8859-1 (Latin 1). Bar code and OCR-font printing from SAP is not supported. This device type is compatible with all SAP releases from 4.0A.
IBMIP70
Device type for laser printer IBM InfoPrint 70. IBMIP70 uses character set ISO 8859-1 (Latin 1). Bar code and OCR-font printing from SAP is not supported. This device type is compatible with all SAP releases from 4.0A.
IBM4247
Device type for line printer IBM 4247. The printer's 4247 emulation and character set IBM2 is used. OCR-fonts are supported. Bar code printing from SAP is not supported.
Attention: Please follow note 396462 when installing the printer.
NEW DEVICE TYPES IN RELEASE 6.20:
IBM6400
Device type for line printer IBM 6400. The printer's "P-Series" emulation and character set PC850 is used. OCR-fonts are supported. Bar code printing from SAP is not supported.
Attention: Please follow note 396462 when installing the printer.
HP1200
Device type for HP LaserJet 1200/1220. HP1200 uses character set "ISO 8859/1" (Latin 1).
HP1200 is compatible with all releases from 4.0A.
HP2200
Device type for HP LaserJet 2200. HP2200 uses character set "ISO 8859/1" (Latin 1).
HP2200 is compatible with all releases from 4.0A.
HP2250
Device type for HP Business Inkjet 2250. HP2250 uses character set "ISO 8859/1" (Latin 1).
HP2250 is compatible with all releases from 4.5B.
Attention: Business Inkjet 2200 is not compatible with HP2250.
HP2500
Device type for HP DeskJet 2500C with PCL-5 option. HP2500 uses character set "ISO 8859/1" (Latin 1).
HP2500 is compatible with all releases from 4.0A.
HP3200
Device type for HP LaserJet 3200m. HP3200 uses character set "ISO 8859/1" (Latin 1).
HP3200 is compatible with all releases from 4.0A.
HP4100
Device type for HP LaserJet 4100. HP4100 uses character set "ISO 8859/1" (Latin 1).
HP4100 is compatible with all releases from 4.0A.
HP4550
Device type for HP LaserJet 4550 (color laser). HP4550 uses character set "ISO 8859/1" (Latin 1).
HP4550 is compatible with all releases from 4.5A.
HP8150
Device type for HP LaserJet 8150. HP8150 uses character set "ISO 8859/1" (Latin 1).
HP8150 is compatible with all releases from 4.0A.
HP8550
Device type for HP LaserJet 8550 (color laser). HP8550 uses character set "ISO 8859/1" (Latin 1).
HP4550 is compatible with all releases from 4.5A.
HP9000
Device type for HP LaserJet 9000. HP9000 uses character set "ISO 8859/1" (Latin 1).
HP9000 is compatible with all releases from 4.0A.
NEW DEVICE TYPES IN RELEASE NW04:
BRHL
Device type for Brother laser printer HL-2460. This device type is compatible to other Brother laser printers, see below.
OCR-A and OCR-B fonts as well as bar codes are supported.
BRHL is compatible with all releases from 4.5A.
IP2085
Device type for the IBM Infoprint 2085 Laser printer with printer language PCL-5. OCR font and bar code printing from SAP are not supported.
IP2085 is compatible with all releases 4.5A and higher.
IP2085P
Device type for the IBM Infoprint 2085 Laser printer with printer language PostScript. OCR font and bar code printing from SAP are not supported.
IP2085P is compatible with all releases 4.5A and higher.
IP2105
Device type for the IBM Infoprint 2105 Laser printer with printer language PCL-5. OCR font and bar code printing from SAP are not supported.
IP2105 is compatible with all releases 4.5A and higher.
IP2105P
Device type for the IBM Infoprint 2105 Laser printer with printer language PostScript. OCR font and bar code printing from SAP are not supported.
IP2105P is compatible with all releases 4.5A and higher.
LEXT622
Device type for the Lexmark T622 laser printer. OCR-fonts and bar code printing from SAP are supported if the printer is equipped with a corresponding option (note 119471).
LEXT622 is compatible with all releases 4.5A and higher.
LEXW820
Device type for the Lexmark W820 laser printer. OCR-fonts and bar code printing from SAP are supported if the printer is equipped with a corresponding option (note 119471).
LEXW820 is compatible with all releases 4.5A and higher.
LEX4227P
Device type for the Lexmark 4227plus line printer. The device type supports the Latin-1 character set. For using the device type, the IBM emulation must be set in the printer.
OCR fonts and barcode printing from SAP are not supported.
LEX4227P is compatible with all releases.
I5LEX
Device type for Cyrillic printing (e.g. Russian) with Lexmark T522 laser printer. Lexmark T522 natively supports Cyrillic fonts and character set ISO 8859-5.
OCR-fonts are not supported. Bar code printing is supported (with a bar code DIMM, see note 119471).
I5LEX is compatible with all releases 4.0A and higher.
CNLX522
Device type for Lexmark T522 laser printer with add-on "Simplified Chinese DBCS font DIMM kit" (Lexmark product number 09H0690). The device type supports Simplified Chinese. OCR-fonts and bar code printing from SAP are not supported.
CNLX522 is compatible with all releases 4.0A and higher.
JPLX522
Device type for Lexmark T522 laser printer with add-on "Japanese DBCS font DIMM kit" (Lexmark product number 13K0227). The device type supports Japanese character set. OCR-fonts and bar code printing from SAP are not supported.
JPLX522 is compatible with all releases 4.0A and higher.
KPLX522
Device type for Lexmark T522 laser printer with add-on "Korean DBCS font DIMM kit" (Lexmark product number 10G1705). The device type supports Korean character set. OCR-fonts and printing of bar codes from SAP are not supported.
KPLX522 is compatible with all releases 4.0A and higher.
TWLX522
Device type for Lexmark T522 laser printer with add-on "Traditional Chinese DBCS font DIMM kit" (Lexmark product number 09H0691). The device type supports traditional Chinese character set. OCR-fonts and bar code printing from SAP are not supported.
TWLX522 is compatible with all releases 4.0A and higher.
HP5000
Device type for HP LaserJet 5000. HP5000 uses character set "ISO 8859/1" (Latin 1).
HP5000 is compatible with all releases from 4.0A.
HP23
Device type for HP LaserJet 2300. HP23 uses character set "ISO 8859/1" (Latin 1).
HP23 is compatible with all releases from 4.5A.
HP3000
Device type for HP business inkjet 3000. HP3000 uses character set "ISO 8859/1" (Latin 1).
HP3000 is compatible with all releases from 4.5A.
HP4300
Device type for HP LaserJet 4200 and HP LaserJet 4300. HP4300 uses character set "ISO 8859/1" (Latin 1).
HP4300 is compatible with all releases from 4.5A.
HP4600
Device type for HP color LaserJet 4600. HP4600 uses character set "ISO 8859/1" (Latin 1).
HP4600 is compatible with all releases from 4.5A.
HP5100
Device type for HP LaserJet 5100. HP5100 uses character set "ISO 8859/1" (Latin 1).
HP5100 is compatible with all releases from 4.5A.
HP5500
Device type for HP color LaserJet 5500. HP5500 uses character set "ISO 8859/1" (Latin 1).
HP5500 is compatible with all releases from 4.5A.
HP9500
Device type for HP color LaserJet 9500. HP9500 uses character set "ISO 8859/1" (Latin 1).
HP9500 is compatible with all releases from 4.5A.
I2HPPS
Device type for certain HP LaserJet models with PostScript emulation (see Note 575916). I2HPPS supports character set "ISO 8859/2" (Latin 2).
I2HPPS is compatible with all releases as of 4.0A.
Barcode printing and OCR fonts are not supported.
CAN105
Device type for Canon laser printer imageRUNNER 105. CAN105 supports character set ISO 8859-1 (Latin 1).
CAN105 is compatible with all releases as of 4.5A.
OCR-fonts are supported, barcode printing is not supported.
CAN22
Device type for Canon laser printers imageRUNNER 2200/2800/3300/3300i. CAN22 supports character set ISO 8859-1 (Latin 1).
CAN22 is compatible with all releases as of 4.5A.
OCR-fonts are supported, barcode printing is not supported.
CAN5
Device type for Canon laser printers imageRUNNER 5000/5000i/6000. CAN5 supports character set ISO 8859-1 (Latin 1).
CAN5 is compatible with all releases as of 4.5A.
OCR-fonts are supported, barcode printing is not supported.
CAN85
Device type for Canon laser printers imageRUNNER 8500/7200/85. CAN85 supports character set ISO 8859-1 (Latin 1).
CAN85 is compatible with all releases as of 4.5A.
OCR-fonts are supported, barcode printing is not supported.
CN105PS
PostScript device type for Canon laser printer imageRUNNER 105. CN105PS supports character set ISO 8859-1 (Latin 1).
CN105PS is compatible with all releases as of 4.5A.
OCR-fonts and barcode printing is not supported.
CN22PS
PostScript device type for Canon laser printers imageRUNNER 2200/2800/3300/3300i. CN22PS supports character set ISO 8859-1 (Latin 1).
CN22PS is compatible with all releases as of 4.5A.
OCR-fonts and barcode printing is not supported.
CN5PS
PostScript device type for Canon laser printer imageRUNNER 5000/5000i/6000. CN5PS supports character set ISO 8859-1 (Latin 1).
CN5PS is compatible with all releases as of 4.5A.
OCR-fonts and barcode printing is not supported.
CN85PS
PostScript device type for Canon laser printer imageRUNNER 8500/7200/85. CN85PS supports character set ISO 8859-1 (Latin 1).
CN85PS is compatible with all releases as of 4.5A.
OCR-fonts and barcode printing is not supported.
CAN400
PCL5 device type for Canon laser printer imageRUNNER 330/400. CAN400 supports character set ISO 8859-1 (Latin 1).
CAN400 is compatible with all releases as of 4.5A.
OCR-fonts are supported. Barcode printing is not supported.
CN400PS
PostScript device type for Canon laser printer imageRUNNER 330/400. CN400PS supports character set ISO 8859-1 (Latin 1).
CN400PS is compatible with all releases as of 4.5A.
OCR-fonts and barcode printing is not supported.
CANC32
PCL5 device type for Canon color laser printer Color imageRUNNER C3200. CANC32 supports character set ISO 8859-1 (Latin 1).
CANC32 is compatible with all releases as of 4.5A.
OCR-fonts are supported. Barcode printing is not supported.
NEW DEVICE TYPES IN RELEASE SAP NetWeaver 04s:
ARM205
PCL-5 device type for Sharp laser printer AR-M205. ARM205 uses character set ISO 8859-1 (Latin-1).
ARM205 is compatible with all releases as of 4.5A.
OCR fonts are not supported. Barcode printing and OCR fonts are supported with an add-on product (note 733347).
ARM276
PCL-5 device type for Sharp laser printer AR-M276. ARM276 uses character set ISO 8859-1 (Latin-1).
ARM276 is compatible with all releases as of 4.5A.
OCR fonts are not supported. Barcode printing and OCR fonts are supported with an add-on product (note 733347).
ARM450
PCL-5 device type for Sharp laser printer AR-M450. ARM450 uses character set ISO 8859-1 (Latin-1).
ARM450 is compatible with all releases as of 4.5A.
OCR fonts are not supported. Barcode printing and OCR fonts are supported with an add-on product (note 733347).
ARM550
PCL-5 device type for Sharp laser printer AR-M550U. ARM550 uses character set ISO 8859-1 (Latin-1).
ARM550 is compatible with all releases as of 4.5A.
OCR fonts are not supported. Barcode printing and OCR fonts are supported with an add-on product (note 733347).
ARC262P
PostScript device type for Sharp color laser printer ARC-262M. ARC262P is compatible with all releases as of 4.5A.
OCR fonts are not supported.
CAN2220
PCL5 device type for Canon laser printer imageRUNNER 2220n/2220i/3320n/3320i. CAN2220 supports character set ISO 8859-1 (Latin 1).
CAN2220 is compatible with all releases as of 4.5A.
OCR-fonts are supported. Barcode printing is not supported.
CN2220P
PostScript device type for Canon laser printer imageRUNNER 2220n/2220i/3320n/3320i. CN2220P supports character set ISO 8859-1 (Latin 1).
CN2220P is compatible with all releases as of 4.5A.
OCR-fonts and Barcode printing are not supported.
CAN5020
PCL5 device type for Canon laser printer imageRUNNER 5020n/5020i/6020n/6020i. CAN5020 supports character set ISO 8859-1 (Latin 1).
CAN5020 is compatible with all releases as of 4.5A.
OCR-fonts are supported. Barcode printing is not supported.
CN5020P
PostScript device type for Canon laser printer imageRUNNER 5020n/5020i/6020n/6020i. CN5020P supports character set ISO 8859-1 (Latin 1).
CN5020P is compatible with all releases as of 4.5A.
OCR-fonts and Barcode printing are not supported.
CNC3100
PCL5 device type for Canon color laser printer imageRUNNER C3100. CNC3100 supports character set ISO 8859-1 (Latin 1).
CNC3100 is compatible with all releases as of 4.5A.
OCR-fonts are supported. Barcode printing is not supported.
CNC31PS
PostScript device type for Canon color laser printer imageRUNNER C3100. CNC31PS supports character set ISO 8859-1 (Latin 1).
CNC31PS is compatible with all releases as of 4.5A.
OCR-fonts and Barcode printing are not supported.
CNC3220
PCL5 device type for Canon color laser printers imageRUNNER C3220/C2620. CNC3220 supports character set ISO 8859-1 (Latin 1).
CNC3220 is compatible with all releases as of 4.5A.
OCR-fonts are supported. Barcode printing is not supported.
CNC322P
PostScript device type for Canon color laser printers imageRUNNER C3220/C2620. CNC322P supports character set ISO 8859-1 (Latin 1).
CNC322P is compatible with all releases as of 4.5A.
OCR-fonts and Barcode printing are not supported.
CNC6800
PCL5 device type for Canon color laser printers imageRUNNER C5800/C6800. CNC6800 supports character set ISO 8859-1 (Latin 1).
CNC6800 is compatible with all releases as of 4.5A.
OCR-fonts are supported. Barcode printing is not supported.
CNC68PS
PostScript device type for Canon color laser printers imageRUNNER C5800/C6800. CNC68PS supports character set ISO 8859-1 (Latin 1).
CNC68PS is compatible with all releases as of 4.5A.
OCR-fonts and Barcode printing are not supported.
CNC31E
PCL5 device type for Canon color laser printer imageRUNNER C3100 with imagePASS-E1 controller. CNC31E supports character set ISO 8859-1 (Latin 1).
CNC31E is compatible with all releases as of 4.5A.
OCR-fonts and Barcode printing are not supported.
CNC31EP
PostScript device type for Canon color laser printer imageRUNNER C3100 with imagePASS-E1 controller. CNC31EP supports character set ISO 8859-1 (Latin 1).
CNC31EP is compatible with all releases as of 4.5A.
OCR-fonts and Barcode printing are not supported.
CNC322E
PCL5 device type for Canon color laser printer imageRUNNER C3220/C2620 with imagePASS-C1 V.2 controller. CNC322E supports character set ISO 8859-1 (Latin 1).
CNC322E is compatible with all releases as of 4.5A.
OCR-fonts and Barcode printing are not supported.
CNC322EP
PostScript device type for Canon color laser printer imageRUNNER C3220/C2620 with imagePASS-C1 V.2 controller. CNC322EP supports character set ISO 8859-1 (Latin 1).
CNC322EP is compatible with all releases as of 4.5A.
OCR-fonts and Barcode printing are not supported.
CNC68E
PCL5 device type for Canon color laser printers imageRUNNER C5800/C6800 with imagePASS-D1 controller. CNC68E supports character set ISO 8859-1 (Latin 1).
CNC68E is compatible with all releases as of 4.5A.
OCR-fonts and Barcode printing are not supported.
CNC68EP
PostScript device type for Canon color laser printers imageRUNNER C5800/C6800 with imagePASS-D1 controller. CNC68EP supports character set ISO 8859-1 (Latin 1).
CNC68EP is compatible with all releases as of 4.5A.
OCR-fonts and Barcode printing are not supported.
CN2270
PCL5 device type for Canon laser printers imageRUNNER 2270/2870/3570/4570. CN2270 supports character set ISO 8859-1 (Latin 1).
CN2270 is compatible with all releases as of 4.5A.
OCR-fonts are supported. Barcode printing is supported with usage of the optional barcode printing kit.
CN2270P
PostScript device type for Canon laser printer imageRUNNER 2270/2870/3570/4570. CN2270P supports character set ISO 8859-1 (Latin 1).
CN2270P is compatible with all releases as of 4.5A.
OCR-fonts and Barcode printing are not supported.
DL3100
PCL5 device type for DELL color laser printer 3100cn. DL3100 supports character set ISO 8859-1 (Latin 1).
DL3100 is compatible with all releases as of 4.5A.
OCR-fonts and Barcodes are not supported.
DL3100P
PostScript device type for DELL color laser printer 3100cn. DL3100P supports character set ISO 8859-1 (Latin 1).
DL3100P is compatible with all releases as of 4.5A.
OCR-fonts and Barcodes are not supported.
DL5100
PCL5 device type for DELL color laser printer 5100cn. DL5100 supports character set ISO 8859-1 (Latin 1).
DL5100 is compatible with all releases as of 4.5A.
OCR-fonts and Barcodes are not supported.
DL5100P
PostScript device type for DELL color laser printer 5100cn. DL5100P supports character set ISO 8859-1 (Latin 1).
DL5100P is compatible with all releases as of 4.5A.
OCR-fonts and Barcodes are not supported.
HP3700
Device type for HP color LaserJet 3700. HP3700 supports character set ISO 8859-1 (Latin 1).
HP3700 is compatible with all releases as of 4.5A.
HPBI23
Device type for HP business inkjet 2300. HPBI23 supports character set ISO 8859-1 (Latin 1).
HPBI23 is compatible with all releases as of 4.0A.
HP9055
Device type for HP LaserJet 9055mfp. HP9055 supports character set ISO 8859-1 (Latin 1).
HP9055 is compatible with all releases as of 4.5A.
HP9065
Device type for HP LaserJet 9065mfp. HP9065 supports character set ISO 8859-1 (Latin 1).
HP9065 is compatible with all releases as of 4.5A.
I7HP4
Device type for HP LaserJet printers with "Greek Font DIMM" (add-on module with Greek fonts). Information can be found under www.hp.com/go/sap/drivers. I7HP4 supports character setISO 8859/7 (Greek).
I7HP4 is compatible with all releases as of 4.6B.
HP4250
Device type for HP LaserJet 4250 printer. HP4250 supports character set ISO 8859-1 (Latin 1).
HP4250 is compatible with all releases as of 4.5A.
HP1160
Device type for HP LaserJet 1160 printer. HP1160 supports character set ISO 8859-1 (Latin 1).
HP1160 is compatible with all releases as of 4.5A.
HP1320
Device type for HP LaserJet 1320 printer. HP1320 supports character set ISO 8859-1 (Latin 1).
HP1320 is compatible with all releases as of 4.5A.
HP2430
Device type for HP LaserJet 2430 printer. HP2430 supports character set ISO 8859-1 (Latin 1).
HP2430 is compatible with all releases as of 4.5A.
HP3030
Device type for HP LaserJet 3030 printer. HP3030 supports character set ISO 8859-1 (Latin 1).
HP3030 is compatible with all releases as of 4.5A.
HP4650
Device type for HP Color LaserJet 4650 printer. HP4650 supports character set ISO 8859-1 (Latin 1).
HP4650 is compatible with all releases as of 4.5A.
HP5550
Device type for HP Color LaserJet 5550 printer. HP5550 supports character set ISO 8859-1 (Latin 1).
HP5550 is compatible with all releases as of 4.5A.
HP9850
Device type for HP 9850mfp. HP9850 supports character set ISO 8859-1 (Latin 1).
HP9850 is compatible with all releases as of 4.5A.
HPLJ9050
Device type for HP LaserJet 9050 printer. HP9050 supports character set ISO 8859-1 (Latin 1).
HP9050 is compatible with all releases as of 4.5A.
HPOJ9130
Device type for HP officejet 9130. HPOJ9130 supports character set ISO 8859-1 (Latin 1).
HPOJ9130 is compatible with all releases as of 4.0B.
HP4345
Device type for HP LaserJet 4345mfp. HP4345 supports character set ISO 8859-1 (Latin 1).
HP4345 is compatible with all releases as of 4.5B.
HP9040
Device type for HP LaserJet 9040mfp. HP9040 supports character set ISO 8859-1 (Latin 1).
HP9040 is compatible with all releases as of 4.5B.
HP9050
Device type for HP LaserJet 9050mfp. HP9050 supports character set ISO 8859-1 (Latin 1).
HP9050 is compatible with all releases as of 4.5B.
HP9500M
Device type for HP LaserJet 9500mfp. HP9500M supports character set ISO 8859-1 (Latin 1).
HP9500M is compatible with all releases as of 4.5B.
IP2060
Device type for the IBM Infoprint 2060ES Laser printer with printer language PCL-5. IP2060 supports character set ISO 8859-1 (Latin 1). OCR font and bar code printing from SAP are not supported.
IP2060 is compatible with all releases 4.5A and higher.
IP2060P
Device type for the IBM Infoprint 2060ES Laser printer with printer language PostScript. IP2060P supports character set ISO 8859-1 (Latin 1).OCR font and bar code printing from SAP are not supported.
IP2060P is compatible with all releases 4.5A and higher.
IP2075
Device type for the IBM Infoprint 2075ES Laser printer with printer language PCL-5. IP2075 supports character set ISO 8859-1 (Latin 1). OCR font and bar code printing from SAP are not supported.
IP2075 is compatible with all releases 4.5A and higher.
IP2075P
Device type for the IBM Infoprint 2075ES Laser printer with printer language PostScript. IP2075P supports character set ISO 8859-1 (Latin 1). OCR font and bar code printing from SAP are not supported.
IP2075P is compatible with all releases 4.5A and higher.
IP2090
Device type for the IBM Infoprint 2090ES Laser printer with printer language PCL-5. IP2090 supports character set ISO 8859-1 (Latin 1). OCR font and bar code printing from SAP are not supported.
IP2090 is compatible with all releases 4.5A and higher.
IP2090P
Device type for the IBM Infoprint 2090ES Laser printer with printer language PostScript. IP2090P supports character set ISO 8859-1 (Latin 1). OCR font and bar code printing from SAP are not supported.
IP2090P is compatible with all releases 4.5A and higher.
IP2105E
Device type for the IBM Infoprint 2105ES Laser printer with printer language PCL-5. IP2105E supports character set ISO 8859-1 (Latin 1). OCR font and bar code printing from SAP are not supported.
IP2105E is compatible with all releases 4.5A and higher.
IP2105EP
Device type for the IBM Infoprint 2105ES Laser printer with printer language PostScript. IP2105EP supports character set ISO 8859-1 (Latin 1). OCR font and bar code printing from SAP are not supported.
IP2105EP is compatible with all releases 4.5A and higher.
OKI6100
Device type for OKI laser printer B6100. OKI6100 supports character set ISO 8859-1 (Latin 1). OCR-fonts are supported. Barcode printing is supported with an OKI add-on product.
OKI6100 is compatible with all releases as of 4.5A.
OKI8300
Device type for OKI laser printer B8300. OKI8300 supports character set ISO 8859-1 (Latin 1). OCR-fonts are not supported. Barcode printing is supported with an OKI add-on product.
OKI8300 is compatible with all releases as of 4.5A.
OKI9500
Device type for OKI color laser printer C9500. OKI9500 supports character set ISO 8859-1 (Latin 1). OCR-fonts are supported. Barcode printing is supported with an OKI add-on product.
OKI9500 is compatible with all releases as of 4.5A.
OKI4350
Device type for OKI laser printer B4350. OKI4350 supports character set ISO 8859-1 (Latin 1). OCR-fonts are supported. Barcode printing is supported with an OKI add-on product.
OKI4350 is compatible with all releases as of 4.5A.
OKI5400
Device type for OKI color laser printer C5400. OKI5400 supports character set ISO 8859-1 (Latin 1). OCR-fonts are supported. Barcode printing is supported with an OKI add-on product.
OKI5400 is compatible with all releases as of 4.5A.
OKI6300
Device type for OKI laser printer B6300. OKI6300 supports character set ISO 8859-1 (Latin 1). OCR-fonts are supported. Barcode printing is supported with an OKI add-on product.
OKI6300 is compatible with all releases as of 4.5A.
SML1451, SML1451 -
Chinese Character Printing in Smartform (Different Question)
Hi all,
Can anyone explain to me further the OSS Note 776507 that Anji Reddy Vangala recently posted? It involves the preview and printing of different character sets. Currently I've managed to preview my form correctly, but it still prints out #'s. Do I need to re-assign the fonts to the printer device or something, or do I need to use a different printer? The printer I am currently using is an HP 2100. Please please help, anyone?
<b>EDIT:</b> Probably a better question would be how to map the conversion font of CNSONG to something that can be read by the printer?
A copy of the note for everyone's reference:
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<b></b><b></b><b></b>Hi,
there a different things to know.
I produce sapscript forms with cinese and english characters for frontend / backend and archiv printing.
Please check:
Editor displays ###: You have to install the chinese language in your e.g. windows-system to display them.
Script: You have to chose the the font family "CNSONG" (customized for chinese simplified and LATIN).
Transaction I18N: May you have to set correct subfonts for the unicode areas (Cascading fonts, Standard is Courier).
You can print in different ways:
For archiv/PDF: Install the unicode truetype font with chinese characters for the pdf-converter.
For Frontend: Use the Frontendprinter SAPWIN or SAPWIN*CF (Cascading Font) to send it to the gui (note: SAPLPD does not support it, use the newer technology.....)
Backend printing: POSTSCRIPT is not yet implemented :-((
PLease note: What you see in spool / print preview is a simulation of the possible print, but backend print is not frontend preview!!!!
Regards,
Christian -
Preview and Printing of Chinese Characters in Smartform
Hi everyone!
I have a development that needs to output in Smartform a combination of Chinese and English characters, on an English Logon,
When I debug the form, the Chinese characters are shown in the debug screen, but when it is previewed or printed, it shows garbage. Can anyone help me with this?
Thanks a lot! Points for any helpful answer!Hi
check this OSS Note
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
Regards
Anji -
Text should appear both in chinese and english language in smartform-Urgen
Hi All,
In my requirement in smart form, the standard text and values to be printed should appear both in english and chinese language.
When my login language is EN(English), I cannot able to see the chinese text , but only the english text.
If login in Chinese language, I can able to see the both the Chinese and English text in print preview, even then in printout the chinese text is missing.
Please let me know what will be the problem.
What printer i can use to get both chinese and english text.
Thanks in advance
SaravanaHi
See the attached 2 OSS notes for your problem
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
reward if useful
regards,
ANJI -
Passing Select option to smartform
Hi All,
Can any one please suggest how to pass values selected in select-options to smartform.
I am aware of the iuse of var-low and Var-high,
bt what if user inputs multiple values?
Also,is there any standard table type of table that is created when we use select-options.so that we can pass this table to smartform while using select options.
Regards,
SangvirBuild in smartform in form interface select option table
and pass the select option table from the program to the
smartform.
to build select option table in smartform you can built
type in global definition tab types.
Then, use it in form interface. -
Hi Folks,
Here we have designed a Invoice-smartform and converted it into PDF which is by default storing in c-drive as mentioned in the code.When we open the Pdf it is displaying it fine but when given a printout except the logo nothing is getting printed,I mean it is showing all junk characters.May I know what is the problem and how to rectify the same.
Points will be given.
K.Kiran.Hi Kiran, see the OSS notes: 960341 and 776507.
I downloaded and copying here, Hope this will be helpful
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
regards,
Anji -
Smartform output showing another language rather than english
Hi Experts,
in my system if any of the smartform/script output want to see it showing another language.it's not showing in english language.same smartform in my friend's system it is showing english only.
Please suggest me the solution.
Thanks in advance,
Venkat.Hi
See the attached 2 OSS notes for your problem
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</b>
Regards -
Smartforms - kbetr (curr11) in invoice with wrong values
Hello,
I am developing an invoice, and this invoice is built on the standard lb_bil_invoice Smartform. The "only" thing not being standard, is that I have to read the kondition items on position level and print them here.
I read the same table (gs_it_kond), as is in the loop for the kondition items.
This works for all fields, except one;
gs_it_price-kbetr (curr11)
As soon as I have this field together with for instance a discount, this field will print the values
mulitplied by 10, but only from the second line! (the first line always prints correctly)
I have debugged it and the funny thing is that the correct value is in the field until the very end - something happens in the moment where I send it to print (it gets printed over an adobe server) which I cannot explain....
Can anyone help me on this matter?
Regards, Anne KathrineHello Ann,
For all the Amounts, the currency referencing should used in order to print correctly.
Try using something like this.
Data: W_kbetr(11)
Write: konv-kbetr to W_kbetr currency konv-waers.
Also the amount field is displayed based on the Calculation type(KRECH) values 'A', 'B', 'C' etc...Percentage, Amount, Qty. resp.
Make sure that before you're doing the manipulations correctly depends on the Calculation type.
Hope this helps.
Kindly assign points if the matter resolved.
Thanks,
-G -
Hello,
I have to modify an existing Smartform so that it will also display Text in Ukrainian language.I have worked with several Smartforms and used the Standard text with all the required languages but this Smartform is different know.
I have a lot of hardcoded text fields in the Smartform which are displayed in the logon language,so if i log in to the system in german it will be in german and if i log on in english ,the hardcoded texts will be in english.
How is this Smartform built and how can i see the languages in which it is in the system?
thanks
Edited by: seba seba on Jul 23, 2009 4:26 PMHi
Use SE63
TRANSLATION --->ABAP OBJECTS -
> TRANSPORT OBJECT
and
Transport Entry of Object R3TR SSFO ZSMARTFORM
Source Language enUS Eng
Target language deDE Ger
CLICK -
> EDIT
Do all your trasnlations and SAVE and SAVE n ACTIVE 3 to 4 times
Surya -
Print EURO symbol u20AC in smartform
Hi All,
I am trying to print the EURO symbol 'u20AC' in smartform; user types the euro symbol in the Invoice header text, but the Invoice smartform prints some other characters when I print the header text;
Appreciate your help if some of you have a solution to print the euro symbol in the header text by smartform;
Thank you very much
IverGi,
That is strange, it works fine for me. I copy the relevan parts into this thread.
Regards,
Aidan
Symptom
There are problems to print the euro character U20AC and and trademark character U2122.
Cause
This can vary depending on the device type used to create the spool and whether the system is Unicode or non-Unicode. The problem is because the characters are not supported in the system character set or the character set of the device type.
Resolution
In Unicode systems, these characters can be printed via windows and cascading fonts device type SWINCF. The unicode system codepage supports these characters and the character set 4220 of device type SWINCF also supports these characters U20AC and U2122. In a Unicode system, it is also possible to print the euro and trademark characters via Unicode device types like HPUTF8 or LEXUTF8 In this case, the printer must also be Unicode. i.e. It must have a built-in hard disk, which contains Unicode fonts and symbol sets.(see notes 750219 and 215015)
For non-unicode systems, it is more difficult. For sapscript and smartforms, it is possible to use both signs for releases >= 4.6A. In the graphical SAPScript editor, available as of, you can select "Edit" > "Command..."-> "Insert Command" -> "SAP character" and then enter the SAP character number 156 (Euro sign) or 357 (trademark sign). With this method, it is possible to print the euro and tradwmark characters. You need to use one of the device types specified in note #129581. or in the old line editor, you can enter <156> or <357>(between "<" and ">" without spaces). It is not necessary to add any character to the character set if you use one of thes device types listed in note #129581. The print of the euro and trademark characters are only possible for postscript device types POST2, I2HPPS and I4HPPS after you implement note #1334841. -
Hi,
I want to know all in-built functions,programs,reports,tables,fields, transaction codes,and all other standards which are in-built and there description,How can i?hi,
tons of links are avilable.
http://cma.zdnet.com/book/abap/
http://cma.zdnet.com/book/abap/index.htm
http://www.sapdevelopment.co.uk/
http://www.sap-img.com/
http://juliet.stfx.ca/people/fac/infosys/abap.htm
http://help.sap.com/saphelp_46c/helpdata/en/d3/2e974d35c511d1829f0000e829fbfe/frameset.htm
http://help.sap.com/saphelp_46c/helpdata/en/d6/0db357494511d182b70000e829fbfe/frameset.htm
http://www.henrikfrank.dk/abapexamples/SapScript/sapscript.htm
http://www.sapgenie.com/abap/example_code.htm
http://www.geocities.com/SiliconValley/Campus/6345/abapindx.htm
http://help.sap.com/printdocu/core/Print46c/en/Data/Index_en.htm
http://help.sap.com/saphelp_40b/helpdata/en/4f/991f82446d11d189700000e8322d00/applet.htm
http://www.sap-img.com/abap-function.htm
http://www.sapgenie.com/abap/code/abap19.htm
http://www.sap-img.com/abap/more-than-100-abap-interview-faqs.htm
http://www.planetsap.com/Tips_and_Tricks.htm
http://help.sap.com/saphelp_40b/helpdata/ru/d6/0dc169494511d182b70000e829fbfe/applet.htm
http://www.henrikfrank.dk/abapexamples/SapScript/symbols.htm
http://www.henrikfrank.dk/abapexamples/index.html
http://sap.ittoolbox.com/documents/document.asp?i=752
http://members.aol.com/_ht_a/skarkada/sap/
http://sappoint.com/abap/
http://members.tripod.com/abap4/SAP_Functions.html
http://members.ozemail.com.au/~anmari/sap/index.html
http://www.planetsap.com/Userexit_List.htm
http://www.planetsap.com/Tips_and_Tricks.htm
http://www.kabai.com/abaps/q.htm
http://www.planetsap.com/Userexit_List.htm
http://help.sap.com/saphelp_bw21c/helpdata/en/c4/3a8090505211d189550000e829fbbd/frameset.htm
http://www.sapgenie.com/abap/bapi/example.htm
http://help.sap.com/saphelp_45b/helpdata/en/65/897415dc4ad111950d0060b03c6b76/content.htm
http://www.sap-basis-abap.com/index.htm
http://help.sap.com/saphelp_40b/helpdata/en/fc/eb2c46358411d1829f0000e829fbfe/frameset.htm
http://help.sap.com/saphelp_46c/helpdata/en/aa/aeb23789e95378e10000009b38f8cf/frameset.htm
http://www.geocities.com/ResearchTriangle/1635/system.html
http://www.sapdesignguild.org/resources/MiniSG/3_Managing/3_Functions_Table_Control.htm
http://help.sap.com/saphelp_45b/helpdata/en/d1/801bdf454211d189710000e8322d00/content.htm
http://www.sapfans.com/sapfans/repos/saprep.htm
http://www.planetsap.com/howdo_a.htm
http://help.sap.com/saphelp_util464/helpdata/en/69/c2516e4ba111d189750000e8322d00/content.htm
http://www.sapgenie.com/abap/smartforms_detail.htm
http://www.sap-img.com/abap.htm
http://help.sap.com/saphelp_46c/helpdata/en/fc/eb2d67358411d1829f0000e829fbfe/content.htm
http://www.geocities.com/victorav15/sapr3/abap.html
http://www.henrikfrank.dk/abapexamples/SapScript/sapscript.htm
http://abap4.tripod.com/Other_Useful_Tips.html
http://help.sap.com/saphelp_45b/helpdata/en/cf/21ee2b446011d189700000e8322d00/content.htm
http://www.sap-basis-abap.com/sapmm.htm
http://sap.ittoolbox.com/nav/t.asp?t=303&p=448&h1=303&h2=322&h3=448
http://sapfans.com/
http://cma.zdnet.com/book/abap/ch03/ch03.htm
http://help.sap.com/saphelp_40b/helpdata/en/4f/991f82446d11d189700000e8322d00/applet.htm
http://sappoint.com/abap/
http://www.henrikfrank.dk/abapuk.html
http://www.sts.tu-harburg.de/teaching/sap_r3/ABAP4/abapindx.htm
http://www.sapgenie.com/abap/index.htm
http://www.sap-img.com/abap.htm
http://www.sapdevelopment.co.uk/tips/tipshome.htm
http://help.sap.com/printdocu/core/Print46c/en/Data/Index_en.htm
http://sap.ittoolbox.com/nav/t.asp?t=322&p=322&h1=322
http://sap.ittoolbox.com/nav/t.asp?t=448&p=448&h1=448
http://www.thespot4sap.com/
http://www.kabai.com/abaps/q.htm
http://www.geocities.com/mpioud/Abap_programs.html
http://www.sapgenie.com/abap/tips_and_tricks.htm
http://www.sapassist.com/code/d.asp?whichpage=1&pagesize=10&i=10&a=c&o=&t=&q=&qt=
For FAQ
http://www.sap-img.com/abap/more-than-100-abap-interview-faqs.htm
http://www.sapgenie.com/faq/abap.htm
BAPI-step by step
http://www.sapgenie.com/abap/bapi/example.htm
Weblog for receive email and processing it through ABAP
/people/thomas.jung3/blog/2004/09/09/receiving-e-mail-and-processing-it-with-abap--version-610-and-higher
For Logical database
http://help.sap.com/saphelp_46c/helpdata/en/9f/db9bed35c111d1829f0000e829fbfe/frameset.htm
very useful
http://help.sap.com/saphelp_46c/helpdata/EN/35/2cd77bd7705394e10000009b387c12/frameset.htm
Useful link to websites
http://www.hernangn.com.ar/sap.htm
Useful for background
http://www.sappoint.com/basis/bckprsng.pdf
http://help.sap.com/saphelp_nw04/helpdata/en/6f/08703713bf277ee10000009b38f8cf/frameset.htm
http://publib.boulder.ibm.com/infocenter/wbihelp/index.jsp?topic=/com.ibm.wbix_adapters.doc/doc/mysap4/sap4x41.htm
Table control in BDC
http://www.sap-img.com/abap/bdc-example-using-table-control-in-bdc.htm
For posting weblog,
/people/sap.user72/blog/2005/06/28/sdn-weblogs-making-it-easier
Dynamic Internal table -weblog in sdn
/people/subramanian.venkateswaran2/blog/2004/11/19/dynamic-internal-table
Smartforms
http://www.sap-basis-abap.com/sapsf001.htm
http://www.sap-press.com/downloads/h955_preview.pdf
http://www.ossincorp.com/Black_Box/Black_Box_2.htm
http://www.sap-img.com/smartforms/sap-smart-forms.htm
How to trace smartform
http://help.sap.com/saphelp_47x200/helpdata/en/49/c3d8a4a05b11d5b6ef006094192fe3/frameset.htm
Workflow
http://www.sap-img.com/workflow/sap-workflow.htm
http://help.sap.com/saphelp_47x200/helpdata/en/a5/172437130e0d09e10000009b38f839/frameset.htm
For examples on WorkFlow...check the below link..
http://help.sap.com/saphelp_47x200/helpdata/en/3d/6a9b3c874da309e10000000a114027/frameset.htm
http://help.sap.com/printdocu/core/Print46c/en/data/pdf/PSWFL/PSWFL.pdf
http://help.sap.com/saphelp_47x200/helpdata/en/4a/dac507002f11d295340000e82dec10/frameset.htm
http://www.workflowing.com/id18.htm
http://www.e-workflow.org/
http://web.mit.edu/sapr3/dev/newdevstand.html
ALV
http://www.geocities.com/mpioud/Abap_programs.html
Mail
http://www.geocities.com/mpioud/Z_EMAIL_ABAP_REPORT.html
http://www.thespot4sap.com/Articles/SAP_Mail_SO_Object_Send.asp
http://www.sapdevelopment.co.uk/reporting/email/attach_xls.htm
BOM Explosion
/people/prakash.singh4/blog/2005/05/15/explode-boms-in-enterprise-portal-using-htmlb-tree--part-1-abap
BOM
http://help.sap.com/saphelp_erp2005/helpdata/en/ea/e9b7234c7211d189520000e829fbbd/frameset.htm
http://help.sap.com/saphelp_erp2005/helpdata/en/d1/2e4114a61711d2b423006094b9d648/frameset.htm
http://www.sap-img.com/sap-sd/sales-bom-implementation.htm
http://www.sap-basis-abap.com/sappp007.htm
OLE
http://www.sapgenie.com/abap/ole.htm
http://help.sap.com/saphelp_46c/helpdata/en/59/ae3f2e488f11d189490000e829fbbd/frameset.htm
ALVGRID with refresh
http://www.geocities.com/mpioud/Z_DEMO_ALV_REFRESH_BUTTON.html
For language setting and decimal separator
/people/horst.keller/blog/2004/11/16/abap-geek-7-150-babylonian-confusion
Oracle queries
http://sqlzoo.net/
To format SQL
http://www.sqlinform.com/
SCOT settings
http://www.sap-img.com/basis/basis-faq.htm
Status Icon [ALV,Table Control,Tab Strip]
http://www.sapdesignguild.org/resources/MiniSG-old/from_develop/norm_status_icons.htm#positioning_4
ALV Group Heading
http://www.sap-img.com/fu037.htm
For multiMedia
/people/thomas.jung3/blog/2005/05/11/using-classic-activex-controls-in-the-abap-control-framework
Uploading LOGO in SAP
http://www.sap-img.com/ts001.htm
LSMW
http://www.sap-img.com/sap-data-migration.htm
http://www.sapgenie.com/saptech/lsmw.htm
http://sapabap.iespana.es/sapabap/manuales/pdf/lsmw.pdf
http://www.sap.info/public/INT/int/glossary/int/glossaryletter/Word-17643ed1d6d658821_glossary/L#Word-17643ed1d6d658821_glossary
Here are the two links which contains lots of PDFS:
http://www.easymarketplace.de/online-pdfs-q-s.php
http://www.consolut.de/saphelp/sap_online_help.html
Regards
Anver
<b><i>if hlped kindly mark points</i></b>
Maybe you are looking for
-
Print delivery address in a Purchase Order
Hello, Could you please tell me, what I should to do for print delivery address in a purchase order? I need to configure or activate these fields: Name y Street/House number in the PO printed Thanks!! Best Regards, Mariela
-
Can you use apple tv for 2 televisions
i have apple tv hooked up to a samsung tv. i have another samsung tv and would like to be able to use the apple tv on both samsung tv's. both samsung tv are lan connected to my router.
-
Hi All, my source file is a flat csv file, ex: 10,20,30,40,50 11,21,31,41,51 five fields in source structure. fields 3 and 4 are optional . in this case, when both the fields values are not coming ,how my source file looks like? wat i mean is
-
Images on Facebook do not appear when using different web browsers
Images on Facebook do not appear when using Safari on my Macbook Pro (I've tried Google Chrome too with the same result). This makes me think it's a setting within OS Mavericks that I'm missing. I have not seen this issue on any other computers. T
-
How to make Geological Cross Sections in Adobe Illustrator?
I have been tasked with producing a geological cross section in Adobe Illustrator. It is a lengthy process, as I am new to the software. I never learned it in my GIS studies. I know that there is plenty of GIS software out there to produce x sections