Differences in printout of SAPScript

Hello everyone!
My requirement is the following:
I have a SAPScript form and two computers.
I want to print this form using a virtual PDF printer.
In Print Preview this form prints out fine in both computers.
When I print the form to a PDF file, in one computer it prints out fine, in the other the logos don't appear and the footer is slightly pushed up.
Any ideas why this happens?
Best regards,
Luís Andrade.

Hi Luis,
Just go through these links, I hope it will help you.
[Link1|Logo not getting printed in SAP SCRIPT;
[Link2|LOGO IS NOT GETTING PRINTED IN DOT MATRIX in SAP SCRIPTS;
Regards,
Nidhi Kothiyal

Similar Messages

  • Excise Invoice Printout through Sapscript

    Hi Friends,
    I am facing a strange problem in Excise Invoice Printout using Sapscript, using Tcode J1IV (Program is J_1IEXCP_OUTPUT).
    The print preview is coming correctly but print out is not happening.
    Please guide me the solution.
    Thanks in advance.
    MARK K

    Hi Mark,
    you have two options here,
    you can set printer name and print immediately option in the output type for your transaction code.
    or you can set the flag dailog = 'x' in your SAP script print program.
    It will popup one window when you execute it and you can chooose printer name and other options to print immediately.
    If it is not printed still, just go to the transaction J1IV and open the output type window and then check the logfile for your output type. it will give you correct information why you are getting printout.
    regards,
    ram

  • Smart Forms and Sapscripts?

    Hi,
    I have read that one of the differences between smartforms and sapscript is that smartform is client independent while sapscript is client dependent.Can anyone please explain me why it is so?
    Regards
    Arya
    Moderator Message: Please search for available information before posting.
    Edited by: kishan P on Oct 27, 2010 10:58 AM

    example u create a script in client 800 .
    take that script name and go to another client 810 and run the script at that time u know the difference .
    for smartform  it is client independent because some function modules are created dynamically so u can run this
    form in any client .

  • Standard sapscript form migration to adobe form

    Hello guys,
    Is it possible to migrate standard SAP Script forms to adobe forms?
    If yes then please let me know how ?

    Hi,
    It is possible, but not simple. 
    You first have to migrate the SAPscript to Smartforms, then the Smartform to adobe forms.  However, there are significant differences between the way SAPscript works compared to Smartforms so there are always manual changes needed after the migration.  Then there are differences between Smartforms and adobe forms, so more manual changes are needed.
    Once you've done all this it could have been easier to build an adobe form from scratch, based on the design of you SAPscript.
    Regards,
    Nick

  • What is the difference between smart forms and scripts.?

    what is the difference between smart forms and scripts.?

    Differences between Smartforms and SAPscript
    a) Multiple page formats are possible in smartforms which is not the case in SAPScripts
    b) It is possible to have a smartform without a main window .
    c) Routines can be written in smartforms tool.
    d) Smartforms generates a function module when activated.
    e) Smartforms can create web enable forms like XML
    f) smartforms itself contine subroutine pools need not to main separetly like in case of scripts
    Request you to refer the following links
    www.sap-img.com/smartforms/smartform-sapscripts.htm
    www.erpgenie.com/abap/smartforms_sapscript.htm
    Sapscript vs Smartforms
    Difference with SMARTFORMS vs. SapScript(SE71)
    The Following are the differences :-
    a) Multiple page formats are possible in smartforms which is not the case in SAPScripts
    b) It is possible to have a smartform without a main window .
    c) Labels cannot be created in smartforms.
    d) Routines can be written in smartforms tool.
    e) Smartforms generates a function module when activated
    Scripts are client dependent whereas smartforms aren't.
    Upto 99 main windows are possible in scripts and only one in smarforms.
    To create multiple main windows in scripts, you just have to give the window type as MAIN whnever you create a window.
    Scripts still exists but smartforms are in use from 4.6c version, now the lastest version of these two is adobe forms
    SAP Smart Forms is introduced in SAP Basis Release 4.6C as the tool for creating and maintaining forms.SAP Smart Forms allow you to execute simple modifications to the form and in the form logic by using simple graphical tools; in 90% of all cases, this won't include any programming effort. Thus, a power user without any programming knowledge can
    configure forms with data from an SAP System for the relevant business processes.
    Advantages of SAP Smart Forms
    SAP Smart Forms have the following advantages:
    1. The adaptation of forms is supported to a large extent by graphic tools for layout and logic, so that no programming knowledge is necessary (at least 90% of all adjustments). Therefore, power user forms can also make configurations for your business processes with data from an SAP system. Consultants are only required in special cases.
    2. Displaying table structures (dynamic framing of texts)
    3. Output of background graphics, for form design in particular the use of templates which were scanned.
    4. Colored output of texts
    5. User-friendly and integrated Form Painter for the graphical design of forms
    6. Graphical Table Painter for drawing tables
    7. Reusing Font and paragraph formats in forms (Smart Styles)
    8. Data interface in XML format (XML for Smart Forms, in short XSF)
    9. Form translation is supported by standard translation tools
    10. Flexible reuse of text modules
    11. HTML output of forms (Basis release 6.10)
    12. Interactive Web forms with input fields, pushbuttons, radio buttons, etc. (Basis-Release 6.10)
    Reward Points if useful.

  • Doucments on Sapscript

    Hi friends,
    I havent worked on SAPSCRIPT , but my current project requires a development in SAPSCRIPT could anyone of you pass me any link or any documents from where I can learn this topic?
    And also please let me know whats the difference between Smartforms and SAPSCRIPT.
    Helpful answers would be appreciated.
    Thanks,
    Rinky

    Hi,
    Check all the below links u will find lot of info on scripts..
    SAP Scripts
    http://www.sap-img.com/sapscripts.htm
    http://sappoint.com/abap/
    http://www.henrikfrank.dk/abapexamples/SapScript/sapscript.htm
    http://help.sap.com/saphelp_crm40/helpdata/en/16/c832857cc111d686e0000086568e5f/content.htm
    http://www.sap-basis-abap.com/sapabap01.htm
    http://www.sap-img.com/sapscripts.htm
    http://searchsap.techtarget.com/tip/1,289483,sid21_gci943419,00.html
    http://sap.ittoolbox.com/topics/t.asp?t=303&p=452&h2=452&h1=303
    http://www.sapgenie.com/phpBB2/viewtopic.php?t=14007&sid=09eec5147a0dbeee1b5edd21af8ebc6a
    Other Links
    http://www.virtuosollc.com/PDF/Get_Reporter.pdf
    http://help.sap.com/saphelp_47x200/helpdata/en/da/6ada3889432f48e10000000a114084/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/66/bc7d2543c211d182b30000e829fbfe/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/5b/d22cee43c611d182b30000e829fbfe/frameset.htm
    http://www.virtuosollc.com/PDF/Get_Reporter.pdf
    http://help.sap.com/saphelp_47x200/helpdata/en/da/6ada3889432f48e10000000a114084/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/66/bc7d2543c211d182b30000e829fbfe/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/5b/d22cee43c611d182b30000e829fbfe/frameset.htm
    drawing lins, boxes and shadings
    http://help.sap.com/saphelp_46c/helpdata/en/d1/802ec5454211d189710000e8322d00/frameset.htm
    How to create Box in scripts
    http://www.thespot4sap.com/Articles/Code_CostCentreReport.asp
    http://www.allsaplinks.com/dialog_programming.html
    http://help.sap.com/saphelp_webas630/helpdata/en/9f/db9cdc35c111d1829f0000e829fbfe/frameset.htm
    http://www.allsaplinks.com/files/using_table_in_screen.pdf
    http://www.geocities.com/ZSAPcHAT
    If u find it useful mark the points
    ~~Guduri

  • Difference between Smartforms and Sapscrits.

    Hi Experts,
    I have a interview coming up next week and I was just wondering: difference between Smartforms and SAPscripts..
    So experts, can anyone please let me know what are the main differences between Smartforms and SAPScripts??
    I will really appreciate your answers.. guys..
    Regards,
       -Ashok Patel.

    Hi,
    <b>Difference with SMARTFORMS vs. SapScript(SE71)</b>
    The Following are the differences :-
    a) Multiple page formats are possible in smartforms which is not the case in SAPScripts
    b) It is possible to have a smartform without a main window .
    c) Labels cannot be created in smartforms.
    d) Routines can be written in smartforms tool.
    e) Smartforms generates a function module when activated.
    f) Unlike sapscripts (RSTXSCRP), you cannot upload/download Smartform to your local harddisk. 
    It was said that it was provided in CRM 3.0 version, but not available in R/3.  You can download smartforms into Local PC in a XML format.  In the same way you can upload this XML format into Smartform.  From the smartform editor itself you can call download option, if you are working in CRM 3.0 environment. 
    In R3 also, you can download into XML format. However, it's not sure about uploading. Refer to the program 'SF_XSF_DEMO'.
    In 4.7 Enterprise, other have seen this utlity which is completey missing in 4.6c. There is functionality to downlaod a complete form or only a particular node. (Utilities -> Download form). It will create a XML file and save it in the hard disk. 
    For others, if you want to download/upload the Smartforms source, you will need the help from the Basis people.  What you can do is to create a Transport and then FTP down to your local harddisk.   When you need the Smartform source in another system, you have FTP up the Smartforms file back to the SAP server.  Finally, the Basis team, will tp it into your system.
    g) The protect and endprotect command in sapscript doesn't work with smartforms. For example on a invoice: First data of position no 80. is printed on page one, other data of position no 80 is printed on page 2. And there's nothing you can do about it.  Actually, there is something you can do about it.  By using a folder node and checking the 'protect' checkbox, everything in that folder will be page protected.
    Check the link,
    <u>http://www.sap-img.com/smartforms/sap-smart-forms.htm</u>
    <b>Conversion of SAPSCRIPT to SMARTFORMS</b>
    SAP provides a conversion for SAPscript documents to SMARTforms.
    This is basically a function module, called FB_MIGRATE_FORM. You can  start this function module by hand (via SE37), or create a small ABAP which migrates all SAPscript forms automatically.
    You can also do this one-by-one in transaction SMARTFORMS, under 
    Utilities -> Migrate SAPscript form.
    You could also write a small batch program calling transaction SMARTFORMS and running the migration tool.
    Hope it helps u.
    Thanks&Regards,
    Ruthra.R

  • Smartform and sapscript..

    in which scenario v prefer smartform over sapscripts and in which scenarios sapscript over smartforms?

    Hi,
    Smartforms are better to use than scripts as they provide more facility like color, graphical user interface etc, but scripts are the oldest form of layout available in SAP. There is no advantage of using script over smartform. This entirely depends on the choice in case of new developments. However, if you have to change/customize existing script then you have to deal with scripts only.
    Difference with SMARTFORMS vs SapScript(SE71).
    a) Multiple page formats are possible in smartforms which is not the case in SAPScripts
    b) It is possible to have a smartform without a main window .
    c) Smartforms generates a function module when activated.
    d) Unlike sapscripts (RSTXSCRP), you cannot upload/download Smartform to your local harddisk.
    e) In smartforms there is only one main window.
    In scripts we can create 99 main windows.
    f) Smartforms are client independent. but scripts are client dependent.
    g) we can execute smartforms directly without driver program. But it is not possible in script.
    h) peform statement is possible in script but not in smartforms.
    i) loop statement is possible in smartforms.
    In script for every data record controls moves from
    script to driver program and to script.
    In smrtforms this is not rquired.
    In 4.7 Enterprise, other have seen this utlity which is completey missing in 4.6c. There is functionality to downlaod a complete form or only a particular node. (Utilities -> Download form). It will create a XML file and save it in the hard disk.
    For others, if you want to download/upload the Smartforms source, you will need the help from the Basis people. What you can do is to create a Transport and then FTP down to your local harddisk. When you need the Smartform source in another system, you have FTP up the Smartforms file back to the SAP server. Finally, the Basis team, will tp it into your system.
    i) The protect and endprotect command in sapscript doesn't work with smartforms. For example on a invoice: First data of position no 80. is printed on page one, other data of position no 80 is printed on page 2. And there's nothing you can do about it. Actually, there is something you can do about it. By using a folder node and checking the 'protect' checkbox, everything in that folder will be page protected.
    Check the link,
    http://www.sap-img.com/smartforms/sap-smart-forms.htm
    Conversion of SAPSCRIPT to SMARTFORMS
    SAP provides a conversion for SAPscript documents to SMARTforms.
    This is basically a function module, called FB_MIGRATE_FORM. You can start this function module by hand (via SE37), or create a small ABAP which migrates all SAPscript forms automatically.
    You can also do this one-by-one in transaction SMARTFORMS, under
    Utilities -> Migrate SAPscript form.
    Regards,
    Richa

  • Need information on SMARTFORMS

    hi i m looking for some information on SMARTFORMS.
    why it is needed?
    what is difference between smartforms and sapscripting?
    if someone could send some docs. how to work on smartforms it will begreat

    Hi,
    Here I am sending the full information about smartforms. Reward if helpful.
    SAP Smart Forms (BC-SRV-SCR)
    Purpose
    You use SAP Smart Forms to create and maintain forms for mass printing in SAP Systems. As output medium SAP Smart Forms support a printer, a fax, e-mail, or the Internet (by using the generated XML output).
    In addition to the tool, SAP delivers a selection of forms for central business processes. This includes forms in Customer Relationship Management (CRM) as well as in the applications SD, FI, and HR of the R/3 Release.
    SAP Smart Forms offer the following advantages:
    •     Creating and maintaining forms requiring half the time
    •     Adapting forms without any programming knowledge due to entirely graphical user interface
    •     Web Publishing using the generated XML output
      The SAP Smart Forms replace the SAPscript forms. SAPscript forms will also be supported in the future; you can use them without making any changes for years to come. You can use SAPscript texts in the Smart Forms. Migration of SAPscript forms into Smart Forms is supported.
    Features
    SAP Smart Forms allow you to execute simple modifications to the form and in the form logic by using simple graphical tools; in 90% of all cases, this won't include any programming effort. Thus, a power user without any programming knowledge can configure forms with data from an SAP System for the relevant business processes.
    To print a form, you need a program for data retrieval and a Smart Form that contains the entire from logic. As data retrieval and form logic are separated, you must only adapt the Smart Form if changes to the form logic are necessary. The application program passes the data via a function module interface to the Smart Form. When activating the Smart Form, the system automatically generates a function module. At runtime, the system processes this function module.
    You design a form using the graphical Form Painter and the graphical Table Painter. The form logic is represented by a hierarchy structure (tree structure) that consists of individual nodes, such as nodes for global settings, nodes for texts, nodes for output tables, or nodes for graphics. To make changes, use Drag&Drop, Copy&Paste, and select different attributes. These actions do not include writing of coding lines or using a Script language.
    For Web publishing, the system provides a generated XML output of the processed form.
    You can insert static and dynamic tables. This includes line feeds in individual table cells, triggering events for table headings and subtotals, and sorting data before output.
    You can check individual nodes as well as the entire form and find any existing errors in the tree structure. The data flow analysis checks whether all fields (variables) have a defined value at the moment they are displayed.
    SAP Smart Forms allow you to include graphics, which you can display either as part of the form or as background graphics. You use background graphics to copy the layout of an existing (scanned) form or to lend forms a company-specific look. During printout, you can suppress the background graphic, if desired.
    SAP Smart Forms also support postage optimizing.
    General Concepts on Form Printing
    Form printing covers creating and maintaining a form for mass printing in SAP Systems. This includes design and layout of the form as well as form logic.
    The layout determines the page structure, that is the number of differently structured pages and the positions of the output areas on these pages. Within the output areas, you use tables, paragraphs, paragraph formats and character formats to structure and format texts and data.
    The form logic controls the dynamic formatting of the form. It allows you to display variable fields, to display texts only if a certain condition is true (for first dunning, use this text, for second dunning another), or to repeatedly process invoice items within a table.
    Forms can be:
    •     Order confirmations
    •     Invoices
    •     Account statements
    •     Checks
    •     Salary statements
    •     Delivery notes
    •     Customs forms
    •     Industry-specific forms, such as quality forms in automobile manufacturing
    The concepts on form printing presented below are independent of any tool. As of mySAP.com release 4.6C use the SAP Smart Forms [Extern] in SAP Systems.
    This documentation does not cover document output and control on printers. Description of the process ends with transferring a processed file to the output management, which in the R/3 System is the spool.
    Structure of a Form
    Definition
    A form consists of pages, output areas, addresses, graphics (such as company logo), and data or text contents. Within an output area, you can use static or dynamic tables to display data or texts in lines, columns, or cells. To further structure and format text and data, use paragraphs with the paragraph and character formats.
    SAP calls output areas "windows". You can position windows freely on a page (see also Pages of a Form [Seite 8] and Main Windows and Subwindows [Seite 8]).
    Example of a Form Structure
    We use a simple invoice. For certain customers, we display their flight bookings with prices in a table in a window. The invoice also contains other windows for the company logo, the sender address, the customer address, company-specific data (clerk, customer number, reference, date, and so on), bank data, and pagination.
    The first page displays the customer letter, followed by a table containing the flight bookings of that customer. The output length of the table depends on the number of booking items (dynamic table). The table header contains the column headings, the table footer contains the total. If the space on the first page is not sufficient to take all items, the table continues on the next page, thereby repeating the column headings. In addition, the first page contains:
    •     the company logo inserted as graphic in bitmap format.
    •     the customer address. This address appears only on the first page (for the window in the envelope) and is preceded by the sender address in small font.
    •     a window containing company-related data in several fonts and font sizes (invoice, clerk, phone/fax, reference, customer number, date).
    •     the footer containing the company and bank data.
    The second page contains the current page number and the total number of pages in the document.
    Pages of a Form
    Definition
    On the pages of a form you determine the page layout and the sequence of pages with different structures.
    The page layout includes the page format (for example, DIN A4, Letter, DIN A5 landscape) and the position of the windows on a page.
    Use
    The individual pages of a form differ in their structure. The first page of an invoice, for example, contains the address, which you do not want to display on the next page; and you want to display the General Terms of Business on the last page. For each page, you must specify a next page to make the page sequence clear. You can also repeatedly call the same page if you want recursive output (for example, if the list of invoice items is very long and does not fit onto one document page).
    The page break either is triggered automatically by the main window (see also Main Window and Subwindows [Seite 8]) or you code it manually into the form logic (see also Specifying the Page Sequence [Seite 52]).
    Many forms contain only two pages of different structure: the first page, which calls the next page, and the next page, which calls itself. If the text does not entirely fit onto the second page, another document page is automatically displayed.
    Main Window and Subwindows
    Definition
    On a page, there are two different types of output areas for texts and data: the main window and the subwindow.
    Use
    You can position windows anywhere on a page, even overlapping. You can position the same window (determined by the technical name) on several pages of a form, so that the same contents are displayed on all these pages. You can choose a different size for the window on each page, except for the main window.
    Main Window
    In a main window you display text and data, which can cover several pages (flow text). As soon as a main window is completely filled with text and data, the system continues displaying the text in the main window of the next page. It automatically triggers the page break.
    You can define only one window in a form as main window.
    The main window must have the same width on each page, but can differ in height.
    A page without main window must not call itself as next page, since this would trigger an endless loop. In such a case, the system automatically terminates after three pages.
    Subwindows
    In a subwindow you display text and data in a predetermined output area. There is no flow text display with page break. If you position a subwindow with the same name on several pages, the system displays the contents of this subwindow on each page.
    Text and data that do not fit into the subwindow are truncated and not displayed.
    Texts and Data in a Form
    Definition
    You enter text in an editor (see also Positioning Text on a Form [Seite 26]).
    Data can be character strings or numbers. The system reads this data from a database and uses fields (parameters) to dynamically display it (see also Using Parameters in a Form [Seite 37]).
    Use
    To display text and data in table format (for example, lists or invoice items), you use tables or templates.
    To format texts and fields (data), you use paragraph and character formats. You assign paragraph formats to entire paragraphs and character formats to individual character strings, for example, to highlight a word.
    The paragraph format determines:
    •     Font family and font size,
    •     Indents and spacing,
    •     Text alignment within the paragraph,
    •     Tabs,
    •     Outline options, such as numbering,
    •     Protection of paragraphs against page breaks.
    To determine the paragraph and character formats, use the Smart Styles (see also Smart Styles [Seite 54]).
    Overview
    This section describes the architecture  [Seite 10]of SAP Smart Forms and how to create a form [Seite 11]. Essential for creating forms is to understand the form logic [Seite 13].
    Architecture
    If you create forms for an application, you want to include application data into the form. The architecture of SAP Smart Forms separates application data retrieval from the actual definition of the form:
    In a Smart Form you describe:
    •     The layout of your form (element positions on a page)
    •     Individual elements you want to display (text, graphics, addresses, tables, and so on)
    •     the form logic you use, for example, to read application data from internal tables, to introduce conditions, and to control process flows (see also: Form Logic: Introduction [Seite 13])
    •     a form interface to transfer application data to the form definition
    When you activate the Smart Form, the system generates a function module that encapsulates all attributes of the Smart Form. As soon as the application program calls the function module, the Smart Form uses the modules interface (which corresponds to the form interface) to transfer any table data previously selected and to print the form according to the form description.
    The form description can also contain statements that select further data during form processing. However, you should not use this method of data retrieval. Especially if you print mass forms, performance will deteriorate considerably.
    Creating Forms Using SAP Smart Forms
    This section gives an overview of how to create a form in which to display application data from database tables.
    For more detailed information on this procedure, see Using SAP Smart Forms [Seite 14].
    When creating a form, you must:
    1.     Retrieve the application data [Seite 11].
    2.     Describe your form [Seite 12].
    3.     Pass the application data to the form [Seite 38].
    Printing the Form
    Call a function module generated by Smart Forms to print your form. Smart Forms support the forllowing output options:
    •     The form is printed on a printer connected to the SAP System. Before printing, use the print preview to check whether the form is correct.
    •     The function module generates an XSF datastream that transfers, for example, the form description including the retrieved data to programs of third-party companies.
    Retrieving Application Data
    Prerequisites
    To achieve a good performance when printing a form, you must separate data selection from the use of data in the form. Thus you can bundle database operations before you start processing the form.
    Before you retrieve data, you should know:
    •     Which application data you want to appear in the form
    •     Which database tables you must access to retrieve this data
    Process Flow
    Write an ABAP program to retrieve data or include a retrieval routine into your application. This code consists of statements that select data from the database according to certain selection criteria. Store the retrieved data in internal tables, structures, or variables and transfer it to the form in one step.
    While you initialize the form, you can format the data, which you passed to the form, for output in the form. Formatting data in the form and not in the data retrieval program allows you to use one data retrieval program for several forms with different formatting routines.
    Result
    You store the application data in internal tables of the data retrieval program. Since you know now which table types occur, you can define a form interface to transfer this data to the appropriate form.
    Describing the Form
    You describe a form using a Smart Form. To do this, use the Form Builder (see also: Graphical User Interface [Seite 15]):
    1.     Describe the interface of the form. It results from the application data previously selected.
    2.     Create one or more pages. On a page, you can position windows, addresses, and graphics. Within a window, you can create additional elements.
    3.     Create elements (text, graphics, tables, and so on) for each page, using other tools of the Form Builder:
    &#61485;     Use the Form Painter [Seite 17] to position windows, graphics, and addresses on a page (the other elements are displayed in an assigned window).
    &#61485;     Use the PC Editor [Seite 19] to write your texts.
    &#61485;     Use the Table Painter [Seite 20] to format your tables.
    For an overview of the elements available on page level, see Node Types: Overview [Seite 23].
    4.     Use the flow control [Seite 50] to control whether and when to print pages and elements.
    Result
    When you activate your Smart Form, the Form Builder generates a function module that encapsulates the form description.
    Form Logic: Introduction
    In the Form Builder you describe a Smart Form by a set of nodes. To do this, you build up a tree structure on the left side of the user interface:
    This graphic already contains some nodes. The node Global Settings as well as its three successors Form attributes, Form interface, and Global definitions always exist for any newly created forms. To describe the Form logic, create a hierarchy under the node Pages and windows. This hierarchy determines the rules used to process the nodes of the tree. Depending on the node type, this could include:
    •     printing the node contents (text, addresses, graphics).
    •     executing the node statements.
    •     executing the successors of a node according to other rules (for example, in a loop).
    You use the form logic to control the flow of the form output. The following rules apply throughout:
    1.     The nodes in the tree structure are processed from top to bottom. This is easier to understand, if you imagine all nodes to be expanded.
    2.     For each node there is a tab, which you can use to link the node to a condition [Seite 51]. If the condition is true, the system processes the node. If not, it skips the node and all its successors.
    3.     You must define a next page for each page. However, you can also go to other pages dynamically (see also: Flow Control [Seite 50]).
    In addition, the page break depends on how much space there is left on the current page.
    For the complete rules for processing the tree structure, see Processing a Form [Seite 63].
    Example for Form Logic
    The diagram below shows the tree structure of the root node Pages and windows:
    The numbering of the nodes also shows the sequence in which they are processed (from top to bottom). The first node is the root node. The successors of a node are all nodes included directly under this node in the hierarchy. For node 5 these are the nodes 6 to 9 (direct successors are only the nodes of the next hierarchy level, that is 6, 7, and 9).
    A node without a successor node is also called end node. Elementary nodes can never have successors (see also Node Types: Overview [Seite 23]). If the condition of node 7 is false, neither node 7 nor node 8 are processed. Processing resumes directly with node 9.
    In this example, we assume that no pages are called dynamically and that there is enough space on the page for the output.
    Using SAP Smart Forms
    Graphical User Interface
    Use
    SAP Smart Forms provide a graphical user interface that helps you create and maintain the layout and the form logic of a form: the SAP Form Builder. You need neither have any programming knowledge nor use a Script language to adapt standard forms. Basic ABAP programming skills are required only in special cases (for example, to call a function module you created or for complex and extensive conditions).
    Features
    The SAP Form Builder of the SAP Smart Forms consists of:
    •     Form Painter for creating the layout of a form,
    •     PC Editor for entering texts and fields into output areas,
    •     Navigation tree for maintaining the form logic,
    •     Table Painter for creating templates and tables,
    •     Form check.
    To define text formats, use style maintenance (transaction SMARTSTYLES;see also Smart Styles [Seite 54]).
    Activities
    The SAP Smart Forms initial screen is the starting point for maintaining forms, styles [Seite 54], and text modules [Seite 54]:
    1.     Choose transction SMARTFORMS.
    The dialog window SAP Smart Forms: Request appears.
    2.     Select Form, Style, or Text module, depending on which object you want to create, display, or change.
    3.     Enter the name of the object.
    4.     Choose Create, Change, or Display.
    Depending on the radio button you selected (Form, Style, Text module), the system branches to the Form Builder, the style maintenance (transaction SMARTSTYLES ), or to the text module maintenance.
    Navigating in the SAP Form Builder
    The screen capture below shows the three different areas of the SAP Form Builder: The navigation tree (hierarchy structure of a Smart Form) on the left, the maintenance screen in the middle, and the Form Painter on the right.
    If you select a tree in the node, the system updates the maintenance screen and marks the relevant window in the Form Painter. You can also select a window in the Form Painter; the system them marks the relevant node in the tree.
    In the tree you determine the hierarchy of the form logic (see also Form Logic: Introduction [Seite 13]); in the Form Painter you determine the layout. If you, for example, move a window in the tree, this does not effect the layout of the Smart Form.
    Tree Navigation
    Selecting a Node
    To select a node in the tree, double-click it. The system updates the maintenance screen accordingly.
    Drag&Drop
    Use Drag&Drop to move (left mouse button) or copy (Ctrl + left mouse button) subtrees.
    Drag&Drop is a "move" operation, consisting of a "cut" and a "paste" operation with its own clipboard. If the node you are moving can be appended either on the same level as the target node or as a successor of the target node, the context menu offers both possbilities.
    Context Menu
    Use the right mouse button to display a sensitive context menu in the tree (that is, depending on the current node type). The following functions exist:
    •     Creating or deleting (only in change mode)
    Depending on the selected node type only valid node types appear.
    •     Clipboard operations (see below), such as cutting, copying to clipboard, pasting from clipboard (only in change mode)
    •     Expanding and collapsing a subtree
    Clipboard
    There are three clipboard operations:
    •     Copy
    Copies the selected node with all its successor nodes into the clipboard.
    •     Cut
    Copies the selected node with all its successor nodes into the clipboard and deletes the copied nodes from the tree.
    •     Paste
    Before pasting, the system checks whether and where you are allowed to append the root node of the clipboard contents.
    Maintenance Screen
    On the maintenance screen you can select different tab pages depending on the node type. For more information see Node Types: Overview [Seite 23].
    Form Painter
    You can suppress or display the Form Painter (choose Form Painter on/off). For more information on how to work with the Form Painter see Graphical Form Painter [Seite 17].
    Form Painter
    Use
    You use the Form Painter to design the layout of the pages of a Smart Form. You can include windows and graphics on a page, determine their positions and choose the window sizes.
    The Form Painter offers the following functions:
    •     Design area with ruler, cursor with help lines, and grid and main grid
    •     Display of the cursor position in the ruler, which you can suppress and set
    •     Two-level grid with engage function, which you can customize at will
    •     When creating, changing, and moving a window, the window size appears in the ruler.
    •     Detachable toolbar containing the most important functions
    •     Autoscrolling when moving windows; placing windows into the background
    •     Zoom factors you can set to any value and autozooming of the design area to the window size
    •     Sensitive context menu
    •     Placing a scanned graphic into the background of the design area (see also Printing Graphics [Seite 31])
    Activities
    To display or suppress the Form Painter choose Form Painter on/off.
    To make detailed settings in the Form Painter (for example, step size of the grid, zoom factors, and so on), choose Settings in its toolbar.
    PC Editor
    You use the PC Editor to enter and format texts and fields.
    Among others, the PC Editor offers the following functions:
    •     Enter, delete, select, cut, and copy texts (see also Entering Text in the PC Editor [Seite 27]).
    •     Assign paragraph and character formats (for a list of the available formats use the list boxes Paragraph formats and Character formats)
    •     Include, change, and delete fields (see also Using Fields in the Form [Seite 42])
    The PC Editor displays fields with a gray background.
    Table Painter
    Use
    You use the Table Painter to design templates and tables in a window (see also Displaying a Table with Static Data [Seite 33]).
    The Table Painter offers the following functions:
    •     Drawing lines and columns
    •     Inserting, cutting, copying, and deleting lines
    •     Deleting cells
    •     Changing cell size and moving cell separator lines
    •     Splitting cells
    •     Selecting table patterns
    Activities
    To display or suppress the Table Painter, choose Table Painter on/off on the Table tab on the maintenance screen of a table or template.
    The design area does not mirror the size of your window into which you include the table. Therefore, remember to check the size in the ruler.
    If you want to insert two tables one after the other, you must create two tables in the window node one after the other.
    To execute a function, mark a cell and choose the function in the context menu (right mouse button).
    To select a table pattern, select the Table tab in the node and choose Select pattern.
    To make detailed settings in the Table Painter (for example, step size of the grid, zoom factors, and so on), choose Settings in its toolbar.
    Style Builder
    The screen capture shows the Style Builder that you use to define Smart Styles. On the left, you see the style tree which consists of predetermined nodes (header data, folder for paragraph formats, folder for character formats). You can navigate between the nodes and create new nodes. On the right, you see the maintenance screen with its tab pages (here, for example, standard settings for the font in the selected color blue). At the bottom you see the preview of the selected font.
    For detailed information on how to create and maintain a Smart Style see Smart Styles [Seite 54].
    Field List and Error List
    Field List
    The field list displays the following data in a tree structure:
    •     all tables, structures, and fields passed via the form interface [Seite 38].
    •     system fields [Seite 43] and fields you defined in the global definitions [Seite 41]
    This allows you to check that you enter the correct field name when you include a field, and that the Smart Form actually knows the field.
    To display the field list, in the Form Builder choose Field list on/off.
    Error List
    When you check the Smart Form and any errors occur, the system displays a list of errors and warnings at the bottom of the maintenance screen. To find the error or warning in the tree, select the node in the second column. The system then goes to the corresponding position in the tree and you can correct the error.
    To check the entire Smart Form choose Check. If an error occurs the error list appears.
    For more information on testing and checking forms see Checking and Testing a Smart Form [Seite 58].
    Node Types: Overview
    When you create a Smart Form, the tree structure of the Form Painter already contains two root nodes:
    •     You use the successors of the Global Settings node to maintain Form attributes, the Form interface, and Global definitions.
    •     You use the successors of the Pages and windows node to create the pages of your form, position elements on these pages, and determine the sequence in which you want to process these elements.
    Apart from the two root nodes, each node has attributes. You can maintain these attributes on tabs on the right half of the screen. The attributes you can maintain on the tabs General Attributes, Output Options, and Conditions are the same for most of the node types (see: Shared Attributes of the Node Types [Seite 24]).
    Successors of Node Pages and windows
    As direct successors to root node Pages and windows you can create only page nodes. The tables below describe these page nodes and the other successors:
    Output areas
    Node type     Description     Possible direct successors
    Page [Seite 25]
    A page of the form. Direct successors of this node can be placed directly on the page.     Window, graphic, address
    Window [Seite 26]
    Output area on a page. There are main windows and subwindows.     All except window and page nodes
    Elementary nodes (without successors)
    Node type     Description
    Text [Seite 26]
    You use this node to print any texts (and table contents), except addresses.
    Graphic [Seite 31]
    You use this node to position graphics in the form. To include background graphics, use node type Page.
    Address [Seite 30]
    You use this node to include an address. The system reads the address data directly from the database tables and formats them for print output.
    Table output
    Node type     Description     Possible direct successors
    Template [Seite 33]
    Output of a table containing static data     All except window, page, table, and template nodes
    Table [Seite 46]
    Output of a table containing application data     As with template node
    Flow control
    Node type     Description     Possible direct successors
    Command [Seite 52]
    Executes special commands (next page, paragraph numbering, printer control)     (no successor)
    Loop [Seite 52]
    Processes successor node repeatedly.     All except window and page nodes
    Alternative [Seite 51]
    Branches depending on condition.     Direct successors are automatically the nodes TRUE and FALSE. The direct successors of these are all nodes except window and page nodes.
    Other nodes
    Node type     Description     Possible direct successors
    Folder [Seite 36]
    Combines successor nodes to logical groups     All except window and page nodes
    Complex section [Seite 60]
    Combines all attributes of the node types template, table, loop, folder     All except window and page nodes
    Program lines [Seite 61]
    Executes ABAP program code (for example, conversion routines).     (no successors)
    Shared Attributes of the Node Types
    The following tab pages are used in common by several node types:
    Tabs for general node attributes
    Name     Description
    General Attributes     Shows contents or description of the node
    Output Options     Contains attributes such as position, style, box and shading
    Conditions [Seite 51]
    Allows to display the node only if certain conditions are true (see also: Flow Control [Seite 50])
    The node types Table, Template, Loop, Folder, and Complex section share a different tab in the place of General Attributes.
    Output Options
    Except for the page nodes in the subtree Pages and windows, you can always use this tab to determine a box and shading for the respective node. Nodes with text output also have the attribute Style. You use this attribute to overwrite for the current subtree the style that was set in the form.
    Depending on where you insert a node, it can have additional output options (for example, if the predecessor is a template [Seite 33]).
    Basic Elements of a Form
    Creating Pages
    Use
    Each form consists of one or more pages. The first page in the tree structure is the start page (when you create a form, the start page already exists). With this page, processing of the form starts.
    When you call pages repeatedly or process pages again because the main window is not filled yet, a page node creates several print pages.
    See also: General Concepts on Form Printing [Seite 7].
    Procedure
    1.     Open the context menu for an existing page node and choose Create &#61614; Page.
    2.     Enter a unique name for the node and a description (for example, business terms).
    3.     Determine the format and the mode of the page counter [Seite 53] on the General Attributes tab. In the default setting, the next page is the page itself.
    4.     Determine the print attributes of the page on the Output Options tab (see F1 help).
    5.     Determine a background graphic for the entire page on the Background tab. For information on how to select the graphic see Printing Graphics [Seite 31]. If you do not determine an Output mode in the Output attributes box (in print preview only, on the printer as well), the system ignores the background graphic.
    If you select an output mode, the user can still choose Background graphic in the print preview to display or suppress it.
    Result
    You can now define the page contents. For each page, the Form Painter shows an individual layout. Whether the page is included into the printout depends on whether it is evaluated during form processing [Seite 62] (a page can be omitted even though it is part of the tree structure).
    Creating Windows
    Use
    Windows are output areas for all output data. You can set the size and position of a window graphically in the Form Painter. There are main windows and subwindows [Seite 8]. The most important difference is that the output in a main window can cover several pages.
    After you created a form, a main window already exists on the first page.
    Prerequisites
    A page [Seite 25] exists on which you want to create a window.
    Procedure
    6.     Open the context menu for an existing page node and choose Create &#61614; Window.
    If you create the window in the Form Painter using the context menu, you can use the mouse to position it immediately.
    7.     Enter a unique name for the node and a description (for example, booked flights).
    8.     On the General Attributes tab indicate whether the window is a Main window. If you want to create a subwindow, leave the checkbox empty.
    For each page you can indicate only one main window.
    9.     The Position and Size values in the Output options box correspond to the position in the Form Painter. If you want to, maintain other attributes [Seite 24].
    Result
    You can see the window in the Form Painter and in the tree structure. You can always change the specification of the main window or subwindow.
    Positioning Texts on the Form
    Use
    You display all texts in the form using text nodes. The only exception are addresses [Seite 30], which use their own node.
    Integration
    The predecessor node [Seite 14] of the text node determines its use:
    Examples for using text nodes
    Predecessor node     Used to
    Subwindow     Exactly position text on one or more pages
    Main window     Display text in relation to other nodes in the main window; it may cover several pages
    Template     Display texts for table cells of a static table [Seite 33]
    Table     Display table contents
    Header and footer [Seite 49]
    Display column headings and grand totals in tables
    Event node [Seite 48]
    Display subtotals in a table
    Features
    There are the following text types:
    •     Text element: to enter new text in the PC Editor [Seite 27]
    •     Text module: to include a text module [Seite 28]
    •     Include text: to include an existing SAPscript text [Seite 29]
    Positioning the Text
    The position of the text depends on the direct predecessor node (for example, you can assign text of a table cell) as well as on the processing sequence in the tree structure. In addition, you determine output of a text node in relation to the preceding node on the same level [Seite 14]. You can append the text directly to the output of that node or start it in a new paragraph or a new line (select via radiobutton).
    Entering Texts in the PC Editor
    Use
    You use the PC Editor [Seite 19] to enter new text. The position of this text on the form is determined by the predecessor node.
    To include data from the form interface (data from application tables) or system data (date, time) into the text, use system fields or user-defined fields, respectively, in the text (see Using Parameters in the Form [Seite 37]). When processing the form, Smart Forms replace these fields with the corresponding values.
    Procedure
    1.     To create a text node, call the context menu for that node in the tree structure that should receive the text. Then choose Create &#61614; Text.
    2.     Enter a unique name for the node and a node description (for example, letter).
    3.     On the General Attributes tab choose Text element as text type.
    Since you edit a text element, an included text, or a text module exclusively using the text node, the system stores only information on the selected type. When you change the text type, the system therefore asks for your confirmation.
    4.     Enter your text in the PC Editor
    &#61485;     either directly on the tab if you use the inplace version of the PC Editor
    &#61485;     or choose Text editor to go to the fullscreen mode of the PC Editor. If, after entering the text, you use the green arrow (F3) to leave the fullscreen editor, the system transfers the text into the inplace version.
    5.     In the Text node box choose whether you want the text to start with a new paragraph or only in a new line. You can also choose to append the text directly to the end of the current paragraph.
    6.     If desired, choose the Output Options [Seite 24] tab to maintain the style or box and shading of the text.
    Result
    The system displays the node in the tree structure, including its name and description.
    Including Text Modules
    Use
    You use the text type Text module of the text node [Seite 26] to refer to an existing text module  [Seite 54]in the system. This allows you to easily use texts from text modules in several forms. In addition, it is not necessary to load the entire form description to maintain these texts.
    You can use text modules in two ways:
    •     Refer to the text module. The text then appears read-only in the PC editor and is included when you print the form.
    •     Copy the text module. The system then copies the text of the module and automatically converts the text node into an editable text element.
    Text modules can be used cross-client and are connected to the transport and translation systems.
    Prerequisites
    The text module you want to include must exist in the system. To create a text module use the SAP Smart Forms initial screen [Seite 15].
    Procedure
    5.     To create a text node, call the context menu for that node in the tree structure that shall contain the text and choose Create &#61614; Text.
    6.     Enter a unique name for the node and a description (for example, business terms).
    7.     On the General attributes tab select the text type Text module.
    Since you edit a text element, an included text, or a text module exclusively via the text node, the system stores only information on the selected type. When you change the text type, the system therefore asks for your confirmation.
    8.     Enter the name of the text module in the Text name field. Or click on the black arrow and enter the name of a field to be evaluated dynamically [Seite 37].
    9.     If you want to change the text of the text module for the current form, choose Copy. The Form Builder changes the text type to Text element and copies the text of the module into the PC Editor, where you can edit it. In this case, the original text module remains unchanged.
    10.     Use the checkbox Always copy style from text to determine that the style of the text module is of higher priority than that of the text node or any style inherited from a predecessor. This is important if you specified the name of a field in step 4 (see F1 help).
    11.     If required, use the Output options [Seite 24] tab to maintain attributes for style, box and shading of the text.
    Result
    The system displays the node including name and description in the tree structure. It includes the relevant text itself in the moment the form is processed. If you refer to a text module, it appears in the PC Editor in read-only mode, if you copy it you can edit it.
    Including SAPscript Texts
    Use
    You use the text type Include text of the text node to refer to a SAPscript text that already exists in the system. To identify the text, you need the text name, the text object, the text ID, and the language. Thus, you can easily use the texts in several forms. In addition, you need not load the entire form description [Seite 12] to maintain these texts.
    This text type corresponds to the SAPscript statement INCLUDE. However, Smart Forms do not allow any control statements in include texts. When processing the form, they are simply ignored.
    To administer application-specific form texts, applications use transaction SE75 to define their own text objects with subordinate text IDs. Use text object TEXT with text ID ST to enter general standard texts. To maintain them, use the standard text editor (transaction SO10).
    If there is no need for you to use old SAPscript texts, you better use text modules [Seite 28]. They can be used cross-client and are connected to the transport and translation systems.
    Procedure
    1.     To create a text node, call the context menu for that node in the tree structure that shall receive the text and choose Create &#61614; Text.
    2.     Enter a unique name for the node and a node description (for example, letter).
    3.     On the General Attributes tab choose Include text as text type.
    Since you edit a text element, an included text, or a text module exclusively via the text node, the system stores only information on the selected type. When you change the text type, the system therefore asks for your confirmation.
    4.     In the Text key box, identify the include text.
    &#61485;     To identify individual text objects, use the search help in this field.
    &#61485;     The search help of the Text name field allows you include the attributes of SAPscript texts into the search.
    7.     If required, use the Paragraph formats box to format the include text:
    &#61485;     The style assigned to the text node contains a format for the standard paragraph ('*'). If you enter a paragraph format in the Standard paragraph field, this format overwrites the style format for all standard paragraphs in the include text that use this paragraph format.
    &#61485;     Use the First paragraph field to set a paragraph format for the first paragraph of the include text. This format also overwrites the format set in the style. If you set the First paragraph field but leave the Standard paragraph field empty, the system uses the format set in the First paragraph field for any standard paragraphs in the include text.
    6.     In the Text node box choose whether you want the text to start in a new paragraph, in a new line, or directly at the end of the current paragraph.
    7.     If desired, choose the Output Options [Seite 24] tab to maintain the style or box and shading of the text.
    Result
    The system displays the node in the tree structure, including its name and description. The included text is included only at the moment the form is processed.
    Inserting Addresses
    Use
    In many applications, addresses are administered using the Central Address Administration [Extern]. Depending on how the address is used, the application uses a particular address type [Extern]. The addresses are stored in the database tables of the central address administration and identified by the application via a number.
    You use the address node to insert an address into the form. This guarantees that the address is formatted according to the postal rules of the sender country.
    Prerequisites
    Your application must administer addresses using the central address administration. Otherwise you must use the text node [Seite 26] to insert your addresses.
    Procedure
    1.     To create an address node, call the context menu for that node in the tree structure that you want to contain the text and choose Create &#61614; Text.
    Create the address node as direct successor of the page node or use the context menu in the layout of the Form Painter. You can then position the address anywhere on the page.
    2.     Enter a unique name for the node and a description (for example, customer address).
    3.     Determine the address type on the General attributes tab.
    For a description of how to determine the address type dynamically and how to use fields instead of fixed values, see Using Parameters in the Form [Seite 37].
    4.     For organization addresses you must specify only an address number. For any other address types, you must specify a person number and an address number. To do this, use the search help.
    5.     In the box Additional address specifications you can maintain other attributes to specify how you want to display the address:
    &#61485;     Use field Output starts with paragraph to set the paragraph format of the style that you want to use to display the address.
    &#61485;     If the number of lines you specify in the field Number of lines to be used is smaller than the number of lines required to display the address, the central address administration suppresses lines of the address.
    &#61485;     As default, the system uses as sender country the country that was specified when creating the address. You can use the parameter Sender country to overwrite this setting.
    &#61485;     For addresses that have a P.O. box as well as a street address, use the other fields in the box to determine which of these addresses to display.
    6.     If desired, you can use the Output Options [Seite 24] tab to maintain attributes for style, box, and shading of the text. In addition, you can set values for position and size of the output area (instead of in the Form Painter).
    Result
    The system displays the node including name and description in the tree structure. If you insert the address as direct successor of a page or by using the Form Painter, the system displays an extra output area for the address. The address itself is inserted only at the moment the form is processed. You cannot view it in the Form Builder.
    Printing Graphics
    Use
    You use the graphic node to display graphics, such as a company logo, on the form. For performance reasons, make sure that the graphics are held in the printer memory. SAP Smart Forms support this method, provided that:
    •     The printer can be controlled accordingly.
    •     There is enough memory space on the printer.
    •     You activated this property in transaction SE78 (see below).
    In this case, the system sends the graphics to the printer only once during one print job.
    To include background graphics, use the Background graphic tab of a page node.
    Prerequisites
    You use the SAPscript Graphic Administration (transaction SE78) to import graphics into the SAP-System:
    1.     Double-click on a graphic format in the tree structure in the forder Document server &#61614; GRAPHICS General graphics.
    2.     Choose Graphic &#61614; import.
    The transaction imports the graphic and stores it on the Business Document Server (BDS). Now you can display it on a form.
    See also: Graphic Administration [Seite 65]
    Procedure
    1.     To create a graphic node, call the context menu for that node in the tree structure that you want to contain the graphic and choose Create &#61614; Graphic.
    Create the graphic node as direct successor of the page node or use the context menu in the layout of the Form Painter. You can then position the graphic anywhere on the page.
    In the Form Painter the system displays a small box for the newly created node.
    2.     Enter a unique name for the node and a description (for example, company logo).
    3.     On the General Attributes tab determine whether you want to include a colored graphic or a graphic in black and white.
    4.     Use the fields Object, ID, and Name to identify the graphic. Use F4 help of the Name field to copy the values of these fields. If you copy them with ENTER, the system displays the graphic in the Form Painter.
    The box for the graphic in the Form Painter also contains the name of the graphic node, which in part overlays the graphic.
    5.     In the Technical Attributes box determine the graphic resolution according to what the printer supprts. Small resolutions increase the size of the graphic on the form, higher resolutions reduce the size.
    6.     For graphic nodes that are displayed in a window, there is a box Horizontal position in addition to the general output options [Seite 24]. The parameters Reference point and Alignment determine the horizontal position in the window, while the vertical position is determined by the previous output in the window.
    At present, you cannot overlay graphics with text. However, if you use a template node [Seite 33], you can display graphics and text side by side.
    Result
    The system displays the node with name and description in the tree structure. If you insert a graphic as direct successor of a page or if you used the Form Painter, the system displays the graphic. Graphics in windows are inserted only when the form is processed. You can therefore not see them in the Form Builder. In addition, the system automatically dispalys the graphic on the next page if there is not enough space left on the current page.
    Displaying a Static Table
    Use
    Use node type Template to display a table whose layout and size (number of lines and columns) is determined before the runtime of the print program.
    To create a template, define a table layout to determine the cell structure for each line. The cells are used to display the contents of the successor nodes of the template node. This allows you to position text and a graphic side by side (see Displaying Graphics in Templates [Seite 36]).
    The template node is also suited for label printing.
    Integration
    You can use system fields or your own fields &#61630; for example, to display the current date &#61630; in table cells (see also Using Parameters in the Form [Seite 37]).
    To display application data, use the table node. For this node type the number of table lines to be displayed is not known before the form is actually printed (the number depends on the volume of application data selected in the data retrieval program [Seite 38]).
    Prerequisites
    You can create a template node only as a successor to a window node. If you want to display the template in a particular area of the page, create a subwindow for it. Otherwise, use the main window.
    Features
    The node type displays a table layout [Seite 34]. You can either enter the table layout directly or use the Table Painter to define it.
    To set other attributes, use the attributes the node types share [Seite 24].
    Activities
    To use a template, you must:
    1.     Define the table layout [Seite 34].
    2.     Display contents in the table cells [Seite 35].
    Defining the Table Layout
    Use
    You use the table layout to determine:
    •     The number of lines and cells
    •     The height of each line
    •     The width of each cell
    •     The alignment of the table in the window
    •     Whether and where to display separator lines or frames
    Procedure
    Create a template node and maintain the attributes Width, Horizontal alignment, and Vertical alignment (See F1 help).
    Use the table control on the Template tab to define the layout of the lines. Each line of the template must have a definition. You can use one line in the table control to define either the layout of one template line or a common layout for several template lines:
    •     Use the columns From and To to specify the lines of your template, for which the definition applies. The numbering starts with 1. The intervals in the line definition may neither overlap nor leave gaps.
    •     The Height you specify applies for all cells of this line. Specify a Width for each cell you want to display. The sum of the width values must amount to the specified Width of the template.
    •     You can reuse the Name of the template line for other lines of the same template. Enter it in the Reference column of the desired lines. The system then copies the values you specified for the line height and the individual cell widths.
    Use the Pattern box to select the desired table pattern.
    Example
    You define the following lines in the table control (in the example without measurement units):
    Name     From     To     Reference     Height     1.     2.     3
    Line1_2     1     2          1     1     2     3
    Line3     3     3          2     2     2     2
    Line4     4     4     Line1_2     1     1     2     3
    You use the Pattern box to specify that all cells are separated by visible lines and that the template is framed.
    Result
    On the form, the template may look like this:
    Displaying Contents in Cells
    Use
    The template node defines the table layout [Seite 34]. The successor nodes of the template node determine the data to be displayed in the table cells.
    Prerequisites
    You already created a template node as successor of a window node and defined the table layout.
    Procedure
    1.     Use the context menu of the template node to create successor nodes.
    For clarity reasons create one folder node [Seite 36] for each line. The folder node is an outline node that you can use to combine related nodes. For folder nodes, you need not fill in the input fields in the Output structure box (see next step).
    2.     The Output options tabs of the inserted nodes now contain an additional box Output structure with the fields Line and Column. Assign each node to the cell in which you want the output to appear.
    You can assign several nodes to one cell. The output sequence within the cell is determined by the sequence of the nodes in the tree.
    Result
    The system displays the contents in the print preview or prints them, respectively.

  • I want to know what exactly the diff between script and smart form?

    wherther script is version dependent?langauge dependent?
    where can we  maintain script styles?

    Hi,
    Script is Language Dependent & Client Dependent.
    U can create styles ie., paragraph format , character format using transaction <b>SE72</b>.
    <b>DIFFERENCE BETWEEN SMARTFORMS AND SAPSCRIPTS ARE:</b>
    1).Smartforms are client independent and Sapscripts are client dependent.
    2).Multiple page formats are possible in smartforms which is not the case in SAPScripts
    3).It is possible to have a smartform without a main window .
    4).Labels cannot be created in smartforms.
    5).Routines can be written in smartforms tool.
    6).Smartforms generates a function module when activated.
    Multiple page formats are possible in SmartForms which is not the case in SAPScripts
    It is possible to have a SmartForm without a main window.
    Labels cannot be created in SmartForms.
    Routines can be written in SmartForms tool.
    SmartForms generates a function module when activated.
    Regards,
    Padmam.

  • Smartforms & Scripts

    Hai can anybody tell me answers for these Questions......
    1.What is the difference between a script & a report ?
    2.What are the components/elements in sap script ?
    3.Can you create a script with out a main window ?
    4.How many main windows can be created for a script ?
    5.How can we use tables in sap scripts?
    6.How to print a logo in a sap script?
    7.When we need to modify standard scripts(eg:medruck) given
    by sap?
    8.What is the use of transaction code NACE in sap scripts?
    9.what is the table name that will contain all the script form
    names and print program names?
    10.Can you assign your own form to a standard print program?
    how?
    11.What is the use of PROTECT & ENDPROTECT?
    12.How to add extra functionality to a standard print program with
    out touching the print program?
    13.what is sub routine pool in sap script? when it is used?
    14.How to read text in sapscripts?
    15.What is the transaction code for logo uploading?
    16.what is the difference between paragraph & character format?
    17.How to use a sapscript for multiple languages ? (english,
    germany etc)
    18.How to download/upload sapscripts from & to your PC ?
    19.What is the difference between scripts & smart forms?
    20.What is the standard program used for uploading the logo to
    script?
    21.How can you send forms from one client to other?
    22.what does open_form, write_form, close_form do?
    23.How to convert a sapscript to smart form?
    24.How to send a smartform result through mail?
    25.how to select desired paper size in sapscript?

    For all the details abt smartforms, have a look at below link. It will answer all the questions related to smartforms.
    http://sap.ionelburlacu.ro/sap0/sapsf001.htm
    <b>Difference with SMARTFORMS and SapScript</b>
    The Following are the differences :-
    a) Multiple page formats are possible in smartforms which is not the case in SAPScripts
    b) It is possible to have a smartform without a main window .
    c) Labels cannot be created in smartforms.
    d) Routines can be written in smartforms tool.
    e) Smartforms generates a function module when activated.
    <b>Upload/Download SAP Scripts To/From PC</b>
    If you wish to keep a copy of your layout sets in your own hardisk.  You can run this SAP program.  You can keep it as a backup copy and upload it back whenever you need it again.
    <b>RSTXSCRP - SAP Scripts Export/Import</b>
    Also have a look at below link. It has many answers.
    http://www.sap-img.com/sapscripts/faq-for-sap-scripts.htm
    I hope it helps.
    Best Regards,
    Vibha
    *Please mark all the helpful answers

  • Urgent:Why Script is cliend dependant and smartform is not client dependant

    Hi all,
    Can any one pls tell me why script is client dependent and smartform is not client dependant.
    <b>Please give some real time examples in brief</b>
    regards
    tapu

    Hi
    DIFFERENCE BETWEEN SMARTFORMS AND SAPSCRIPTS ARE:
    1. script is client dependent one while smartform is client independent.
    2. In scripts we have to write print program while in smart forms it is not necessary.
    3. In scripts we can print background logo while in smartforms we cant print background logo
    4. In scripts we have 99 main windows while in smartforms we have only 1 main window.
    5. In scripts we should write paragraph format otherwise we cant execute program while in smartforms no need to create paragraph formats .
    6. In scripts we can print the text in only two character formats.
    while in smartforms we can do with more.
    7. In scripts we dont have line types while in smartforms we have linetypes.
    8.Multiple page formats are possible in smartforms which is not the case in SAPScripts
    9.It is possible to have a smartform without a main window .
    10.Labels cannot be created in smartforms.
    11.Routines can be written in smartforms tool.
    12.Smartforms generates a function module when activated.
    SAPscript technology is based on a mainframe product from the 1980s, while Smart Forms have only been around since (roughly) 2001. With that sort of time gap, there are bound to be significant differences between the two tools. Client dependence is a fundamental one. Although SAPscript has had some incremental improvements over time, its forms have always been -- under the hood -- relatively ...
    also refer
    difference between smartforms and scripts
    Diff betwen Scripts & smartforms
    advantages of smartforms over scripts
    Whenever a smartform is created, a funciton module gets generated. So, we can access the smartform in different clients. But in case of scripts, it is not so.. So, scripts are client dependent.
    Smart Forms are implemented using the Function Module SSF*, and all the logic lies in the FM. Function Modules are client independent objects, so Smart forms are also client independent
    SAP Scripts are the Layout Forms that you design and there are aviable in the client in which you have created them, for making them available you have to copy across the clients.
    Because, Sapscripts are saved in ITF format as text in client dependant tables STXH and STXL. smartforms are not saved in client dependant tables and visible across clients.
    SAPscript technology is based on a mainframe product from the 1980s, while Smart Forms have only been around since (roughly) 2001. With that sort of time gap, there are bound to be significant differences between the two tools. As you have noted correctly, client dependence is a fundamental one.
    Although SAPscript has had some incremental improvements over time, its forms have always been -- under the hood -- relatively passive objects, with minimal embedded logic. These forms were designed to be driven and controlled by ABAP programs, much in the way ABAP programs read in database tables to produce reports; if you ever download a SAPscript form (e.g., via utility program RSTXSCRP), and look at the portable text file it produces you'll see what I mean. Many text objects (e.g., invoice header texts) are bound directly to documents which are client-dependent, so it makes sense for these text objects to also be client-dependent. From a complexity standpoint, SAPscript forms are close enough to these text objects where I can see how it made sense at the time to make them client-dependent too.
    Conversely, a Smart Form is significantly more robust and complex. For instance, it can contain program nodes and nested tables with patterns. When a Smart Form is compiled, it generates an ABAP function module – and these are always client-independent. This is appropriate, given that this form has more in common with an ABAP program than its predecessor. For instance, when a print program calls a Smart Form, the form itself takes over to produce output, without any further direction from the print program. In fact, the join is so seamless that I often find myself using a Smart Form's Initialization section for logic to handle any data gathering not handled by the print program. I would never even think to attempt this with SAPscript.
    I suspect several factors figured into SAP's decision to make Smart Forms client-independent, including customer feedback. There are significant advantages to client-independence. For instance, a change made in one development client happens immediately across all development clients. Among other things, this means we don't have to waste time figuring which client contains the most recent version -- they all do! In addition, transporting Smart Forms is easier, since we can safely bundle them together in the same transport as their client-independent print programs (no worry about mixing client-dependent and independent objects).
    <b>Reward points for useful Answers</b>
    Regards
    Anji

  • Create Smartform in Russian

    Hello
    We have to create a russian smartform.
    However, when we enter the text (e.g.) Наименование, smartform converts them automatically to #####.
    This happens already in the SMARTFORMS - not at printing.
    We tried both editors (graphical and normal), but no difference.
    In SE71 (SapScript) and SE63 (Translating the Smartform) it runs perfect.
    Also when we include an "Include-Text" it runs, but entering the text directly in "Text Element" always fails.
    Thx for help in advance
    Christian

    I think the problem is the graphical (newer) editor in smartforms.
    Because when I enter the text in the old editor (in smartform), it is displayed corretly.
    But after that I always have to switch back (with F3) to the newer editor.
    And I think, the newer editor don't understands the russian letters.
    The same effect is in SE71.
    I've entered a russian text in the old editor and it is displayed correctly.
    When I change to the newer one, the russian letters are displayed as ####.
    Any ideas for the editor problem?
    Or is there an another way to maintain the text in smartforms?
    (except the usage of include-text)
    Thx

  • Smartform questions

    Please provide details and examples on the following two questions:
    1. How can we create a smartform without a main window? Any example??
    2. How can we debug any smartform? best practices??
    Tx
    Good answers r rewarded.

    In the Smartform, create a Code Node and within the Code Node you can hardcode a normal abap
    Break Point.
    to Debug SF:
    For debugging -
    1. Write BREAK POINT in the code window.
    2. Put a break point on the call function in the driver program
    3. Put a break point in the generated Function module.
    OR
    1) DEBUG Smartform:
    1) One way to debug smartform is to debug the Function Module of that smartforms.
    If you want to debug particular smartform node that the solution would be,
    insert a "Program Line" just above the node you want to debug and this program line write a normal abap breakpoint.
    So whenever you call the smartforms, it will stop at this breakpoint and you can debug onwards.
    2) SFTRACE can be used for debugging SMARTFORMS.
    OR
    Four ways you can debugging.....
    1.place SFTRACE inplace where we enter T_CODE and press ENTER.
    after that press F8.
    2 ./H
    3 /SH
    4.after generating the function module there is a button DEBUGGING
    These are Help links
    http://help.sap.com/saphelp_erp2005/helpdata/en/c4/8d4a4273bb3830e10000000a155106/frameset.htm
    See the Link below:
    http://help.sap.com/saphelp_47x200/helpdata/en/df/ef7f380c2f2e3ce10000009b38f8cf/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/60/6fc10c6748479392101e09c9e8d33a/frameset.htm
    http://help.sap.com/saphelp_erp2005/helpdata/en/42/c1151c55b33119e10000000a1553f7/frameset.htm
    Go through the following Links, here u can find example with step
    by step.
    http://smoschid.tripod.com/How_to_do_things_in_SAP/How_To_Build_SMARTFORMS/How_To_Build_SMARTFORMS.html
    Check these step-by-step links
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/ccab6730-0501-0010-ee84-de050a6cc287
    https://sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/8fd773b3-0301-0010-eabe-82149bcc292e
    https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.docs/library/uuid/3c5d9ae3-0501-0010-0090-bdfb2d458985
    Check these links also.
    http://www.sap-basis-abap.com/sapsf001.htm
    http://www.sap-press.com/downloads/h955_preview.pdf
    http://www.ossincorp.com/Black_Box/Black_Box_2.htm
    http://www.sap-img.com/smartforms/sap-smart-forms.htm
    http://www.sap-img.com/smartforms/smartform-tutorial.htm
    http://www.sapgenie.com/abap/smartforms.htm
    for Smartforms material
    http://www.sap-basis-abap.com/sapsf001.htm
    http://www.sap-press.com/downloads/h955_preview.pdf
    http://www.ossincorp.com/Black_Box/Black_Box_2.htm
    http://www.sap-img.com/smartforms/sap-smart-forms.htm
    http://www.sap-img.com/smartforms/smartform-tutorial.htm
    http://www.sapgenie.com/abap/smartforms.htm
    How to trace smartform
    http://help.sap.com/saphelp_47x200/helpdata/en/49/c3d8a4a05b11d5b6ef006094192fe3/frameset.htm
    http://www.help.sap.com/bp_presmartformsv1500/DOCU/OVIEW_EN.PDF
    http://www.sap-img.com/smartforms/smart-006.htm
    http://www.sap-img.com/smartforms/smartforms-faq-part-two.htm
    Re: Need FAQ's
    http://www.sap-img.com/smartforms/smart-006.htm
    http://www.sap-img.com/smartforms/smartforms-faq-part-two.htm
    Re: Need FAQ's
    scripts
    http://www.sappoint.com/abap/ssintro.pdf
    http://www.sappoint.com/abap/sscript.pdf
    http://www.sappoint.com/abap/sscript.pdf
    http://www.sappoint.com/abap/lsetssap.pdf
    http://www.sappoint.com/abap/sscrtpex1.pdf
    http://www.sap-img.com/sapscripts.htm
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVSCRPROG/BCSRVSCRPROG.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVSCRRDI/BCSRVSCRRDI.pdf
    http://help.sap.com/printdocu/core/Print46c/en/data/pdf/BCSRVSCREDIT/BCSRVSCREDIT.pdf
    How to create a New smartfrom, it is having step by step procedure
    http://sap.niraj.tripod.com/id67.html
    step by step good ex link is....
    http://smoschid.tripod.com/How_to_do_things_in_SAP/How_To_Build_SMARTFORMS/How_To_Build_SMARTFORMS.html
    Here is the procedure
    1. Create a new smartforms
    Transaction code SMARTFORMS
    Create new smartforms call ZSMART
    2. Define looping process for internal table
    Pages and windows
    First Page -> Header Window (Cursor at First Page then click Edit -> Node -> Create)
    Here, you can specify your title and page numbering
    &SFSY-PAGE& (Page 1) of &SFSY-FORMPAGES(Z4.0)& (Total Page)
    Main windows -> TABLE -> DATA
    In the Loop section, tick Internal table and fill in
    ITAB1 (table in ABAP SMARTFORM calling function) INTO ITAB2
    3. Define table in smartforms
    Global settings :
    Form interface
    Variable name Type assignment Reference type
    ITAB1 TYPE Table Structure
    Global definitions
    Variable name Type assignment Reference type
    ITAB2 TYPE Table Structure
    4. To display the data in the form
    Make used of the Table Painter and declare the Line Type in Tabstrips Table
    e.g. HD_GEN for printing header details,
    IT_GEN for printing data details.
    You have to specify the Line Type in your Text elements in the Tabstrips Output options.
    Tick the New Line and specify the Line Type for outputting the data.
    Declare your output fields in Text elements
    Tabstrips - Output Options
    For different fonts use this Style : IDWTCERTSTYLE
    For Quantity or Amout you can used this variable &GS_ITAB-AMOUNT(12.2)&
    5. Calling SMARTFORMS from your ABAP program
    REPORT ZSMARTFORM.
    Calling SMARTFORMS from your ABAP program.
    Collecting all the table data in your program, and pass once to SMARTFORMS
    SMARTFORMS
    Declare your table type in :-
    Global Settings -> Form Interface
    Global Definintions -> Global Data
    Main Window -> Table -> DATA
    Written by : SAP Hints and Tips on Configuration and ABAP/4 Programming
    http://sapr3.tripod.com
    TABLES: MKPF.
    DATA: FM_NAME TYPE RS38L_FNAM.
    DATA: BEGIN OF INT_MKPF OCCURS 0.
    INCLUDE STRUCTURE MKPF.
    DATA: END OF INT_MKPF.
    SELECT-OPTIONS S_MBLNR FOR MKPF-MBLNR MEMORY ID 001.
    SELECT * FROM MKPF WHERE MBLNR IN S_MBLNR.
    MOVE-CORRESPONDING MKPF TO INT_MKPF.
    APPEND INT_MKPF.
    ENDSELECT.
    At the end of your program.
    Passing data to SMARTFORMS
    call function 'SSF_FUNCTION_MODULE_NAME'
    exporting
    formname = 'ZSMARTFORM'
    VARIANT = ' '
    DIRECT_CALL = ' '
    IMPORTING
    FM_NAME = FM_NAME
    EXCEPTIONS
    NO_FORM = 1
    NO_FUNCTION_MODULE = 2
    OTHERS = 3.
    if sy-subrc <> 0.
    WRITE: / 'ERROR 1'.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    endif.
    call function FM_NAME
    EXPORTING
    ARCHIVE_INDEX =
    ARCHIVE_INDEX_TAB =
    ARCHIVE_PARAMETERS =
    CONTROL_PARAMETERS =
    MAIL_APPL_OBJ =
    MAIL_RECIPIENT =
    MAIL_SENDER =
    OUTPUT_OPTIONS =
    USER_SETTINGS = 'X'
    IMPORTING
    DOCUMENT_OUTPUT_INFO =
    JOB_OUTPUT_INFO =
    JOB_OUTPUT_OPTIONS =
    TABLES
    GS_MKPF = INT_MKPF
    EXCEPTIONS
    FORMATTING_ERROR = 1
    INTERNAL_ERROR = 2
    SEND_ERROR = 3
    USER_CANCELED = 4
    OTHERS = 5.
    if sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    endif.
    for Smartforms material
    http://www.sap-basis-abap.com/sapsf001.htm
    http://www.sap-press.com/downloads/h955_preview.pdf
    http://www.ossincorp.com/Black_Box/Black_Box_2.htm
    http://www.sap-img.com/smartforms/sap-smart-forms.htm
    http://www.sap-img.com/smartforms/smartform-tutorial.htm
    http://www.sapgenie.com/abap/smartforms.htm
    How to trace smartform
    http://help.sap.com/saphelp_47x200/helpdata/en/49/c3d8a4a05b11d5b6ef006094192fe3/frameset.htm
    http://www.help.sap.com/bp_presmartformsv1500/DOCU/OVIEW_EN.PDF
    http://www.sap-img.com/smartforms/smart-006.htm
    http://www.sap-img.com/smartforms/smartforms-faq-part-two.htm
    Re: Need FAQ's
    check most imp link
    http://www.sapbrain.com/ARTICLES/TECHNICAL/SMARTFORMS/smartforms.html
    step by step good ex link is....
    http://smoschid.tripod.com/How_to_do_things_in_SAP/How_To_Build_SMARTFORMS/How_To_Build_SMARTFORMS.html
    Subtotals - Check the link...
    Re: Subtotal with Table Node in smartforms
    SCRIPTS
    SAPScripts
    SAPScripts
    Link for SAP Scripts (step by step procedure)
    http://smoschid.tripod.com/How_to_do_things_in_SAP/How_To_Create_A_SAPSCRIPT_Form/How_to_Create_SAPSCRIPT.html
    http://esnips.com/doc/1ff9f8e8-0a4c-42a7-8819-6e3ff9e7ab44/sapscripts.pdf
    http://esnips.com/doc/1e487f0c-8009-4ae1-9f9c-c07bd953dbfa/script-command.pdf
    http://esnips.com/doc/64d4eccb-e09b-48e1-9be9-e2818d73f074/faqss.pdf
    http://esnips.com/doc/cb7e39b4-3161-437f-bfc6-21e6a50e1b39/sscript.pdf
    http://esnips.com/doc/fced4d36-ba52-4df9-ab35-b3d194830bbf/symbols-in-scripts.pdf
    http://esnips.com/doc/b57e8989-ccf0-40d0-8992-8183be831030/sapscript-how-to-calculate-totals-and-subtotals.htm
    SAP SCRIPT FIELDS
    http://help.sap.com/saphelp_erp2005vp/helpdata/en/d1/8033ea454211d189710000e8322d00/content.htm
    scripts easy material
    http://www.allsaplinks.com/sap_script_made_easy.html
    DIFFERENCE BETWEEN SMARTFORMS AND SAPSCRIPTS ARE:
    1. script is client dependent one while smartform is client independent.
    2. In scripts we have to write print program while in smart forms it is not necessary.
    3. In scripts we can print background logo while in smartforms we cant print background logo
    4. In scripts we have 99 main windows while in smartforms we have only 1 main window.
    5. In scripts we should write paragraph format otherwise we cant execute program while in smartforms no need to create paragraph formats .
    6. In scripts we can print the text in only two character formats.
    while in smartforms we can do with more.
    7. In scripts we dont have line types while in smartforms we have linetypes.
    8.Multiple page formats are possible in smartforms which is not the case in SAPScripts
    9.It is possible to have a smartform without a main window .
    10.Labels cannot be created in smartforms.
    11.Routines can be written in smartforms tool.
    12.Smartforms generates a function module when activated.
    SAPscript technology is based on a mainframe product from the 1980s, while Smart Forms have only been around since (roughly) 2001. With that sort of time gap, there are bound to be significant differences between the two tools. Client dependence is a fundamental one. Although SAPscript has had some incremental improvements over time, its forms have always been -- under the hood -- relatively ...
    also refer
    difference between smartforms and scripts
    Diff betwen Scripts & smartforms
    advantages of smartforms over scripts
    Whenever a smartform is created, a funciton module gets generated. So, we can access the smartform in different clients. But in case of scripts, it is not so.. So, scripts are client dependent.
    Smart Forms are implemented using the Function Module SSF*, and all the logic lies in the FM. Function Modules are client independent objects, so Smart forms are also client independent
    SAP Scripts are the Layout Forms that you design and there are aviable in the client in which you have created them, for making them available you have to copy across the clients.
    Because, Sapscripts are saved in ITF format as text in client dependant tables STXH and STXL. smartforms are not saved in client dependant tables and visible across clients.
    SAPscript technology is based on a mainframe product from the 1980s, while Smart Forms have only been around since (roughly) 2001. With that sort of time gap, there are bound to be significant differences between the two tools. As you have noted correctly, client dependence is a fundamental one.
    Although SAPscript has had some incremental improvements over time, its forms have always been -- under the hood -- relatively passive objects, with minimal embedded logic. These forms were designed to be driven and controlled by ABAP programs, much in the way ABAP programs read in database tables to produce reports; if you ever download a SAPscript form (e.g., via utility program RSTXSCRP), and look at the portable text file it produces you'll see what I mean. Many text objects (e.g., invoice header texts) are bound directly to documents which are client-dependent, so it makes sense for these text objects to also be client-dependent. From a complexity standpoint, SAPscript forms are close enough to these text objects where I can see how it made sense at the time to make them client-dependent too.
    Conversely, a Smart Form is significantly more robust and complex. For instance, it can contain program nodes and nested tables with patterns. When a Smart Form is compiled, it generates an ABAP function module – and these are always client-independent. This is appropriate, given that this form has more in common with an ABAP program than its predecessor. For instance, when a print program calls a Smart Form, the form itself takes over to produce output, without any further direction from the print program. In fact, the join is so seamless that I often find myself using a Smart Form's Initialization section for logic to handle any data gathering not handled by the print program. I would never even think to attempt this with SAPscript.
    I suspect several factors figured into SAP's decision to make Smart Forms client-independent, including customer feedback. There are significant advantages to client-independence. For instance, a change made in one development client happens immediately across all development clients. Among other things, this means we don't have to waste time figuring which client contains the most recent version -- they all do! In addition, transporting Smart Forms is easier, since we can safely bundle them together in the same transport as their client-independent print programs (no worry about mixing client-dependent and independent objects).
    Structure of a print program
    OPEN_FORM function
    CLOSE_FORM function
    WRITE_FORM
    START_FORM function
    END_FORM function
    CONTROL_FORM function
    The print program is used to print forms. The program retieves the necesary data from datbase tables, defines the order of in which text elements are printed, chooses a form for printing and selects an output device and print options.
    Function modules in a printprogram:
    • When you print a form you must used the staments OPEN_FORM and CLOSE_FORM. To combine forms into a single spool request use START_FORM and END_FORM.
    • To print textelements in a form use WRITE_FORM. The order in which the textelements are printed, is determined by the order of the WRITE_FORM statements. Note: for printing lines in the body, you can also use the WRITE_FORM_LINES function module.
    • To transfer control command to a form use CONTROL_FORM.
    Structure of a print program
    Read data
    Tables: xxx.
    SELECT *
    FROM xxx.
    Open form printing - Must be called before working with any of the other form function modules.
    Must be ended with function module CLOSE FORM
    call function 'OPEN_FORM'.....
    To begin several indentical forms containing different data within a single spool request, begin each form using START_FORM, and end it using END_FORM
    call funtion 'START_FORM'.....
    Write text elements to a window of the form
    call function 'WRITE_FORM'.....
    Ends spool request started with START_FORM
    call funtion 'END_FORM'.....
    Closes form printing
    call function 'CLOSE_FORM'...
    OPEN_FORM function
    Syntax:
    CALL FUNCTION 'OPEN_FORM'
    EXPORTING
    APPLICATION = 'TX'
    ARCHIVE_INDEX =
    ARCHIVE_PARAMS =
    DEVICE = 'PRINTER'
    DIALOG = 'X'
    FORM = ' '
    LANGUAGE = SY-LANGU
    OPTIONS =
    MAIL_SENDER =
    MAIL_RECIPIENT =
    MAIL_APPL_OBJECT =
    RAW_DATA_INTERFACE = '*'
    IMPORTING
    LANGUAGE =
    NEW_ARCHIVE_PARAMS =
    RESULT =
    EXCEPTIONS
    CANCELED = 1
    DEVICE = 2
    FORM = 3
    OPTIONS = 4
    UNCLOSED = 5
    MAIL_OPTIONS = 6
    ARCHIVE_ERROR = 7
    INVALID_FAX_NUMBER = 8
    MORE_PARAMS_NEEDED_IN_BATCH = 9
    SPOOL_ERROR = 10
    OTHERS = 11
    IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    Some important parameters:
    FORM Name of the form
    DEVICE • PRINTER : Print output using spool
    • TELEFAX: Fax output
    • SCREEN: Output to screen
    OPTIONS Used to control attrubutes for printing or faxing (Number of copies, immediate output....
    The input for the parameter is structure ITCPO.
    CLOSE_FORM function
    CALL FUNCTION 'CLOSE_FORM'
    IMPORTING
    RESULT =
    RDI_RESULT =
    TABLES
    OTFDATA =
    EXCEPTIONS
    UNOPENED = 1
    BAD_PAGEFORMAT_FOR_PRINT = 2
    SEND_ERROR = 3
    SPOOL_ERROR = 4
    OTHERS = 5
    IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    Paramerters:
    RESULT Returns status information and print/fax parameters after the form has been printed. RESULT is of structure ITCPP.
    WRITE_FORM function
    CALL FUNCTION 'WRITE_FORM'
    EXPORTING
    ELEMENT = ' '
    FUNCTION = 'SET'
    TYPE = 'BODY'
    WINDOW = 'MAIN'
    IMPORTING
    PENDING_LINES =
    EXCEPTIONS
    ELEMENT = 1
    FUNCTION = 2
    TYPE = 3
    UNOPENED = 4
    UNSTARTED = 5
    WINDOW = 6
    BAD_PAGEFORMAT_FOR_PRINT = 7
    SPOOL_ERROR = 8
    OTHERS = 9
    IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    Some important parameters:
    ELEMENT Specifies which textelement is printed
    WINDOW Specifies which window is printed
    TYPE Specifies the output area of the main window. This can be:
    • TOP - Used for headers
    • BODY
    • BOTTOM - Used for footers
    FUNCTION Specifies whether text is to be appended, replaced or added
    Example of how to use the WRITE_FORM function module together with a script.
    Form layout of the MAIN window
    /E INTRODUCTION
    Dear Customer
    /E ITEM_HEADER
    IH Carrier, Departure
    /E ITEM_LINE
    IL &SBOOK-CARRID&, &SPFLI-DEPTIME&
    /E CLOSING_REMARK
    The print program
    Writing INTRODUCTION
    CALL FUNCTION 'WRITE_FORM'
    EXPORTING
    ELEMENT = 'INTRODUCTION'
    FUNCTION = 'SET'
    TYPE = 'BODY'
    WINDOW = 'MAIN'
    EXCEPTIONS
    OTHERS = 8
    Writing ITEM_HEADER
    CALL FUNCTION 'WRITE_FORM'
    EXPORTING
    ELEMENT = 'ITEM_HEADER'
    FUNCTION = 'SET'
    TYPE = 'BODY'
    WINDOW = 'MAIN'
    EXCEPTIONS
    OTHERS = 8
    Set ITEM_HEADER into TOP area of main window for subsequent pages
    CALL FUNCTION 'WRITE_FORM'
    EXPORTING
    ELEMENT = 'ITEM_HEADER'
    FUNCTION = 'SET'
    TYPE = 'TOP'
    WINDOW = 'MAIN'
    EXCEPTIONS
    OTHERS = 8
    Write ITEM_LINE
    LOOP AT .....
    CALL FUNCTION 'WRITE_FORM'
    EXPORTING
    ELEMENT = 'ITEM_LINE'
    FUNCTION = 'SET'
    TYPE = 'BODY'
    WINDOW = 'MAIN'
    EXCEPTIONS
    OTHERS = 8.
    ENDLOOP.
    Delete ITEM_HEADER from TOP area of main window
    CALL FUNCTION 'WRITE_FORM'
    EXPORTING
    ELEMENT = 'ITEM_HEADER'
    FUNCTION = 'DELETE'
    TYPE = 'TOP'
    WINDOW = 'MAIN'
    EXCEPTIONS
    OTHERS = 8
    Print CLOSING_REMARK
    CALL FUNCTION 'WRITE_FORM'
    EXPORTING
    ELEMENT = 'CLOSING_REMARK'
    FUNCTION = 'SET'
    TYPE = 'BODY'
    WINDOW = 'MAIN'
    EXCEPTIONS
    OTHERS = 8
    START_FORM function
    CALL FUNCTION 'START_FORM'
    EXPORTING
    ARCHIVE_INDEX =
    FORM = ' '
    LANGUAGE = ' '
    STARTPAGE = ' '
    PROGRAM = ' '
    MAIL_APPL_OBJECT =
    IMPORTING
    LANGUAGE =
    EXCEPTIONS
    FORM = 1
    FORMAT = 2
    UNENDED = 3
    UNOPENED = 4
    UNUSED = 5
    SPOOL_ERROR = 6
    OTHERS = 7
    IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    END_FORM function
    CALL FUNCTION 'END_FORM'
    IMPORTING
    RESULT =
    EXCEPTIONS
    UNOPENED = 1
    BAD_PAGEFORMAT_FOR_PRINT = 2
    SPOOL_ERROR = 3
    OTHERS = 4
    IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    CONTROL_FORM function
    The CONTROL_FORM function module alows you to create SapScript control statements from within an APAB program.
    Syntax:
    CALL FUNCTION 'CONTROL_FORM'
    EXPORTING
    command =
    EXCEPTIONS
    UNOPENED = 1
    UNSTARTED = 2
    OTHERS = 3
    IF sy-subrc <> 0.
    MESSAGE ID SY-MSGID TYPE SY-MSGTY NUMBER SY-MSGNO
    WITH SY-MSGV1 SY-MSGV2 SY-MSGV3 SY-MSGV4.
    ENDIF.
    Example:
    Protecting the text element ITEM_LINE
    CALL FUNCTION 'CONTROL_FORM'
    EXPORTING
    COMMAND = 'PROTECT'.
    CALL FUNCTION 'WRITE_FORM'
    EXPORTING
    TEXELEMENT = 'ITEM_LINE'.
    CALL FUNCTION 'CONTROL_FORM'
    EXPORTING
    COMMAND = 'ENDPROTECT'.
    debugging smartform
    for Smartforms material
    http://www.sap-basis-abap.com/sapsf001.htm
    http://www.sap-press.com/downloads/h955_preview.pdf
    http://www.ossincorp.com/Black_Box/Black_Box_2.htm
    http://www.sap-img.com/smartforms/sap-smart-forms.htm
    http://www.sap-img.com/smartforms/smartform-tutorial.htm
    http://www.sapgenie.com/abap/smartforms.htm
    How to trace smartform
    http://help.sap.com/saphelp_47x200/helpdata/en/49/c3d8a4a05b11d5b6ef006094192fe3/frameset.htm
    http://www.help.sap.com/bp_presmartformsv1500/DOCU/OVIEW_EN.PDF
    http://www.sap-img.com/smartforms/smart-006.htm
    http://www.sap-img.com/smartforms/smartforms-faq-part-two.htm
    Re: Need FAQ's
    check most imp link
    http://www.sapbrain.com/ARTICLES/TECHNICAL/SMARTFORMS/smartforms.html
    step by step good ex link is....
    http://smoschid.tripod.com/How_to_do_things_in_SAP/How_To_Build_SMARTFORMS/How_To_Build_SMARTFORMS.html

  • Printout is distinct font  in different printer but same SAPscript form

    Dear experts,
    I have one SAPscript form ,Pintout in pinter HP2200 and HP4100, but printout is distinct font.
    Could you help me?
    Thanks and regards,
    collysun

    Hi,
    just ask your basis people to check whether the page format has been attached to the second printer's device type. the page format should be attached to the printer. else font differences occur.
    Kumar

Maybe you are looking for