topic Re: smartforms(from scratch) in Application Development and Automation Discussions

smartforms(from scratch)

Former Member — Thu, 28 Feb 2008 07:36:59 GMT

hi all

can anyone send me document for smartfroms from scratch...

i want to work in smartforms..i dono anythin about smartforms..

Regards

Asha

Re: smartforms(from scratch)

RaymondGiuseppi — Thu, 28 Feb 2008 07:40:19 GMT

SAP sources of informations

SAP Service Marketplacehttp://service.sap.com/smartforms

SAP Library in SAP Help Portal http://help.sap.com/

- SAP NetWeaver -> SAP Web Application Server 6.20-> mySAP Technology Components-> SAP Web Application Server-> Basis Services / Communication Interfaces (BC-SRV)-> SAP Smart Forms (BC-SRV-SSF)

Training

- BC470 -Form Printing Using SAP Smart Forms (2 days training course)

Demos

- Reports / Forms: SF_EXAMPLE_01, SF_EXAMPLE_02, SF_EXAMPLE_03, SF_EXAMPLE_04

- BSP applications:SF_WEBFORM_01, SF_WEBFORM_02, SF_WEBFORM_03

SAP Press Book

- SAP Smart Forms –Creating forms quickly and easily -no programming required“, 450 pages, ISBN 1-59229-010-8, (order at www.sap-press.com)

SAP Notes in SAP Service Marketplace:168368, 412293, 430621, 526824

SDN source of information

Look at this contribution [Smart Forms|https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/8fd773b3-0301-0010-eabe-82149bcc292e]

Regards

Re: smartforms(from scratch)

Former Member — Thu, 28 Feb 2008 07:41:57 GMT

for Smartforms material

http://sap-img.com/smartforms/sap-smart-forms.htm

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

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...

Go through these SAP Standard programs also,

sf_example_01

sf_example_02

sf_example_03.

2) here you can attach it in two ways

a) Stand alone program: you can directly call the form in the print program itself using function module generated by smartform when it is activated.

b) If it likned to transaction then you can attach it using Output type . These will be configured in NACE transaction

3) In the NACE transaction itself you can attched program. Or you can check TNAPR table . Give the SFORM (Smartform name) you will get Print program and Output typem configured in NACE

4)Output type is used to attach Print medium for smartfrom like print output, email, Fax etc..

5)Develop smartform, Develop print progra, Configure it in NACE transaction , Then configure the messages in corresponding transaction

First create your program, and then say you want to display table itab thru SF.

So create a SF and in the form interface section go to the tables tab and then give itab like zitab (structure of the same type of itab, this needs to be created).

Now in the main window create a table, right click on the window and you will have an option.

In the table you have header, main body and footer. Create line types for these and then for each cell create a text element and give what ever is required. Here you also have a loop where you give loop at itab into itab.

Say you have to display seq, order, item, desc, amt. Give these in the header in 5 cells, your header line type has to have 5 cells, so is your main body.

In the main body give &itab-seq&, &itab-vbeln&, &itab-posnr&, &itab-arktx&, &itab-netwr& in the respective text elements of the cells.

So now your SF is done, go to your program and then call the FM

CALL FUNCTION 'SSF_FUNCTION_MODULE_NAME'

EXPORTING

formname = 'ZSF2' "name of the SF tht you have created

IMPORTING

fm_name = fnam.

CALL FUNCTION fnam

EXPORTING

gv_name = gv_name " If you need to export any variables you can do it here.

TABLES

itab = itab.

Thats it and your data is displayed.

Hope this is fine, if you need anything else just post it.

Reward points if useful.

Re: smartforms(from scratch)

Former Member — Thu, 28 Feb 2008 07:43:11 GMT

Hi,

SMARTFORMS:

ADVANTAGES OF SMARTFORMS:

1. Smartforms does not require paragraph formats as a mandatory one.

2. Smartforms does not duplicate the data.

3. Smartforms are Client-independent and language-independent.

4. We can apply styles for the texts using Smartforms.

5. Print programs does not contain any function modules to call the form.

SMARTFORMS is the Tcode to create smartforms in ABAP.

Smartforms has three components:

Global Settings:

1. Form Attributes - Holds the description about the smartform.

2. Form Interface - Holds the import and export parameters for the smartforms.

3. Global Definitions - Used to declare variables for the smartform that can be accessed by any component within the smartform.

Pages and Windows:

This area is used to create new pages, windows (header, footer, constant window, main window, variable window, graphic window).

Navigations to create Smartforms:

SMARTFORMS -> Specify form name starting with Z or Y -> Click on Create -> Opens an interface -> Enter short description -> Double click on Form Interface -> Specify following parameter in IMPORT tab button:

STR TYPE C

-> Expand Pages and Windows -> By default, a Main Window is present -> Right click on Main Window -> Create -> Text -> Opens Form Editor -> To go to line editor, Click on 'Txt Editor' pushbutton on the upper left corner of the form editor -> Specify the variable (&STR&) in the first line of line editor -> Come back -> Save -> Activate -> Execute -> Opens Form Builder with autogenerated function module for the smartform ('/1BCDWB/SF00000042') -> Copy the function module generated.

To invoke the smartform from SE38 editor, Call the Function module and paste the FM copied from smart form function builder screen as follows:

DATA NAME(10) VALUE 'INDIA'.

CALL FUNCTION '/1BCDWB/SF00000042'

EXPORTING

STR = NAME.

-> Save -> Activate -> Execute in the same way as Sapscript.

Navigations to pass internal table as an argument to Smartforms:

Create a smartform -> In the Form interface -> Click on Tables tab button -> Specify the following internal table:

ITAB LIKE MARA.

-> Double click on Global Definitions -> Specify the global variable as follows:

ITAB1 LIKE MARA.

-> Expand Pages and Windows -> Right click on Main Window -> Create -> Table -> Click on Data tab button -> In the LOOP section, for the operand fields, specify the following:

ITAB INTO ITAB1.

-> Right click on Main Area -> Create -> Table Line -> In the Line Type input field, a line type called %LTYPE1 is automatically generated -> Select it.

To create internal table fields, right click on Text cell -> Create -> Text -> Select General Attributes tab button -> Opens Form Editor -> Goto Line editor by clicking on 'Txt Editor' pushbutton -> Specify the following in the first line:

&ITAB1-MATNR&,,&ITAB1-MTART&,,&ITAB1-MBRSH&,,&ITAB1-MEINS&

-> Come back -> Save -> Activate -> Execute -> Copy the autogenerated FM.

In SE38 program, specify the following:

DATA ITAB1 LIKE MARA OCCURS 0 WITH HEADER LINE.

SELECT * FROM MARA INTO TABLE ITAB1.

CALL FUNCTION '/1BCDWB/SF00000043'

TABLES

ITAB = ITAB1.

Save -> Activate -> Execute in the same way as above.

Regards,

Priya

Re: smartforms(from scratch)

Former Member — Thu, 28 Feb 2008 07:45:37 GMT

hi,

SAP Smartforms can be used for creating and maintaining forms for mass printing in SAP Systems. The output medium for Smartforms support printer, fax, e-mail, or the Internet (by using the generated XML output).

According to SAP, you need neither have any programming knowledge nor use a Script language to adapt standard forms. However, 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).

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.

Additional Fonts for your SMARTFORMS

You can create additional fonts and style with transaction SMARTSTYLES

This can then be define in the paragraph and character formats, which you can then be assign to texts and fields in the Smart Form.

The character formats includes effects such as superscript, subscript, barcode and font attributes

Refer to this link.

http://www.sap-img.com/smartforms/smart-001.htm

Re: smartforms(from scratch)

Former Member — Mon, 12 May 2008 11:02:25 GMT

Smart Forms: An Overview

1. INTRODUCTION 4

1.1 WHAT ARE SMART FORMS? 4

1.2 HOW ARE SMART FORMS DIFFERENT FROM SAPSCRIPTS? 4

1.3 ARCHITECTURE: 5

1.4 MAIN FEATURES OF SMART FORMS 6

1.5 CREATING SMART FORMS 6

2. ABOUT FORM BUILDER: ITS COMPONENTS 8

2.1 BASIC TREE STRUCTURE 8

2.2 GLOBAL SETTINGS: 9

2.2.1 Form Attributes 9

2.2.2 Form Interface 9

2.2.3 Global Definitions: 11

3. PAGES AND WINDOWS 13

3.1 NODE 'PAGE' 13

3.1.1 General Attributes: 14

3.1.2 Output Options: 14

3.1.3 Background Picture: 14

3.2 WINDOWS 15

3.2.1 General Attributes of a 'window' node: 16

3.2.2 Output Options: 17

3.2.3 Conditions: 17

4. SUCCESSOR NODES OF WINDOW/PAGE 19

4.1 BASIC NODES 19

4.1.1 Text 19

4.1.2 Text Module 21

4.1.3 Graphic 22

4.1.4 Address 23

4.2 AUXILIARY NODES 24

4.2.1 Template 24

PROLOGUE

Metamorphosis is an improved change in structure and function of an entity. The aspect of creation and maintenance of forms in SAP has metamorphosed from SAPscripts to Smart Forms. Smart Forms has revolutionized the creation and maintenance of forms in that, the same is more user friendly and consumes unbelievably lesser time. The overview that follows is structured in such a way as to help any technical person understand the content and use the same for handling this new feature of SAP with confidence. The principal sources that have served for the preparation of this technical paper include our ever helpful SAP’s ‘F1’s and ‘F4’s , SAP 4.6C documentation on SAP Smart Forms, the fundamentals of SAPscripts that I gathered from interactions with my team leader Mr. Anupam Dutta and the results of various experiments that I am guilty of indulging in during the development of the Smart Form (Total Compensation Statement) for Nestle Project, which incidentally happens to be the first smart form development in i-SDC.

This paper is introductory in nature and is first in the series of technical guides for Smart Forms. Suggestions are sought from the users so as to make the documents that shall follow better in terms of quality and content.

I take this opportunity to thank my senior colleagues Mr. Samit K. Sen and Mr. Anindya Mitra for their guidance.

- Taraka Chaitanya Vyas

1. Introduction

1.1 What are smart forms?

SAP Smart Forms are used 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).

SAP Smart Forms offer the following advantages:

· Creating and maintaining forms requiring half the time (compared to SAPscript forms)

· Adapting forms (those provided by SAP or a custom one) without any programming knowledge due to entirely graphical user interface. Thus, a functional consultant without any programming knowledge can configure forms with data from an SAP System for the relevant business processes.

· Web Publishing using the generated XML output.

SAP quotes--

"The SAP Smart Forms replace the SAPscript forms. But, SAPscript forms will also be supported in the future; you can use them without making any changes for years to come. SAPscript texts can be used in the Smart Forms. SAPscript forms can be migrated to Smart Forms."

1.2 How are Smart Forms different from SAPscripts?

Ø The main difference is that, the flow (viz., when, which windows/text elements are to be printed) in SAPscripts is controlled by the driver program, but in Smart Forms, the flow logic is entirely incorporated in the form itself. The driver program retrieves data from Database and sends it at one go to the Smart Form through a function module (which is generated when a Smart Form is activated). So, calling a smart form from a driver program boils down to calling a function module. Database tables can be accessed from the form also.

Ø Also, ABAP code can be written in Smart Forms; basically they can be used as though they are function modules, in defining local variables, subroutines, etc. Thus, Smart Forms can be run by just executing the concerning function module, without being called from a driver program (thus, they can be of stand-alone type). But writing DB selection codes in a form should be avoided as, it increases over-head, especially in the case of batch printing.

Ø There are some more minor differences like, instead of standard texts, text modules can be used in Smart Forms. Also, graphic object can be included directly in smart forms. These graphic objects can be maintained through the transaction, SE78. Address can be printed by just using the corresponding address number (if the central Address system is being maintained), and the format of it is automatically taken care of, based on the value given for country field.

Ø The system variables, which were available in SAPscripts aren't in Smart Forms. Different set of system variables are used. (for printing date, page no., etc).

Ø Any field inside a smart form accepts variables, instead of just hard-coded values. For example, the name of the text module to be used, name of the graphic to be printed, etc can be determined dynamically during run-time.

Ø Boxes and frames can be incorporated by just clicking at few check-boxes.

Ø Use of 'tabs', those ubiquitous pair of commas is almost redundant in Smart Forms, as the same functionality can be better achieved by using line types inside a template or a table node.

1.3 Architecture:

First, you have an application program, which fetches the data from the Database. A Smart Form is created, the activation of which generates a function module. DB selections can also be done inside the Smart Form. The application program calls the function module in question, which in turn submits the print job to the spool.

1.4 Main Features of Smart Forms

Ø Smart forms are created in a utility, 'Form Builder' which is very user-friendly compared to the environment for SAPscript creation. Form Builder comes with utilities like, Form Painter, PC editor, Line editor (which are same as that for SAPscript), table painter (this is a new addition, which is useful in creating dynamic tables, static tables/templates).

Ø 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.(this can be done through XSF option)

Ø Static and dynamic tables can be inserted. This includes line feeds in individual table cells, triggering events for table headings and subtotals, and sorting data before output. In SAPscripts, this was all done in the driver program, by a maze of codes.

Ø Check on individual nodes as well as the entire form can be done to 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.(thus avoiding hop-chop way of debugging lay-out sets, that we used to do in the case of SAPscripts)

Ø Graphics can be included in Smart Forms, which can be displayed either as part of the form or as background graphics. Background graphics can be used to copy the layout of an existing (scanned) form or to lend forms a company-specific look. During printout, if desired, the background graphic can be suppressed.

Ø SAP Smart Forms also support postage optimizing. (I haven't yet gone deeper in to this feature)

Sounds interesting, right? The way in which all the above features are incorporated will be covered in following sections.

1.5 Creating Smart Forms

The transaction is 'SMARTFORMS' and the menu path is

'SAP menu->Tools->Form Printout->Smart Forms'.

Smart form can be created by either migrating an existing SAPscript or either by copying existing smart form, apart from creating it afresh.

Testing/Running Smart Forms:

After, the Smart Form is created, it has to be activated, by which the function module for that smart form gets generated. The name of the function module generally has the following pattern, /1BCDWB/SF00000034. Name of the function module can be got from the menu path (in form builder screen), 'Environment->Function Module Name'.

2. About Form Builder: Its components

2.1 Basic tree structure

The two basic nodes are 'Global Settings' and 'Pages and Windows'.

2.2 Global Settings:

2.2.1 Form Attributes

2.2.2 Form Interface

This will be the interface of the function module that will be generated when this form is activated. First 9 importing parameters (which are blocked out) are provided by the system, manipulating which, output can be controlled. (viz., whether dialog box has to be displayed or not, setting output device, Facsimile parameters, spool parameters).

Importing Parameters

The Exporting Parameters:

Exceptions:

2.2.3 Global Definitions:

Anything defined under this, are visible inside the form.(in Initialization, Subroutines, inside the nodes)

Global Data:

Types:

Field Symbols:

Initialization:

Form Routines:

Here, you define all your subroutines (for eg., conversion before output). These can be accessed from 'program lines' nodes.

Done with Global settings. Lets move onto the other major node of the tree structure, 'Pages and Windows'.

3. Pages and Windows

The sub-nodes that can be created under this node are of type 'Page'. The System automatically creates the start page and a window (of type MAIN) under it. The basic concept of pages, windows and text elements remain the same (compared to SAPscripts). Also the functionality of MAIN window and sub-windows remain unchanged from SAPscripts.

The following will discuss the various features of 'PAGE' node. (for creating a sub-node or subsequent node, 'right-click' on the parent node and go for 'create' on the pop-up menu, and then select the required node).

3.1 Node 'PAGE'

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. Various attributes of this 'page' are to be determined, the following way.

3.1.1 General Attributes:

3.1.2 Output Options:

3.1.3 Background Picture:

You can have a Graphic Object to appear as background image of this page. (sounds kewl!!). If you select an output mode, the user will still have the choice of either displaying or suppressing it in the print preview.

Now, we can 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 (a page can be omitted even though it is part of the tree structure).

3.2 Windows

Creating a window:

3.2.1 General Attributes of a 'window' node:

3.2.2 Output Options:

3.2.3 Conditions:

Within a Smart Form a node and all successor nodes are processed only if

the respective output condition is true. A condition can either be a logical expression on field values or consist of events or position queries in the form processing.

You can determine a condition as logical expression using a table control. Each line of the table control consists of a field name, a comparison operator, and a comparison value. The comparison value can itself be a field name. As comparison operators, the ABAP operators =, <>, <, >, <=, >=, CP (contains pattern) and NP (not contains pattern) are allowed.

All lines of the table control are linked with the logical AND. In addition, you can use a pushbutton of the table control to insert an OR link for comparisons. In the table control, it is displayed as line with gray background. The Check function checks whether all field names that appear in the comparisons are declared in the form interface or in the global data of the form.

Above features can be referred to in the following screen shot.

Output Options and Conditions are the same for every node.

4. Successor nodes of window/page

Various nodes that are available can broadly be classified into two categories, viz.,

1. Basic nodes, whose contents are actually printed (either as a part of an output area (window) or independently as part of a page.

2. Auxiliary Nodes, which can be used to control the flow of the layout. These are basically used to incorporate the Form Logic (which in case of SAPscripts was carried out by ABAP code written in driver program).

4.1 Basic Nodes

Graphic, Address and Text fall under this category. A 'text' node can be created only as a successor of a Window node (i.e., it cannot be created directly under a page), as it needs some output area in which it has to appear. On the other hand, Graphic and Address can either be created as successor nodes of a 'window' node or they can be directly created under a 'page' node. In the former case, the address (or graphic) does not appear on the Form Painter as windows are processed only during the runtime). If defined as direct successor of 'page' node, they become visible on the layout displayed by the form painter, and thus can be placed and resized according to our needs.

4.1.1 Text

This node is used to print any texts (and table contents), except addresses.

There are following text types:

1. Text Element (to enter new text in the PC editor)

2. Include Text (to include an existing SAPscript text)

3. Text Modules (to include a text module).The first two types are same as that were in SAPscripts.

Parameters and system fields can be printed inside these text nodes. (this poperty deviates very little from that of SAPscripts in that only the system fields here are different). All the fields available inside the form can be seen, by setting Field List- On.

System fields made available are listed under the node, SFSY. The fields can be referred to as, SFSY-DATE. Another interesting feature of including fields other than by the normal way (by clicking on ‘+’ symbolled icon lying in the tool bar of a text node, and entering the field name between ampersands) is to simply drag the required field from the field list and drop them on the PC editor of the text node.

General Attributes of 'text' node:

4.1.2 Text Module

You use text modules to centrally store texts in the system that you frequently use in forms. This detaches the text maintenance from the form maintenance so that you need not call the Form Builder to edit individual texts.

Features of Text Modules:

Through text module maintenance function we can create and edit text modules. Similar to text nodes, text modules have the following characteristics:

· They can be used cross-client

· They are connected to the transport system

· They are connected to the translation tools in the system

Fields can also be referred from a text module. But if those fields are not defined in the Smart Form which includes this text module, syntax error is raised.

Management of Text Module:

4.1.3 Graphic

You use the graphic node to display graphics, such as a company logo, on the form. This node is used the same way as the background picture for a page. Check out section 3.1.3.

In SAPscripts, graphics were incorporated in a form by including a standard text containing TIFF image. As of Release 4.6, graphics are stored on a document server. In addition to .TIF ,.BMP files can also be imported and used in forms.

Maintaining Graphics

Graphic administration is used to import, administer, and transport graphics, and to display them in a print preview. You can either incorporate graphics statically into a form (for example, the company logo) or include them dynamically using an appropriate field (for example, material graphic showing the displayed material). This was also discussed in sec 3.1.3.

The transaction for Graphic administration -> SE78.

4.1.4 Address

4.2 Auxiliary Nodes

These are used to control the flow logic. Various Auxiliary nodes are,

· Template- Output of a table containing static data

· Table - Output of a table containing application data

· Loop - Processes successor node repeatedly.

· Alternative- Branches depending on condition.

· Command - Executes special commands (next page, paragraph numbering, printer control)

· Folder- Combines successor nodes to logical groups

· Complex Section- Combines all attributes of the node types template, table, loop, folder

· Program Lines - Executes ABAP program code (for example, conversion routines ).

4.2.1 Template

This node is to be used for displaying a table whose layout and number of rows and columns is determined before run-time. The text nodes created as successors of this node actually hold the data to be printed. This node just defines the way, the successive text nodes have to be printed. Thus making the concept of defining ‘tabs’ in paragraph formats redundant.

First, the table layout has to be defined.

The pattern(no. of cells, width of each cell) of each row of table that is being printed is defined in the line types. In the above example, two line types are defined. L1 is applicable to rows from 1 to 3, and it has height of 1 cm, has 4 cells, each of varied length. Previous line type can be referred to in creating new line types.

Table Painter: Table Painter graphically depicts the various line types, and here, the width, height of cells can adjusted.

Select Pattern: You can select the pattern in which the final table should be appearing( encasing each cell with in a box etc.,). Thus the concept of drawing frames and boxes which was followed in SAPscripts is redundant.

To actually display contents inside this table layout, text nodes have to be created under this template node, and these will be containing the data to be displayed. You can specify which text element is to be printed in which cell of which line type.

In the following example, there are in all 3 lines of a table have to be printed. For that 3 line types are declared as follows,

Now, 10 text elements have been defined under this template node to which will be outputing data in 10 cells (of 3 lines)

The output options of a text node defined under ‘template’ node has extra fields for mentioning the line number and column number in which it has to be printed.

Group all the text nodes that belong to a particular line into a folder. This improves clarity and has no effect on functionality.

The length of a line type should exactly be equal to the width of table/template.

Epilogue

This document is not consummate in itself and awaits a further version, which will be covering the following features of Smart Forms, that could not have been covered here.

The Auxillary nodes à

Table,

Loop,

Alternative,

Command,

Folder,

Complex Section,

Program Lines.

and

Style Builder

If I have missed anything other than the above, please let me know. I would also like to hear from you regarding any improvements that can be made in the present document, and they will duly be incorporated in the new additions.

- TCV.

reward if useful

Arif Shaik

Re: smartforms(from scratch)

Former Member — Wed, 03 Jul 2013 09:53:22 GMT

This message was moderated.

Re: smartforms(from scratch)

Former Member — Wed, 03 Jul 2013 10:21:27 GMT

Hi Asha,

Refer the below links

http://wiki.sdn.sap.com/wiki/display/ABAP/Learn+making+First+Smartform+Step+by+Step

http://saptechnical.com/Tutorials/Smartforms/PO/page1.htm

http://saptechnical.com/Tutorials/Smartforms/SFMain.htm

http://www.saptechies.com/simple-smartform-tutorial/

Regards,

Karthik