Beruflich Dokumente
Kultur Dokumente
A digital signature is a security mechanism for protecting digital data. The digital signature does
the same function for processing digital data as hand written signature does for the paper based
documents.
Step1: SFP is the transaction to create adobe form. Provide the interface name and click on create
button.
Activate the interface and come back to initial screen of form builder.
Sign icon (Marked as Yellow color) as shown in tool bar is in disable mode. After the signature has been
filled this icon becomes enable mode.
The following Add Digital ID screen will appear when click on Next button and fill the related
information.
Now click on finish button.
Now the created signature will appear on the signatory field as shown below.
Click on signature field, you will get the pop up box as shown below.
If you want to check the signature properties then click on signature properties button.
If the signature is valid then you will get 'Signed and all signatures are valid' message appear at the
top of the window.
Here we can also change the field entries even after the signature field has been filled. When saving
the form after we modified the any of the field entries in the form, you will get the following message at
the top ‘Signed and all signatures are valid, but with unsigned changes after the last signature’.
Click on signature panel at the top right side corner (Shown on above picture), there you can find the
log as shown below.
When you click on highlighted statement under Form Fields Filled In, it would show the modified value
of the field. And also you can check the value before modification in the Click to view this version
under signature details.
Provide the required information and press Next button as shown below.
We get the following screen. It asks for password. Provide the password and press finish button.
We get the following screen.
After providing the password only you can able to sign in. Suppose if you press the sign button without
giving password, it asks for password saying that ‘A password is required to use this digital ID’.
Click here to continue...
Now press the sign button. The signature would be appeared in signature field.
In the above two cases, we can able to change the field entries after the signature field is filled in the
form. But, we can also have an option to avoid / restrict making changes to the content of the fields
(‘Date’ in this case) once the signature field is filled.
Now go to library tab-Web Dynpro native. Drag and drop the signature-sign and lock to layout
editor.
Save and activate the form.
Click on signature&lock field. The following screen appears. Select the existing id or create new id as
shown below.
Select ID Phani
Cross Application -
RCSIGSEA Find digital signatures
Digital Signature
SAPLQSS6 Dokumentzugriffe im QM -
Cross Application -
DSIG_BOOKING_EX Report DSIG_BOOKING_EX
Digital Signature
FI - Information
RFSOPO00 General Ledger Line Items
System
BW - Business
UPP_LAYOUT_CHECKIN Program UPP_LAYOUT_CHECKIN Planning and
Simulation
Personnel Mgmt -
Creation of digital Personnel File
RPASRCREATEDPF HR Administrative
Using Personnel No. or Ref. No.
Services
Creating PDF:
Using transaction 'SFP' to go to Form Builder or through SE80 (to create an interface and then the
form).
Before creating a PDF, you need to have an interface which contains all the fields which you will be
using in the form.
Hence before creating a form you need to create an Interface and assign this interface in the pop-up,
which comes while you create the respective form.
SFP stands for SAP Forms Process.
Structure of PDF Form:
Form interfaces and form contexts with layout are called as form objects. These are different
transportable object types. The same interface can be used
by multiple forms (like say in purchasing order, scheduling forms etc).
Enter transaction SFP and you go to the screen shown in the next Figure.
below.
Form Interface:
When you click the field 'Import', you get the above screen. Here you can add ( ) the fields we need
in the form. Here I have added the field 'EMPLOYEE_NAME' and
activated the interface
Note that the parameter, '1BCDWB/DOCPARAMS' is common for all interfaces. It comes by default
and this has a type of SFPDOCPARAMS. This parameter is used
to pass the country key, language and other related details while calling the form through the
standard function module.
When you double-click Export, you see the standard parameter /1BCDWB/FORMOUTPUT of the
generated function module. You cannot
change this parameter.
You use this parameter in your application program, to make the generated form available as a PDF
for further processing, for example.
As we have activated the interface, now we can create a form and assign this interface to the form.
For that, return back and create the form as in fig below.
Global Definitions:
Use
Global definitions belong to the interface in the Form Builder. Here, you have the option of defining
your own fields to be used anywhere in the form. You can initialize
global data before you start to process the form, for example, to convert selected application data.
Features
Global Data
Here, you define any data needed by the form, but which has not been provided by the form
interface (for example, to display totals).
Types
Here, you create data types as free ABAP code, if the ABAP Dictionary does not provide a type.
Field Symbols
You can use field symbols as pointers when you extract data from internal tables.
Initialization:
Use
You can initialize global data before you start to process the form, for example, to convert selected
application data.
Prerequisites
You have defined global data.
Features
You use the ABAP Editor to write the program code (Code Initialization) that is executed before the
form is processed. You can include subroutines (Form Routines)
when you do this.
Specifying a Currency or Quantity Reference:
Use
In the ABAP Dictionary, you can assign a currency or quantity field to a table field. In the output of
these fields, the system can then insert the relevant currency or
unit.
If the value field is in the same table as the corresponding currency or quantity field, the system
recognizes the reference automatically, and formats the value field
according to the currency or unit in the assigned field.
If the value field is in a different table from the currency or quantity field, the system cannot
recognize this reference automatically.
Conditions
Use
1.You can define conditions for individual nodes, or for whole subhierarchies of the context.
2.A node, or all its subnodes, is then only processed if the related condition is met.
3.To select from two alternative subhierarchies in the form output, use the alternative node.
Prerequisites
A node exists for which you want to define conditions. This node must allow conditions to be defined.
Features
You can define conditions using logical relationships.
Layout
Once the required parameters are included in the context, you can now go to the layout to design the
form. Click in the tab 'Layout' and you get the screen below, which is basically the Adobe designer.
1.You create the body and master pages for the form design in the Layout Editor.
2.You can also view and edit the form design and preview the form (the form that the user will work
with) in PDF.
3.The Layout Editor contains four tabs: Body Pages, Master Pages, XML Source, and PDF Preview.
Boilerplate objects
Boilerplate objects are read-only objects that improve the aesthetic appeal of a form and may provide
context or assistance for users. They can be added to
body pages or master pages.
The following objects are boilerplate objects:
1.Circle
2.Image
3.Line
4.Rectangle
5.Text
About Palettes
If you are not seeing any palettes at either ends, then search them in the field 'Palettes'. (Fig Above)
Palettes provide easy access to the tools without cluttering your workspace. Palettes can include one
or more tabs, each containing common properties.
For example, all objects are stored in the Library palette. As you can see in the following figure, the
objects are further grouped into tabs.
You can arrange the palettes in the workspace to suit your work style. For example, you can hide the
rarely used palettes and move the frequently used ones
into one palette window.
Palettes continued..
The Data view palette contains the parameters and structures that we have defined in the context
level.
(Here the parameter - 'EMPLOYEE_NAME'). The hierarchy palette contains the flow with which we
have defined the fields in the layout. All the objects /
fields which you use in the layout design are reflected in the hierarchy. By default, the hierarchy
contains a master page and the body page. You place
the fields in the layout by dragging them from the Data view palette.
(refer the fig: below).
The properties of all objects in the layout are maintained in palettes - 'Layout', 'Border', 'object' and
'Accessibility'.
Designing of the form can be made, at your comfort level, by setting the scales and measurements in
the palette 'Drawing Aids'.
Hierarchy Palette
The Hierarchy palette is a graphical representation of the contents in the Body Pages and Master
Pages tabs. The palette also displays referenced objects
under the Referenced Objects node. A referenced object is an object that is only added to a form
when it is required.
Library Palette
The Library palette contains all the objects that you can add to a form design.
Objects are organized into groups. Each group is contained in a tab labeled with the group's name.
Object Palette
Use the Object palette to modify properties that are specific to the selected object. The object that is
selected in the Layout Editor determines which tabs are available in this palette.
Border Palette
Use the Border palette to edit the border properties for objects in the form design. You can edit the
borders individually (left, right, top, and bottom) or together. You can also specify the type of border
corner and background color.
Accessibility
Use the Accessibility palette to specify custom text for an object that a Microsoft Active Accessibility
(MSAA) compliant screen reader reads as it passes through the form. If custom screen reader text is
available for the object, the screen reader will read the custom text and not the tool tip.
Layout Palette
When you select an object on a body or master page, the Layout palette automatically displays the
selected object's settings. Any changes that you
make to the settings in the Layout palette are applied to the selected object.
Similarly, you can edit most of an object's layout settings directly in the Layout Editor. For example, to
change an object's position, you can drag it to
the new location on the page.
* PRINT:
3 COMMENTS:
1.
Nice article..
Reply
Replies
Reply
2.
It was very nice blog to learn about Selenium.Thanks for sharing new
things.selenium training in chennai
Reply
Replies
Reply
3.
You can contact 8122241286 for Best SAP Training in Chennai or reach
www.thecreatingexperts.com
Reply
Former Member
December 18, 2015 at 13:26 PM
0 Likes
Correct Answer
Markus Meisl
Not what you were looking for? View more on this topic or Ask a question
11 replies
Helpful Answer
Correct Answer
1. report fp_pdf_test_07.
2. * set signature
3.
4. class cl_fp definition load.
5.
6. selection-screen begin of block s_files with frame title text-100.
7. parameters: p_pdf(64) type c lower case obligatory,
8. p_out(64) type c lower case obligatory.
9. selection-screen end of block s_files.
10. selection-screen begin of block s_conn with frame title text-101.
11. parameters: p_dest type rfcdest default 'ADS' obligatory.
12. selection-screen end of block s_conn.
13. selection-screen begin of block s_sig with frame title text-102.
14. parameters: s_key(64) type c lower case,
15. s_field(64) type c lower case,
16. s_reason(64) type c lower case,
17. s_loc(64) type c lower case,
18. s_cinfo(64) type c lower case.
19. selection-screen end of block s_sig.
20.
21. types: ty_raw(255) type x,
22. ty_tab type standard table of ty_raw.
23.
24. data: l_filename_pdf type string,
25. l_filename_out type string,
26. l_fp type ref to if_fp,
27. l_pdfobj type ref to if_fp_pdf_object,
28. l_pdf type xstring,
29. l_out type xstring,
30. l_fpex type ref to cx_fp_runtime.
31.
32. l_filename_pdf = p_pdf.
33. l_filename_out = p_out.
34.
35. perform load_file using l_filename_pdf
36. changing l_pdf.
37.
38. * get FP reference
39. l_fp = cl_fp=>get_reference( ).
40.
41. try.
42. * create PDF Object
43. l_pdfobj = l_fp->create_pdf_object( connection = p_dest ).
44.
45. * set document
46. call method l_pdfobj->set_document
47. exporting
48. pdfdata = l_pdf.
49.
50. * set signature
51. call method l_pdfobj->set_signature
52. exporting
53. keyname = s_key
54. fieldname = s_field
55. reason = s_reason
56. location = s_loc
57. contactinfo = s_cinfo.
58.
59. * execute, call ADS
60. call method l_pdfobj->execute( ).
61.
62. * get result -> l_out
63. call method l_pdfobj->get_document
64. importing
65. pdfdata = l_out.
66.
67. catch cx_fp_runtime_internal into l_fpex.
68. perform error using l_fpex 'INTERNAL ERROR'.
69. catch cx_fp_runtime_system into l_fpex.
70. perform error using l_fpex 'SYSTEM ERROR'.
71. catch cx_fp_runtime_usage into l_fpex.
72. perform error using l_fpex 'USAGE ERROR'.
73. endtry.
74.
75. check l_fpex is initial.
76.
77. * download PDF
78. data: l_len type i,
79. l_tab type tsfixml.
80.
81. call function 'SCMS_XSTRING_TO_BINARY'
82. exporting
83. buffer = l_out
84. importing
85. output_length = l_len
86. tables
87. binary_tab = l_tab.
88. call method cl_gui_frontend_services=>gui_download
89. exporting
90. bin_filesize = l_len
91. filename = l_filename_out
92. filetype = 'BIN'
93. changing
94. data_tab = l_tab
95. exceptions
96. others = 1.
97. if sy-subrc = 0.
98. write:/ 'Datei erfolgreich geschrieben'(001).
99. else.
100. write:/ 'Fehler beim Schreiben der Datei'(002).
101. endif.
102.
103. form error using p_fpex type ref to cx_fp_runtime
104. p_str type string.
105. data: l_errcode type i,
106. l_errmsg type string,
107. l_string type string.
108.
109. write:/ '***************************************************'.
110. write:/ '***', p_str.
111. write:/ '***************************************************'.
112. skip 2.
113.
114. call method p_fpex->get_errall
115. importing
116. errcode = l_errcode
117. errmsg = l_errmsg.
118.
119. write:/ 'ERROR CODE : ', l_errcode.
120. write:/ 'ERROR MESSAGE : ', l_errmsg.
121.
122. l_string = p_fpex->get_text( ).
123. write:/ l_string.
124.
125. endform.
126.
127.
128. form load_file using p_filename type string
129. changing p_content type xstring.
130. data: l_rawtab type ty_tab,
131. l_len type i.
132.
133. call method cl_gui_frontend_services=>gui_upload
134. exporting
135. filename = p_filename
136. filetype = 'BIN'
137. importing
138. filelength = l_len
139. changing
140. data_tab = l_rawtab
141. exceptions
142. file_open_error = 1
143. file_read_error = 2
144. no_batch = 3
145. gui_refuse_filetransfer = 4
146. invalid_type = 5
147. no_authority = 6
148. unknown_error = 7
149. bad_data_format = 8
150. header_not_allowed = 9
151. separator_not_allowed = 10
152. header_too_long = 11
153. unknown_dp_error = 12
154. access_denied = 13
155. dp_out_of_memory = 14
156. disk_full = 15
157. dp_timeout = 16
158. not_supported_by_gui = 17
159. error_no_gui = 18
160. others = 19.
161. if sy-subrc <> 0.
162. message id sy-msgid type sy-msgty number sy-msgno
163. with sy-msgv1 sy-msgv2 sy-msgv3 sy-msgv4.
164. endif.
165.
166. perform convert_tab_to_x using l_rawtab l_len
167. changing p_content.
168.
169. endform.
170.
171.
172. form convert_tab_to_x using p_rawtab type ty_tab
173. p_len type i
174. changing p_xstr type xstring.
175. data: l_line type ty_raw,
176. l_count type i,
177. l_len type i,
178. l_rest type i.
179.
180. describe table p_rawtab lines l_count.
181.
182. loop at p_rawtab into l_line.
183. if sy-tabix = l_count.
184. l_rest = p_len - l_len.
185. concatenate p_xstr l_line(l_rest) into p_xstr in byte mode.
186. else.
187. concatenate p_xstr l_line into p_xstr in byte mode.
188. add 255 to l_len.
189. endif.
190. endloop.
191.
192. endform.
Good Luck!
Pablo
0 likes
Former Member replied
March 16, 2007 at 11:50 AM
Hello,
Please anyone can help me include automatically (in the server-side) digital signature in pdf Forms (using
the Adobe Document Service). I know this is possible but I can’t find any documentation about the
system configuration.
thanks
Nuno Abrantes
0 likes
I have done some research regarding Adobe signatures but I am not arriving at desired conclusion.
Request your help.
Requirement: Client currently signs PDF forms using dongle provided by third party services like E-Mudra.
At the time of signing the PDF, client needs to enter pin code. Only on entering the correct pin code, the
PDF gets signed. Can this be accomplished in SAP ? I need to get the Adobe forms signed automatically
from SAP using the same signature.
From what I know, following will be the process for digitally signing Adobe forms. Please confirm.
1. Get the license for Adobe Interactive forms ( mandatory ) as the signature field is interactive one.
* set document
call method l_pdfobj->set_document
* set signature
call method l_pdfobj->set_signature
exporting
keyname = s_key
fieldname = s_field
reason = s_reason
location = s_loc
contactinfo = s_cinfo.
3. Is the keyname, which is passed in l_pdfobj->set_signature, an encoded key? If yes, how can it be
obtained?
6. As client is entering pin code to digitally sign the document, nobody else can sign the document even if
dongle is available with the person ( as pin code is not known ). Can this be covered in SAP? As per my
understanding, client will have to continue with the current process.
Thanks,
Sanket
Tags:
interactive
adobe
adobe_form
digital_signature
sap_interactive_forms_by_adobetagssap
pdf