SAP Duplex printing on Xerox

I need to print SAP R/3 invoices in duplex mode to a Xerox Phaser 7400 printer. It prints non-SAP stuff in double-sided ok but not from SAP. Any suggestions please?
Thanks
Kerry

Hi kerry,
Try to change the print attributes in the pages push button of your form....In the Print Attributes u find the print mode, there u can select the required...is this the answer u r looking for...
Cheers
Badri

Similar Messages

Duplex printing on Xerox Phaser 6125

Hi all, I am having trouble duplex printing on my Xerox Phaser 6125 which has a manual duplex function. At least in Windows XP, where it works flawlessly. The Duplex choice in the printing/layout screen is greyed out, with whichever Xerox driver I install. Xerox Europe Ltd claim it's the Mac OS which causes this.
Before I decide to switch from XP to Mac: is this true? Is OS Lion resolving this issue?? Such a simple thing which works flawlessly in antiquated XP should surely work on a superior OS, right?

Hi, I faced the same issue, migrating from Windows to MAC and facing this issue in the driver.
I found a workable solution, involving even more manual tasks but works...
Here is how, inside Adobe Reader, but imagine that it would work from other printing apps also:
1. Select Print, select Booklet
2. From Booklet subset, select front sides only
3. Print.
3a. transfer pages into feeder, no turning, flipping, just pick up en in the drawer as they were
4. Select Print again, under Pages to Print, select More Options
5. check Reverse Pages
6. From Booklet subset, select back sides only
7. Print and a booklet should appear.

Has anyone found a solution for duplex printing from OS 10.8 to Xerox Phaser 8560?

Is anyone else having duplex printing issues from OS 10.8 to Xerox Phaser 8560?

The next time you have the problem, note the exact time: hour, minute, second.
If you have more than one user account, these instructions must be carried out as an administrator.
Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select
View ▹ Show Log List
from the menu bar.
Scroll back in the log to the time you noted above. Select any messages timestamped from then until the end of the episode. Copy them to the Clipboard (command-C). Paste into a reply to this message (command-V).
When posting a log extract, be selective. In most cases, a few dozen lines are more than enough.
Please do not indiscriminately dump thousands of lines from the log into this discussion.
Important: Some private information, such as your name, may appear in the log. Anonymize before posting.

Xerox Phaser 4500 and Duplex Printing on Solaris 10

Dear all,
we have installed a Xerox printer on a system running Solaris 10 10/08
using this command:
#lpadmin -p xerox_p -s localhost -v socket://IP -m uri -A write -n /usr/lib/lp/model/ppd/system/foomatic/Xerox/xr_p4500.ppd
-o banner=always -I postscript -u allow:all
The printer is running very well except for printing duplex pages by the lp command.
I tried to print with -o DuplexNoTumble or with -o sides=two-sided-long-edge but without success.
Does anybody know the correct option -o ???? to do duplex printing and/or does one have to modify the xr_p4500.ppd file?
THX, Rainer

Hi, I faced the same issue, migrating from Windows to MAC and facing this issue in the driver.
I found a workable solution, involving even more manual tasks but works...
Here is how, inside Adobe Reader, but imagine that it would work from other printing apps also:
1. Select Print, select Booklet
2. From Booklet subset, select front sides only
3. Print.
3a. transfer pages into feeder, no turning, flipping, just pick up en in the drawer as they were
4. Select Print again, under Pages to Print, select More Options
5. check Reverse Pages
6. From Booklet subset, select back sides only
7. Print and a booklet should appear.

Can anyone help me troubleshoot duplex printing issue to Xerox 8560?

Can anyone help me troubleshoot duplex printing issue to Xerox 8560 phaser?

Solution may be found if you search in the "More Like This" section over in the right column and by contacting Xerox tech support.

Can't do duplex printing!

I'm in an office with four iMacs running OS X Leopard v10.5.8.
We're all using CS4 Acrobat 9 Pro v9.4.6 (which Check For Updates tells me is up-to-date).
We're printing to a networked Xerox Phaser 6180DN.
And we can't print anything in two-sided duplex from Acrobat Pro.
We can print in duplex from every other application on the iMacs (including other CS4 apps) without problem.
But I need to be able to print non-CS PDF files in duplex.
I've done Google searches and searches within Adobe Help.
I've found the File>Properties>Advanced>Duplex Flip Long Edge
This doesn't make any difference.
Please don't tell me to upgrade to CS5 or Acrobat X Pro ... that's out of my hands.
Please do tell me how I can enable duplex printing from Acrobat 9 Pro!

Guys ... I've been using Macs and Adobe products since the late 80s.
I still have a copy of Illustrator 88 (the original one) sitting on a ZIP disc somewhere.
I do have a clue on using these applications.
That's why problems like this are so frustrating. It should simply work ... and it doesn't!
And Yes ... both are set to double sided printing and No it doesn't print doubled sided:
1. File>Properties>Advanced>Duplex Mode is set to: Duplex Flip Long Edge
2. In the Layout pane in the Print window, Two Sided is set to Long Edge Binding
And all the pages are printed one one side of the paper.
Further, we went the long way around and tried to print the catalog directly from the source InDesign file, which takes fricking forever.
Even more annoying was that some of the pages were printed double sided and some of the pages were printed single sided.
Now, I can pull up large documents in Microsoft Word 2008 Mac (which I HATE - I use Apple Pages at home) and just click Two Sided from Off to Long Edge Binding ... and I get a perfect (well almost) double sided print.
Now what?????

Adobe Form output cropped when sent directly from SAP to printer

I have created an Adobe Form (not interactive) that looks perfectly OK when previewed in Adobe Acrobat viewer but when printed blank margins of 4-5 millimeters are applied on all 4 paper edges. The form was designed with a coloured frame around it but the margins effectively remove most of the frame. The form content is being cropped instead of being compressed inside the margins.
The form has been created with LiveCycle Designer via SAP transaction SFP. I am generating the form from an ABAP program
When the form is printed from the Adobe Acrobat viewer I have the option to set Page Scaling to 'Fit to Printable Area'. This makes the form content being compressed inside the blank margins and the coloured frame remains intact. If I leave the Page Scaling setting as 'None' the output is being cropped as described above.
The real problem occurs when I want to print without previewing first. I need to do that since previewing enables the user to skip printing and the application must know if the form has been printed or not. I have so far found no way to make the printer print on the paper edges or fit the content to printable area. Is there some setting in the output parameters than handles this?
Also there is a need for duplex printing when sending form directly to printer. On help.sap.com there is information about duplex print for SAPscript and Smartforms but nothing for Adobe Forms.
Here is an excerpt of the ABAP code used for printing the Adobe Form:
DATA: zs_outparams TYPE sfpoutputparams,
             z_fmname     TYPE rs38l_fnam.
Set some print parameters
zs_outparams-nodialog = abap_true.        "No user dialog
zs_outparams-device   = 'PRINTER'.          "Output device
zs_outparams-dest     = z_pdest.              "Printer name
zs_outparams-reqnew   = abap_true.        "New spool request
zs_outparams-reqimm   = abap_true.        "Print immediately
Open print job
CALL FUNCTION 'FP_JOB_OPEN'
    CHANGING
      ie_outputparams = zs_outparams
    EXCEPTIONS
      cancel          = 1
      usage_error     = 2
      system_error    = 3
      internal_error = 4
      OTHERS          = 5.
IF sy-subrc <> 0.
    RAISE print_error.
ENDIF.
Get FM name for form
CALL FUNCTION 'FP_FUNCTION_MODULE_NAME'
    EXPORTING
      i_name     = 'Z_TEST_FORM'
    IMPORTING
      e_funcname = z_fmname.
Call FM to print form
CALL FUNCTION z_fmname
    EXPORTING
      i_header       = t_data_for_form
    EXCEPTIONS
      usage_error    = 1
      system_error   = 2
      internal_error = 3
      OTHERS         = 4.
IF sy-subrc <> 0.
    RAISE print_error.
ENDIF.
Close print job
CALL FUNCTION 'FP_JOB_CLOSE'
    EXCEPTIONS
      usage_error    = 1
      system_error   = 2
      internal_error = 3
      OTHERS         = 4.
IF sy-subrc <> 0.
    "Ignore
ENDIF.
Please advise on how to
- avoid the content cropping
- enable duplex print
when sending Adobe forms directly to the printer
Thanks very much!
Bernt Evensen

Thanks for your answer, Ramachandra!
However I need some more specific information to solve this.
Which printer layout settings are relevant for the handling of margins and duplex printing for Adobe Forms?
I have not set up the printer myself but when talking to the printer guy which settings should I recommend him to look at?
I can see in transaction SPAD that there are settings specific to SmartForms but there is nothing said about Adobe Forms. Is there some way to make Adobe Forms related setting appear in SPAD for a device type?
Maybe my problem is not related to the printer device settings but rather to the way the printer is being called. When printing duplex we will have to override the default settings of the printer anyway.
Function module FP_JOB_OPEN has a parameter structure of the type SFPOUTPUTPARAMS. Which fields in this parameter structure are to be manipulated to get duplex print and output fitted to page size?

Problem in Duplex Printing

Hi,
After following the discussion given in the below mentioned threads
1) issue
2) issue
I am able to print in duplex mode but still there is problem with the number of pages being printed.
Actually I just have to print two pages (back to back on a single sheet of paper), namely 1st page = 'Front' & 2nd page = 'Back'.
For the page 'Front'
Next Page = 'Back'
Print Mode = 'D'
There is command in the Main Window, having Go to new page = 'Back' set & Include printer control = 'SPMDU'
For the page 'Back'
Next Page = 'Front'
Print Mode = ' '
When I print with these settings the output is of 3 pages out of which the first 2 pages are perfectly alright (as they appear on a single sheet back to back) but then the 'Front' pages repeats itself on a new sheet.
How can I restrict the print out to just 2 pages?
I have myslef tried to set the Next Page of 'Back' to 'Back' or even left it empty but it does not work.

Hi Khan,
Refer these links. Might come handy...
<a href="http://help.sap.com/saphelp_webas620/helpdata/en/90/78f07e030211d399b90000e83dd9fc/content.htm">Duplex printing</a>
<a href="http://help.sap.com/saphelp_webas620/helpdata/en/d9/4a8eb751ea11d189570000e829fbbd/content.htm">SAP Printing guide</a>
Regards,
Raj

Issue with character formats using duplex printing in smartform

Hi all,
I am getting a problem with character formats using duplex printing in smartform. I am using a text module with a bold character to display text in a window. The problem is that on the first back page,the text is being printed normally (without bold), but on the next pages, the back pages are being printed with the bold character format.
Can anyone know where is the problem..please.
Points to be rewarded..
Thanks.
Regards,
Zaheed.

Hi Zaheed,
Normally this should not happen.. and also there is no internal formatting done by SAP.. it will show based on what fomatting option we have specified..
If you are saying it is happening in ur case then
     1. Recheck whether whether you have same text module getting printed on the
         two page. If they are different then then individual check formatting option for
         each..
      2. If above point does'nt work for you ..then instead of bold char use normal
          format for text element and see if it is printing same on both page..
Try this out and let us know your findings...
Enjoy SAP.
Pankaj Singh

Duplex printing issues

Hi all, run into a problem with duplex printing in oracle reports lately where data for seperate groups is ending up on the previous or next group's page. This is using 10g and a xerox high speed printer.
Basically if I have a report with groups a, b, and c. The output should be:
1st page - A1/A2
2nd page - A3/Blank
3rd page - B1/B2
4th page - C1/C2
5th page - C3/C4
Instead what we are getting is:
1st page - A1/A2
2nd page - A3/B1
3rd page - B2/C1
4th page - C2/C3
5th page - C4/BLANK
Is there any way to set a break or blank page between groups in oracle from the same query to seperate them for duplex printing? I've looked and a solution seems to be to add an empty boilerplate object in the header/body that checks the mod of the page number, and if odd, prints or displays to get a blank page, otherwise if even does nothing. Is there a better or "cleaner" solution to this?

So I've actually tried to do this and it doesn't seem to work. From Oracles FAQ's:
"I am printing statements on a double-sided stationary capable printer. To ensure that each new statement starts on a new physical piece of paper, I need to add a blank page if the previous statement had an odd number of page sides. How can I do this?
Place an invisible boilerplate line before the repeating frame that contains your data. Give it a Page Break before and anchor it to the repeating frame. Then write a format trigger that only prints the boilerplate object (and thus the page break) if it is an odd page number. "
I've tried adding a line, with page break before on, and anchoring it to my repeating frame with the following:
physicalpage number;
begin
     srw.get_page_num(physicalpage);
IF MOD(physicalpage,2) = 0 THEN
          return(FALSE);
     ELSE
     return(TRUE);
     END IF;
end;, it either does nothing or gives an error saying horizontal line does not fit withing repeating group x.
Does anyone know how to properly seperate repeating groups from an oracle report when using duplex, or double sided printing?

SAPScript Duplex Printing (SD Invoice)

Hi all gurus,
After reading some threads and as I told on this "answered" question from Manfred:
Re: Duplex Printing SapScript: Invoice - Printer tries but fails backside?
We need to print SD invoices in duplex mode.
Settings that we have changed by now:
- Sapscript: first page printmode as DUPLEX, next as default -> OK
- Since read from official SAP documentation, for sapscript duplex you don't need to change display type or device type from SPAD. So I left the one was been used. Anyway, to be sure, I change its print mode to DUPLEX. I have also check if the print control SPMDU appears on the device -> OK
- The printer we use is an OCE MP 1020 which can print on duplex mode and has PCL
- I have tried printing the text SAPSCRIPT-PRINTMODETEST from SO10 but duplex does not work. They print on different pages.
Following those instructions, I could not manage to do it.
I have some questions:
- Do we need to configure the printer locally in any way?
- About the example "SAPSCRIPT-PRINTMODETEST", do you need to configure something before testing it for duplex printing?
Could you please explain the needed steps to accomplish SAPScript duplex print?
Thanks in advance,
John

Hi Aidan,
Thanks for your response.
I have changed the device type from SAPWIN to HPLJ4000.
When I try to print the text: SAPSCRIPT-PRINTMODETEST
The SAPLPD.LOG says:
(11:10:16) Number of processors: 4
(11:10:16) Icon DLL loaded.
(11:10:16)
(11:10:16) Network Communication via SAP-NiLib
(11:10:16) Hostname: xxxxxxxx
(11:10:16) IP Address: 9954064.2684488.2684488.1617840
(11:10:16)
(11:10:16) SAPLPD Version 6.29 for Windows/NT (OPT) is listening
(11:10:16) OS-Info: version = 6.1, build = 0/7601, text = Service Pack 1
(11:10:16) Copyright © 1992-2001 SAP AG
(11:10:16)
(11:10:26)
(11:10:26) Receive job for printer __DEFAULT (Berkeley LPD protocol / RFC1179)
(11:10:26) send_status called
(11:10:26) send_status called
(11:10:26) send_status called
(11:10:26) send_status called
(11:10:26) send_status called
(11:10:26) Job 002aBOrZ.IS1 for user XXXXXX queued.
(11:10:26) Job 002aBOrZ.IS1 (raw) started on printer \XXXXXXXXXX
(11:10:26) Job 002aBOrZ.IS1 (raw) with 4955 bytes finished
The printer is not printing any page :S
This is the printer model:
http://www.oce.co.uk/products/mp1020/specifications.aspx
It supports PCL and Postscript
What could be the problem?
Thanks in advance

Duplex printing of abap list

Hi,
we are trying to printing some abap lists on both sides. ich have found some information about duplex printing of sapscript / smart forms, but nothing about printing of abap lists.
Ich habe changed attribute printmode ( transaction SPAD ) of printer to Duplex mode, and print parameter DUPPRINT of the user is changed too ( Function UPDATE_DEFAULT_PRINTPARAMS DB-Table TPRI_DEF ).
But still could not able to print. Thanks in advance for your help.
Regards,
Sumiya.

You can print ABAP lists in duplex, if your printer supports duplex printing and uses one of the following device types:
->        Device types for PCL-5 printers:
        HP4550
        HP8550
        HP9000
        HPLJ1100
        HPLJ8000
        HPLJ4000
        BRHL
->        Device type for Prescribe II printers: KYOFS170
->        Device type for PostScript Level 2 printers: POST2
To be able to use both the simplex and duplex modes of your printer for list printing, you should create two different device definitions. For information about the procedure for doing this, see Creating Output Devices (http://help.sap.com/saphelp_webas620/helpdata/en/7e/36e4c4023411d399b70000e83dd9fc/content.htm).
On the Output attributes tab for the device definition, specify the desired Print mode.
Above extract is from help.sap.com.
Please reqard points if helpful.
Good Luck.

EHS - Duplex printing of MSDS

Hi all,
I would like to know whether printing of MSDS in duplex mode (double sided) is possible when using cg54 transaction to send MSDS to customers. I did not find any provision for duplex printing in customizing.
Thanks,
Mohan

Hi Mohan
have a look at this link may be it will give you some more information.
http://help.sap.com/saphelp_erp2005/helpdata/en/90/78f078030211d399b90000e83dd9fc/frameset.htm
Cheers
Badri
Points appreciated if helpful

Sap scripts print modes

What are the print modes available in the sap scripts?

Hi
Parent Topic: SAPScript
HOWTO:Sap script
Edit this entry - Discuss - Rename - Watch - History -
Major contributors: gopang, cmurphy262 | All Contributors
Your votes have been tallied! See which wiki entry took top honors and find out who is this year's Wiki Ironman. View the winners.
White Papers
Do You Need a Fax Server? A Special Guide on Fax Servers and SAP Electronic Document Delivery
Achieving Real-Time Supply Chain Integration
E-Invoicing for Business Process Efficiency with SAP(R) Systems
Jobs
SAP Consultants (Any City) - SD, MM, PP, FI/CO, CS, ABAP (Dice)
SAP ABAP LEAD (Dice)
SAP ABAP Workflow Developer -Contract (Dice)
Community Content
3 days until GO-LIVE!!! (Blogs)
RE: RE: RE: RE: RE: Lost connection when using tcode FS00 (Groups)
SAP SCRIPT
Table of contents Show TOCHide TOC
1. 1 Concepts
1.1. 1.1 Modifying SAP Forms
1.2. 1.2 Forms: Concepts
1.3. 1.3 Client and Language Versioning: Concepts
2. 2 Componentes
2.1. 2.1 Header Data
2.2. 2.2 Paragraph Formats and Attributes
2.2.1. 2.2.1 Standard Paragraph Attributes
2.2.2. 2.2.2 Font Attributes for Paragraphs
2.2.3. 2.2.3 Tabs in Paragraph Formats
2.2.4. 2.2.4 Paragraph and Heading Numbering
2.3. 2.3 Character Formats and Attributes
2.3.1. 2.3.1 Standard Attributes for Character Formats
2.3.2. 2.3.2 Font Attributes for Character Formats
2.4. 2.4 Windows
2.4.1. 2.4.1 Default Paragraph
2.5. 2.5 Pages
2.5.1. 2.5.1 Defining Follow-On Pages in Duplex Print Modes
2.5.2. 2.5.2 Testing Tray Selection and Print Mode Selection
2.6. 2.6 Page Windows
2.7. 2.7 Text Elements
2.7.1. 2.7.1 Default Text Element
2.8. 2.8 Main Window
3. 3 Técnicas
3.1. 3.1 Displaying Versions of Forms
3.2. 3.2 Including Graphics
3.2.1. 3.2.1 Using Boxes, Lines, and Shading
3.2.2. 3.2.2 Supported Printers
3.2.3. 3.2.3 Boxes, Lines, Shading: BOX, POSITION, SIZE
3.2.3.1. 3.2.3.1 BOX Command
3.2.3.2. 3.2.3.2 POSITION Command
3.2.3.3. 3.2.3.3 SIZE Command
3.2.4. 3.2.4 Pre-Setting BOX Position Arguments
3.2.5. 3.2.5 Using the Commands in Texts and Forms
3.2.6. 3.2.6 Tips and Guidelines
4. 4 Design Tools
4.1. 4.1 Form Components
4.2. 4.2 Processing in Overview
4.2.1. 4.2.1 Defining Header Data
4.2.1.1. 4.2.1.1 Completing the Header Data After Defining the Attributes
4.2.1.2. 4.2.1.2 Passing Data to an External Program
4.2.2. 4.2.2 Defining Paragraph Formats
4.2.3. 4.2.3 Defining Character Formats
4.2.4. 4.2.4 Defining Pages
4.2.5. 4.2.5 Defining Windows
4.2.6. 4.2.6 Using Text Elements in Page Windows
4.2.7. 4.2.7 Defining Page Windows
4.2.7.1. 4.2.7.1 Filling Page Windows with Text
4.2.8. 4.2.8 Using Text Elements in Page Windows
4.2.9. 4.2.9 Defining Main Windows in Page Windows
4.3. 4.3 Test-Printing a Form
5. 5 Releasing Forms
6. 6 SAPscript Control Commands
6.1. 6.1 Syntax of Control Commands
6.2. 6.2 Explicit Page Break: NEW-PAGE
6.3. 6.3 Preventing Page Breaks: PROTECT
6.4. 6.4 Next Main Window: NEW-WINDOW
6.5. 6.5 Assigning a Value to a Text Symbol: DEFINE
6.6. 6.6 Formatting Date Fields: SET DATE MASK
6.7. 6.7 Formatting Time Fields: SET TIME MASK
6.8. 6.8 Country-Dependent Formatting: SET COUNTRY
6.9. 6.9 Position of the Leading Sign: SET SIGN
6.10. 6.10 Initializing Numbered Paragraphs: RESET
6.11. 6.11 Including Other Texts: INCLUDE
6.12. 6.12 Changing the Style: STYLE
6.13. 6.13 Formatting Addresses: ADDRESS
6.13.1. 6.13.1 Parameters
6.14. 6.14 Setting a Footer Text in the Main Window: BOTTOM
6.15. 6.15 Conditional Text: IF
6.16. 6.16 Finding a Match: CASE
6.17. 6.17 Calling ABAP Subroutines: PERFORM
6.18. 6.18 Inserting Print Controls: PRINT-CONTROL
6.19. 6.19 Boxes, Lines, Shading: BOX, POSITION, SIZE
6.20. 6.20 Hexadecimal Data: HEX, ENDHEX
6.21. 6.21 Summing a Program Symbol: SUMMING
6.21.1. 6.21.1 Summing and Carrying Forward is Incorrect
7. 7 SAPscript Symbols
7.1. 7.1 Syntax of Symbols
7.2. 7.2 System Symbols
7.2.1. 7.2.1 Current Date
7.2.2. 7.2.2 Current Day Number
7.2.3. 7.2.3 Current Month Number
7.2.4. 7.2.4 Current Year Number
7.2.5. 7.2.5 Current Day Name (Long Form)
7.2.6. 7.2.6 Current Month Name (Long Form)
7.2.7. 7.2.7 Current Time
7.2.8. 7.2.8 Hours Component of Current Time
7.2.9. 7.2.9 Minutes Component of Current Time
7.2.10. 7.2.10 Seconds Component of Current Time
7.2.11. 7.2.11 Current Page Number
7.2.12. 7.2.12 Page Number of the Next Page
7.2.13. 7.2.13 Selected Device Type
7.2.14. 7.2.14 Spaces
7.2.15. 7.2.15 Underline
7.2.16. 7.2.16 Vertical Line
7.3. 7.3 Program Symbols
7.3.1. 7.3.1 SYST: System Fields in the ABAP Programming Environment
7.3.2. 7.3.2 USR03: User Address Data
7.3.3. 7.3.3 SAPSCRIPT: General SAPscript Fields
7.4. 7.4 Standard Symbols
7.5. 7.5 Text Symbols
7.6. 7.6 Formatting Options
7.6.1. 7.6.1 Offset
7.6.2. 7.6.2 Output Length
7.6.3. 7.6.3 Omitting the Leading Sign
7.6.4. 7.6.4 Leading Sign to the Left
7.6.5. 7.6.5 Leading Sign to the Right
7.6.6. 7.6.6 Omitting Leading Zeros
7.6.7. 7.6.7 Space Compression
7.6.8. 7.6.8 Number of Decimal Places
7.6.9. 7.6.9 Omitting the Separator for Thousands
7.6.10. 7.6.10 Specifying an Exponent for Floating Point Numbers
7.6.11. 7.6.11 Right-Justified Output
7.6.12. 7.6.12 Fill Characters
7.6.13. 7.6.13 Suppressing Output of Initial Values
7.6.14. 7.6.14 Ignoring Conversion Routines
7.6.15. 7.6.15 Changing the Value of a Counter
7.6.16. 7.6.16 Preceding and Subsequent Texts (Pre-Text / Post-Text)
7.7. 7.7 Country-Dependent Formatting
7.7.1. 7.7.1 Date Mask
7.7.2. 7.7.2 Time Mask
7.8. 7.8 Formatting Conventions
7.8.1. 7.8.1 Primary Formatting of System Symbols
7.8.2. 7.8.2 Primary Formatting of Standard Symbols
7.8.3. 7.8.3 Primary Formatting of Program Symbols
7.8.4. 7.8.4 Primary Formatting of Text Symbols
7.8.5. 7.8.5 End Formatting
1 Concepts Edit section
1.1 Modifying SAP Forms Edit section
If you want to modify SAP forms, set up your development environment as follows:
1. Make sure that no SAP-standard forms are stored as client-specific copies in your development client. Such forms should be held only in client 000, the SAP development and installation client. If you access an SAP-standard form from another client, then the central copy in client 000 is used.
If you need to remove SAP-standard objects from your development client, see Notes 10388 and 3355 in the SAP Online Service System (OSS). These notes explain the procedure for saving modified forms and then deleting all forms.
2. To modify SAP standard forms,
Copy the forms you need from client 000 to your development client.
Rename the forms using a name from the customer name reserve (names starting with Y or Z).
Copy the forms to one of your own Y or Z development classes.
Renaming the SAP standard object makes it possible to manage and transport your changes with the SAP workbench organizer. The organizer is not activated for SAP-standard objects that are modified in clients other than 000.
3. To put your modifications into effect, you must also modify the ABAP print program used to print documents that use this form. You should rename such print programs and store them in your own Y or Z development classes.
You can use the SAP Customizing System to replace the SAP print program with your modified print program in the affected applications
1.2 Forms: Concepts Edit section
Forms are used to control the page layout and also the text formatting in your documents. Before formatting a document for output to the screen or to a printer, you must assign a form to it. If you do not specify a form for a document, then the SYSTEM form is assigned to the document by default.
Application-specific forms are used in SAP applications to specify the page layout for such special documents as invoice or checks. These forms specify the structure of the information on the page(s) of such a document. They define, for example, the address header, item lines, the footer, and so on. There are two ways to format texts with forms:
In the standard SAPscript text processing (Tools  Word processing  Standard text), you can select a form for a document. You can then type text into the main window of the form and output the document in the format defined in the form.
For example, you can select a form for a letter. You can then type the body text of the letter in the main window. When you print the letter, the default text elements in the other windows of the form (heading, footer, and so on) are printed with the body text.
A document can be generated by a print program in one of the SAP applications. The print program uses a form to generate the document. Most correspondence and document generation in the SAP System are handled by way of print programs.
A print program selects the text elements that are to be printed in the windows of a form. It may also collect information from the user or ask the user to input text directly, as in some correspondence functions. The print program may also provide data for variables defined in the form.
Finally, the print program uses the form to format the document for display or printing.
1.3 Client and Language Versioning: Concepts Edit section
Forms and styles are client-specific. That is, a form or style other than the SAP standard in client 000 is available only in the client in which it was created.
Forms and styles are also language-specific. That is, the definitions and texts in a form or style are defined for a particular language. Forms and styles can be translated using the standard SAP translation tools.
Client 000 Defaulting: SAPscript accords forms and styles in client 000 a special status.
If a form or style that is used in a document is not available in the client in which the document is being printed, then SAPscript checks for the form or style in client 000. If it is found there, then the client 000 version is used to print the document.
SAP standard forms and styles are always held in client 000. You can take advantage of the client 000 defaulting as well by storing your Yxxx and Zxxx forms and styles there. That way, if a local version of a form or style is not present in a client, the client 000 version is used instead.
Language rules: SAPscript uses the following rules to manage versions of forms and styles in different languages:
The language in which a form or style is created is its "original language." You can translate a form or style into other languages using SAPs translation tools.
If a form or style is needed only in its original language and need not be translated, then you can indicate this in the language attributes in the header data. The form or style then does not appear in work lists in the translation tools.
In versions other than the original language version, changes to a form or style are limited only to translation of texts. No changes to definitions and attributes are permitted.
2 Componentes Edit section
2.1 Header Data Edit section
You can find header data in both form and style maintenance. In style maintenance, it is used primarily to present important information information designed to make it easier for the end user to select a style. The header data in form maintenance, on the other hand, is used for information and control purposes. For this reason, the header data of a form will be described in more detail.
Below, the header data is described as it appears in the alphanumeric Form Painter.
Like the header data of a style, the header data of a form comprises two parts: the data set by the system and the data you are expected to enter. The latter is dealt with separately.
Device-independent entries.
Description
A short explanatory description of the form (also applies to the style), designed to make selection easier for the end user.
Form class
You can assign a form to a class to help you organize and search for forms. The default set of classes is the set of program classes in your system.
Start page
Tells the print program which page format in a form to use first for printing.
Default paragraph
Paragraph set to * in standard text maintenance.
Tab stop
A grid set at specified intervals in all windows defined in the form. However, you should note that the tab stops are only valid in paragraphs where you have not defined your own tabs.
Language, Original language, Translation applic
Use these fields to record the master language and language of the current version of a form. Marking Translation applic makes the form accessible for translation from the SAP Systems translation tools (transaction SE63).
Device-dependent entries.
You can only enter values here that are supported in the R/3 printer definition. If you make other entries, this leads to errors in the check routine.
Page format
Determined from the spool administration table with transaction SPAD. Make sure there is a printer assignment there must be an additional spool format for the printer with the same page format.
Orientation
Depends on the page format selected. This can also be determined from the spool administration table. Please note that the formats landscape and portrait are not supported by all printers.
Lines per inch (LPI)
Basis for converting the unit of measurement LN in style and form maintenance. The value 6.00 is set by the system, as this value is supported by all printers.
Characters per inch (CPI)
Basis for converting the unit of measurement CH in style and form maintenance. The value 10.00 is set by the system, as this value is supported by all printers.
Font attributes
With these fields, you can set the default font for a form. The default font applies if other objects do not specify a font. SAPscript suggests a default font, which you can change.
2.2 Paragraph Formats and Attributes Edit section
In SAPscript, paragraphs are formatted using formats and their corresponding attributes. Text processing is simplified by the use of different paragraph attribute groups:
Standard
Font
Tabs
Outline
There are naming conventions for paragraph tags:
The paragraph tag can have one or two characters.
The first character in the paragraph tag must be a letter, the second a letter, number, or blank; special characters are not valid.
The paragraph format must be identified in the Description field.
2.2.1 Standard Paragraph Attributes Edit section
In the Standard attribute group, you find the general attributes that can be defined in paragraph formats:
Description
Precise explanation of your paragraph tag, so that the user can immediately identify it.
Left or right margin
Amount of space between the paragraph and the left or right border of the form window.
Indent first line
Indent of the first line of a paragraph. If the value is positive, it is indented to the right, if it is negative, it is indented to the left.
If you specify a negative value, then you must place the minus sign after the number: 1- .
Space before and space after
Space before and space after control the amount of space between paragraphs. The actual space between paragraphs results from the space after the preceding paragraph and the space before the following paragraph.
Alignment
Alignment of a paragraph.
Left-aligned
LEFT
Right-aligned RIGHT
Centered CENTER
Justified BLOCK
Line spacing
Spacing between the lines. The default value is 1 line; the LPI value (lines per inch) in the header data is used to calculate the line spacing.
No blank lines
Suppression of blank lines. You can control whether the blank lines of a paragraph should be suppressed in the printout or not:
No entry
blank lines not suppressed
X blank lines suppressed
Page protection
Cohesion of a paragraph. It is possible to determine whether or not a paragraph can be divided by a page break.
No entry
no page protection (default)
X all lines of the paragraph are on one page
Next paragraph same page
Cohesion of two adjacent paragraphs. Here you can define whether the subsequent paragraph should begin on the same page (that is, at least the first line of the subsequent paragraph must be on the same page).
No entry
subsequent paragraph is output on the same page or the next page, depending on the amount of space (default)
X subsequent paragraph begins on the same page
2.2.2 Font Attributes for Paragraphs Edit section
You can specify font attributes for paragraph formats. They control the font used in the text. You can specify these attributes both for the default font in the header and for particular paragraph formats:
Font family
Enter a font supported in the SAPscript font maintenance.
Font size
Enter the size of a character font. It is measured in 1/10 point.
Bold/Italic
Specify whether to use bold-face printing or italics.
Underlined
Mark this attribute to underline entire blocks of text.
When defining a paragraph format, use More to specify these underline attributes:
Spacing between the base line and the underline
Thickness
Intensity
Intensity is expressed in percent: 0 % is a black underline; 100 % is no underline.
If you defined default underlining in the header, then the fields for underline attributes are already displayed on the screen.
The following selection criteria apply to the font attributes bold, italics, and underlined:
Off attribute is not set
Retain inherited
On attribute is set
The combination of font family, font size, bold type attribute and italics attribute is referred to as a system font or SAP font. To use the SAPscript font maintenance, choose Tools  Word processing  Font.
2.2.3 Tabs in Paragraph Formats Edit section
You can define as many tab positions as you require for each paragraph format. The text can be aligned in different ways:
Left-aligned with LEFT
Right-aligned with RIGHT
Centered with CENTER
At the sign with SIGN
At the comma or decimal point with DECIMAL
You can control the tab feed in a paragraph with tab positions. The tab stops you define in the paragraph format replace the tab spacing you defined in the header data of the form. However, this depends on the extent to which you have defined tab stops in the paragraph format. If there are fewer tabs in the paragraph formats than in the header data, the tab stops of the header data are used for the rest of the line. The tab stops are represented as, , in the text editor.
You can use different units of measurement to define a tab position:
CH Characters
CM Centimeters
MM Millimeters
PT Points
TW Twips (1/20 point)
The unit of measurement CH is converted to an absolute unit of measurement using the CPI value (characters per inch) from the header data of the form.
2.2.4 Paragraph and Heading Numbering Edit section
The paragraph numbering and marking attributes are used to structure texts into chapters, subchapters, and sections. Numbering is carried out automatically by SAPscript.
You can create an outline with the entry options available:
Outline
Enter the name of the highest-level paragraph in an outline hierarchy here. The outline hierarchy is created by assigning this paragraph to all outline paragraphs.
Outline level
Enter the level in the outline hierarchy. The outline levels of the paragraphs are numbered upwards from 1; the highest outline level therefore has the outline number 1.
Number margin
Specify the space between numbering and window border. Note that your numbering may extend into the text area of the paragraph if the difference between the left margin and the number margin is not great enough to hold the numbering characters.
Left/right delimiter
Specify the character that precedes or follows the numbering.
Number chaining
Specify whether you want the paragraph numbering of the paragraph to be preceded by the numbering of all higher paragraphs in the hierarchy.
Example for number chaining
with   without
3.     3.
3.1     1.
3.2     2.
3.2.1     1.
Character string
Specify the numbering format. The numbering can be assigned a different font or character format to the rest of the paragraph.
Numbering type
ARABIC
Arabic numerals: 1, 2, 3.
CHAR Fixed character: letter or numeral, entered in the field
LETTER Letters: A-Z
ROMAN Roman numerals: I, II, III, IV
Depending upon the numbering type that you select, the following attributes may also apply:
Fixed character
Define the fixed character to be used for numbering. You should only make an entry in the field Fixed character if you have specified CHAR as the numbering type. Fixed characters include + - and o .
Output length
Enter the number of characters for Arabic numerals.
Upper case
Specify for letters or Roman numerals.
2.3 Character Formats and Attributes Edit section
Character formats, as opposed to paragraph attributes, allow you to format entire blocks of text within a paragraph.
Character attribute groups can be:
Standard
Font
When you define character formats, observe the following naming conventions:
The character format can have one or two characters.
The first character must be a letter, the second a letter, number, or blank; special characters are not valid.
Enter a simple explanation in the field Description. It is intended to help the user make a selection.
2.3.1 Standard Attributes for Character Formats Edit section
Marker
Links a search key to the selected character string when the end user uses this character format. Examples include glossary, hypertext, and data element links. Here, selected character strings are assigned the appropriate key.
Bar code
Bar code that is required for certain variables and is known to the printer, for example EAN8. The character string is printed as a bar code if the character string concerned is selected.
Bar code names, such as EAN8, refer to system bar codes. These are defined in the SAPscript font maintenance (Tools  Word processing  Font).
Protected
The character string is not split by a line break, but printed together on the next line.
Hidden
The character string is not printed. The text is only visible in the text editor.
Superscript/subscript
The character string is printed half a line higher or lower.
The following options are available for defining these attribute types:
Off
Attribute is not set
Retain Attribute is inherited
On Attribute is set
2.3.2 Font Attributes for Character Formats Edit section
Font attributes can be specified for character formats as well as for paragraph formats. You have the same options as for defining font attributes for paragraph formats.
2.4 Windows Edit section
Windows are defined in form maintenance. They represent areas that are positioned on pages as page windows and in which at a later time text is printed. You must define at least one window for each form. Otherwise, SAPscript cannot format the text.
You can assign window names and window types. However, note that you can define only one main window per form.
Use one of these window types:
MAIN
Main window in which continuous text is printed. This is the window used by dialog users of a print program and form. For example, the body text of a letter would be entered in MAIN.
The text in the main window can extend over several pages. If the text fills one page, output continues in the window of the next and subsequent pages, as long as MAIN has been defined for these pages.
VAR
Window with variable contents. The text can vary on each page in which the window is positioned. Variable windows are formatted for each page.
To every window you can assign text, which is printed in the corresponding window when the form is formatted. To assign text, use text elements, which are stored with the form.
To create and maintain text elements with the SAPscript Editor, choose Text elements. Should the text selected for the window exceed the window size, then the text is cut off.
CONST
Window with constant contents that is formatted only once.
Currently, CONST windows are processed in the same way as VAR windows. You should only use windows of type VAR.
2.4.1 Default Paragraph Edit section
For a particular window, you can override the default paragraph format that is set in the form header. Enter the default format that should apply in the window in the Default paragraph field in the window definition screen.
2.5 Pages Edit section
You must define at least one page for every form. And you must designate a "first" page in the form header. Otherwise text formatting is not possible. In addition, you should inform the system which page is to be used after reaching the end of the first page. If you do not specify a next page, the output of your text ends at the end of the current page.
To define a page, give it a name and specify attributes for it:
Name of the next page
Page counter mode
INC Increases the counter by 1
HOLD Counter remains unchanged
START Sets the counter to 1
You can display the contents of the page counter with the system symbol&PAGE&.
Numbering type of the page counter
ARABIC Arabic numerals
LETTER Letters
ROMAN Roman numerals
Although CHAR is displayed as an entry option for the numbering type of the page counter, internally CHAR is converted to ARABIC.
Output length for page numbering with numerals
Upper or lower case for numbering with Roman numerals or letters
Resource name
With Resource name, you specify that the paper for this page should be taken from a particular paper tray at the printer.
In Resource name, enter the print control that has been defined for switching to the paper tray you want to use. In printer types pre-defined by SAP, these print controls are generally as follows:
TRY01 Select first paper tray
TRY02 Select second paper tray (if available at the printer)
TRY03 Select third paper tray (if available at the printer)
TRYEN Print envelopes (if available at the printer)
TRYMN Switch the printer to manual paper feed (if available at the printer). The printer pauses until you feed a sheet of paper into it.
TRYME Switch the printer to manual envelope feed (if available at the printer). The printer pauses until you feed an envelope into it.
You can use all tray selection print controls except TRY03 with suitably equipped printers that are defined with the following SAP device types: HPLJSTND, HPLJ_II, HPLJIIID, HPLJ4, LX4039, and SNI20XX8.
You can use TRY01, TRY02, TRY03, and TRYMN on suitably equipped printers that are defined with these device types: KYOF1000, KYOF1200, KYOFS1500.
See the spool system (transaction SPAD) to check on how your printers are defined.
Print mode
With Print mode, you can specify single- or double-sided printing for a page. You can choose from the following values:
' ' Currently active printing mode continues unchanged.
S The page is printed in simplex mode. That is, the printer should print on only one side of the paper. If another mode was previously active, then the printer is switched to simplex mode with the start of the page.
D The page is printed on the first side of a sheet in duplex mode. If another mode was previously active, then the printer is switched to duplex mode with the start of the pageand continues in this mode.
T The page is printed on the first side of a sheet in tumble duplex mode. That is, the printer prints on both sides. The page on the second side is always inverted, so that the footer of the second page is printed opposite the header of the first page.
If another mode was previously active, then the printer is switched to tumble duplex mode with the start of the page and continues printing in this mode.
Print modes are currently supported for printers that use the PCL-5 language. These are printers that are defined with the following SAP device types: HPLJ_II, HPLJIIID, HPLJ4, LX4039, SNI20XX8.
See the spool system (transaction SPAD) to check on how your printers are defined.
The print controls for these functions are SPMSI (begin simplex printing); SPMDU (begin duplex printing); SPMTU (begin tumble duplex printing); SPMFS (print on first side of sheet in duplex or tumble duplex mode); and SPMBS (print on second side of sheet in duplex or tumble duplex mode).
2.5.1 Defining Follow-On Pages in Duplex Print Modes Edit section
You switch to duplex or tumble duplex mode with a form page for which one of these modes is specified. To continue printing in the current mode, for follow-on pages you must define another page in which the Print mode field is empty. Otherwise, the following pages after the mode switch will continue to be printed only on the front sides of new sheets of paper.
The reason: When SAPscript sends a page with Print mode D or T to the printer, it not only sets the print mode accordingly. To ensure that the first page in the new mode is correctly output, SAPscript also instructs the printer to output the page on the front side of a sheet. If SAPscript sends a sequence of D or T pages to the printer, the output is printed only on the front side of each sheet.
You define a first page named FIRST for a form to be printed in duplex mode. You therefore set the Print mode in FIRST to D.
To make the duplex printing work correctly, you must define a second page FOLLOWER in which Print mode is left empty. In the form definition, you specify FOLLOWER as the follow-on page for FIRST and for itself as well.
Your text is then printed in duplex mode. FIRST switches the printer to duplex mode and forces printing of the first page on the front side of a new sheet. FOLLOWER accepts the duplex mode and sends no further mode print controls to the printer. The printer therefore alternately prints FOLLOWER pages on the fronts and backs of sheets.
2.5.2 Testing Tray Selection and Print Mode Selection Edit section
SAP provides predefined SAPscript documents with which you can test whether tray selection and print mode selection are working properly on your printers.
For tray selection, print the SAPscript document SAPSCRIPT-TRAYTEST, ID ST, Language D or E.
For print mode selection, print the SAPscript document SAPSCRIPT-PRINTMODETEST, ID ST, Language D or E.
2.6 Page Windows Edit section
When you define page windows, the window names are linked to page names. You must specify the position and size of the window on the assigned page.
Define the position of a window by specifying the left margin and upper margin and the size of a window by specifying its width and height.
Left margin
Space between the window and left margin of the page
Upper margin Space between the window and upper margin of the page
Window width Width of the window depending on the page format selected
Window height Height of the window depending on the page format selected
Note that the width of the main window must be the same on all pages. All other window types can have different sizes and positions on different pages.
To print multiple columns, define several main windows on a page. As text entry is continuous, once the first main window has been filled, output continues in the second main window.
Rewards if helpfull
Regards
Pavan

HP LaserJet 4250 stalls on 2nd page of Duplex print

I work in a University IT Department where we maintain over 80 networked HP Laser printers, mostly HP LJ4250's with duplexers installed. When students send a "PDF" duplex print job, the printer quickly prints the first page and sucks it back into the printer to prepare the other side of the page, as designed. The problem is that it appears as tho the printer stalls and displays the processing message on the LCD screen. The page never spits out. If we turn the printer off and back on, the page will finally spit out, but without any print on the backside of the page.
We have tried to print by specifing the "Print as Image" option, but still the same results. We are at the point of telling students to waste paper and print single pages just so they don't have to stand there waiting for something that seems like it will never print.
Is this a fight between Adobe and HP? If so what can someone recommend other than waiting for Internet Explorer 9 and its version of reader?

Did anyone find anything on this? It's a problem that can be duplicated, and is very frustrating.
From what I have tested, the problem only exists on HP PCL Universal Drivers. I have not had it happen with with the PS drivers or the device specific drivers.
Furthermore, it seems that the second page on the PS driver re-queues or somthing, as there is a considerable lag on the print. The paper sits inside the duplexer for seveal seconds before printing the second page. It is without a doubt a driver issue in the PCL, as the Xerox Global PCL prints it just fine, but prints MS Word and outlook doucuments all wonky (as a xerox driver probably should on an HP printer).
JetDirect, Device Firmware, and Universal print drivers are all up to date on this system. And as I stated earlier, the problem can be duplicated.

SAP Duplex printing on Xerox

Similar Messages

Maybe you are looking for