Documente Academic
Documente Profesional
Documente Cultură
Copyright 2011 Accenture All Rights Reserved. Accenture, its logo, and High Performance Delivered are trademarks of Accenture.
Agenda
Abstract Disadvantages SmartForms/Adobe Print Forms MetaNet/InfoNet Transactions (HRFORMS/SFP) LiveCycle Designer
Fundamentals Workbench Accessibility Performance
Abstract
Abstract SAP Interactive Forms by Adobe SAP Interactive Forms by Adobe became available with the Releases SAP ERP HCM 6.0 and SAP Netweaver 7.0 Future development in the area of forms will be based on SAP Interactive Forms Adobe LiveCycle Designer (WYSIWYG-Editor) can be used to create forms Transactions to access the LiveCycle Designer
HRFORMS HR Forms Workplace SFP Form Builder: Entry Point
Abstract SAP Interactive Forms by Adobe Following forms can be created using the LiveCycle Designer Interactive Forms: The contained fields are ready for input. Users can fill in the fields on the computer. Print Forms: The contained fields can not be edited. The information in the form can be accessed dynamically, e. g. Payslip.
Abstract SAP Interactive Forms by Adobe Within HRForms you can open and edit Adobe Forms as well as SmartForms Accessibility by creating a PDF-Based Form, Adobe creates tags within the form which can be recognized by a screenreader Required Interface, ABAP Dictionary Structure as well as Print program will be created automatically by activating the form ADS Adobe Document Services are required to generate the forms
Disadvantages Adobe PrintForms The Adobe LiveCycle Designer o Is a Windows application which is embedded in SAP o Takes a couple of seconds to get started o Has to be installed seperately o Data-Dictionary-Objects can not be shown due to double-click in SE11 A Java-Stack has to be installed and configurated Complex code has to be implemented using JavaScript or FormCalc ADS needs to be installed on sophisticated hardware
Copyright 2011 Accenture All Rights Reserved. 8
Disadvantages SmartForms Accessibility SmartForms are not barrier-free, they can`t be read with a screenreader SmartForms are also supported in the near future but the main part of future developments are based on Adobe PDF-fields can not configured to be ready for input Graphics can not be embedded, they have to be loaded from an application server Text can not be rotated Forms can not be signed digitally PDF preview within the form is not available
Copyright 2011 Accenture All Rights Reserved. 9
Architecture SmartForms
10
11
MetaNet/InfoNet
MetaNet/InfoNet MetaNet can be accessed using the HR Metadata Workplace (Transaction: HRFORMS_METADATA) The MetaNet provides the data which can be used/read in the created form The data is organized/described within fields, structs, tables All required data are defined in Metadata Workplace and contained in the MetaNet MetaNet can be specified for different countries
13
MetaNet/InfoNet Custom structs or data can be added to the MetaNet useful by using custom Infotypes and/or tables The specific data which is used within a form is organized by using a InfoNet The InfoNet is a part of the data contained in the MetaNet data can be added to the InfoNet due Transaction HRFORMS
14
MetaNet/InfoNet
MetaFields: Perform either as keys or attributes of a MetaDimension MetaFigures: Are indicators which are used within MetaStars
16
MetaNet/InfoNet MetaDimensions: Exists of MetaFields which either perform as a key or a attribut of a MetaDimension MetaStars: Exists of MetaDimensions and MetaFigures
17
MetaNet/InfoNet adding field of infotype Description: In this case the field of payee (Infotype 0009) will be added to the MetaNet 01. Transaction: HRFORMS_METADATA 02. Create a copy of the SAP_DEFAULT MetaNet 03. Create a new MetaDimension 04. Fill in the required Fields
Create Field
18
MetaNet/InfoNet adding field of infotype 06. Fill in the required Fields (EMFTX is the Field Name shown in the Technical Information)
19
MetaNet/InfoNet adding field of infotype 08. Field EMFTX has to be changed to Key Field
20
MetaNet/InfoNet adding field of infotype 11. Add the following information in the required fields:
12. Add the MetaDimension via drag and drop to the MetaStar. The result looks like:
21
MetaNet/InfoNet adding field of infotype 13. Select the MetaStar add the field which has to be read: and
Finally the MetaStar has to be added to the MetaNet via drag and drop and MetaNet has to be saved
Copyright 2011 Accenture All Rights Reserved. 22
Transactions (HRFORMS/SFP)
Transactions (HRFORMS/SFP) Opening a Form with HRFORMS leads to the following Screen:
24
Transactions (HRFORMS/SFP) Opening a Form with SFP leads to the following Screen:
25
Transactions (HRFORMS/SFP) The entry screen of Transaction SFP is the same screen as the next screen of Transaction HRFORMS using the -Button From here, the following areas can be accessed: Properties: Gives access to the Interface where custom code can be added manually Context: Shows the imported data and the data which is available to be used within the form Layout: Opens the LiveCycle Designer
Copyright 2011 Accenture All Rights Reserved. 26
Transactions (HRFORMS/SFP) The Context allows you to add the following amongst other things: Where Conditions
Conditions
27
Fundamentals LiveCycle Designer It is available as an application of its own as well as an application embedded in SAP GUI First Version 6.0 was released in 2004 Graphical WYSIWYG Tool The generated forms are based on XFA (XML Forms Architecture) Available scripting languages JavaScript
PostScript
Fundamentals - XML XML = Extensible Markup Language Standard for the modelling of structured data in a tree structure Tags for the description of the data structure can be self-defined An XML scheme (also known as: Document Type Definition, DTD) describes the elements within an XML-Dokument formally XML within LiveCycle Designer should not be edited manually
30
Script Editor
Object Properties
32
33
34
35
36
37
INFO: It is also possible to edit only the Caption or only the Value. The part which has to be formated must be selected in each of the windows
39
INFO: It is a very convenient way to organize objects within a Subform or to delete a Subform, Insert a New Master Page, etc.
40
Adobe LiveCycle Designer Accessibility Text which has to be read by the screenreader can be defined
Therefor a tagged PDF form has to be created (saving the form design as a PDF file)
The default behaviour in LiveCycle Designer is the creation of tagged PDF forms The applied tagging for accessibility increases the file size, thereby the performance gets reduced the form objects should be chosen very carefully
41
Adobe LiveCycle Designer Accessibility Related information should be combined by using subforms The form layout should be kept in mind by defining the order of the elements (left to right, top to bottom) Try to avoid problems by using default colors for text and background It is not possible for screen readers to read texts highlighted by s p a c i n g between individual letters Only use simple tables instead of complex tables
43
Performance Fonts:
Try to keep the number of fonts to a minimum
44
INFO: ADS performs two tasks and is the runtime component of the solution: