Enhancement on smartforms

Hi experts,
I want to place a code when the print button (i . e Text --> Print ) is clicked.
I searched for exits and Badi's (Package name : SMART) but none existed.
I also checked the layout .  the function code in the PF STATUS is SPRI.
Please help me out . Can you help me where to place the
case sy-ucomm.
   when 'SPRI'.
endcase.
Thanks in advance guys,

Hi,
Make sure that the component names and the component types of the newly added fields start with 'ZZ'
Goto se14, enter PA0006 and click on activate and adjust.
Hope this helps.
Regards,
Pulkit

Similar Messages

  • Automatically login the user when he clicks on a URL in Adobe Form

    Hi Experts,
    Am currently working on the e-recruitment module & have a query pertaining to Adobe Forms. As per client requirement the offer letters are despatched to the candidates in the form of an Adobe Form. This form will contain a URL to a 3rd party website. On clicking the URL the candidate would be taken to a website where in he can attend some online training sessions. Now the complexity lies in the fact that the client is adamant upon the user being automatically logged on to that website when he clicks on this link. Am new to Adobe Forms and could just realize up to creating an URL for navigating to the logon page. But how can I embed even the users credentials within this link so that he is automatically logged on to the website? Any inputs on this would be highly appreciated.
    Regards,
    Uday

    Hi Otto,
    Sorry for the late reply its 10pm for me here... And yes I do very much need your help as to how to proceed with the development. We were all thinking to try say to the client as it isnt that easy to come up with a solution! Would really appreciate your inputs over the same...
    And please forgive me I just got to get some more clarifications. There is a standard smartform provided by SAP HRRCF_CS_EXA_OFFER_CONTRACT which is used as a template by the system when an offer is extended to someone. (This template is maintained in SPRO against the extend offer activity) Internally SAP does convert this smartform into a pdf for mail/preview/print purpose. So am sorry that this isn't directly an Adobe Form which I can enhance. I guess I would have to enhance the smartform to contain a URL....  Sorry for the mixup & hope you can help me with this form instead. I would at least like to learn this URL generation logic if you aren't knowledgeable about including a URL in a smartform.
    Regards,
    Uday
    PS: I have sent across some further technical details to you.

  • Category in Email-Notification

    Hi,
    when a new service-desk-message is created the support-team gets an email-notification.
    Now, we woulld like to add the category in the email.
    Is it possible an what are the steps requiered?
    Regards,
    Bjoern

    Hi Bjorn,
    you have to enhance the mail action with your own code, therefore a zaction is needed
    you have 2 choices:
    1. you enhance the Smartform directly with your coding. Just check how the other fields are filled there.
    2. you enhance the mail sending method with your own code.
    Check FM CRM_GET_ACT_CATEGORY to recive the needed data.
    Tell me if your need more information.
    Regards
    Ali

  • Using Smartforms with Dunning

    Hi,
    I want to use a smartform (e.g. the default F150_DUNN_SF) but can't get it to work. I know the procedure:
    - go to Customizing - Financial Accounting Global Settings - Tools - Customer Enhancements - Business Transaction Events -> Settings | P/S modules | ...of an SAP appl.
    - change the FM for 1720 from FI_PRINT_DUNNING_NOTICE to FI_PRINT_DUNNING_NOTICE_SMARTF
    - go to Customizing - Financial Accounting (New) - Accounts Receivable and Payable - Business Transactions - Dunning - Printout - Assign Dunning forms
    - select a procedure and double click "Forms for normal dunning procedure" and enter a company code. Then I get the names of the forms used for each level and should be able to change them.
    There is the problem: when I fill in a smartform, like the default F150_DUNN_SF, I get the error "Form F150_DUNN_SF is not defined or is not active" (while clearly it is both). I'm guessing he only looks for sapscript forms.
    So how do I specify which smartform to use for Dunning? Has anyone managed to do this? I've read all the help and forum posts about this, saw some other people with the same problem, but no solution posted.

    I actually knew that I was supposed to ignore the error, but I couldn't get it to save. But your reply made me try clicking the green checkmark and that was the key to saving. So thank you, problem solved

  • SAPFM06P - Can this program be used for triggering a Smartform Output??

    Hi Experts!
    I researched a lot and came to a conclusion that Program SAPFM06P can only be used trigger either a SAP SRIPT Output or a PDF FORM output. It cannot be used to trigger a SMARTFORM output directly as there is no code in it to trigger a SMARTFORM.
    My understanding:
    I will have to either create an Enhancement to the Program or a Zcopy of SAPFM06P where I need to write the logic in form routine ENTRY_NEU to call a SMARTFORM.
    Please tell me if my understanding is correct and please guide me if there is any easier way to achieve the same functionality.
    Thanks for help!
    Greetings,
    Amit

    Hi,
        U can Copy this standard Program to ZProgram and Insert the FM SSF_FUNCTIONMODULE_NAME and call ur smartform and assign the same combination to the Output type Given to u in NACE Transaction..
    This is the Driver Program which I used for PO Smartform
    [http://vjkvijaya.blogspot.com/2009/03/puchace-order-smartform-driver-program.html]
    Regards,
    Vijaya Lakshmi.T

  • Standard Smartform printing purchase requisition through - ME51N / ME52N

    Hi Experts,
    we are trying to build functionality to print Purchase requisition through transaction ME51N / ME52N / ME53N. we have created a print button on Customer data screen for that. Now we are looking for any standard smartform or script which can be used for printing Purchase requisition.
    Please provide me some pointers for the same.
    There is print button avalable at item level of purchase requisition. but it will not print header records. i am not able to find this form in system also. how can i find this form?
    thanks

    >
    rajpal sehrawat wrote:
    > Hi,
    >
    >
    > Header records means we might provide some header level information like PR number , short text and logo. Currently we are able to print only line items present in the ALV grid.
    >
    >
    > we are looking for some similar form which can be enhanced.
    >
    >
    > thanks
    actually the PR number is a line item field - it comes out of table EBAN. You would have to store the logo someplace else, since it does not belong to the PR (EBAN) -> neither header nor item, but is 'simply' graphics stored elsewhere in the database.
    I wouldn't know of any form in MM-PUR which you could easily adapt to printing PRs (and have never before heard of the need to print them) - so you will have to do a custom abap. Since there is no possibility to maintain NACE for PRs (it's simply not available) - I wouldn't know where you could use a smartform/sapscript ... that custom abap is all you can do ...

  • 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
    smita

    Yes, 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

  • Print the head text in a Smartforms - READ_TEXT Function

    Hello,
    I have a huge problem to print a MM document's. I need show the text head in the footer of the document. For this i use the READ_TEXT function. To use this function i enter to vl03n transaction, enter the document number, go to the text head, double click, and i see the parameters = Name (document number), language (ES), id (0001), object (VBBK)...
    In the smartform code I write this:
    <b>DATA: leng TYPE thead-tdspras,
          l_fname TYPE thead-tdname.
    DATA: il_tline LIKE tline OCCURS 0 WITH HEADER LINE.
    leng = 'ES'.
    l_fname = is_dlv_delnote-hd_gen-deliv_numb.
    CALL FUNCTION 'READ_TEXT'
      EXPORTING
        client   = sy-mandt
        id       = '0001'
        language = leng
        name     = l_fname
        object   = 'VBBK'
      TABLES
        lines    = il_tline.
    comentario = ''.
    LOOP AT il_tline.
      CONCATENATE comentario il_tline-tdline INTO comentario SEPARATED BY space.
    ENDLOOP.</b>
    But to try print a document with number 0012345678 through to the IDCP transaction return me the follow error:
    Text 0012345678 ID 0001 language <b>EN</b> no exist
    why change the language?
    i see the STXH table, and i found this register:
    MANDT   TDOBJECT      TDNAME         TDID      TDSPRAS
    200             VBBK       0012345678           0001        S
    Where is my problem?
    Please, help me!!!
    Regards.

    Hi rudiRocket,
    Welcome to Numbers discussions.
    Yes I see what you're talking about, never noticed it. To remove the shadow I tried numerous fonts but, still the shadow. Let's hope someone else has a better answer. Be aware folks on these Discussion boards are, as yourself end users not Apple employees.
    In the mean time please read the below instructions:
    Send feedback directly to the Numbers team for enhancement requests: at the top of your screen to the right of the blue Apple please click "Numbers" > "Provide Numbers Feedback". Explain in detailed what you've found. This makes your request known to the Numbers team directly; don't expect to hear back from them. I've sent many as well.
    Let's hope the next version of iWork incorporates many of the requested enhancements.
    Thank you in advance for doing that.
    Again, welcome to Numbers Discussions, have fun here.
    Sincerely,
    RicD

  • How to call smartform in me54n

    Hai All,
              Iam developing a smartform for PR print with  ztcode,the user asked me that,he dont want seperate tcode,in me54n tcode itself he want
    print.I have tried in the enhancement spot but it is not firing.
    Regards,
    Siva jyothi.

    Hi ,
    The print button creates a spool number through which you can get ALV output of the ITEM details but cannot call smartform from that.
    PR is just an internal document.There is no other way to do it(As far as i know).
    You now have only two options to go for:
    1) Create a subscreen with a pushbutton , and then call the driver program to print the smartform.
    2) A Z transaction to print the PR , which you have already done.
    Let me know if you find any other way to do it.
    Br.
    Giri

  • Change e-mail sender smartforms

    Hi Experts,
    When I send a billing document from VF03 to a customer, the e-mail address is read from my sap user (SU01). I would like an e-mail address for each billing type, but I don't now how to change "mail_sender" parameters in the smartforms (RLB_INVOICE program).
    Can you help me, please?
    Thanks.
    Luca

    No, it certainly is an ABAP-related issue.  Developers are the only ones smart enough to figure this stuff out ;-).  The note says nothing about sender configuration for medium '5'.  The sender is hard-coded as SY-UNAME during the communication strategy analysis (since the call to CONVERT_COMM_TYPE_DATA does not specify a sender).
    This is a common issue - most companies normally use a single sender for all invoices (or invoices per company code) and identify the correct sender details on the job user ID.  If this isn't good enough, then you have two choices: use a custom program to generate the email yourself after rendering the form (a copy of RLB_INVOICE) and specify the sender OR enhance the existing function to return a different sender based on your criteria.  Personally, I'd go with the custom approach.

  • Steps involved to Configure a Smartform for printing TO Item

    Hi,
    I want to develop a Smartform to print TO for each Item.
    Currently it is being done using SAP Script.
    I checked the Configuration in OMLV and assigned my print program Z****** .
    This thing here is I don't see any values passed to my program like TO Number, Whse Number etc when called through LT31.
    Where as I assign the standard program RLVSDR40 and debug it all the details are being passed to this program.
    I am not sure if I am missing any configuration.
    Please help me to figure out the issue and let me know all the steps involved in configuring the Smartforms to print Transfer Orders.
    Thanks in Advance.
    MK.

    Hi Murali,
    The SAP delivers the solution to print the TO item by SAPScript, but we can do it by Smartform as well, as in
    You need to create a project for the enhancement MWMD0001, because EXIT_RLVSDR40_001 will fulfill your purpose of doing it the other ways i.e. via Smart from.
    For this you have to use CMOD transaction to create the project for the above said enhancement.
    Note: If you do this way any configuration done via OMNU wont't be considered.
    Then after in teh import parameters you have a table XRLDRI, which contains both the warehouse number and the transfer order number, the same can be passed on to the designed Smartform to fulfill your purpose.
    Sample Code, you can refer to:
    *local variable declaration.
       DATA: l_wa_fm_name            TYPE rs38l_fnam.
    * Local Field Symbols
       FIELD-SYMBOLS : <l_fs_rldri> TYPE rldri.
    * Local Constant declaration
       CONSTANTS : lc_fmname TYPE tdsfname   VALUE 'XYXYXYXY',  "Smartform name, here designated by 'XYXYXYXY'
                   lc_chk      TYPE rldrudruck VALUE 'X'.
    *Moving Transfer Order Print :Item level data into corresponding work area.
       LOOP AT xrldri ASSIGNING <l_fs_rldri>.
    * Determine smartform function module
         CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'
           EXPORTING
             formname           = lc_fmname
           IMPORTING
             fm_name            = l_wa_fm_name
           EXCEPTIONS
             no_form            = 1
             no_function_module = 2
             OTHERS             = 3.
        IF sy-subrc = 0.
    * Call the function module of the smartform
           CALL FUNCTION l_wa_fm_name
             EXPORTING
               user_settings    = lc_chk
               tanum            = <l_fs_rldri>-tanum
               lgnum            = <l_fs_rldri>-lgnum
             EXCEPTIONS
               formatting_error = 1
               internal_error   = 2
               send_error       = 3
               user_canceled    = 4
               OTHERS           = 5.
           IF sy-subrc = 0.
           ENDIF.
         ENDIF.
       ENDLOOP."LOOP AT xrldri ASSIGNING <l_fs_rldri>. 
    Please validate the same at your end and let me know in case you require any further inputs from my end.
    BR/Thanks
    Pranav Agrawal

  • Advantages of  adobe forms over sapscripts and smartforms.

    Good day ,
    Can anyone pls mention atleast 2 to 3 major differences between sapscripts,smartforms and adobe forms?
    I want to know wat r the drawbacks in each n how we rectified it in adobe forms.Are there any disadvantages in adobe forms??
    Awaiting your reply,
    Thanks,
    Deepthi.

    Hi Martina,
    SAP Interactive Forms by Adobe offer you the following business advantages:
    1.  Interactive functions automate the creation of data for SAP systems
    2.  Full integration into the SAP development environments for Java and ABAP
    3.  User-friendly tools reduce the time and costs associated with creating form layouts.
    4.  The usage of the PDF format means that forms retain their appearance regardless of the environment they are used in.
    Moreover,
    SAP Interactive Forms by Adobe offer the following basic functions:
    1.  Create form templates for the layout that include logos or pictures
    2.  Generate documents by merging form templates and current system data
    3.  Edit forms online or offline
    4.  Forms can be filled in advance automatically with specific data from SAP applications and then sent to the correct recipients using secure methods
    5.  Automatic consistency checks for forms
    6.  Activate enhanced functions such as comments
    7.  Digital signatures and form certification
    8.  Send completed forms to the SAP application with automatic updates of the business data
    There are not any disadvantages in adobe forms as such except the value help is not present but that could be done after a little coding.
    Reward if useful.
    Regards,
    Vaibhav Tiwari.

  • Purchase Order Form Smartform

    Gurus,
    I need help in transforming the standard sapscript PO form into smartform.
    I understand that the smartform for this is /SMB40/MMPO_L
    What would be the print program for this?
    If I use SAPFM06P, the print preview would display a message that says "Error in OPEN_FORM for document ...."
    If possible, please guide me with the step by step process on how to do this.
    Points will be rewarded.
    Thanks

    In researching this, it appears SAP realized they missed the print program /SMB40/FM06P for smartform /SMB40/MMPO_L.  SAP has a note 968332 for patching the SAP best practices baseline package (US) V1.600 that includes these essential transports to get the missing PO print program installed and working:
    RS5K908607, RS5K920133, RS5K942991, RS5K912175 and RS5K919363.
    The next problem I ran into was trying to email the PO smartform. Next I found they had a bug in this new print program (or at least I perceive it as a bug) but could find no notes specific to this. That being said I made this change and now I can email the PO smart form.
    The bug is within form get_addr_key where they move l_lfa1-adrnr to ls_addr_key. However the local changing parameter is named l_addr_key (not LS). So I made the following two enhancements:
    Old: CHANGING l_addr_key.
    New:  CHANGING l_addr_key type addr_key.
    Old: MOVE l_lfa1-adrnr TO ls_addr_key.
    New: MOVE l_lfa1-adrnr TO l_addr_key-addrnumber.
    Other than this everything else seems to be working as expected. Even updates to our document management system as expected (print and archive).
    Tim

  • SAPSCRIPT,SMARTFORMS,PDFFORMS

    Hi SDN Friends!
    I had this question.
    Given a SAP Script or SMART Form ... how do we identify (table names?)
    The Print program associated with them?  Also, how does that concept differ from PDF forms?
    Any body can answer please........
    Markiv

    hi,
    Interactive Forms based on Adobe software is SAP's new solution for forms development. Its first release has the focus on interactive use of forms. High-volume printing is supported in principle, but - being a new solution - the performance has not yet reached the same level as Smart Forms or SAPscript, two established solutions that had years to grow. Interactive Forms is the only solution that will continue to be enhanced with new features, while SAPscript and Smart Forms will be supported without limitations.
    When (or if) to move to Interactive Forms depends on your requirements. For interactive forms usage, i.e. the new functions, you have no choice, as the existing solutions don't support it. High-volume print scenarios need to be carefully analyzed to see whether your concrete requirements can be met at this point.
    However, it is possible to move to Smart Forms and design your forms in such a way that a migration at any point in the future would be but a small step. Smart Forms offers from Web AS 6.40 a migration wizard to Interactive Forms. Technically, everything can be migrated, but we recommend against things like ABAP program nodes, for example.
    You are not forced to ever go to Interactive Forms if you don't want to. It really depends on whether your client needs any of the new features in Interactive Forms. Also, if they are currently working with JetForms, they could enquire with Adobe directly what migration path they offer to the joint solution.
    It is impossible to make a blanket statement on what needs to be done in each of the applications using a form for output. Despite the same underlying technology, forms handling has always been a decision for each SAP application: Some do it through customizing, some through coding, some in yet anither way.
    What I CAN say from a technology pespective is that all applications are in the process of creating their forms based on Interactive Forms so that by 2007 pretty much all SAP forms will be PDF-based. Obviously, each application does it within the framework of their application - but they all use Interactive Forms.
    By the way, be aware that in ERP 2004 this forms solution is subject to a limitation for high-volume printing scenarios as we cannot ensure that ALL customers will be content with the performance in ALL scenarios with this release. (see SAP Note 863893).
    creating :
    To get an overview idea about Adobe forms ,
    Using SFP , first you need to create a interface . in interface you can declare the import and export parameters and also the declaration part, coding etc : This is nothing but similar to Function module interface.
    And now we have to create the Form which is interactive. Create the form and enter the interface name which you have created in first step, so that the parameters , declarations of fields etc : will be copied and available in the form layout. So that you can drag and drop these declared fields ( dclared fields of interface ) to the layout.
    Create the context and layout in the form.
    The layout generated can be previewed and saved as PDF output.
    Now we need to integrate the driver program and the PDF form to get the final output as per the requirement.
    On activating and executing the form you will get a function module name just similar to smartforms.
    The driver program needs to call this FM.
    Refer to the below sample code :
    DATA : is_customer TYPE scustom.
    DATA : it_bookings TYPE ty_bookings.
    DATA : iv_image_url TYPE string.
    DATA : iv_sending_country TYPE adrc-country.
    DATA : it_sums TYPE TABLE OF flprice_t.
    DATA : docparams TYPE sfpdocparams.
    DATA : formoutput TYPE fpformoutput.
    DATA : outputparams TYPE sfpoutputparams.
    PARAMETERS : pa_cusid TYPE scustom-id.
    SELECT SINGLE * FROM scustom INTO is_customer
    WHERE id = pa_cusid.
    SELECT * FROM sbook
    INTO CORRESPONDING FIELDS OF TABLE it_bookings
    WHERE customid = pa_cusid.
    outputparams-nodialog = 'X'.
    outputparams-getpdf = 'X'.
    *outputparams-adstrlevel = '02'.
    CALL FUNCTION 'FP_JOB_OPEN'
    CHANGING
    ie_outputparams = outputparams
    EXCEPTIONS
    cancel = 1
    usage_error = 2
    system_error = 3
    internal_error = 4
    OTHERS = 5.
    IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
    WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    ENDIF.
    docparams-langu = 'E'.
    docparams-country = 'US'.
    docparams-fillable = 'X'.
    CALL FUNCTION '/1BCDWB/SM00000043'
    EXPORTING
    /1bcdwb/docparams = docparams
    is_customer = is_customer
    it_bookings = it_bookings
    IV_IMAGE_URL =
    iv_sending_country = 'US'
    IT_SUMS =
    IMPORTING
    /1bcdwb/formoutput = formoutput
    EXCEPTIONS
    usage_error = 1
    system_error = 2
    internal_error = 3
    OTHERS = 4
    IF sy-subrc <> 0.
    MESSAGE ID sy-msgid TYPE sy-msgty NUMBER sy-msgno
    WITH sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
    ENDIF.
    CALL FUNCTION 'FP_JOB_CLOSE'
    IMPORTING
    E_RESULT =
    EXCEPTIONS
    usage_error = 1
    system_error = 2
    internal_error = 3
    OTHERS = 4
    IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    use link
    http://help.sap.com/saphelp_nw04/helpdata/en/d2/4a94696de6429cada345c12098b009/frameset.htm
    regards,
    Prabhu
    reward if it is helpful

  • High Priority, Change PO output enhancement / userexit?

    Hello guru's,
    Will anyone guide me. I have an issue, if i go to change mode of a PO (ME22N) and delete the existing Output Medium (Fax, Printer,IDOC,..) etc,. it shouldn't send any output after saving the Order.  Is there any user exit existing within SAP Scope to support this functionality?.  or will anyone suggest me any enhancement for this function? so that i will proceed.  It will be of great help. It is an urgent issue pl
    Reward full points

    Hi venkat,
    in the print program the Fm which u wud be calling for smartform takes control parameters as input.
    TDNEWID = 'X'.
    TDIMMED = 'X'.
    TDDEST='locl' <ur printer>
    set these parameters of the struture tht u wud be passing as control parameters
    it wud print automatically when smartform gets processed
    Hope it will help you.
    Regards ,
    Nikita

Maybe you are looking for