Sie müssen Javascript aktivieren, um diese Seite korrekt darzustellen.

Printing in SAP R/3

Certifications | Principles | Benefits & Detriments
Print Control | Creating forms | Resources | Support
Generals | External solutions | Internal solutions | Demo

Integrator | JetForm | Advanced-Volume-Printing
Cheque Printing | Bar Code Printing | eForms

HP LaserJet Drucker series 4000, 5000, 8000 and 8100 passed the check/3 program for SAP R/3 on Windows/NT sais iXOS test report.

[download] Click here for the certification (PDF format: 254 K)

These printers are the best basis for stethos printing solutions, which also passed the check/3 program for SAP R/3 on Windows/NT by iXOS.

[download] Click here for the certification (PDF format: 56 K)

The complete test report is here readable.

[download] Click here for the testreport (PDF format: 610 K)


Here you find an overview of the supported printer features and the avaliable device types. If you don't find your HP printer or the needed feature please contact us if we have a solution or an updated device type.

[download] Click here to get a document which describes the supported printer features (PDF Format: 79 K)

[download] Click here for a view of the SAP notes 8928 (R/3 supported printers) from 9th July 03 (PDF: 107 K)


Before we start to introduce all particular solutions (not only by stethos) we want to explain the principles of printing in SAP. The print preparation can be merged in two strategies:

  • internal with SAP standart tools : SAPScript
  • external means the data stream will be send to an  "external" software (outside of SAP R/3) which  prepares the print job.

We will show you the benefits and detriments of both solutions from the point of view of a system integrator. Due this you will be able to make the right decision for your requirements.

Various ABAP programs transmit the collected raw datas to the 'forms generator' SAPScript, which creates via 'device types' (similar to a print driver) a printer specific data stream based on precast layout sets. That is the technical point of view.

One way of the extern strategy is to analyse the complete data stream prepared by SAP. Normally a ASCII driver in SAP sytems is used. Further special layout sets are responsible for the fact, that SAPScript just have to transmit the datas in a special format to the printing preparing software.


Benefits and detriments of every single solution:

print control:

My system should normally have full control of the printer. Finally it is very important if a document like a bill had really been printed. 

intern: SAP keeps full control, all entries are dependable caused by direct communication with printer:
real end of job

extern: The datas will only be sent to the preparing program. There is normally no confirmation about printing the documents.

Efford for creating forms:

Necessary forms are complex and should carry the corporate design (own font, logo, etc.) of the enterprise.

intern: Possibilities by SAP using SAPScript programming and construction of device types get no limits, but it is difficult, time consuming and painful without using any special extensions. Due the fact that printing stands normally at the end of implementation, time consuming will be the greatest problem.

extern: In most cases you can use a comfortable program for designing forms under MS Windows.

human resources:

Employees are not only needed while implementation, you have to administrate your forms, too. Nothing gets older faster then a form (changing adresses, phone numbers or CEOs).

intern: Administration of forms is reduced to SAPScript and ABAP programming.

extern: Additonal to know-how about printing preparing in extern systems you have to get known about intern workflows. If you need for example a variable of the data base, which is normally not distributed by ABAP, you need to know how you can get it using SAPScript or ABAP.

hardware and system resources:

Not enough available at any time.

intern: No more resources required. Only little cutbacks are the printer languages  supplied by SAP: Using better and unified device types drivers the data stream could be reduced (laser printer) and graphics could be integrated as well.

extern: To disburden the data base server normally  an add on program is additionally installed on an extern print server. Before transmitting the varibable datas they will prepared with a SAPScript
layout set, means SAP will not be disburden in an effective way. Using an extern product when printing complex documents the printing can be faster in relation to common SAP printing.

Printer support:

In most cases you will not find an unified printer environment, caused by different requirements and producers. But the capable printers are normally page printers (laser printers). By the way, there are a solutions for multi documents sets on laser printers, but later more.

intern: All relevant printer languages are supported, but in relation to PCL only the rudimentary basis commands. Due to this only a little part of the whole feature spectrum (like feeding out of various trays, duplex, etc.) can be used.

extern: Depending to the used software nearly all printing systems are supported under MS Windows, but in some cases with really big data streams.

Future versions of SAP:

Every bigger investment requires continuity.

intern: Should be guaranteed by SAP

extern: Depends on take over of the datas. Some systems modifying SAP (e.g. new layout sets) other systems uses the data stream created by SAP.


The generally difficulty is known at SAP, because in the new R/3 version 4.0 a SAPScript based editor and a RDI (raw data interface) are integreted.

Printing preparing had not be changed in version 4.0, only form creation is supported with a MS Windows SAPScript generator, but at least this generator generates SAPScript layout sets and nothing had changed in relation to functionality of SAPScript.

Please notice, that all named solutions only work on local and network printers and not on remote printers (SAPLPD).

Of course this confrontation can not offer you the all over including solution. Click here for "internal" and here for "external" products and solutions. In some cases the solutions exceed the named borders, but reduce to printing on page printers (e.g. laser printers).

TIP: You should have a look at this solutions, because you will find solutions for laser printers you would not normally think of.


Demo with possibilities of from printing in SAP

stethos is intensivly engaged in possibillities of [form] printing under SAP. We have the possibility to create forms as you want them to be, only by using the standart tools of SAP and in some cases a flash memory solution. Placing of logos, bar codes or water marks is no longer a problem.
A small demo file should demonstrate, what could be done. The first two pages are the common SAP printing pages. After that for comparing you get known of what SAP can really do.
By modifying the printer driver all possibilities of SAP are avialable and a special lack when printing copies will be deleted:
Every time when SAP has to print originals and copies, SAP makes a print preparing and a complete data base request for each copy. That raises costs, bottlenecks in network and pc resources. With a solution by stethos, this problem will be gone.
Our demo example shows, how this will be done with only 30kB additional data after the original page, and that with watermarks and logo.
We kindly offer you our know-how. With only one day consulting you will be able to fit your printing forms by yourself. Please contact us directly for information about this special service.

[download] Click here for downloading the demo file (PCL5 printfile sapprint.zip: 11 K)