
3
A Zebra Technologies White Paper
This paper will:
Present options for bar code printing •
from SAP;
Explain the advantages and limitations of •
different output methods for common SAP
usage scenarios including:
Direct Printing from SAP (SAP Smart Forms •
and Interactive Forms)
Upload Method (SAPscript)•
Zebra’s Upload Solution: Zebra • BAR-ONE
®
for mySAP™ Business Suite
Third-party Bar Code Software for Upload•
Output Management Software•
PC-based Labelling Software (Middleware);•
Describe how to use Unicode™-enabled •
printers to avoid custom forms design to
support international character printing; and
Explain how SAP information can be output •
from mobile and wireless printers.
Zebra has extensive SAP bar code printing experience
and has specific products to support each method.
Zebra is thus uniquely positioned to recommend
the optimal SAP bar code printing solution for its
customers, regardless of their legacy environment.
Introduction
Without native support, printing bar codes from
SAP requires software to execute several functions.
Static and/or variable data required for the bar code
label must be extracted from the SAP system.
Next, information must be encoded in a bar code
or otherwise formatted to meet the content and
presentation requirements for specific label fields.
The label file, with all bar code, text, and graphics,
also needs to be formatted for the printer control
language of the printer where the output is directed.
Prior to SAP’s breakthrough developments, a variety
of alternatives were developed so SAP customers
could output enterprise information in bar code format
wherever and whenever necessary. All the approaches
for bar code label printing from SAP are based on
either uploading the printer control language to the
SAP application, or downloading SAP conversion
functionality to the print system. The three most
common approaches for bar code printing in the SAP
environment are:
The upload method, in which bar code labels •
are designed using a third-party software
package and uploaded into mySAP™ Business
Suite through SAPscript programming. This is
by far the simplest, least expensive, and most
common method of driving bar code label
printers today. One product for the upload
method is called Zebra BAR-ONE for mySAP™
Business Suite.
Using third-party output management software •
to design forms and labels. This approach is
known as middleware as it requires that the
software convert SAP output into bar codes
and commands that printers can recognise.
Running bar code labelling software networked •
to the SAP system to query directories or print
queues. This is another middleware approach
and normally requires the software to run as
a Windows Server™ converting SAP output to
that of the printer control language.
Printer control language support has been the main
obstacle to efficiently integrating bar code label printers
with SAP systems. For years, SAP software only
supported two printer control languages, PostScript
and PCL. These languages are common in laser,
inkjet, and other office printers, but are not supported
by thermal bar code printers, which are designed
to produce labels, not documents. So, further data
conversion and command manipulation was always
required so bar code printers could recognise SAP
output.
Finding the best way to make the conversion depends
on several variables. These include the number of label
formats that are used, the frequency that labels change
and that new formats are needed, the number of bar
code printing locations, the legacy base of bar code
label printers, and the amount of SAP programming
and support resources you want to commit.
The following sections present the options for
generating bar code label output from SAP, with
guidance to where each method is appropriate.
Comentarios a estos manuales