Application Development Discussions
Join the discussions or start your own on all things application development, including tools and APIs, programming models, and keeping your skills sharp.
cancel
Showing results for 
Search instead for 
Did you mean: 

Dot matrix printer skips in Production but is fine in Dev and QA

Former Member
0 Kudos

Hi,

I am having a problem with printing in Epson LX 300+ II printer. I created a custom paper format with a size of 8.5 x 6.5 inches.

I followed proper procedure like creating page format, creating format type(same name as page format), adding the page format to the device type, changing the paper size in sapscript.

The problem now is that after working fine in Dev then QA, I requested the changes to be transported to Prod, the printer skips 1 continuous paper.

It's like the modifications I made of changing paper size of the report from DINA4 to the custom paper size 8.5 x 6.5 does not effect in Prod.

I will be really glad if someone can shed a light on this topic.

Thanks & Regards,

Rod

1 ACCEPTED SOLUTION

alexander_bolloni
Contributor
0 Kudos

First I would check whether the spool request in PROD has correct custom format type  (i.e. not DINA4). Then ensure that the printer in PROD uses the modified device type which contains the proper custom format type... And finally check the SAPscript form in PROD to use the custom page format.

8 REPLIES 8

alexander_bolloni
Contributor
0 Kudos

First I would check whether the spool request in PROD has correct custom format type  (i.e. not DINA4). Then ensure that the printer in PROD uses the modified device type which contains the proper custom format type... And finally check the SAPscript form in PROD to use the custom page format.

0 Kudos

Thanks for the reply.

I did check what you said:

  • The report is displayed in print preview as 8.5x6.5.
  • I already transported the modified device type which contains the custom format(8.5x6.5).
  • The sapscript is also set to custom page format (8.5x6.5).

I even have the output device, we are using, transported to QA and Production. Same problem occured. The reports can be printed in QA using continuous paper of size 8.5x6.5 inch with no problem while it is still skipping one paper in Production.

0 Kudos

Hi Rod,

Just to give a thought can you please check all the attributes like Device attribute, access method, output are same in PROD as of DEV and QAS.


Cheers

Sharma

0 Kudos

Hi,

strange. The skipping of one page indicates that either the page length is set "too short" in PROD or (for whatever reason) in PROD more lines get printed on the page than intended.

Does the print output in PROD occupy all available lines on the page (including the last line)? I remember  vaguely that when you print the last line and then send a NL, the printer advances to the first line of the next page, if then a FF follows, you get a blank page.

You can trace printer output (=Printer commands)  via the output log for an output request in  SP01 by using SPAD menu "Edit->Test Tool" (when editing a printer), then select "Logging the first 10 kB". This will result in an output log for every printout to that printer.

Regards,

  Alex


0 Kudos

Hi Deepanshu, Alexander,

Thank you for your insights. Sorry i was not able to reply last week because i have to work on other tasks.

I am going to work on this again today but when I was planning to request a printer so i can test on my workstation, the user said that it is already working fine. It's just weird because i haven't done anything aside from comparing items in SPAD from Dev, QA and Prod. I have no idea if the transport needs a few days to trigger the changes.

Thanks,

Rod

0 Kudos

Hi Rod,

Please let us know about the update.

Cheers

Sharma

Jelena
Active Contributor
0 Kudos

I can only guess that output may have been sent to LOCL printer and dot matrix one happened to be the user's default. So the printout would come out from the printer, but all your configuration would be bypassed. You'd see the printer name in the spool request settings.

In any case, if this has been resolved, kindly close the discussion (see this blog).

Former Member
0 Kudos

Hi,

I close the discussion. thanks to your replies.

Rod