A. Mostly PCL, but SAP also includes device types for Postscript, thermal printers, and plain ASCII output.
A. There are 2 methods: interactive and batch printing. Interactive printing provides the user with a print "icon" on their SAP-GUI workspace, which will print their current screen. Batch printing may be setup by the user, but is usually done at specific scheduled times.
A. SAP R/3 is a client-server architecture, and SAP-GUI is a Windows program that is loaded on the user system. It connects to the SAP R/3 application server.
A. Each user should have a printer Output Device assigned to the printer they are supposed to use. Their SAP-GUI print dialog should have one or more Output Devices available to them to use.
A. It is a unique name assigned to these components, collected as a group together:
A. This list is by no means comprehensive, and each method is represented by a single character:
A. This is an advanced Windows Front-End Printing method, only available in R/3 versions 6.20 and higher.
A. Yes. The device type is a system-independeent transport method to install the device type into your SAP system.
A. NO. Device type files (usually .PRI extensions) are transport methods, and should never be directly modified.
A. Follow these general instructions: readme_upload.txt.
A. You should never modify an existing device type, but instead copy it and then modify it:
A. Use the LEXUTF8 device type, and a Lexmark printer using the International Printing for mySAP Business Suite.
A. Yes, use a Lexmark Font Card for Japanese, Simplified Chinese, Traditional Chinese, or Korean, and the appropriate Asian device type.
A. Not at this time. Please use the internal I2HP4 device type in your SAP system.
A. Yes. Use the I5LEX device type.
A. Use the Lexmark Bar Code Card or Forms and Bar Code Card in your Lexmark printer.
Then add a SBPxx mnemonic to your desired device type, and use that mnemonic within your SAPscript form. This is added in the Controls section of your device type Don't forget to terminate the sequence with another SBSxx mnemonic.
If in doubt, install the ZOPTRA device type and copy the HEX sequences from it.
Also, install the Bar Code Unit Test Program, which will provide SAP Standard Text examples for the programmer.
A. Not really. Your SAP print screen shows the progress of your print job, through the TempSe print spooler. Once the job leaves TempSe, it is completed. In many cases, the print stream output is delivered to the printer, but for many reasons does not print (paper jam, out of paper, etc). The solution for that situation is to employ third-party output management middleware, which will count the pages from the printer, and inform the SAP spooler of it's progress.
A. No. This product is available from companies such as Plus Technologies, Macro4, and HP (Dazel).
A. Typically the OMS has a small SAP component that runs on the SAP server, and hooks into the SAP X-OM print interface. This interface allows the output management software server to "hold off" the SAP print system from immediately confirming the print job, as well as providing job status and intervention information to the SAP user that they otherwise would not receive.
A. Please read all the material on this SAP web site, and if necessary, contact 1-800-LEXMARK.
A. There are several methods, but the most popular is either intercepting a Unix spool, or using the FILE output method in Windows.