Sap postscript file

This is to check the file for the postscript formatting and commands used by SAP. This can be useful to note where to insert postscript commands via print controls also for any trouble shooting. For reference you can check out the one I prepared earlier. One way is with client or printer side scripting to insert the code prior to further processing.

Another way is to insert the code into an SAP device type. So this blog focuses on this method. I could expand on the options available in subsequent posts, depending on feedback.

SAP device types have some built in limitations that make the use of the postscript BWIPP code harder than a simple cut and paste of the code. It should be clear but to clearly state, inserting postscript programs is outside normal SAP helpdesk support. The way a page is printed in SAP is linked to so called formats in a device type. If you take a look into a format of POST2 it looks like the following. These procedures play an important role in generating the barcodes. The limitations found in any ACTION page are that they are limited to 72 characters per line , can have a total of lines and any white space at the end of a line will be truncated.

We need to extract the appropriate code for the barcode required. The barcode. Take QR Code as an example and the barcode. The code sections required would appear in the following text files. So due to the limitation in the ACTION pages described earlier, then you need to manually split the code into lines no longer than 72 characters and the number of lines of each file is less than You need to run this script against the 3 files, making sure not to remove all the comments from the credits file.

Filenames generated should have the following naming convention. This will be achieved by using print controls to call postscript procedures in the same way as the SAP method above. These procedures are called at the required place via printer controls in smartforms or sapscript. The code in postscript would appear as. The bwippst procedure sets up the position and size of the barcode.

Below are other print controls that can control the appearance of the barcode. This is important as you need to pass consistent length of data to get a consistent position for the barcode.

We can control the barcode size and position relative to the current position on the page. The consistent positioning is only possible if a known length of characters is passed every time within one print job. Allow enough room for the barcodes size in the smartforms cell or sapscript page.

Carriage returns can be used before the actual text of the barcode to make the required space for the barcode. See the video at the end of this blog demonstrating the use of printer controls in smartforms. This is a freeware program that can be used for commercial purposes. Next a Frontend output device needs to be created in SAP. To have a dedicated front end printer for barcodes then you can rename the Cute PDF writer to match the entry in the SAP output device.

Here the frontend printer name matches the name of the printer on the desktop. We are going to introduce a link QR or Datamatrix on our papers where customers can get further information. Like 0 Share Right click and copy the link to share this comment Former Member November 9, at am Hello, thanks for the comment, As for printing to non postscript printers then you could try… I have not tested these. I have tried this I cant recommend it though but it is easy to setup.

I have tested a postscript driver for HP found on the HP support site. So it could be possible with other HP printers, check if the HP printer supports postscript on the config page, most likely there will be a postscript driver probably :.

Like 0 Share Right click and copy the link to share this comment Sergio Ferrari November 8, at am Thanks for this blog Robert, I would invite you to create a wiki section about mobile tagging and I'll be happy to contribute with you. This is really an hot topic, let's cooperate Sergio Like 0 Share Right click and copy the link to share this comment Former Member November 9, at am Hello Sergio, Thank you for your comment and additional information. I would be keen to contribute and cooperate on this.

I have no permissions to create wiki pages, but I can add a page to the stage area and see where that takes me. Best Regards, Robert Like 0 Share Right click and copy the link to share this comment Former Member July 7, at pm Hi Robbert i want to ask you regarding smartforms that i built with include printer-control.

So I suggest you check out the raw format of the spool request. As you get the barcode then I guess ZBW01 will not show up.

For testing purposes swap out the device type and print controls for SAP standard and see if they appear. Check out my business card for my email address, I am happy to help further via email. The mapping is stored in table TSP0B. You can use transaction SE16 display the data in the table for the corresponding "new device type assigned to each of these key entries:.

If you want to add an additional device type to the table, you can specify in the report which SAP device type is to be assigned which XDC file, and create the entry in the table. The basic device types delivered by default should not be changed. This assignment between printer language and standard XDC file can be specified in the lower table.

When creating or modifying an entry, you need to specify the name of the XDC file in question. The type specifies which printer language is used by the XDC file. Choose F4 to display a list of the permitted values If the type of the XDC file does not match the printer language of the device type, a warning is displayed. This entry is highlighted in red in the overview.