SAP Document Printing

I have a client on SAP Business One 2007 SP00 PL49. In Document Printing if you select Delivery Tickets they do not print. All other document types print. If you open a Delivery Ticket it will print. But if you select the rows or a row from the Document Printing it does not print.
This was working about a week ago. The only thing the client did was to Create BP Groups and assign to BP's.
There is a test database from before they changed the groups and in that database the delivery tickets print.
Any suggestions?

business one?
I guess you are better looking for a forum for that. This here is more about R/3 and ERP.
Regards
Hein

Similar Messages

PO print OUT And material Document Print Out is coming In English

HI all.
I have Created Vendor In ZH(chinese Language,)and in material master I have maintained description in Chinese language.
I'M taking PO and material Documents print outs in Chinese Server log-in.
even Though Im taking Print outs in Chinese Log-In server, IM getting Print outs in English Language only not In chines language..
At the Time Of PO creation the Communication Language is ZH(Chines)..
I have read some related post even 89899..
But I have not find solution
plz help me.
thanks and regards
ramesh reddy.'

Check SAP Note 894444 - Tool for server-based printing on Windows (SAPSprint) for your requirement,
Installation
Before you install SAPSprint, delete SAPLPD manually. To do this, you normally need to completely delete the installation directory only. If you installed SAPLPD as a service using the srvany tool, you can remove the service by calling 'Instsrv SAPLPD remove'.
You can download SAPSprint as a self-extracting executable file from SAP Service Marketplace:
1. Entry by Application Group (on the left)
2. SAP Frontend Components (on the right)
3. SAPSPRINT (on the right)
4. SAPSPRINT <Release> (on the right)
5. SAPSPRINT <Release> (on the right)
6. Win32 (on the right)
Start the program. After you enter the installation path, the system prompts you to enter the TCP/IP port.
Normally, the default setting of 515 is suitable for the port. You should only change this setting if the Windows TCP/IP print service is also running on the computer. The SAPSprint Windows service starts as soon as the installation is over.
We recommend that you set up the following options for the service in the Windows Service Control Manager:
The service should run under a domain user that has the relevant authorizations for the required printers. After the installation, the service runs under "Local system account". This can access locally-defined printers only. You can set the user in the Windows Service Control Manager, in the options of the SAPSprint service.
If you want to delete SAPSprint, you can do so using the normal Windows uninstall tool.
We recommend that you install the SAPSprint service on a separate computer and not together with a SAP system, especially if you use a large number of printers. All printers that SAPSprint uses must be installed on the SAPSprint computer. This applies particularly to released printers from other computers. These should be installed as a queue on the SAPSprint server.
Also note further settings in accordance with Note 1069483.
Settings
You can display the call parameters available for SAPSprint by calling 'sapsprint -?' on the command line. The most important parameters are those that set options, especially log options for troubleshooting.
You can set the log level to 5 by specifying 'sapsprint -oi LogLevel 5'. Immediately after installation, no log level is set up, which means that no log file is created. By setting the log level to 1, 5, or 9, you can ensure that more information is available in the directory that you specified during the installation. A file called sapsprint.dbg and a print job specific file with a variable name are generated. The second file is deleted after successful printing. It is only retained if the printout is recognized as incorrect. If you set the option 'sapsprint -oi KeepFile 1', then both this file and the print file are retained. This is primarily intended for troubleshooting by SAP Support.
All options are case-sensitive. You can display the most important SAPSprint options by calling 'sapsprint -?'. All possible options are described in Note 85469. Normally, the options described there are not necessary - you should use them only in exceptional circumstances.

SAP Script Printing

Hi,
Can we have 'Collate' functionality as in Word document in SAP script printing.

Hi Rathakrishnan,
It's not a functionality of SAP script, but you have to set an attribute of the output device. Use transaction SPAD, select your printer and hit button Output Device. Then go to Tab 'Output attributes' and set 'Copies as separate output requests (in SAP System)'. This is similar to the collate functionality.
Does this solve your problem?
Regards,
John.

Document printing - differrent layout

Hi,
We have developed in PLD an Invoice and a Quotation.
1. Invoice - in PLD Document Properties, the Format is A5.
2. Quotation - in PLD Document Properties, the Format is A4.
In SAP screen, File--> Page Set up, the page is A4.
When we print the Invoice, SAP is printing out in A4 format. We have
refer to note 1030589, and thought that it is the PLD should have
overwritten the default Page setting.
Could you please advise how we could print different format in SAP? Is
this a design restriction?

Hi,
Just got a reply from SAP support, in case anyone is interested.
(Question raised)
If I understand you correctly, does that mean:
- although I have set different paper size on Print Layout designer, SAP
will ignore it. The page format in Print Layout does not take effect.
- Every time when I need to print A4, I need to go to Page Set up to make
sure A4 is selected. When I need to print document in A5, I need to go to
Page set up to make sure A5 is selected.
(Answer from Support)
Yes, for the paper format the settings are to be done in this way.
As the system will always take the paper size which has been set as
default for the printer.

SAP Adobe Print forms - Issue with Chinese characters

Hi All,
We are using SAP Adobe Print forms to create a business document. This is designed using Adobe Life Cycle Designer (ALD). The form is displayed in Chinese language. The requirement is to display captions for few fields in bold.
When designing the form we have put the caption as BOLD but when the actual form is generated only few characters are displayed in bold.
I am not sure if this is problem with Adobe Reader or should there be any specific fonts to be installed in the ADS server?
Please let me know which all font packs needs to be installed in the local machine?

Hi Pat,
Thank you again for your reply.
Now, I changed the font in the designer to "Adobe Song Std L" and made the text as "BOLD". Then I get a message
The following is the Designer screen shot.
Questions:
1. Does "Adobe Song Std L" support characters in BOLD?
2. Do I need to install any of those BOLD fonts? If so, where can I get them?
3. I understand that the BOLD font needs to be installed in the local machine (where the design actually happens so that the font can be specified), the ADS Server (where the actual PDF is rendered) and also in the viewers local machine (where the PDF document is viewed). Is this correct?
4. Is the font a freeware or will there be any licensing issues?
Again, thank you for your responses till now.

Selective Document Printing

Hello All!
I wonder if there are any plans on adding a feature to the new SAP upgrade which would allow selective document printing.
What I mean is it would be great, when printing a batch of AR Invoices for example, to be able to select not only a date range and/or a document range but also some other fields like a sales employee or a particular customer, etc.
Thank you,
Michael

This date has not relation to your posting date.
The 03/13 is the check date. Your transactions are still from your February date range.
You created the checks today and a check needs to have a date on it and this 03/13 is the date that will be printed on the check
By default the date you process the checks will be the date check date.
Posting Date is nothing but the date the transaction / JE is posted on.
Suda

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

Output forrmats for SAP documents

Hi,
I am trying to set up our SAP system such that all SAP documents are sent with HTML attachments.
I have gone into transaction SCOT and under the 'Output formats for SAP documents' section, I tried to select the HTM option for SAPSCripts/Smart Forms, however there is no such option.
I can see the HTM option for ABAP List though.
Does anyone know how I can select the HTML option for SAPScripts?
Thanks,
Ruby

Here is some sample code for achieving manual conversion to the OTF format.
In case of more than 10 pages:
- Check the spool request
- Click Edit -> OTF display -> No. of OTF pages
Convert SAP Script to text:
- Display the spool request
- Then click Goto -> List display
Automatic conversion to the OTF format:
tables: tline.
data:   begin of int_tline1 occurs 100.
             include structure tline.
data:   end of int_tline1.
call function 'OPEN_FORM'
                 device         = 'OTF_MEM'
after CLOSE_FORM
call function 'CONVERT_OTF_MEMORY'
     exporting
          format                = 'ASCII'
          max_linewidth         = 132
     tables
           lines                 = int_tline1
     exceptions
          err_max_linewidth        = 1
          err_format                    = 2
          err_conv_not_possible = 3
          others                          = 4.
write the text file to spool
loop at int_tline1.
   if int_tline1-tdline = space.
      skip.
   else.
      write:/ int_tline1-tdline.
   endif.
endloop.
CONVERT_OTF
Convert SAP documents (SAPScript) to other types.
Example:
CALL FUNCTION "CONVERT_OTF"
       EXPORTING    FORMAT                = "PDF"
       IMPORTING    BIN_FILESIZE          = FILE_LEN
       TABLES       OTF                   = OTFDATA
                    LINES                 = PDFDATA
       EXCEPTIONS   ERR_MAX_LINEWIDTH     = 1
                    ERR_FORMAT            = 2
                    ERR_CONV_NOT_POSSIBLE = 3
                    OTHERS                = 4.
CONVERT_OTFSPOOLJOB_2_PDF converts a OTF spool to PDF (i.e. Sapscript document)
SX_OBJECT_CONVERT_OTF_PDF Conversion From OTF to PDF (SAPScript conversion)
SX_OBJECT_CONVERT_OTF_PRT Conversion From OTF to Printer Format (SAPScript conversion)
SX_OBJECT_CONVERT_OTF_RAW Conversion From OTF to ASCII (SAPScript conversion)
regards,
srinivas
<b>*reward for useful answers*</b>

GR document printed on wrong printer.

Hello,
Please suggest solution for my problem below,
when ever user does the GR via MIGO , the GR document goes to local printer instead of SAP default printer.
Please let me know if there is any customization setting maintained for GR (MIGO) where we can set the printer for particular transaction or printer for particular user .
Thank you ,

Dear PP/PI User,
Assign the default printer(output Device) in SU3 for the user and save the data under Defaults tab page.
If this does not works means check the setting in OMJR.
Check with this setting and revert back.
Regards
S Mangalraj

Crash after batch document printing in 8.8

Hey gang. This is my first post to the SAP forums. I'm told that this is the place to turn to for help. I appreciate having you on my side.
Just upgraded to 8.8 and am testing out the Document Printing feature (Sales - A/R, Document Printing). When I try to print more than 1 document to a printer, SAP crashes and vanishes from the screen. It actually crashed after the 2nd document gets printed. This occurs regardless of the printer I'm sending it to. From the same window, if I just choose 1 document to print, the application does not crash. We used this functionality almost every day in ver 2007 without issue.
Is this a bug in SAP?
Randy Davis
Denver, CO

Hey Gordon--
Here's more information. We are using Crystal Reports, created from scratch. These are actually various marketing documents that seem to all have the same issue. The symptoms are actually this: printing a document multiple times to a printer crashes the system. Even printing different documents one after the other crashes it. It seems like it always will prints at least 2 or 3 documents before it crashes.
While I'm writing this, another member of my team is researching other sites and found a post that seemed to indicate that subreports in Crystal are sometimes a problem. If so, is there a way to make subreports work properly?
Use to use PLD in the old version. We are at PL 16.
Randy Davis
Denver, CO
Oh, one of your FFF buddies told me to tell you he's sitting next to me right now waiting on your answer. When he gets it, he will get to your book review

Customer Account Statement Does not show SAP document number

Hello,
I want to have the SAP-document number on a customer-statement printed with report RFKORD11. I changed the used form now multiple times without success. If I enter the BSID-BELNR as an output parameter the system always gives me BSID-XBLNR what makes no sense to me!
If I look into the table the field is maintained correctly and I really have no idea why the system is always taking the XBLNR-content. If it output XBLNR I am getting the XBLNR-content but not the other way round...
Maybe it is a stupid problem but I have no idea why it works that way and I need the SAP-document number printed on the customer-statement. The other table RF140 does not offer me the document-number as a field.
Thanks in advance for all hints and solutions!
Regards,
Steffen

Hello Steffen,
It seems to be that the field XBLNR is blank.
This behaviour is of SAP standard design. It is the standard logic hard coded into the relevant program itself, see include RFKORI16 in SE38 for customer open items:
IF BSID-XBLNR IS INITIAL.
MOVE BSID-BELNR TO RF140-BELEGNUM.
ELSE.
MOVE BSID-XBLNR TO RF140-BELEGNUM.
ENDIF.
If you look at the description of the field RF140-BELEGNUM structure using transaction SE11 it is clearly mentioned that "Ref.Document Number, if available, otherwise Document Number".
The only other option you would have would be to consider a modification of the standard.
I hope it helped you
Best Regards,
Vanessa.

All the Pages are Printed - Document Printing Sales Orders

When using the Document Printing option for Sales Orders, if I select multiple documents and select print I get a message after each document that says "All the Pages are Printed", then the next document comes for printing. I also get a prompt each time whether or not to print Sales Order only or Sales Order and Pick List.
I don't have the same issue if printing Invoices from Document Printing. It asks what to print and prints all records without additional prompts between each record. I don't see anything in Print Preferences that would cause the Order to act differently from the Invoice.
We are using B1 9.0 PL 06.
Alan

Hello there, linafrompereira.
The following portion of the online Pages Help for Mac provides information on grouping items in Pages:
Layer, group, and lock objects - Pages Help for Mac
http://help.apple.com/pages/mac/5.2/#/tan5eab46568
Group and ungroup objects
Shift-click to select multiple objects.
In the Arrange pane of the Format inspector, click Group (or choose Arrange > Group from the Arrange menu at the top of your computer screen).
To ungroup an object, select it, then click Ungroup or choose Arrange > Ungroup.
Tip: You can Control-click objects, then choose Group or Ungroup from the shortcut menu. You can also add these buttons to the toolbar: Group and Ungroup.
Thanks for reaching out to Apple Support Communities.
Cheers,
Pedro.

T-Code to view SAP Document no.

Dear,
Need a T-code to view SAP Document number created while SAP Stock Creation.
After creation through MB1C a number is generated & i need to know what is the process to get this Document Number.
Thanks in Advance.

hi,
You can check MSEG table to get numbers..
Or USe MB51 to get list of material document as per your selections on the initial screen...
Regards
Priyanka.P

How can i duplicate a document print layout from one DB to another DB?

hi experts,
I make all document print layouts in a test DB, and now I want to move them to my production DB.
is there any easy way to copy a document layout from a database to another? please advise, thanks a lot.

Hi,
There is one more option
1.Open the PLD in the test database
2.Go to edit-> select all(including hidden fields)
3.Go to edit->Copy
4.Log off from test system(Administration-Choose company-select live database),log in live database
5.Open the corresponding documents system pld
6.Go to edit-select all
7.In the properties window uncheck the visible checkbox(Under General tab)
8.Save layout as different name say <Test>
9.Again open the layout <Test>
10.Go to edit-Paste and save layout.
NB:Don't delete the existing fields,you should only hide them as mentioned in step7

Printing from Windows = only the first half of documents print

I'm trying to set up a home print server, to allow access to an HP LaserJet 1005. It's working OK locally and accessed when printing from another Linux box. From XP and Vista, however, the first half of multiple-page documents print, and one-page ones don't print at all. This seems to be the case when using any Windows postscript driver (such as Apple LaserWriter 16/600 PS and HP LaserJet III Postscript Cartridge), and with documents from any program.
I can't see anything obvious in the logs when set to debug, as far as I understand them, they appear to show all pages printing, including the one-page documents which disappear completely. Whether this show it to be a Cups problem rather than a Windows one, I'd rather not attempt to say! This is /var/log/cups/error_log when printing a five-page document, in case there's something useful in it which I have missed.
/etc/cups/cupsd.conf:
LogLevel debug
SystemGroup sys root lp
# Allow remote access
Port 631
Listen /var/run/cups/cups.sock
# Enable printer sharing and shared printers.
Browsing On
BrowseOrder allow,deny
BrowseAllow all
BrowseRemoteProtocols CUPS
BrowseAddress @LOCAL
BrowseLocalProtocols CUPS dnssd
DefaultAuthType Basic
DefaultEncryption Never
<Location />
# Allow shared printing and remote administration...
Order allow,deny
Allow all
Allow From all
</Location>
<Location /admin>
# Allow remote administration...
Order allow,deny
Allow all
Allow From localhost
Allow From 192.168.1.33
Allow From 192.168.1.34
</Location>
<Location /admin/conf>
AuthType Default
Require user @SYSTEM
# Allow remote access to the configuration files...
Order allow,deny
Allow all
Allow From localhost
Allow From 192.168.1.33
Allow From 192.168.1.34
</Location>
<Policy default>
<Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs Set-Job-Attributes Create-Job-Subscription Renew-Subscription Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job Suspend-Current-Job Resume-Job CUPS-Move-Job CUPS-Get-Document>
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>
<Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer CUPS-Add-Modify-Class CUPS-Delete-Class CUPS-Set-Default CUPS-Get-Devices>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>
<Limit Pause-Printer Resume-Printer Enable-Printer Disable-Printer Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer Startup-Printer Promote-Job Schedule-Job-After CUPS-Accept-Jobs CUPS-Reject-Jobs>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>
<Limit Cancel-Job CUPS-Authenticate-Job>
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>
<Limit All>
Order deny,allow
</Limit>
</Policy>
<Policy authenticated>
<Limit Create-Job Print-Job Print-URI>
AuthType Default
Order deny,allow
</Limit>
<Limit Send-Document Send-URI Hold-Job Release-Job Restart-Job Purge-Jobs Set-Job-Attributes Create-Job-Subscription Renew-Subscription Cancel-Subscription Get-Notifications Reprocess-Job Cancel-Current-Job Suspend-Current-Job Resume-Job CUPS-Move-Job CUPS-Get-Document>
AuthType Default
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>
<Limit CUPS-Add-Modify-Printer CUPS-Delete-Printer CUPS-Add-Modify-Class CUPS-Delete-Class CUPS-Set-Default>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>
<Limit Pause-Printer Resume-Printer Enable-Printer Disable-Printer Pause-Printer-After-Current-Job Hold-New-Jobs Release-Held-New-Jobs Deactivate-Printer Activate-Printer Restart-Printer Shutdown-Printer Startup-Printer Promote-Job Schedule-Job-After CUPS-Accept-Jobs CUPS-Reject-Jobs>
AuthType Default
Require user @SYSTEM
Order deny,allow
</Limit>
<Limit Cancel-Job CUPS-Authenticate-Job>
AuthType Default
Require user @OWNER @SYSTEM
Order deny,allow
</Limit>
<Limit All>
Order deny,allow
</Limit>
</Policy>
/etc/cups/printers.conf:
# Printer configuration file for CUPS v1.4.3
# Written by cupsd on 2010-04-11 22:13
# DO NOT EDIT THIS FILE WHEN CUPSD IS RUNNING
<Printer hp-laserjet-1005>
Info HP LaserJet 1005 series
Location Presario
MakeModel HP LaserJet 1005 Series hpijs, 3.10.2, requires proprietary plugin
DeviceURI hp:/usb/hp_LaserJet_1005_series?serial=0
State Idle
StateTime 1271020410
Type 8425484
Filter application/vnd.cups-raw 0 -
Filter application/vnd.cups-postscript 100 foomatic-rip-hplip
Filter application/vnd.cups-pdf 0 foomatic-rip-hplip
Accepting Yes
Shared Yes
JobSheets none none
QuotaPeriod 0
PageLimit 0
KLimit 0
OpPolicy default
ErrorPolicy retry-job
</Printer>

Are you using Samba?
Firstly a shot in the gloom: If so, have you tried setting
use client driver = yes
in smb.conf, under the printers section? Or if it is yes, try no.
The other thing you can try is to stop the file being printed/removed from the spool directory(s), and see where the lost stuff gets lost.
To be honest, I'm not sure where/how you can do this, but I believe that samba will store the file initially in a spool file specified by smb.conf and then Cups will store it somewhere else. Changing the print commands to not print/remove the file from these two points may help identify the loss point.
Can you plug the printer directly into the windows box and see what happens?

SAP Document Printing

Similar Messages

Maybe you are looking for