This document provides an overview of building forms using Adobe Forms and Interface Designer in SAP. It discusses the TCodes used to access Adobe Forms and Interface Designer, how to build an interface by declaring importing and global parameters, and how to then build a form by dragging and dropping elements from the interface. It also covers topics like form layout design, mapping fields, setting numeric/date formats, adding images and tables. The document compares Adobe Forms to Smart Forms and includes a brief quiz at the end.

1. ADOBE FORM
Tutorial -1
Robin Thakral

2. TCodes
 SE37 – Driver Function Module
 SE38 – Driver Program
 SFP – Adobe Form & Interface Designer
* Unlike Smart Form, here Interface is designed as a reusable separate work
piece and need not Smart Style not be designed.

3. Interface Building
 You just declare the importing and global parameters here like you in
Smartfom to handle logics/output at Form level.
 Best point is that you can use this interface for multiple forms unlike SF
interface.

4. Form Building
 Drag and Drop the items you want to use in your Form from the Interface.
 Deactivate the elements/fields you may/do not required.

5.  Click on Layout to Design the Layout and assign fields now.
 Highlighted one allows you open layout in min tab below but encircled one let
you open the layout in a new pop-up tab giving access to Layout only.
 Make sure you are in Change mode as Adobe form layout can be changed even
in display mode, but it will not allow to save till you come back again in
change mode.
Form Building

6.  Hierarchy is for the current page elements you are holding.(Extreme Left)
 Data view in the same side is for the elements fetched from Interface to
Adobe form.
 Design is for the designing the page and positioning the elements and its
content area basically.
 Master Page to set the Page layout where you provide header texts, Logo,
page no and content area.
 Preview PDF is to get the view.
 Object Library is the list available for elements to be designed.
Form Building

7.  Now here we can, draw our output field
i.e., X_CARRID by 2 ways:
❖ Drag and Drop the field from
Data View to Design View.
❖ Design a field from
Object Library-> Standard and map
it to X_CARRID, which can be either
done by 2 ways:
✓ Text –> Select “Text” -> Right
Click ->Floating Field
✓ Text Field
Form Building

8.  Now Drag and Dropped field has mapping already done that can be seen with
Role on tabs in Right side.
❖ Binding to bind the
Elements(mapping).
❖ Value to set default and
control
❖ Field to assign field type,
Caption, length, patterns.
Form Building

9.  But fields designed are still not mapped to any element.
1. Click on Object- Field, changing appearance to None instead of Sunken Box or what
ever required.
2. Click on Object-Binding-> data binding(3 lines for options) and select for the field
to be mapped, tick the required fields as properties.
Form Building

10.  FONT
❖ You can change the font and size of the text in the marked section above.
❖ If you do not find Font toolbar by default, you can activate it as shown
below. Go to Palettes -> Toolbar / Press on Font.
Form Building

11.  Numeric & Date Field
❖ ADOBEFORMS are more convenient than scripts or smart forms because we can set
the date format or decimal format or display % or display currency format directly
in the layout.
 Numeric/Decimal:
❖ This is used to set separators like thousand separators or display % next to
value using num{z,zzz,zzz,zz9},num{($zzzz9.99)} , num{z,zzz,zz9%}. To display
to 2 decimals, we can use this format. For setting this, make sure you use
num{($zzzz9.99)} format.
 Date:
Form Building

12.  IMAGE
❖ Click on Object Library - Image, Drop image workspace on layout. Double Click on
Image, go for OK push button and select the required image from presentation
server; else opt for F4 icon OBJECT – DRAW.
❖ Don’t forget to Mark Check box – “EMBED IMAGE DATA”.
Form Building

13.  Table
❖ Page should be flowed for it.
 Header
 Body Row
 Footer
❖ All these setting can be handled in
“Accessibility”. Make sure you opt for
the same in OBJECT- ROW.
❖ Binding for table is only “IT_BUT000”
i.e., interface table name.
❖ Binding for body row is “DATA[*]”
i.e., internal table data that will be
fetched automatically wherever you
replicate this body row.
❖ No Binding for Header, Footer.
❖ Make sure to opt for Object – Table –
Allow Page Breaks for table & body
Form Building

14.  ….Tables
➢ Header
❖ Don’t opt for Page break in it, generally Left to Right.
❖ Object –Pagination , opt for occurrence on following pages
❖ Border is used to give any Background color and border thickness.
❖ Border details can be opted at Cell level as well instead of Header.
Form Building

15.  ….Tables
➢ Body
❖ Allow Page break in OBJECT – ROW.
❖ Repeat row count should be checked.
❖ For Custom height of the cells, select all cells and provide as no height for Body.
❖ Assure the binding of cells and Accessibility of Body row.
❖ Zebra pattern feature is available at Table level at OBJECT – ROW SHADING
Form Building

16.  ….Tables
➢ Table Object Method
❖ Keeping it simple, used for mostly standard tables.
❖ Have feature to repeat header on each page.
❖ XML coding , treated as a Subform only.
❖ Difficult to handle nested tables.
➢ Subform Method
❖ Gives more flexibility but must handle header to overflow.
❖ Suitable option for nested tables.
❖ Building Interface would be same for both.
Form Building
Interface building
and usage

17.  Adobe v/s Smart Form
❑ Adobe Form:
❑ Re-use the interface of forms.
❑ User-friendly tools reduce the time and costs associated with creating form layouts.
❑ Adobe Designer can import existing PDF forms
❑ A ‘paper-like’ layout Leverages people's experiences with paper forms.
❑ Easy client-side form printing that custom font and printer setting issue.
❑ Enable new functionality in Adobe Reader, Annotations, Digital Signature and
Certification.
❑ We don't have "Version management" in Smart forms which is there in Adobe forms.
❑ Graphics are used directly without conversion.
❑ Smart Forms:
❑ Smart forms have easy condition-based checks.
❑ Background graphics are not supported in SAP Interactive Forms just like in Smart Forms.
❑ Control commands - Explicit Page Break
❑ User must use scripting for calculations which must be created on the page break (page
subtotals, for example).
❑ The OTF output format is not supported by SAP Interactive Forms.
Form Building

18. QUIZ TIME
1. Can we use Same Interface in Multiple Adobe forms??
2. Is it possible to use multiple interface in single Adobe form??
3. How many scripting languages are available in Adobe forms ??
a) 1. b) 2 c) 3 d) 4
4. Which points are true??
5. Form Interface don’t have :
a) Import b)Changing c)Export d) none
Form Building – Quiz

19. QUIZ TIME
6. Adobe form is called using which function modules:
7. While designing , can we able to see the preview of layout without executing??
8. Do we need to save Interface and Form in same version??
Form Building – Quiz