Problems with the output device 'LOCL'
I am setting up shop papers (PM) in Smart Forms using Helvetica font. The shop papers were designed with output device LOCL. The output changes (spaces between words) based on the output device. How do I fix this?
As a rule, I advise clients to avoid designing forms using output device LOCL. It can generate inconsistent results. Unlike named logical devices, LOCL is a special device that dynamically looks for a printer defined on your own computer. There is no guarantee it will always find the same type of printer. For instance, your forms developer may have a default printer installed on his or her personal computer -- which LOCL goes to -- that is completely different from that of the functional owner/tester. Even worse, these both may differ from the final intended destination. The result of this is chaos.
To paraphrase Stephen Covey, a far better approach is to begin with the end in mind: Identify in advance the SAP device type of the ultimate Production output device(s). Then make sure a logical device using this type is set up in both your development and quality environments, and rely upon that one exclusively for design and testing. It will greatly reduce your pain down the road.
Dig Deeper on SAP development and programming languages
Related Q&A from Mark Smithson
How to fix a slip print-out error in an SAP Smart Form
An SAP user is looking to fix an error with a packing slip print-out in an SAP Smart Form. Continue Reading
Setting soft breakpoints in ABAP that reside in Smart Forms
I've always set hard-coded breakpoints in ABAP code that reside in a Smart Form. Is it possible to set soft breakpoints instead? Continue Reading
Printing addresses without a country line using SAPscript
The address key is handy for printing addresses, but what if you don't want the country name printed? Expert Mark Smithson lets you know how to ... Continue Reading