SAPscript Output Problem - Very Urgent - Please help

[Former Member]

Hi,

I am having the following problem with SAPscript.

In the Main Window, I have instructions to the printer in the ZPL2 language (For Zebra Printer).

There are also several variables, which are highlighted in Gray and enclosed in the’&’.

There are also several elements – all of them empty except for the one where this code is.

Now, I received this program to modify in terms of code and the output.

IF you have never done any work with Zebra Printing, the way it is done is that you create a label using the Zebra BarOne or Zebra Designer program, then output it to an ‘itf’ file, upload it into a standard text as .itf and copy the uploaded contents to the main window. When printing to a Zebra printer, the Zebra printer will read the instructions and will print the output.

Here is the problem: The config for the output type is correct.

When doing a printing test from SAPscript, I get the right output and the Zebra printer is able to print it.

However, the real process for this task will go through MB02. There, if I create a spool request using the proper method (select output type and etc.), it will go the spool. However, if I print preview or output (doesn’t work with the Zebra printer, so I have to output to the Laser printer), it will output the following (none of the following includes any of the ZPL2 code/instructions. Instead, it seams to print the variables contents with the field name next to it – This isn’t whats it’s the Main window!!!)

http://img244.imageshack.us/img244/6915/66052475zk2.jpg

Please help. I have debugged but don’t know what to do and can’t find anything wrong.

This is very urgent. Any help will be useful.

Thanks,

John

[RichHeilman]

Interesting, I would have expect to see all of the ZPLII coding, and the actual values where the variables were in the coding of the sapscript. Basically, the ZPLII coding can only be read and rendered by the zebra printer, sendint his to a laser printer will give you the ZPL coding and not want it would be rendered to in the Zebra Printer.

Is this the issue? Do you expect this label output to be rendered on a laser printer? I'm not sure what you are asking, sorry.

REgards,

Rich Heilman

[Former Member]

Ok, maybe I have confused others in regards to the issue as well.

We expect this label to be output from a Zebra Printer.

When output through Sapscripts printing test, the preview from the spool shows the ZPL2 code in small font (non readible if a created a screenshot) and if sent to the Zebra Printer, it prints the label correctly.

When output through MB02, the preview from the spool shows the code that I have attached to the 1st post in this thread. If I try to output to the Zebra Printer, nothing happens because the ZPL2 instructions are not even in the preview and therefore, the Zebra printer recieves no instructions. I should not have mentioned the laser printer, because it has nothing to do with this issue.

I hope that this makes the issue a little more clear and understandable. Please help.

Here is the ZPL2 coding before uploading to standard text (only difference is that once uploaded, the '/' characters are removed.) However, I believe that the problem may lie in the print program and how it compiles but I debugged and haven't really seen where it comes from:

/:NEW-PAGE

/ ^XA

/ ^DFNEW-RE-1FS

/ ^PRC

/ ^LH0,0FS

/ ^LL1830

/ ^MD0

/ ^MNY

/ ^LH0,0FS

/ ^FO244,854A0N,55,46^CI13FR^FB154,1,0,LFN999^FS

/ ^FO819,698A0N,55,46^CI13FR^FN998FS

/ ^FO245,477A0N,55,46^CI13FR^FB755,1,0,RFN997^FS

/ ^FO389,926A0N,55,46^CI13FR^FB654,1,0,RFN996^FS

/ ^BY3,3.0FO42,1072^{B3N,N,152,N,Y}FR^FN995FS

/ ^FO276,1258A0N,55,46^CI13FR^FN995FS

/ ^FO484,774A0N,55,46^CI13FR^FN994FS

/ ^FO817,774A0N,55,46^CI13FR^FN993FS

/ ^FO611,556A0N,55,46^CI13FR^FN992FS

/ ^FO245,556A0N,55,46^CI13FR^FN991FS

/ ^FO397,117A0N,55,46^CI13FR^FN990FS

/ ^FO245,405A0N,55,46^CI13FR^FB880,1,0,RFN989^FS

/ ^FO244,698A0N,55,46^CI13FR^FN988FS

/ ^FO629,998A0N,55,46^CI13FR^FN987FS

/ ^FO244,623A0N,52,42^CI13FR^FN986FS

/ ^FO397,261A0N,55,46^CI13FR^FB404,1,0,RFN985^FS

/ ^FO819,854A0N,55,46^CI13FR^FN984FS

/ ^FO725,554A0N,55,46^CI13FR^FN983FS

/ ^FO397,189A0N,55,42^CI13FR^FB695,1,0,RFN982^FS

/ ^FO397,333A0N,55,42^CI13FR^FN981FS

/ ^FO638,333A0N,55,42^CI13FR^FN980FS

/ ^FO391,21A0N,63,63^CI13FR^FB433,1,0,CFN979^FS

/ ^FO36,698A0N,55,46^CI13FR

/ ^FDWBS:FS

/ ^FO37,405A0N,55,46^CI13FR

/ ^FDMATL:FS

/ ^FO37,478A0N,62,44^CI13FR

/ ^FDDESC:FS

/ ^FO554,698A0N,55,46^CI13FR

/ ^FDSUPPLIER:FS

/ ^FO32,625A0N,55,46^CI13FR

/ ^FDTEXT:FS

/ ^FO35,1258A0N,55,46^CI13FR

/ ^{FDBATCH NO:}FS

/ ^FO770,775A0N,63,51^CI13FR

/ ^FD/FS

/ ^FO32,854A0N,55,46^CI13FR

/ ^FDESHM:FS

/ ^FO37,556A0N,55,46^CI13FR

/ ^FDQTY:FS

/ ^FO32,998A0N,55,46^CI13FR

/ ^{FDSAP MATERIAL DOC NO:}FS

/ ^FO525,333A0N,55,46^CI13FR

/ ^FDofFS

/ ^FO556,854A0N,55,46^CI13FR

/ ^FDINSPECT:FS

/ ^FO32,926A0N,55,46^CI13FR

/ ^FDUNLOADING:FS

/ ^FO37,117A0N,55,46^CI13FR

/ ^{FDSTOCK TYPE:}FS

/ ^FO32,774A0N,55,46^CI13FR

/ ^{FDPURCHASE ORDER:}FS

/ ^FO37,188A0N,55,46^CI13FR

/ ^{FDDELIVER TO:}FS

/ ^FO37,260A0N,55,46^CI13FR

/ ^{FDSTORAGE LOC:}FS

/ ^FO37,332A0N,55,46^CI13FR

/ ^{FDCONTAINERS:}FS

/ ^FO1,1359GB1217,0,6^FS

/ ^FO594,1359GB0,474,6^FS

/ ^XZ

/:NEW-PAGE

/ ^XA

/ ^XFNEW-RE-1.ZPL

/ ^FN999FD&ATWRT_HAZAMAT(6)&^FS

/ ^FN998FD&EKKO-LIFNR&^FS

/ ^FN997FD&MABDR-MAKTX&^FS

/ ^FN996FD&MSEG-ABLAD&^FS

/ ^FN995FD&MSEG-CHARG&^FS

/ ^FN994FD&MSEG-EBELN&^FS

/ ^FN993FD&MSEG-EBELP&^FS

/ ^FN992FD&MSEG-ERFME&^FS

/ ^FN991FD&MSEG-ERFMG&^FS

/ ^FN990FD&MSEG-INSMK(1)&^FS

/ ^FN989FD&MSEG-MATNR&^FS

/ ^FN988FD&MSEG-MAT_PSPNR&^FS

/ ^FN987FD&MSEG-MBLNR&^FS

/ ^FN986FD&MSEG-SGTXT(40)&^FS

/ ^FN985FD&MSEG-UMLGO&^FS

/ ^FN984FD&QALS-PRUEFLOS&^FS

/ ^FN983FD&V_BACKORDER&^FS

/ ^FN982FD&V_NAME3&^FS

/ ^FN981FD&WS_CNTR&^FS

/ ^FN980FD&WS_CON&^FS

/ ^FN979FD&WS_HEADER& &^FS

/ ^PQ1,0,1,N

/ ^XZ

/ ^FX End of job

[RichHeilman]

When you upload to standard text, are the "/" and the "/:"(you see this next to the NEW-PAGE statement) begin stored in the paragraph format, which is the 2 character field next to the field which holds the text? Or are the "/" and the "/" gone completely? If so, I think this will definintly cause a problem when this text is included in your sapscript window. You may want to directly put the ZPLII code directly in the window of the sapscript form instead of using the standard text.

Regards,

RIch Heilman

[Former Member]

No, they aren't gone completely.

They are stored as you mentioned.

Also, note 179534 describes the method of printing labels, which is the one I use.

However, just to be on the safe side, I tried your suggested but It didn't help.

[RichHeilman]

Then maybe your sapscript form is not the form which is printing from MB02? Are you sure that the configuration has been done correctly?

Has the output type been configured to use your print program as custom sapscript form as well?

Regards,

Rich Heilman

[Former Member]

Yes, the configuration is correct. I have tested it as well by say changing something in the print program and the sapscript. As such, the relevant changes are reflected in the output.

Most likely, its in the way the Form compiles or how the print program reads the main window text. I am out of ideas and do appreciate your suggestions.

[Former Member]

BUMP - anyone?