HR280_EN_Col92_FV_Ltr
Short Description
HR280_EN_Col92_FV_Ltr...
Description
HR280 Smart & Adobe Forms in HCM
THE BEST-RUN BUSINESSES RUN SAP © SAP AG 2009
© SAP AG 2009
SAP ERP Course version 92 Material number 50093950
For internal use by CSC only
For internal use by CSC only
HR280 Smart & Adobe Forms in HCM
Copyright
No part of this publication may be reproduced or transmitted in any form or for any purpose without the express written permission of SAP AG.
© SAP AG 2008
Some of the software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Microsoft, Windows, Excel, Outlook and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, System i, System i5, System p, System p5, System x, System z, System z9, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, POWER5+, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation. Adobe, the Adobe logo, Acrobat, PostScript and Reader are trademarks or registered trademarks of Adobe Systems Incorporated in the USA and/or other countries. Oracle is a registered trademark of Oracle Corporation. UNIX, X/Open, OSF/1 and Motif are registered trademarks of Open Group. Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame and MultiWin are trademarks or registered trademarks of Citrix Systems, Inc. HTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium, Massachusetts Institute of Technology. Java is a registered trademark of Sun Microsystems, Inc.
For internal use by CSC only
For internal use by CSC only
Copyright 2008 SAP AG. All rights reserved.
JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology developed and implemented by Netscape. MaxDB is a trademark of MySQL AB, Sweden.
The information contained in this document is the copyrighted property of SAP AG. No part of this document may be reproduced or transmitted in any form or for any purpose without the express written permission of SAP AG. This document is a preliminary version and it is not subject to your license agreement or any other agreement with SAP. The information contained in this document describes projected strategies, developments and functions of the SAP® product only, and in no way represents an obligation on the part of SAP AG to follow a particular company plan, a particular product strategy and/or particular development work. Note that this document is subject to change and SAP can make changes at any time without notice. SAP assumes no responsibility for errors or omissions in this document. SAP assumes no responsibility for errors or omissions in the information, texts, graphics, links or other elements of this material. This document is provided without a warranty of any kind, either express or implied. This applies to (among other things) the fitness for a particular purpose or to exclusion of rights violations. SAP assumes no responsibility for damages of any kind. These include (among other things), direct, special, indirect or consequential damages that arise from using these materials. These limitations shall not apply in cases of intent or gross negligence. The statutory liability for personal injury and defective products is not affected. SAP cannot control the information that you access using the links contained in this document. Furthermore, SAP assumes no responsibility if you visit such third-party websites or for any set of circumstances involving third-party websites.
For internal use by CSC only
For internal use by CSC only
SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned here are the trademarks of their respective owners. Data contained in this document is used for information purposes only. Product specifications may vary from country to country.
Course Content
Unit 1
HR Metadata Workplace
Unit 2
HR Forms Workplace
Unit 3
Adobe Interactive Forms in SAP ERP 6.0 – Overview
Unit 4
Adobe Interactive Forms in SAP ERP 6.0 – Technical Part
Unit 5
Adobe Interactive Forms in SAP ERP 6.0 – Practical Part Appendix
© SAP AG 2008
For internal use by CSC only
For internal use by CSC only
Preface
HR Metadata Workplace
Overview of HR Forms Workplace
HR Metadata Workplace
For internal use by CSC only
For internal use by CSC only
Contents:
© SAP AG 2008
© SAP AG
HR280
1-1
Overview of HR Metadata Workplace: Unit Objectives
Explain the process of creating HR forms and the HR metadata model
Enhance the HR metadata model to provide additional HR data for the purpose of creating forms
For internal use by CSC only
For internal use by CSC only
At the conclusion of this unit, you will be able to:
© SAP AG 2008
© SAP AG
HR280
1-2
Overview of HR Metadata Workplace: Business Scenario
You would like to recreate the form for the remuneration statement with HR Forms to include the weekly and monthly working times from the planned working time infotype.
For internal use by CSC only
For internal use by CSC only
© SAP AG 2008
© SAP AG
HR280
1-3
Overview of HR Forms Workplace: Unit Overview Diagram
Unit Heading Lesson 1: Overview of HR Forms Workplace
For internal use by CSC only
For internal use by CSC only
Lesson 2: HR Metadata Workplace
© SAP AG 2008
© SAP AG
HR280
1-4
Overview of HR Forms Workplace: Unit Objectives
Describe the process of creating HR forms
Explain the MetaNet as a view of the printable data
For internal use by CSC only
For internal use by CSC only
At the conclusion of this lesson, you will be able to
© SAP AG 2008
© SAP AG
HR280
1-5
Overview of HR Forms Workplace: Business Scenario
You would like to recreate the form for the remuneration statement with HR Forms. To do this, you first need an overview of this tool. For internal use by CSC only
For internal use by CSC only
© SAP AG 2008
© SAP AG
HR280
1-6
HR Data Sources
z Master data
For internal use by CSC only
For internal use by CSC only
z Payroll z Time management z Other HR appl. z Function modules
© SAP AG 2008
The payroll form is created on the basis of the payroll results. This means that it is possible reprint remuneration statements that have already been created as often as required for previous payroll periods. The standard form is called SAP_PAYSLIP. Customer forms must always begin with the letter Z.
© SAP AG
HR280
1-7
The Process of Creating HR Forms
HR Form
Data selection and data retrieval with the Forms Workplace
Form logic and layout with SAP Smart Forms (Form Builder)
For internal use by CSC only
For internal use by CSC only
Catalog of international and country-dependent data sources
Smart Form InfoNet
MetaNet
MetaStar1
MetaStar2
MetaStar3
InfoStar1
InfoStar3
© SAP AG 2008
There are three basic steps in the process of creating a form: 1. Compile a catalog containing the required data from the master data and the payroll and time evaluation results 2. Select data from the catalog to be used in the forms 3. Prepare and arrange the graphical layout of the data selected You use the HR Metadata Workplace for the first step and the HR Forms Workplace for the second. You can arrange the graphical layout with SAP Smart Forms. The following two fundamental approaches can be taken when creating forms: You can create a new form from scratch or copy an existing form from the SAP standard delivery and adapt it to suit your requirements.
© SAP AG
HR280
1-8
MetaNet
MetaDimension1
MetaNet
MetaDimension3
MetaStar 1
MetaFields
MetaFields
For internal use by CSC only
MetaDimension4 MetaDimension2
For internal use by CSC only
MetaDimensions MetaFigures
MetaStar 2
MetaFields MetaDimensions MetaFigures
MetaFields
MetaStar 3 MetaDimensions
MetaDimension5 MetaFields
© SAP AG 2008
The MetaNet is a view showing the printable data in the ERP system. A MetaNet comprises all HR data sources that can be used in the process of creating forms and is provided by SAP for the remuneration statement. All data to be included on a form must be contained in the MetaNet. The metadata in the MetaNet describes the printable HR data and the way in which this data is retrieved in the form of a catalog. You can edit this catalog with the HRFORMS_METADATA transaction. You define this metadata and save all required reading information in the Metadata Workplace. This information is used at a later stage to generate the Data Dictionary structures on an HR form. Each country has its own view of this data in HR since each country has its own country-specific data sources. Every country version contains the international part of the MetaNet. The SAP_DEFAULT MetaNet is provided in the standard delivery.
© SAP AG
HR280
1-9
MetaStar
MetaDimension
Key
MetaFields
MetaFields
MetaStar Key
Key Key
Key
MetaDimensions
MetaFigures
MetaDimension
Key
For internal use by CSC only
For internal use by CSC only
Key
MetaDimension
MetaDimension
Key
MetaFields
MetaFields
© SAP AG 2008
A MetaNet, together with its MetaStars, forms the catalog that contains all of the data used to create forms. It is a view of the data that can be read from a particular data source in the ERP system. A MetaStar contains information revealing where the data comes from and how it has to be read. In the simplest case, the data is read directly from table fields. In most cases, however, reading the information is more complicated and function modules are used. For example, one MetaStar might contain payroll payments/deductions, while another contains data pertaining to the absence type. It is both advisable and feasible to have different MetaDimensions for each of these MetaStars. For deductions, for example, the type of deduction (taxes or benefits-related deductions), and for the absence type, when the absence occurred and the amount that was paid to cover it.
© SAP AG
HR280
1-10
MetaDimension
For internal use by CSC only
For internal use by CSC only
MetaStar
MetaDimensions MetaFigures
© SAP AG 2008
MetaDimensions and MetaFigures are used to describe a MetaStar. A MetaDimension is a full description of a business object or concept and comprises MetaFields,which are either key fields or attribute fields. MetaDimensions and MetaFigures with their relationships make up a MetaStar and can be used in several MetaStars. For example, the EMPLOYEE MetaDimension contains an employee's personnel number, name, address, and date of birth, while the WAGETYPE MetaDimension contains wage type data.
© SAP AG
HR280
1-11
MetaFigure
For internal use by CSC only
For internal use by CSC only
MetaStar
MetaDimensions MetaFigures
© SAP AG 2008
A MetaFigure is a key figure that can be used in several MetaStars. When a key figure is connected to a unit, this unit is also part of the MetaFigure, for example an amount with currency (5 USD). MetaFigures and MetaDimensions with their relationships make up a MetaStar and can be used in several MetaStars.
© SAP AG
HR280
1-12
Overview of HR Forms Workplace: Summary
Describe the process of creating HR forms
Explain the MetaNet as a view of the printable data
For internal use by CSC only
For internal use by CSC only
You are now able to:
© SAP AG 2008
© SAP AG
HR280
1-13
HR Metadata Workplace: Unit Overview Diagram
Unit Overview Lesson 1: Overview of HR Forms Workplace
For internal use by CSC only
For internal use by CSC only
Lesson 2: HR Metadata Workplace
© SAP AG 2008
© SAP AG
HR280
1-14
HR Metadata Workplace: Lesson Objectives
At the conclusion of this lesson, you will be able to Enhance the HR metadata model to provide additional HR data for the purpose of creating forms For internal use by CSC only
For internal use by CSC only
© SAP AG 2008
© SAP AG
HR280
1-15
HR Metadata Workplace: Business Scenario
The weekly and monthly working times from the planned working time infotype are to be included in the remuneration statement. For internal use by CSC only
For internal use by CSC only
© SAP AG 2008
© SAP AG
HR280
1-16
For internal use by CSC only
For internal use by CSC only
HR Metadata Workplace
© SAP AG 2009
If you create your own MetaNet, define that the MetaStars are inherited from the SAP_DEFAULT MetaNet. In this case, any changes to the SAP_DEFAULT MetaNet are also transferred to your MetaNet. You process the MetaNet and the meta objects presented earlier with the HR Metadata Workplace. The metadata is displayed there in four overview trees: • MetaFigures • MetaDimensions • MetaStars • MetaNets You can hide trees and any settings you have changed remain intact. You have to display hidden trees again the next time you call the Metadata Workplace if required. If you want to enhance the metadata, copy the SAP standard MetaNet for your country to the customer namespace. Alternatively, you can create a new MetaNet that inherits the MetaStars from the standard MetaNet. Note: When you are maintaining metadata, the transaction is locked for all other users since the objects are dependent on each other.
© SAP AG
HR280
1-17
CUMULATED_PAY MetaStar Legend
Key field Attribute field
For internal use by CSC only
For internal use by CSC only
Inherited object
© SAP AG 2008
Here, you can see the CUMULATED_PAY MetaStar (cumulated payroll results) in the forth column as part of the ZHR280 MetaNet. The MetaDimensions that make up the CUMULATED_PAY MetaStar can be seen in the MetaStars column. The WAGETYPE MetaDimension consists of the COUNTRY and WAGETYPE key fields and the LONGTEXT and SHORTTEXT attribute fields (see also the MetaDimensions column), as well as the PAY_AMOUNT and PAY_NUMBER MetaFigures.
© SAP AG
HR280
1-18
For internal use by CSC only
For internal use by CSC only
MetaStar Types (1)
© SAP AG 2008
A MetaStar is attributed a particular type. The CUMULATED_PAY MetaStar has type Payroll. For each type, different reading information is required to generate the program. If a MetaStar is used in a form, an internal table is created for the MetaStar when the print program is generated. The line structure specified determines the structure of the internal table of the print program. Once the print program has filled the table with the function module specified in the Read Function field, it has to read the MetaDimensions and MetaFigures from each row of the table. You specify the information required here on the MetaDimensions, MetaFields, and MetaFigures tab pages.
© SAP AG
HR280
1-19
For internal use by CSC only
For internal use by CSC only
MetaStar Types (2)
© SAP AG 2008
Depending on the MetaStar type, further information may be required to read the data. In the case of the Master data type, data is read directly from the infotype using the HR_READ_INFOTYPE function module. These MetaStars, as well as those of the Time Evaluation Data type, are filled and processed in the print program at the time of GET PERNR. MetaStars of the Payroll type are filled and processed on the basis of the payroll results at the time of GET PAYROLL. Person-dependent data that does not belong to master data or payroll data is identified with Special type A. Special type U is used for data that is not person-dependent. It is read at the time of START-OFSELECTION.
© SAP AG
HR280
1-20
For internal use by CSC only
For internal use by CSC only
MetaDimensions and MetaFields
© SAP AG 2008
MetaDimensions and MetaFigures are used to describe a MetaStar (the CUMULATED_PAY MetaStar has been selected in the example above). The MetaDimension is the full description of a business object or concept. A MetaDimension can be used in more than one MetaStar. The MetaDimension consists of several information fields known as MetaFields. A MetaField is either a key field of a MetaDimension or an attribute that constitutes a further property of the MetaDimension.
© SAP AG
HR280
1-21
For internal use by CSC only
For internal use by CSC only
MetaFields and MetaFigures
© SAP AG 2008
The MetaFigure is a key figure that can be used in several MetaStars. If it is connected to a unit, this unit is also part of the MetaFigure. The tables created on the basis of the MetaStar are filled in the generated print program through the COLLECT ABAP statement. If the Cumulate Values indicator has been set, the values are cumulated if the key fields of the internal table are the same. If this indicator has not been set, the MetaFigure is treated as a key field of the table, that is to say, different values in this MetaFigure result in separate rows in the table.
© SAP AG
HR280
1-22
For internal use by CSC only
For internal use by CSC only
Create Customer-Specific MetaDimension (1)
© SAP AG 2008
To provide additional information in the MetaNet, you want to include the working times (per week and per month) from infotype 0007. You want this information to be included in the MetaNet as a customerspecific MetaStar. First, you need a MetaDimension with the required information from infotype 0007. This can be created directly from the metadata overview screen. The MetaDimension for the start and end date is already defined in the standard delivery as DATE_RANGE. Since the information is obtained from the master data, a function module is not needed to read the data. If the Always Read w/ MetaStar indicator has been set, the attributes of the MetaDimension are filled when the MetaStar is read. However, this is not necessary if the key of the MetaDimension has been created correctly.
© SAP AG
HR280
1-23
For internal use by CSC only
For internal use by CSC only
Create Customer-Specific MetaDimension (2)
© SAP AG 2008
You can create MetaFields by right-clicking on the MetaDimension (see the context menu above). You can then see what you have created on the MetaFields tab page. Fields ZWT_MOSTD and ZWT_WOSTD have been created. You must then specify a data element for each of the new fields in the Field Type column. In the example above, the data elements MOSTD and WOSTD have been specified. This entry results in both fields being defined as key fields. If you create your own MetaDimensions, define whether a field is a key field or an attribute (click on the icon in the Key column). There are two options for key fields: a) Validity of selection options: This allows you to define whether all possible uses of a given dimension are to be linked to the same selection conditions in the form or not. You can enter global (InfoNet-wide) or local here. b) Restrictions for selection options: This allows you to permit multiple or individual selections or prevent all selections.
© SAP AG
HR280
1-24
For internal use by CSC only
For internal use by CSC only
Create Customer-Specific MetaStar (1)
© SAP AG 2008
The Master data routines are used to read data from the customer-specific MetaStar for the specified infotype 0007.
© SAP AG
HR280
1-25
For internal use by CSC only
For internal use by CSC only
Create Customer-Specific MetaStar (2)
© SAP AG 2008
You assign the DATE_RANGE standard MetaDimension and customer-specific ZWT_0007 to the customer-specific MetaStar that has already been created by means of drag and drop. In addition, you have to assign the MetaFields with the read infotype's table fields, which can be selected from the input help shown.
© SAP AG
HR280
1-26
For internal use by CSC only
For internal use by CSC only
Enhance MetaNet with Your Own MetaStar
© SAP AG 2008
Copy your MetaStar to the MetaNet by means of drag and drop to enhance it with the required data from infotype 0007.
© SAP AG
HR280
1-27
HR Metadata Workplace: Summary
You are now able to: Enhance the HR metadata model to provide additional HR data for the purpose of creating forms. For internal use by CSC only
For internal use by CSC only
© SAP AG 2008
© SAP AG
HR280
1-28
Overview of HR Metadata Workplace: Summary
Explain the process of creating HR forms and the HR metadata model.
Enhance the HR metadata model to provide additional HR data for the purpose of creating forms.
For internal use by CSC only
For internal use by CSC only
You are now able to:
© SAP AG 2008
© SAP AG
HR280
1-29
For internal use by CSC only
For internal use by CSC only
1-30
HR280
© SAP AG
HR Forms Workplace (1)
Create Form
Pages and Windows
Data on the Form
Texts on the Form
Tables and Templates
Flow Control
For internal use by CSC only
For internal use by CSC only
Contents:
© SAP AG 2008
© SAP AG
HR280
2-1
HR Forms Workplace: Unit Objectives
At the conclusion of this unit, you will be able to: Set up a form for the remuneration statement with different windows, a logo, and a flow logic to output retroactive accounting wage types
For internal use by CSC only
For internal use by CSC only
© SAP AG 2008
© SAP AG
HR280
2-2
HR Forms Workplace: Business Scenario
Your company wants to redesign the remuneration statement so that it has the company logo, employee's personal data, gross wage types, statutory deductions, and net wage types on it in a well arranged layout. The wage types that have resulted from retroactive accounting from the previous period are to be shown on a separate page.
For internal use by CSC only
For internal use by CSC only
© SAP AG 2008
© SAP AG
HR280
2-3
Create Form: Unit Overview Diagram
Unit Overview Lesson 1: Create Form
For internal use by CSC only
For internal use by CSC only
Lesson 2: Pages and Windows Lesson 3: Data on the Form Lesson 4: Texts on the Form Lesson 5: Tables and Templates Lesson 6: Flow Control
© SAP AG 2008
© SAP AG
HR280
2-4
Create Form: Unit Objectives
Create a form for the remuneration statement
Set up the InfoNet with selections
Control the selection of data
Create global data definitions
For internal use by CSC only
For internal use by CSC only
At the conclusion of this lesson, you will be able to
© SAP AG 2008
© SAP AG
HR280
2-5
Create Form: Business Scenario
Your company wants to redesign the form for the remuneration statement using the HR Forms Workplace. For internal use by CSC only
For internal use by CSC only
© SAP AG 2008
© SAP AG
HR280
2-6
Process Steps for Creating HR Forms HR Form
Catalog of international and country-dependent data sources
Data selection and data retrieval with the Forms Workplace
Form logic and layout with SAP Smart Forms (Form Builder)
InfoNet
Smart Form
MetaStar1
MetaStar2
MetaStar3
InfoStar1
For internal use by CSC only
For internal use by CSC only
MetaNet
InfoStar3
1. Select data 2. Generate an ABAP Dictionary structure 3. Create the SAP Smart Form 4. Generate the print program © SAP AG 2008
Select data First, you select and logically group (business-related grouping) the part from the MetaNet that is later to be printed on the form. The result is the InfoNet. Generate an ABAP Dictionary structure The HR Forms Workplace generates an ABAP Dictionary structure from the InfoNet containing the selected data. This structure will later act as an interface between the generated print program and SAP Smart Forms. Create the SAP Smart Form Next, you have to arrange the information from the generated ABAP Dictionary structure on the form and format it. The result is an SAP Smart Form. A function module is generated on the basis of this SAP Smart Form with the interface to the generated ABAP Dictionary structure. Form output is created from this interface using form logic. Generate the print program The HR Forms Workplace then generates a print program from the data structure and the SAP Smart Form. This program generates internal tables from the defined data structure, fills them with data from the system, and then calls the SAP Smart Form function module. The print program is an ABAP report that can be executed independently. Status management is performed in the HR Forms Workplace.
© SAP AG
HR280
2-7
Objects of an HR Form
Object
For internal use by CSC only
For internal use by CSC only
An HR form consists of several parts, which are shown here in an example of a customer-specific form called Zform: Name
InfoNet (form name)
Zform
ABAP Dictionary structure
/1pyxxfo/Zform
SAP Smart Form
zpyxxfo_Zform
Print program
/1pyxxfo/Zform_prnt
© SAP AG 2008
In the example here (form 'Zform'), the names shown above are generated for the individual objects. The objects and in particular the naming conventions are extremely important when you create a form manually. In this case, the names have to be altered in the right places. If you use the HR Forms Workplace to create a form, the individual names are altered automatically.
© SAP AG
HR280
2-8
Tools for Configuring the Form
SAP Smart Forms
Database
HR Forms selects the data to be printed from the database.
+
For internal use by CSC only
For internal use by CSC only
HR Forms
Data is prepared for printing in SAP Smart Forms.
© SAP AG 2008
The combination of HR Forms and SAP Smart Forms offers considerable benefits: • It is simpler to adapt a form, firstly because the tools offer more functions (for example, the SAP Smart Forms Table Painter allows you to create tables with great ease), and secondly because the interface between form and application program is better laid out. • You do not have to use special script language commands to realize particular requirements, for example additional data retrieval within the form. In addition, you can insert normal ABAP coding.
© SAP AG
HR280
2-9
HR Forms Workplace (2) The structure of the HR Forms Workplace is divided into three parts:
For internal use by CSC only
For internal use by CSC only
Initial screen with overview of all HR forms (HR Forms)
Maintenance screen for data structure (HR Forms)
Maintenance screen for layout (SAP Smart Forms)
© SAP AG 2008
You can call up the HR Forms Workplace with transaction HRFORMS. In the HR Forms Workplace, you select the data to be printed from HR. You design the layout in SAP Smart Forms, which you can call up directly from HR Forms by choosing the Layout button.
© SAP AG
HR280
2-10
For internal use by CSC only
For internal use by CSC only
HR Forms Workplace: Initial Screen
© SAP AG 2008
All HR forms are displayed on the initial screen with the SAP List Viewer. Each line in the table represents an HR form. Each form has a name, a status, and information about changes. The status is also indicated by a symbol at the start of the line. The symbols have the following meaning: • Red – inactive form • Green – active form You can change the appearance of the initial screen: • Show or hide columns containing information • Set filters • Sort the HR forms You can save such changes in a layout to be reused.
© SAP AG
HR280
2-11
HR Forms Workplace: Data Structure
InfoNet MetaNet
InfoNet tree data to be printed
InfoDimension
For internal use by CSC only
For internal use by CSC only
InfoStar
MetaStar InfoFigure MetaDimension
Detailed information about InfoNet tree MetaFigure
MetaNet tree data to be provided for the purpose of printing © SAP AG 2008
You choose the data that is required on the form from the overview tree of the MetaNet. To do so, select the MetaStars, MetaDimensions, and MetaFigures in the MetaNet overview tree. You can then move the selected objects to the right-hand side of the screen into the InfoNet overview tree by means of drag and drop. In this way, the objects corresponding to the objects in the MetaNet are created in the InfoNet. The InfoNet overview tree contains the data that you have selected to be printed. You can arrange this data on the form and add formatting at a later stage. Additional information is provided on the individual tab pages for each node in the overview tree. The MetaNet is a technical grouping, while the InfoNet is a business-related grouping of available data. The InfoStars tab page provides an overview of the InfoStars contained in the InfoNet of the form as well as the MetaStars used to create them.
© SAP AG
HR280
2-12
For internal use by CSC only
For internal use by CSC only
Create the InfoNet
© SAP AG 2009
You create the InfoNet in the HR Forms Workplace editor. Using drag and drop, you move the required data (MetaStars, MetaDimenions, MetaFields, and MetaFigures) from the MetaNet to the InfoNet of the new form. The statuses for the DDIC structure, the SAP Smart Form, the print program, and the HR Form are still inactive at this time. InfoStars can contain the same InfoDimensions and InfoFigures. Their business significance varies on the basis of the wage types selected.
© SAP AG
HR280
2-13
For internal use by CSC only
For internal use by CSC only
Insert Selections
© SAP AG 2008
There are two ways to further restrict the data you have selected. • Variable selection, which is redefined every time the HR form is printed. • Fixed selection, which is specified when the form is designed. In the example form, select the payroll period and personnel numbers using the selection screen of the subsequent print program with variable selections. You can restrict the value area with the fixed selection by choosing the Insert Selection pushbutton. In the form shown here, the wage types to be printed are restricted to /101 (total gross), /559 (bank transfer), and the wage type range from M000 to M400. By choosing the Layout pushbutton, you exit HR Forms and enter SAP Smart Forms. At the same time, the ABAP Dictionary structure is generated and the Smart Form created. Here, you save the new (empty) Smart Form and activate it. Exit the Smart Form editor with the Back function and return to the HR Form editor. Choose Activate. Upon successful activation, the following three parts become active: • ABAP Dictionary structure • Smart Form • Print program © SAP AG
HR280
2-14
For internal use by CSC only
For internal use by CSC only
HR Form Attributes
© SAP AG 2009
You can find and enter general information on the HR Form tab page. This is where the form class is specified (remuneration statement, time statement, other forms), and also where you choose the layout editor to be used. If you choose flat structure in the Star Structuring field, the InfoStar tables also contain attribute fields. This means you do not have to execute LOOP statements to represent associated data. The HR Forms Workplace executes these automatically after it has read the data. The InfoDimension tables are available in both layout editors but are no longer required for the form. This considerably simplifies the process of creating a form. In the Form Parts area, you can see the names and generation status of the previous mentioned HR form objects. Here, the following steps have already been performed successfully: Creation of the ABAP Dictionary structure (takes place when layout editor is called), form definition, and print program. You can make adjustments to the selection screen on the Select. Screen tab page. If the form class is a time statement, you can select a report class here.
© SAP AG
HR280
2-15
For internal use by CSC only
For internal use by CSC only
Verify the Data Selection
© SAP AG 2008
Once you have created the InfoNet and activated everything, choose Form → Print Program (Test), to start the program and to check the data selection. The print program selection screen appears. Use an employee with payroll results and choose Execute. An overview tree containing the generated internal tables appears on the left-hand side and the table content is displayed on the right. The example on the slide shows the relationships between the star and dimensions tables. You can see the STAR_PAY_RESULT table with the amounts. Each amount is characterized by the EMPLOYEE, INPERIOD, and WAGETYPE dimensions.
© SAP AG
HR280
2-16
SAP Smart Forms: Form Interface
For internal use by CSC only
For internal use by CSC only
Field list
HR interface
© SAP AG 2008
When an application program calls up an SAP Smart Form (or rather, the generated function module of the form), it must be possible to communicate with it. Data must be sent to the form and be returned by form to the calling program. All data is exchanged through the interface of the form. You define the interface in the global settings of the Form Builder. All parameters of the interface are global, which means they are recognized in all nodes of the form. The HRDATA parameter can be found under the Form Interface node. This parameter represents the HR data selected. The other parameters are predefined by SAP Smart Forms. They contain print and archiving parameters. The associated type of the HRDATA parameter is the generated ABAP Dictionary structure of HR Forms. The structure name consists of the namespace /1PYXXFO/ and the name of the HR form. In this case, the name is /Z99_PAYSLIP. Choose Field list on/off to display the ABAP Dictionary structure as an overview tree. You can use drag and drop to select fields to be printed from this list during subsequent processing steps.
© SAP AG
HR280
2-17
For internal use by CSC only
For internal use by CSC only
SAP Smart Forms: Global Definitions
© SAP AG 2008
Here, you define the work areas required in form processing as line types of the tables. These are filled in a loop and output on the form. The work area variables (WA_...) for use within the form relate to the structure of the HR form. Typing must relate to the dictionary structure generated. The name of the structure follows the naming convention /1pyxxfo/Zform, with Zform standing for the name of the form you have created. It is useful to call up the generated dictionary structure (SE11) in a separate session when you are creating the global definitions. That way, you can see the names of the components that you want to use (STAR_name or DIM_name). Variables entered on the Global Data tab page are recognized in the entire form and can, for instance, be used as work areas of tables or loops. You can check your entries with the Check pushbutton.
© SAP AG
HR280
2-18
Create Form: Summary
Create a form for the remuneration statement
Set up the InfoNet with selections
Control the selection of data
Create global data definitions
For internal use by CSC only
For internal use by CSC only
You are now able to:
© SAP AG 2008
© SAP AG
HR280
2-19
For internal use by CSC only
For internal use by CSC only
2-20
HR280
© SAP AG
Exercises Unit: HR Forms Workplace Lesson: Create Form At the conclusion of this exercise, you will be able to: For internal use by CSC only
• Set up the InfoNet with selections • Control the selection of data • Create global data definitions Your company wants to redesign the form for the remuneration statement using HR Forms.
1-1
1-2
Create a new form by copying the template called ZHR280_G00_EXE1. Call your form ZHR280_G##_EXE1 (## = group number). 1-1-1
Create an InfoStar called PAY_RESULT with InfoDimensions EMPLOYEE, FORPERIOD, and INPERIOD.
1-1-2
Create an InfoStar called PAY_RETRO (retroactive accounting wage types) with InfoDimensions EMPLOYEE, EVALCLASS02, FORPERIOD, INPERIOD, WAGETYPE, and InfoFigures PAY_AMOUNT, PAY_NUMBER, and PAY_RATE.
Create selections for wage types. 1-2-1
1-3
Create the global definitions required for form processing. 1-3-1
1-4
In the PAY_NET InfoStar, add the following selections for the WAGETYPE InfoDimension: /110, /550, /551, /552, and /560.
Add the WA_RESULT and WA_RETRO work areas and generate the form.
Test the form and check the data selected. 1-4-1
© SAP AG
Test the form with the payroll period, payroll area, and personnel number provided by your instructor.
HR280
2-21
For internal use by CSC only
• Create a form for the remuneration statement
For internal use by CSC only
For internal use by CSC only
2-22
HR280
© SAP AG
Solutions Unit: HR Forms Workplace Lesson: Create Form
Create a new form by copying the template called ZHR280_G00_EXE1. Call your form ZHR280_G##_EXE1 (## = group number). Call up transaction HRFORMS by entering it in the command field. Select the copy template and copy it as a local object.
1-2
1-1-1
Open the PAY_RESULT MetaStar in the MetaNet and move it to the InfoNet by drag and drop. Copy the MetaDimensions specified by clicking on them in the MetaNet and moving them to the PAY_RESULT InfoStar by drag and drop.
1-1-2
Click on the PAY_RESULT MetaStar in the MetaNet and move it to the InfoNet again by drag and drop. Click on the PAY_RESULT1 InfoStar, go to the InfoStar tab page, and enter PAY_RETRO as the new name in the InfoStar field. Enter Retroactive Accounting Wage Types as the description. Copy the MetaDimensions and MetaFigures specified by clicking on them in the MetaNet and moving them to the PAY_RETRO InfoStar by drag and drop.
Create selections for wage types. 1-2-1
© SAP AG
In the InfoNet, open the PAY_NET InfoStar and click on the WAGETYPE InfoDimension. Choose Insert Selection in the context menu and enter the specified wage types on the Selections tab page.
HR280
2-23
For internal use by CSC only
For internal use by CSC only
1-1
1-3
Create the global definitions required for form processing. 1-3-1
Choose layout processing for the form (Layout pushbutton). Double-click on Global Definitions in the Global Settings folder. Make the entries listed in the table below.
Field Name or File Type
Entries
WA_RESULT
TYPE LINE OF /1PYXXFO/ZHR280_G##_EXE1STAR_PAY_RESULT
WA_RETRO
1-4
TYPE LINE OF /1PYXXFO/ZHR280_G##_EXE1STAR_PAY_RETRO
Test the form and check the data selected. Choose menu path Form → Print Program (Test) in the Change HR Forms view. 1-4-1
© SAP AG
On the selection screen, enter the payroll period, payroll area, and personnel number provided by your instructor. Choose Execute. Take a look at the data for one of the entries in the ALV list, for example the DIM_WAGETYPE component.
HR280
2-24
For internal use by CSC only
For internal use by CSC only
Check the form in the SAP Form Builder and activate it if there are no errors. Exit the Form Builder and activate your form in the Change HR Forms view.
Pages and Windows: Unit Overview Diagram
Unit Overview Lesson 1: Create Form
For internal use by CSC only
For internal use by CSC only
Lesson 2: Pages and Windows Lesson 3: Data on the Form Lesson 4: Texts on the Form Lesson 5: Tables and Templates Lesson 6: Flow Control
© SAP AG 2008
© SAP AG
HR280
2-25
Pages and Windows: Unit Objectives
Create secondary windows with the Form Painter
Insert a graphic with the company logo
Test the form
For internal use by CSC only
For internal use by CSC only
At the conclusion of this lesson, you will be able to
© SAP AG 2008
© SAP AG
HR280
2-26
Pages and Windows: Business Scenario
The personal data of the employee is to appear in a window with a box on the remuneration statement form. The company logo is to be included in top right corner of every page.
For internal use by CSC only
For internal use by CSC only
© SAP AG 2008
© SAP AG
HR280
2-27
SAP Smart Forms: Areas of the Form Builder
SAP Form Builder: Change Form ZPYXXFO_Z99_PAYSLIP Form Painter Form ZPYXXFO_PAYSLIP
Window
MAIN
Meaning
Main window
TITLE
For internal use by CSC only
For internal use by CSC only
Global Settings Pages and Windows FIRST First Page
Attributes
ADDRESS
EE_DATA
LOGO Company Logo MAIN Main Window TITLE Title
MAIN
Main window
HEADER Header ADDRESS Address EE_DATA Data NEXT Next Page
Navigation Tree
Maintenance Screen
Form Painter
© SAP AG 2008
The following pages about SAP Smart Forms provide details of the parts of the flow logic that are particular to HCM. The entire range of functions is covered in the BC470 training course. You use the graphical SAP Form Builder to edit forms using SAP Smart Forms. The SAP Form Builder consists of three areas: • The left area of the Form Builder is a navigation tree showing the hierarchy of all elements in the form, including the windows that can be seen on the right side of the Form Painter. Each form element is represented by a node in the navigation tree. These nodes guide how the form is processed; they are used to control all of the functions in the form. Below the navigation tree, you can also show the field list of variables. • The central area contains the maintenance screen, which shows the attributes of the node that is currently selected. This is also where the user normally enters data, for example text in the text editor or details of the layout of a table. The Table Painter is used for the latter. It cannot be seen in the example shown above. • The right area contains the Form Painter with a graphical overview of the layout of the current page. The separate areas in the Form Painter are the windows on the form. You use this area to design the layout of a page, for instance the position and size of text windows or graphics. You can also hide the Form Painter by choosing Utilities → Form Painter on/off. You can select a node for editing by double-clicking on it in the navigation tree or in the Form Painter. © SAP AG
HR280
2-28
The Navigation Tree Form ZPYXXFO_Z99_PAYSLIP Global Settings Form Attributes
For internal use by CSC only
For internal use by CSC only
Form Interface Global Definitions Pages and Windows FIRST First Page LOGO Company Logo MAIN Main Window
Three types of direct subnodes of a page
TITLE Title Subsequent node to LOGO © SAP AG 2008
All of the elements on a form are represented by a node in the navigation tree. Subnodes "inherit" attributes from higher-level nodes, for example their style. If a node is not processed, none of its subnodes are either. A subsequent node of a node, on the other hand, is dependent on the node that precedes it. It is processed sequentially after the preceding node. If a node has other subnodes, you can expand its structure by clicking on the triangle symbol beside the node icon. You can select a node for editing by double-clicking it. The system then displays the node in the maintenance screen and in the Form Painter (provided the Form Painter is activated). Below the top node, you always find the following two nodes: Global settings. These include: • Form attributes: For example, administration information and basic settings for formatting. • Form interface: The fields to be filled by the application program or returned to the application program must be defined here. • Global definitions: Here you can define additional fields to be used in the form. • Pages and Windows
© SAP AG
HR280
2-29
Form Attributes: General Attributes Name Meaning
ZPYXXFO_Z99_PAYSLIP Remuneration statement
General Attributes
active
Output Options
For internal use by CSC only
For internal use by CSC only
Status
Creation/ change info Connection to Transport Organizer
Package Language Translate Into All Languages Into Selected Languages Do Not Translate
© SAP AG 2008
The form attributes include not only the name and description of the form but also its current status: active or inactive. A form can exist in either of these two versions. Application programs always use the active version. This means that you can provisionally save your changes without directly affecting application processing. To activate a form, choose Form → Activate. Note that when you copy a form, the status of the copy is always set to inactive. Since SAP Smart Forms are connected to the transport system of the SAP system, they must be assigned to a package. You do this when you first save your form. Every form has an original language. The General Attributes tab page allows you to define whether you want to translate the form into other languages, and if so, which ones. As of SAP Web Application Server 6.20, you can indicate in the Restricted Language Control field that the logon language is not to be used for missing texts.
© SAP AG
HR280
2-30
Form Attributes: Output Options Name Meaning
ZPYXXFO_Z99_PAYSLIP Remuneration statement Output Options
For internal use by CSC only
For internal use by CSC only
General Attributes
Page format CH
Chars. per inch
LN
Lines per inch Style XML output
© SAP AG 2008
The page formats available include the page formats provided in spool administration. The orientation (portrait or landscape) is set individually for each page. You can determine which page format is proposed for a new form as follows: Go to the initial screen of transaction SMARTFORMS and choose Utilities → Settings → tab page General. You must assign a style to each form. A style is a collection of different character and paragraph formats, which are then used in the form. However, you can specify a separate style for most subnodes, which then overrides the default setting of the form. Various styles exist in the system with root name HR*. Characters per inch (CPI). This field allows you to determine the CH unit of measure that you can use for horizontal length specifications (such as window widths) in the form. If you enter the default value 10, 1 CH is equivalent to one tenth of an inch, that is, approximately 2.5 mm. Similarly, the Lines per inch field allows you to determine the LN unit of measure that you can use for vertical length specifications (such as window lengths) in the form. The standard output format for printing is OTF (Output Text Format). A certified XML interface is provided, called the SAP Smart Forms XML Interface (XSF).
© SAP AG
HR280
2-31
Pages
Pages and Windows FIRST First Page
MAIN Main Window
For internal use by CSC only
For internal use by CSC only
LOGO Company Logo
Top page in the tree → first page in the document
INFO Administrator NEXT Next Page
Technical name: A-Z, 0-9, _, %
Description
Create Cut Copy Paste Delete –––––––––––––– Expand Collapse
© SAP AG 2008
Each form consists of at least one page. A page is represented by a node in the navigation tree. As with any other node types (such as texts or tables), right-clicking the mouse on an existing page opens a context menu with the available options: • Create or delete (in change mode only). When you create a new page, the system proposes a unique technical name, which you can change if you wish. Note that when you delete a node, all subnodes on the respective page are also deleted. • Copy to clipboard; cut and insert into clipboard; paste from clipboard. All subnodes are also affected. • Expand or collapse the page in the tree. The same functions can be accessed under menu path Edit→ Node and Edit→ Subtree. Each page - like all subnodes - has a technical name and a meaning. Only letters (without umlauts), numbers, and underscores are permitted for the names. The first character must be a letter. As a special case, the percentage sign is allowed as the first character. The percentage sign is used by the SAP Form Builder to generate names automatically.
© SAP AG
HR280
2-32
Page Attributes Page Meaning
FIRST First Page
1, I, i, A, a,
Output Options
Next page
Page orientation
Numbering Format Mode
Resource name
2, II, ii, B, b,
3 III iii C c
Background Picture
TRY01 TRY02 TRY03
Print mode
Initialize counter Increase counter Leave counter unchanged Page and overall page unchanged
For internal use by CSC only
For internal use by CSC only
General Attributes
Default S Simplex D Duplex T Tumble
© SAP AG 2008
You can make settings on the following tab pages: General Attributes • Next page. The default value is the page itself. • The type of automatic page numbering. You can choose between Roman and Arabic numerals, upper case and lower case, and determine the behavior of the page counter. Note that if you make page number settings, this does not mean that the pages are automatically numbered. You have to output the SFSY-PAGE variable in a text window to have your pages numbered. Output Options • While the page format you specify applies to the entire form, you set the orientation (portrait or landscape) for each page. • You can assign different paper trays to pages, provided you printer supports this feature. This is useful, for instance, if you want to use your company letter head for the first page of a form and normal printer paper for all other pages. • You can set double-sided print mode, provided your printer supports this feature. Background Picture. • Prerequisite: The required picture already exists in the system (after you use transaction SE78 to import it). Text is printed over the picture. © SAP AG
HR280
2-33
Page Structure with Output Areas (1)
Navigation Tree
Document
FIRST First Page
For internal use by CSC only
For internal use by CSC only
Pages and Windows
LOGO Company Logo MAIN Main Window TITLE Title
Processing from top to bottom
© SAP AG 2008
To be able to output information in a form, you must create suitable output areas (windows) on the relevant page. The following output areas are available: • Windows: Subnodes of windows are used to output text and data. • Graphic windows The output areas of a form are represented as nodes in the navigation tree. The icon helps you to identify the three different node types (address, graphic, or window). The order of the page subnodes in the navigation tree does not affect their position in the form, but it does affect their processing: In each page, they are processed from the top down. It is helpful to imagine that all nodes are expanded. You may need to move subnodes using drag and drop (left mouse button). The processing sequence is particularly important if you use fields (variables) that are filled only at runtime.
© SAP AG
HR280
2-34
Page Structure with Output Areas (2)
Pages and Windows FIRST First Page
Same name → same content For internal use by CSC only
For internal use by CSC only
MAIN Main Window TITLE Title ADDRESS Address
Subnodes of MAIN
NEXT Next Page MAIN Main Window TITLE Title ADDRESS Address
Drag and drop
Create Cut Copy Paste Delete –––––––––––– Expand Collapse
© SAP AG 2008
You create output areas as you do other nodes, namely using the context menu (right-click on a page). A unique technical name is proposed which you can change if you wish. You can move (with the left mouse button) or copy (CTRL and left mouse button) subtrees - that is nodes with subnodes - using drag and drop. Alternatively, you can use the clipboard (right mouse button: cut – copy – paste). For example, you can move or copy windows or text nodes from one page to another. If you drag one node (A) onto another node (B), A is inserted after B. However, it is also possible to create A as a subnode of B. A popup appears on which you can choose Under the node... or After the node.... If you choose the second option, A will be inserted at the same level as B but after it. If you place output areas on several pages of a form, any changes to node content (including deleting subnodes) take effect on all pages since the technical names of the nodes are identical. Output areas that share the same content can, however, occupy different positions on each page. If you place output areas in several positions within a page, copies containing the same content are created, but these copies have different technical names to the original. As a result, changes to node content only take effect in the area concerned.
© SAP AG
HR280
2-35
The Form Painter Form Painter TITLE
LOGO
EE_DATA
Ruler
For internal use by CSC only
For internal use by CSC only
Toolbar
ADDRESS
MAIN
Create Cut Copy Paste Delete –––––––––––––– Into background –––––––––––––– Help
Grid
Sizing handles © SAP AG 2008
You use the Form Painter to check/change the layout of a form. You can show or hide the Form Painter in the Form Builder by clicking the corresponding pushbutton or by choosing menu Utilities →Form Painter on/off. The Form Painter always displays the page selected in the navigation tree, including all output areas (windows, graphic windows, and address windows) and the background picture, provided there is one. To edit an output area, select it with a mouse click. The corresponding node is then also displayed on the maintenance screen. You can change the size of a window by clicking one of the sizing handles situated at the corners and the sides of the selection rectangle and dragging the handle to its new position while keeping the left mouse button pressed. If you want to reposition an output area, click the area and move it while keeping the left mouse button pressed (drag and drop). All size and position-related changes that you make are automatically copied to the maintenance screen. The context menu (right mouse button) is also available in the Form Painter. You can use this menu to create or delete output areas and perform normal clipboard functions (cut, copy, paste). Choose the Into background option if a small window is completely hidden by a larger one and you want to edit the small one. Using this option has no effect on the actual print output. (If windows, graphics, or texts overlap, they are printed one by one over another.)
© SAP AG
HR280
2-36
Form Painter: Settings Automatic zoom Zoom Zoom in Zoom out
Align with grid Grid Main grid Ruler
Draw window Detach toolbar
General
For internal use by CSC only
For internal use by CSC only
50%
Grid
Main Grid
Ruler
Tracker
Zoom
Form Painter with 3D Box Align Window with Grid Draw Window Transparent Window Crosshair
© SAP AG 2008
The most important settings options are provided in a detachable toolbar in the Form Painter. For more options, choose Utilities→Settings or right-click on the toolbar. The Draw Window option enables you to draw an output area directly by clicking on an empty spot on the Form Painter, holding down the left mouse button, and moving the mouse until the output area reaches the required size. There are different zoom options to control the view. The Automatic Zoom option is the most convenient of these. You can display a detail grid or a detail grid with main grid to enable you to align your output areas correctly. In addition, you can configure the Form Painter to automatically align output areas to the detail grid when they are moved with the mouse. The intervals in both grids can be configured. Using the crosshair instead of the normal mouse pointer also makes it easier to achieve an exact alignment of the nodes. You can choose this on the General settings tab page. On the Tracker settings tab page, you can define how you want the currently selected window to be highlighted.
© SAP AG
HR280
2-37
Main Window and Secondary Window Secondary window
For internal use by CSC only
For internal use by CSC only
Page 2
Main window (body text) Page 1
© SAP AG 2008
The two types of window that are distinguished between are main and secondary windows: In the subnode of the main window, you output content that can run over several pages (body text). In the example above, it is an employee's wage types. Once the main window has been completely filled with content, all of the page's as yet unprocessed secondary windows are processed. A page break to the next page occurs automatically, where the nodes are again processed in the order in which they are arranged in the navigation tree, and the body text is continued in the main window. • In a form, you can only designate one window as the main window. • The main window must be the same width on every page. However, you can choose its height and position freely. • A page that does not contain a main window cannot refer to itself as the next page since this would trigger an endless loop. In the subnode of a secondary window, you output the text and data in a predefined output area, that is to say, text output as body text with page breaks is not possible. • Text that does not fit in the secondary window is cut short and not output. • A secondary window's height, width, and position can vary from page to page. Graphics always automatically have the right dimensions. In SAP Web AS 6.10, there are another two types of windows, namely Copies Windows and Final Windows. They function exactly as secondary windows when it comes to body text, dimensions, and position. © SAP AG
HR280
2-38
Window Attributes Window Meaning
MAIN Main Window Conditions
Main window
Position and size
Check
Boxes and shading
Field comparisons
For internal use by CSC only
Type Node MAIN
For internal use by CSC only
Output Options
General Attributes
Events
Error MAIN window does not fit on the page (width)
© SAP AG 2008
You can execute checks at different levels, from the bottom node to the entire form. To ensure that all windows are free of errors, they must fit onto the respective page, and the main window must have the same width on all pages. All error messages are displayed in the bottom part of the maintenance screen. You can go directly to a node by clicking its name. You set the position and the appearance of a window using the output options. As with most node types, you can use conditions for windows to determine the time they are processed. You can choose from a number of processing events (such as not on first page or only on page...) and also control processing by means of specific values. For example, you might want to print text A for certain customers only and text B for all other customers. If the conditions set for a window are not fulfilled, neither the window nor its subnodes are processed. (The same applies for all other nodes and subnodes for which conditions have been specified.) If you use identical window nodes on different pages, each node has its own Output Options and Conditions tab pages.
© SAP AG
HR280
2-39
Window: Output Options
Left margin
Upper margin
For internal use by CSC only
For internal use by CSC only
Height
Width Line with 2pt width 2 mm spacing 10% shading, always draw
Red shading, 20%
Current information on the Intranet Page 1
© SAP AG 2009
You determine the position of a window by specifying the left, upper margin and you define its size by specifying the height and width. If you draw the window in the Form Painter, these details are automatically transferred to the maintenance screen, and vice versa. As is the case for all nodes that enable text to be output, you can configure frames and shading for windows. As of SAP Web Application Server 6.10, you can make detailed settings for the four margins of the window (upper, lower, right, and left). You can define lines in different widths and colors. You can also configure the width of the margin (distance from window edge to text) separately for all four margins. Furthermore, you can choose different shading colors and levels of saturation for each window. If you activate Always Draw Box and Shading, the window is always output with your chosen formatting even if it does not have any content. You can use the following units of measure to specify dimensions: CM, MM, IN (1 inch = approx. 2.54 cm), PT (point = 1/72 of an inch), TW (twip = 1/20 of a point). For vertical lengths you can also use LN and for horizontal lengths CH. You specify how these dimensions should be defined in the form attributes.
© SAP AG
HR280
2-40
Graphics on the Form
Form Painter FIRST First Page LOGO
General Attributes
Name Object ID
Output Options
For internal use by CSC only
For internal use by CSC only
LOGO Company Logo
HR280_LOGO GRAPHICS BMAP
Black and White Bitmap Image (BMON) Color Bitmap Image (BCOL) Determine Dynamically (BCOL, BMON) Output Attributes Resolution DPI
Static Dynamic (without preview)
© SAP AG 2008
You can embed graphics not only as background pictures, but also as separate graphic windows (direct subnodes of a page), or as subnodes of a window. A prerequisite for this is that the graphic already exists in the system. You create graphic nodes like you create any other node by using the context menu (right mouse button) or via menu path Edit→ Node → Create. If you create a separate graphic window for the graphic, the graphic is visible in the Form Painter (provided you have not selected the Placeholder for graphics checkbox in the Form Painter settings). You can then easily position the graphic on the page using drag and drop. If you create the graphic as a subnode of an existing node, for example of a window or a template, it is not displayed on the Form Painter and you cannot choose its position with drag and drop; the graphic is output depending on higher-level nodes. You make the settings for the name of the graphic, the object and ID, the type of the graphic (black and white or color) and the resolution in the same way as for a background picture. In particular, you can determine the name of the graphic dynamically at the application program runtime by entering a field. If you do not create the graphic in a separate graphic window of the form but as a subnode, you must also determine its horizontal position on the Output Options tab page. To insert a graphic, it must first be imported from your front-end computer into the system in TIFF or bitmap format using graphics administration (transaction SE78).
© SAP AG
HR280
2-41
Activate and Test Forms
SAP Form Builder: Change Form ZPYXXFO_Z99_PAYSLIP
F8 F8
F8
F8
For internal use by CSC only
For internal use by CSC only
Check Activate
Print Preview Page 0001 of 0003 Remuneration statement Remuneration statement for / (--) Page 1 Personal data Personnel number Date of birth Entry
Test print without data selection
Wage Type
Number
Unit
Amount
Total
© SAP AG 2008
If you make changes to a form, you should check them. You can perform individual checks for most nodes or simply check the entire form. Before you can use a form in programs, you must first activate it. To do so, choose Form → Activate or choose the second pushbutton on the application toolbar in the Form Builder. Activating a form means that the entire form is checked and saved and the function module is generated. To test your form from the Form Builder (using Print Preview or Print), choose Form → Test or choose the third pushbutton in the SAP Form Builder. This takes you to the Function Builder; the development environment for function modules. The name of the generated function module is already entered here. You can add values to the interface of the function module for test purposes. Then choose Test/Execute again (Menu path Function Module → Test → Single Test), then Execute. Enter your printer in the Output Device field in the print attributes and choose Print Preview or Print.. Tip: The quickest way to go to the print preview is to press the F8 function key four times in the SAP Form Builder. You can only test inactive forms as of SAP Web Application Server 6.10. For SAP R/3 4.6C, you must activate a form even just to test it.
© SAP AG
HR280
2-42
Pages and Windows: Summary
Create secondary windows with the Form Painter
Insert a graphic with the company logo
Test the form
For internal use by CSC only
For internal use by CSC only
You are now able to:
© SAP AG 2008
© SAP AG
HR280
2-43
For internal use by CSC only
For internal use by CSC only
2-44
HR280
© SAP AG
Exercises Unit: HR Forms Workplace Lesson: Pages and Windows
• Create a secondary window for the personal data of the employee
For internal use by CSC only
For internal use by CSC only
At the conclusion of this exercise, you will be able to: • Add a graphic to the form with the company logo • Test the form The personal data of the employee is to appear in a window on the remuneration statement form. The company logo is to appear in the upper right corner.
1-1
1-2
1-3
Create a new form by copying the template called ZHR280_G00_EXE2. Call your form ZHR280_G##_EXE2 (## = group number). 1-1-1
Change the name of the existing page called %PAGE1 to MAIN. Enter Main Page as the meaning.
1-1-2
Create a new secondary window in the main page. Position the window in the navigation tree below the MAIN main window. Call it EE_DATA Employee Data and activate the Always Draw Box and Shading option.
Add the company logo to the form. 1-2-1
Create a node called LOGO for company logo HR280_LOGO on the MAIN page.
1-2-2
Position the logo in the upper right corner of the form.
Create another page. 1-3-1
1-4
Copy the MAIN page and call it FOLLOW_PAGE Next Page. It should follow the MAIN page.
Activate your form and test it.
© SAP AG
HR280
2-45
For internal use by CSC only
For internal use by CSC only
2-46
HR280
© SAP AG
Solutions Unit: HR Forms Workplace
1-1
Create a new form by copying the template called ZHR280_G00_EXE2. Call your form ZHR280_G##_EXE2 (## = group number). Call up your form for editing and choose the Layout pushbutton. 1-1-1
Select %PAGE1 in the navigation tree by double-clicking on it and enter MAIN in the Page field and Main Page in the Meaning field.
1-1-2
First, activate the Form Painter. Choose Create → Window from the context menu (right mouse button) on the MAIN page. A window appears in the upper left corner of the Form Painter in a default size and with a default name. Use the mouse to move it to a position to the right of the ADDRESS window. Drag the window in the navigation tree to a position below the MAIN window. Enter the following on the Output Options tab page:
© SAP AG
Field Name
Value
Left Margin
11.00 cm
Upper Margin
4.40 cm
Width
8.5 cm
Height
3.6 cm
HR280
2-47
For internal use by CSC only
For internal use by CSC only
Lesson: Pages and Windows
1-2
Add the company logo to the form.
1-2-2
1-3
Choose Create → Graphic from the context menu (right mouse button) on the MAIN page. Call the new node LOGO, enter the details provided below on the General Attributes tab page, and choose Color Bitmap Image (BCOL): Field Name
Entries
Name
HR280_LOGO
Object
GRAPHICS
ID
BMAP
Position the logo in the upper right corner of the form on the graphical Form Painter.
Create another page. 1-3-1
Select the MAIN page in the navigation tree and choose Copy from the context menu (right mouse button), Then choose Paste from the context menu. Call the new page FOLLOW_PAGE and enter Next Page as the meaning. Select the MAIN window again by double-clicking on it, go to the General Attributes tab page and choose the new page in the Next Page field. Save the new form.
1-4
Activate your form and test it. The quickest way to access the print preview is to choose F8 four times. Use LOCL as the output device.
© SAP AG
HR280
2-48
For internal use by CSC only
For internal use by CSC only
1-2-1
Data on the Form: Unit Overview Diagram
Unit Overview Lesson 1: Create Form
For internal use by CSC only
For internal use by CSC only
Lesson 2: Pages and Windows Lesson 3: Data on the Form Lesson 4: Texts on the Form Lesson 5: Tables and Templates Lesson 6: Flow Control
© SAP AG 2008
© SAP AG
HR280
2-49
Data on the Form: Lesson Objectives
Output employee data in a loop on the form
Process the payroll results in a loop
For internal use by CSC only
For internal use by CSC only
At the conclusion of this lesson, you will be able to
© SAP AG 2008
© SAP AG
HR280
2-50
Data on the Form: Business Scenario
The employee's address is to be printed on the remuneration statements in a window created for this purpose. Wage types are to be output in the main window.
For internal use by CSC only
For internal use by CSC only
© SAP AG 2008
© SAP AG
HR280
2-51
Data and Tables: Technical Background
Database table(s)
MetaStar
Loop in the form
Internal table
InfoStar
For internal use by CSC only
For internal use by CSC only
Data retrieval
Work area
WA_INFOSTAR
© SAP AG 2008
From a technical point of view, a table in an SAP Smart Form is filled by processing an internal table on a line-by-line basis. This is referred to as a "loop." The respective lines are copied into a work area that has the same structure as the table. The internal table must be filled beforehand in the application program (which is the usual case) or in the form. The data is normally taken from database tables. If the data is read in the application program, the internal table must be defined on the SAP Smart Form interface. If the internal table is very large, we recommend that you process the table using field symbols instead of a work area since field symbols can directly access the individual lines and therefore the lines do not need to be copied.
© SAP AG
HR280
2-52
Loop over Payroll Results
RESULTS Loop over Results
LOOP Loop Internal Table
HRDATA-STAR
INTO
WA_RESULT
For internal use by CSC only
For internal use by CSC only
Data
WHERE Condition Already Sorted Sort Criteria Fld Name
Event on Sort B... Event on Sort E...
EMPLOYEE_KEY-PERSON.. INPERIOD_KEY
Control level © SAP AG 2008
Data tab page: Enter the name of the internal table over which the loop is to be executed and the associated work area (assignment type into) or the field symbol (assignment type assigning). You can specify a line range, determine one or more WHERE conditions, and sort the internal table before it is processed. Sorting the internal table is a prerequisite for sort levels (control levels). The node shown is the loop over the HRDATA-STAR_PAY_RESULT InfoStar of the employees. In the loop, all entries are made available one after the other in the WA_RESULT work area. You can also sort the internal table within the form. To do this, enter the names of the fields to be used as the sort criteria. The order of the fields in this list determines the sort sequence. You can subsequently change the sort sequence by placing your cursor on a field and moving it up or down a line by clicking one of the two black triangles displayed above the sort criteria. To the right of the field, you can choose whether the table is to be sorted in ascending or descending order. For technical reasons, the system cannot recognize whether the internal table has already been sorted (for example, in the data retrieval program). If this is the case, you still have to enter the sort criteria but then select the Already Sorted checkbox. (Otherwise, the table will be sorted again.) Sorting is required for subtotals, page breaks, and so on.
© SAP AG
HR280
2-53
Loop over Employees
EMPLOYEE Employee ADDRESS Employee Address
LOOP Internal Table HRDATA-DIM_ Row to
WHERE Condition Fld Name KEY
INTO
Op
For internal use by CSC only
For internal use by CSC only
Data
WA_EMPLOYEE
Comparison Value WA_RESULT-EMPLOYEE_KEY
Insert OR © SAP AG 2008
The node shown is the loop over the HRDATA-DIM_EMPLOYEE dimension table of the employees. In the loop, all entries are made available one after the other in the WA_EMPLOYEE work area. WA_RESULT-EMPLOYEE_KEY serves as a comparison value for the key of the dimension table. Events tab page: If you select Header and/or Footer, event nodes are automatically created in the navigation tree. You can, for example, enter text as a direct subnode of these event nodes. You can output headers at the beginning of the loop and/or after a page break. Similarly, footers can be output at the end of the loop and/or before a page break. You must additionally enter a height for the footer so that the form processor can reserve space for it. Loops can be nested. Notably, it is also possible to use tables or templates in loops.
© SAP AG
HR280
2-54
Data on the Form: Summary
Output employee data in a loop on the form
Process the payroll results in a loop
For internal use by CSC only
For internal use by CSC only
You are now able to:
© SAP AG 2008
© SAP AG
HR280
2-55
For internal use by CSC only
For internal use by CSC only
2-56
HR280
© SAP AG
Exercises Unit: HR Forms Workplace Lesson: Data on the Form At the conclusion of this exercise, you will be able to: For internal use by CSC only
• Process the payroll results in a loop
The employee's address is to be printed on the remuneration statements in a window created for this purpose. Wage types are to be output in the main window.
1-1
1-2
1-3
Create loop over the payroll results Create a new form by copying the template called ZHR280_G00_EXE3. Call your form ZHR280_G##_EXE3 (## = group number). 1-1-1
Create a loop over the HRDATA-STAR_PAY_RESULT InfoStar below the MAIN window. Use the WA_RESULT structure, which is defined in the global definitions, as the work area.
1-1-2
Use the EMPLOYEE_KEY-PERSONNEL_NUMBER and INPERIOD_KEY fields as sort criteria. Select the second field as the control level end.
Create loop over employee 1-2-1
Create a loop over the HRDATA-DIM_EMPLOYEE InfoDimension below the ADDRESS secondary window. Use the WA_EMPLOYEE structure, which is defined in the global definitions, as the work area.
1-2-2
Enter WA_RESULT-EMPLOYEE_KEY as the key for the InfoDimension.
Test the form and check the data selected. 1-3-1
© SAP AG
Test the form with the payroll period, payroll area, and personnel number provided by your instructor.
HR280
2-57
For internal use by CSC only
• Output employee data in a loop on the form
For internal use by CSC only
For internal use by CSC only
2-58
HR280
© SAP AG
Solutions Unit: HR Forms Workplace Lesson: Data on the Form
1-2
1-3
Create loop over the payroll results 1-1-1
Choose Create → Flow Logic → Loop in the context menu (right mouse button) on the MAIN window. Call the new node RESULTS Loop over Results. In the fields for the LOOP loop, enter the HRDATA-STAR_PAY_RESULT InfoStar as the table and WA_RESULT as the structure.
1-1-2
Enter the specified fields EMPLOYEE_KEY-PERSONNEL_NUMBER and INPERIOD_KEY as ascending sort criteria. Select the Event on Sort End field for the period.
Create loop over employee 1-2-1
Choose Create → Flow Logic → Loop in the context menu (right mouse button) on the ADDRESS page. Call the new node EMPLOYEE Employee. In the fields for the LOOP loop, enter the HRDATA-DIM_EMPLOYEE InfoDimension as the table and WA_EMPLOYEE as the structure.
1-2-2
Enter the following as the WHERE condition: KEY = WA_RESULT-EMPLOYEE_KEY.
Test the form and check the data selected. 1-3-1
© SAP AG
On the selection screen, enter the payroll period, payroll area, and personnel number provided by your instructor. Choose Execute. Take a look at the data for one of the entries in the ALV list, for example the HRDATASTAR_PAY_RESULT InfoStar.
HR280
2-59
For internal use by CSC only
For internal use by CSC only
1-1
For internal use by CSC only
For internal use by CSC only
2-60
HR280
© SAP AG
Texts on the Form: Unit Overview Diagram
Unit Overview Lesson 1: Create Form
For internal use by CSC only
For internal use by CSC only
Lesson 2: Pages and Windows Lesson 3: Data on the Form Lesson 4: Texts on the Form Lesson 5: Tables and Templates Lesson 6: Flow Control
© SAP AG 2008
© SAP AG
HR280
2-61
Texts on the Form: Lesson Objectives
Create text nodes in windows
Output texts and field content
For internal use by CSC only
For internal use by CSC only
At the conclusion of this lesson, you will be able to
© SAP AG 2008
© SAP AG
HR280
2-62
Texts on the Form: Business Scenario
The payroll period and page number are to be printed in the title of the remuneration form. The employee's address is to be output in the address window on the form.
For internal use by CSC only
For internal use by CSC only
© SAP AG 2008
© SAP AG
HR280
2-63
Text Nodes
MAIN Main Page LOGO Company Logo
For internal use by CSC only
For internal use by CSC only
MAIN Main Window TITLE Title TITLE Remuneration Statement PAY_PERIOD Payroll Period PAGE_NO Page
Create Cut Copy Paste Delete
Drag and drop
© SAP AG 2008
You enter all of the text on the form using text nodes. Text nodes are subnodes of windows and their subnodes, for example folders or templates. A context menu is available for existing text nodes (right mouse button), which you use, for instance, to create another text node directly after the one you have clicked on (at the same level). Alternatively, you can use the higher-level node's context menu to create text nodes, in which case the new node is inserted as the highest-level subnode of this node. The same functions can be accessed under menu path Edit → Node . Text nodes themselves cannot have any further subnodes. Bear in mind that text in secondary windows that does not fit in the space is cut short. Text only continues to the next page if it is in the main window.
© SAP AG
HR280
2-64
Text Nodes: Attributes Text Meaning
TITLE Remuneration Statement
• Beginning • New paragraph • New line • Append directly
Output Options
• Box and shading • Style
Conditions
• Field comparisons • Events
• Page protection
• Text type • Text element • Text module • Include text © SAP AG 2008
If you select a text node in the navigation tree or in the Form Painter, its attributes are displayed on the maintenance screen. The three tab pages are similar to those for windows. General attributes: • The text type you choose allows you to determine whether the text is saved and edited within the form (as a text element) or outside the form. In the latter case, you can choose between an SAP Smart Forms text module and a SAPscript include text. • You also determine how two directly successive text elements should be combined. • The remaining fields you see on the tab page vary depending on the text type. Output options: • The previous information about boxes and shading for windows also applies to text nodes. • In addition, you can assign a style to the text node. A style is a collection of different character and paragraph formats. • If the text node is in the main window, you can choose Page Protection. This option prevents text from being separated by page breaks. If the protected text does not fit onto the current page, it is output on the next page. Conditions: • See the conditions for windows. © SAP AG
HR280
2-65
For internal use by CSC only
For internal use by CSC only
General Attributes
Linking Text Nodes
New Line:
Title paragraph format
Remuneration statement
Remuneration statement
Remuneration statement for...
Remuneration statement for...
For internal use by CSC only
For internal use by CSC only
New Paragraph:
Title paragraph format
Title paragraph format
Standard paragraph format
Append Directly: Payroll remuneration statement for...
© SAP AG 2008
On the General Attributes tab page, you define how two text nodes the follow one after the other in the same window are to be linked to each other: • Choose New Paragraph to prompt the text of the second node to begin on a new line in the paragraph format that you have defined for this paragraph. This means that both text nodes are completely separate from one another. (Within one text node, return corresponds to a new paragraph.) • Choosing New Line also results in the text of the second node beginning on a new line. In this case, however, the format of the last paragraph of the first text node is used for the first paragraph of the second text. (Within one text node, shift return corresponds to a new paragraph.) • Finally, you can also choose Append Directly. This results in two text nodes that follow directly one after the other being joined together without blank characters or blank lines. In the resulting paragraph, the format of the first text element is used. If the first node is framed or framed and shaded, the second node is always attached with the New Paragraph option, irrespective of your chosen setting.
© SAP AG
HR280
2-66
Text Elements in the Editor Fullscreen editor
Paragraph Formats TI Title
Paragraph mark
For internal use by CSC only
For internal use by CSC only
Clipboard Find
Character Formats IT Italic
Remuneration statement Remuneration statement for...
© SAP AG 2008
If you choose text element as the text type, the online editor is displayed on the General Attributes tab page. You can enter text as you would do in any common word processing program. Alternatively, you can switch to fullscreen mode by choosing the Text Editor pushbutton. You can use the clipboard by selecting text blocks with the mouse and choosing the Cut, Copy, or Paste pushbuttons. This way you can copy sections of text between different windows or forms. Line breaks are inserted into text nodes automatically depending on the window width. You can also use the Enter key in the editor to create a new paragraph that might have a different format than the preceding one. The Shift-Enter key combination allows you to add a line break within a paragraph. The Paragraph Mark On/Off pushbutton enables you to determine whether you want to display nonprinting characters such as blank characters, tabulators, paragraph marks, and line breaks.
© SAP AG
HR280
2-67
Format Texts: Paragraph and Character Formats Display formats Reset character formats Show paragraph marks
Paragraph Formats TI Title
For internal use by CSC only
For internal use by CSC only
List dependent on style
Character Formats IT Italic
Remuneration statement
Page
Remuneration statement for...
Justified
Tabs
© SAP AG 2008
You can format sections of text that you have selected. They are then displayed roughly as they will appear when they are printed (WYSIWYG = What You See Is What You Get). You can choose a paragraph format from the selection list directly in the editor for each paragraph. A paragraph format denotes a collection of format settings, for instance tabs and alignment. The paragraph formats offered in the list depend on the style you have chosen (for example, HRFORMS). If you have entered a style on several nodes (for example, for the form attributes and for a text), the following applies: The style of a node overrides the style of the form attributes, and the style of a lower-level node overrides the style of a higher-level node. If you do not choose a paragraph format, the standard paragraph format for the style is used. Furthermore, you can assign one or more character formats to text that you have selected. Character formats refer to a combination of format settings, such as font or superscript. The same applies to the character formats available for selection as the paragraph formats. The Reset Character Formats pushbutton resets all of the character formats for the area selected back to the paragraph format. The current format setting is automatically shown in the list of paragraph and character formats when you place the cursor in the text. Therefore, it is only necessary to use the Display Formats function if you require detailed information about the format or if the text contains several character formats.
© SAP AG
HR280
2-68
Field List Field List Remuneration statement for &WA_RESULT-INPERIOD_KEY-PERIOD+4(2)& / &WA_RESULT-INPERIOD_KEY-PERIOD(4)&
For internal use by CSC only
For internal use by CSC only
Import Interface Export Interface Global Data WA_RESULT INPERIOD_KEY
Remuneration statement Remuneration statement for 12/2007
Personal data
PAYDATE
Personnel number Date of birth Entry
PERIOD System Fields © SAP AG 2008
Normally, your form contains not only static text but also variable data referred to as fields. These are read from the database at application runtime or are entered by the user. The simplest way to insert fields is to use the field list. You can show or hide the field list by choosing the corresponding pushbutton, or in the menu by choosing Utilities→Field list on/off. The following types of fields are available for selection: • All fields that are recognized by the form as import, export, or table parameters, through the form interface (which means they come from the application program) • All global data and field symbols that you have created in the form in the global definitions • System fields that are filled automatically during program execution You insert the fields using drag and drop. Drag the name of a field from the field list to the desired position in your text element. If a field is structured, click the triangle icon to the left of the corresponding folder to access the individual subfields.
© SAP AG
HR280
2-69
System Fields &SFSY-DATE&
Date
&SFSY-TIME&
Time
&SFSY-PAGE&
Number of current print page
&SFSY-FORMPAGES&
Total number of pages of document currently being
&SFSY-JOBPAGES&
Total number of pages of all documents in current
For internal use by CSC only
For internal use by CSC only
edited print request &SFSY-WINDOWNAME&
Name of current window
&SFSY-PAGENAME&
Number of current page
As of SAP Web Application Server 6.10: &SFSY-XSF&
Indicator for XSF output
&SFSY-COPYCOUNT0&
Copy counter (0 = original, 1 = 1st copy)
&SFSY-COPYCOUNT&
Copy counter (1 = original, 2 = 1st copy)
&SFSY-USERNAME&
User name
© SAP AG 2008
DATE: Displays the date. You define the display format in the user master record. TIME: Time in HH:MM:SS (HH: hours, MM: minutes, SS: seconds). Page numbers: • PAGE: Number of current print page. You define the page number format (for example, Arabic, numeric) and mode (increase, initialize, keep unchanged) on the General Attributes tab page of the page node. • FORMPAGES: Total number of pages of the document currently being edited. This enables you to include details such as "Page x of y." • JOBPAGES: Total number of pages of all documents in the current print request WINDOWNAME: Name of the current window PAGENAME: Number of the current page New as of SAP Web Application Server 6.10: • XSF: Is set if the form is output in XSF or HTML formats. • COPYCOUNT and COPYCOUNT0: Query whether an original or copy is output. • SUBRC: 0 if a text module or include text exists, otherwise 4. • USERNAME: Logon name of user that is printing the form. © SAP AG
HR280
2-70
Edit Fields in Texts Delete field Modify field Insert field
Paragraph Formats TI Title
Character Formats IT Italic
For internal use by CSC only
For internal use by CSC only
Check
Remuneration statement for &WA_RESULT-INPERIOD_KEY-PERIOD+4(2)& / &WA_RESULT-INPERIOD_KEY-PERIOD(4)&
Error Messages Type Node
Error Data object "WA_RESULT" does not have a component with...
© SAP AG 2008
You can also use the Insert Field pushbutton to integrate fields into your text element. Enter the field name with ampersands preceding and following it. In this way, you can also access the ABAP system fields of the SYST structure, for example &sy-uname& (user name). Capitalization is irrelevant. The fields are shown in gray to distinguish them from normal text. They cannot be directly changed or deleted. To delete a field, select it and choose the Delete Field pushbutton. To change a field, place your cursor on the field and choose the Change Field pushbutton. You need this function, for example, to determine formatting options such as the output length for a field. To ensure that your field entries are correct, perform a check by clicking the corresponding pushbutton in the editor. The system notifies you of any errors that may exist (by means of an exclamation mark in a red triangle). If errors exist, you cannot activate the form. Only if you use the check function of the Form Builder (first pushbutton in the toolbar), does the system check if all fields used have been assigned a value when they are processed or if they are still initial. If the fields are initial, the system issues a warning (exclamation mark in a yellow circle) but you can still activate the form. Fields that are initial at application program runtime are ignored. For more information, see the online documentation.
© SAP AG
HR280
2-71
Formatting Options &WA_NAME+4(5)& Smart
&field+6&
Offset (only for character fields; in this case 6)
&field(9)&
Output length (in this case 9)
&field(S)&
Suppress sign
&field( Personnel Management -> HR Administrative Services -> HCM Processes and Forms -> Design Time for Processes and Forms.
© SAP AG
HR280
5-11
Creating a Form Scenario Create form scenario / create ISR scenario Æ Do the preparatory work and define the form logic:
Object selection: Form scenario or process
For internal use by CSC only
For internal use by CSC only
The aim of this unit is to enhance an existing form to include extra fields.
© SAP AG 2009
You create the form scenarios and processes in Design Time. When doing so, you can switch quickly between form scenario and process using the object selection. To create a new form scenario, choose Form Scenario from the dropdown list and enter a (new) object name in the field below. If the object does not yet exist, the system asks if you would like to create it. You can then specify an ISR scenario directly in the dialog box that appears. When you choose the OK pushbutton to confirm this, the ISR scenario is created automatically. You can make the following settings here: • Enter IDs • descriptions of the form scenario, • ISR scenario, and • select a back-end service
© SAP AG
HR280
5-12
Creating a Form Scenario: Overview of Configuration Options for Creating a Form Scenario
Form scenario view
Generate the ISR scenario
For internal use by CSC only
For internal use by CSC only
Assignment of a form scenario group
Assignment of digital personnel file
Configuration options
© SAP AG 2008
In the object processing area, you can do the following: Define the form scenario name Specify and generate the ISR scenario (a popup will ask you if you want to update the form). Note: It makes more sense to generate the ISR scenario once you have already created all the form fields and defined the data binding for the infotype fields. Assign the form scenario group for authorizations Create an anchor number to store (assign) the form in the personnel file once the process has been executed In the object hierarchy area, the following configuration options exist: Define form scenarios Generate/create fields for the form scenario Generate an interactive form, design the layout, and define fields Define form scenario steps Determine back-end services that are used in the form scenario, determine the corresponding back-end fields, and select the respective operations Define other attributes such as attachment types, rules, message mapping, links (additional information) © SAP AG
HR280
5-13
Form Scenario Versions
For internal use by CSC only
For internal use by CSC only
The first version (0) is created automatically by the system.
Version-specific details
© SAP AG 2008
A range of administrative information is displayed under the Version configuration option: • When and by whom was the form scenario created? • When and by whom was it last changed? • The form scenario version Form scenarios are version-dependent. Since processes can vary, it is important to ensure that the corresponding form scenario is adjusted accordingly. You need different versions to create different forms for process variants. Each form scenario has at least one version that is linked to the relevant process. When you create a new form scenario, the system automatically creates the first version with number "0".
© SAP AG
HR280
5-14
Definition for Form Scenario Fields – Fields UI View New main view for Field definition Assigning a field to a service (service-specific and general views) Binding between a form scenario field and a service field
Simple definition for multiple fields of an infotype
Mandatory fields all of which are automatically available – depending on the back-end service selected Field names proposed automatically
For internal use by CSC only
For internal use by CSC only
Filter for fields of a specific back-end service
Information about use in forms
© SAP AG 2008
The Fields configuration option allows you to define form scenario fields that you would like to use in the form. Mandatory fields are displayed automatically and depend on the back-end service that has been selected. You also define the field binding here. You can assign new fields to the form scenario and organize them with the Service Fields pushbutton. Once you have created all form scenario fields and defined their binding, this screen provides you with a good overview of all existing fields and their attributes. You can also filter the fields by back-end services. The Field Attributes column is a new parameter. You can use it to make settings that relate to mandatory fields, which fields are displayed, and so on...
© SAP AG
HR280
5-15
Creating a Form Scenario: Create Form-Scenario-Specific Fields with the Field Wizard "Fields" subview:
For internal use by CSC only
For internal use by CSC only
Service fields (field wizard)
Automatically created fields that feature in every form scenario. All of the embedded and linked fields from the back end that are (currently) available also appear here so that they can be included in the Adobe form. © SAP AG 2008
The mandatory fields are created automatically. New main view for: • Field definition • Assigning a field to a service (service-specific and general views) • Binding form scenario field with service field • Mandatory fields are available automatically • Field names are proposed automatically • Simple definition for multiple fields of an infotype • Information about the usage of the field in the form
© SAP AG
HR280
5-16
Create Form Scenario: Create Form Scenario Fields for an Infotype Simple definition: Naming Fields Mandatory fields Field service assignment Field infotype field binding Multiple fields of an infotype
Specifies country version
Specifies screen structure type Specifies subtype
For internal use by CSC only
For internal use by CSC only
Specifies infotype
Specifies operations
Update
Field selection
Automatically created field name with reference to infotype
© SAP AG 2008
In the old Design Time, the form scenario fields and the binding to an infotype field were defined in different table views. In this popup, the system provides all of the fields of a chosen infotype and its subtypes. Specify the following: Infotype, subtypes, infotype version (country version), screen structure type, and screen structure. Choose Determine Fields so that the respective fields are displayed. You can specify the operations (create, change, delete, change without restriction) for the back-end update straight away. Select the fields directly from the list. The field names (for the form scenario fields) are specified automatically, but you can overwrite them if you wish. If you want a field to contain a default value, you can define this here. You can also specify if a field should have an input help or not.
© SAP AG
HR280
5-17
Creating a Form Scenario: Form Scenario Field View Once Fields Have Been Entered Field attributes
For internal use by CSC only
For internal use by CSC only
Newly created fields, in this example infotype 1; subtype...
Input Input help help
Values proposed by system
© SAP AG 2008
All of the selected fields and mandatory fields are now assigned to the form scenario. You can add other fields and infotypes for the purpose of the exercises in this course. When doing so, note the field links. For fields that have already been selected, you have the following options: • Accept or overwrite automatically proposed default field names • Add, accept, or overwrite the name • Determine field attributes: Invisible, output only, can be edited, required entry, autom. (step relevance), step-dependent • Define the default value by clicking in the respective line in the table (Default Value column) • Define input help by clicking in the respective line in the table (Input Help column) • Activate the collision check (checks are then carried out at process runtime)
© SAP AG
HR280
5-18
For internal use by CSC only
For internal use by CSC only
Implementation: System Behavior When Saving to the Back End
Infotype-specific definition of operations
© SAP AG 2008
In the Back-End Services → SAP_PA → Infotypes and Operations configuration option, you define which operations are performed when data is sent from the form to the back end. The PA service supports the following operations for objects (Operation column): • Create • Change • Delete • Change without restriction • Blank
© SAP AG
HR280
5-19
Create Form Scenario: Save Form Scenario (Also Updates ISR Scenario)
For internal use by CSC only
For internal use by CSC only
Save
© SAP AG 2008
When you save the form scenario, as of EhP2 the ISR scenario is automatically saved as well. It is no longer necessary to save the ISR scenario in a separate step, as was previously the case prior to EhP2.
© SAP AG
HR280
5-20
For internal use by CSC only
For internal use by CSC only
Create Form Scenario: Navigate Backwards and Check Consistency
© SAP AG 2008
© SAP AG
HR280
5-21
Generate the ISR scenario
For internal use by CSC only
For internal use by CSC only
Generate the ISR scenario
© SAP AG 2009
The ISR scenario is generated automatically when you save. The manual generation of the ISR scenario is only required if you have imported the form scenario from an XML file.
© SAP AG
HR280
5-22
Activate and Update Form Scenario
For internal use by CSC only
For internal use by CSC only
Note: The status of the form is now "Active but Not Updated" Æ
Update and activate
The appearance is updated and the status is changed to "Active"
© SAP AG 2008
© SAP AG
HR280
5-23
Check and Test Consistency Test directly from Design Time:
For internal use by CSC only
For internal use by CSC only
Test
© SAP AG 2008
This test program enables you to test an entire process in the back end, for example to check if all of the required data is retrieved from the back end. You can start a new process or continue to test a process that has already been started (from the portal). You can execute the test program in the following IMG activity: → HR Administrative Services → Configuration of Forms/Processes → Process Configuration → Test Process . Alternatively, you can execute it directly in Design Time. To start the test program in Design Time, choose the "Test" pushbutton on the top view, Process Proceed as follows: • Specify the process name • Enter the personnel number of the employee that you would like to test • In addition, you can enter details of the role of the initiator and so on • Choose Execute • You are presented with an overview of the form scenario data. You can then enter field values as you would in the form itself and simulate the entire process.
© SAP AG
HR280
5-24
Architecture: Form Scenario Fields and Service(s) Diagram depicting connections of fields between form, ISR scenario, form scenario (form scenario fields), and service FORM SCENARIO Form
ISR sc.
- F2
- F1
- F3
- F2
- F4
- F3
- F5
- F4
- F6
- F5 - F6
Service(s)
Field
Default Value Input Help
- Field 1
Manual
--
- 1 (SAP_PA)/field 1
- Field 2
Manual
--
- 1 (SAP_PA)/field 2
- Field 3
Manual
Manual
- 1 (SAP_PA)/field 3
- Field 4
Service
Service
- 2 (Z_MGR_POS)/field 4
- Field 5
--
--
- 1 (SAP_PA)/field 5
- Field 6
--
--
- 1 (SAP_PA)/field 6
Form scenario fields:
Service
ID/name
ID/name
Default value
Fields
Input help
Field logic (business logic)
Assignment to service/service field
For internal use by CSC only
For internal use by CSC only
- F1
Form scenario
Operation
© SAP AG 2008
The form scenario fields with their settings for default values and input helps, as well as the assignment of services that contain the business logic, constitute the key entities used to determine how a process is controlled at runtime. The business logic can also be mapped in the form itself; for example, you can define a field as a mandatory entry field. In this case, the effect for the user would be the same as if this attribute had been defined in the service. It is simply a case of the setting for this attribute being made in a different place.
© SAP AG
HR280
5-25
Architecture: Mandatory Fields, Modifiable Fields, and How to Display Fields FORM SCENARIO Form - F1 - F3 - F4 - F5 - F6
Form scenario
Service(s)
Field
Default Value Input Help
- Field 1
Manual
--
- ….
- F1
- Field 2
Manual
--
-…
- F2
- Field 3
Manual
Manual
- 1 (SAP_PA)/field 3
- F3
- Field 4
Service
Service
- 2 (Z_MGR_POS)/field 4
- F4
- Field 5
--
--
- 1 (SAP_PA)/field 5
- F5
- Field 6
--
--
- 1 (SAP_PA)/field 6
For internal use by CSC only
For internal use by CSC only
- F2
ISR sc.
- F6
Mandatory fields: Mandatory for all form scenarios Appear automatically as a result of Design Time
Display fields:
Edit fields:
Default value required
Service assignment not required
Default?
Dependent on Service
Input help? © SAP AG 2008
© SAP AG
HR280
5-26
Adobe Interactive Forms in SAP ERP 6.0 Practical Part: Unit Overview Diagram
Adobe Interactive Forms in SAP ERP 6.0 – Practical Part Lesson 1: Step-by-Step: Create/Edit Processes and Forms
For internal use by CSC only
For internal use by CSC only
Lesson 2: The New Design Time Lesson 3: The Form Builder Lesson 4: Workflow and Process Lesson 5: Further Customizing
© SAP AG 2008
© SAP AG
HR280
5-27
Implementation: The Adobe Form Builder From Design Time...
For internal use by CSC only
For internal use by CSC only
"Change Form" Æ takes you out of Design Time and into the FORM BUILDER…
...to the Form Builder:
© SAP AG 2008
The Form Builder is now located in Adobe Form Builder, which is integrated in the ERP back-end system. You access the Form Builder from Design Time by choosing the Change Form pushbutton in the Form configuration option. For detailed information about the Adobe Form Builder, see the respective documentation You create the form here: layout, field mapping, pushbuttons, scripts, and so on... The Form Builder is where you carry out the preparatory work for the actual form and define its logic: • Form scenario and ISR scenario Customizing • ISR scenario • Form scenario • Fields for layout • Assigned services • Attachment types • Additional links • Link ISR and form scenario © SAP AG
HR280
5-28
For internal use by CSC only
For internal use by CSC only
Create Form: Insert Web Dynpro Script (Required for ZCI Forms)
© SAP AG 2008
The Web Dynpro script is required so that the Adobe interactive forms can also run in the Web Dynpro application. Data, for example input helps, must be transferred from the back end to the form.
© SAP AG
HR280
5-29
For internal use by CSC only
For internal use by CSC only
The Form Builder – ISR Library, Elements, and Detailed Design of a Form
Library
© SAP AG 2008
Use the elements from the ISR library to create your form. Documentation about the ISR library and its elements is available. The following elements in the ISR library are useful to create an initial draft of a form: • ISR CI Process • ISR CH Embedded • ISR CH HalfWidth • ISR CI Embedded • ISR CI HalfWidth • ISR DE Empty • ISR DE Filled • ISR Footer • ISR Header To create the layout of the form, add fields to it. In particular, make use of the ISR library elements that begin with "ISR Text". The Hierarchy tab page provides a good overview of the elements and fields available. To delete fields from the form correctly, use the Hierarchy view. © SAP AG
HR280
5-30
Definition for Layout (Details)
For internal use by CSC only
For internal use by CSC only
Position static text (placeholder)
Edit static text
© SAP AG 2008
You edit static text as you would in any other conventional word processing program. First arrange the headings and different areas then insert the specific fields.
© SAP AG
HR280
5-31
For internal use by CSC only
For internal use by CSC only
Creating a Form: Detailed Design (Layout) – Insert Fields
© SAP AG 2008
Once you have created and named the different areas of your form, insert the fields from the ISR library and rename them.
© SAP AG
HR280
5-32
Include Fields
For internal use by CSC only
For internal use by CSC only
You can see the fields that have been added to the form scenario in the Form Builder
All available fields
All linked fields in the form © SAP AG 2008
In the end, you should have integrated all of the fields required in your form and linked them with the data fields in the back end (Data View). The Data View displays all of the available fields. In addition, fields that are linked are indicated as such (see screenshot).
© SAP AG
HR280
5-33
For internal use by CSC only
For internal use by CSC only
Create Form: Detail Design – Field Binding (1)
© SAP AG 2008
Once you have inserted the elements from the ISR library into the form (which is a purely visual element until this point), you have to link the elements and respective fields with the fields in your form scenario. To link the fields, proceed as follows: • Go to the Object tab page. • Choose the Binding tab page. • In the Default Binding field, click on the right arrow. • Select the form scenario. • Select the field name (follow the path until you are able to link the right field – see screenshot). Alternatively, you can link the form scenario fields with the elements in the form using drag and drop.
© SAP AG
HR280
5-34
For internal use by CSC only
For internal use by CSC only
Create Form: Detail Design – Field Binding (2)
© SAP AG 2008
On the Data View tab page, you can see all of the available fields. In the example above, you can see that the Street field has been included in the binding. It is marked as having been included in the binding in the data view, and in the Binding view you can see the default binding.
© SAP AG
HR280
5-35
For internal use by CSC only
For internal use by CSC only
Create Form: Detailed Design – Preview
© SAP AG 2008
To get an impression of how the form will look at runtime, you can choose the PDF Preview tab page. Once you have created or changed the form, you first have to activate it. When you activate the form, the objects are updated and the interface for the form is created.
© SAP AG
HR280
5-36
The New Design Time and the Form Builder – Summary
Use the basic functions of the new Design Time and the Form Builder
Enhance and adapt an existing form to include additional fields
For internal use by CSC only
For internal use by CSC only
You are now able to:
© SAP AG 2008
© SAP AG
HR280
5-37
For internal use by CSC only
For internal use by CSC only
5-38
HR280
© SAP AG
Exercises (2)/Solutions (2) Unit: HCM Processes and Forms – Practical Part Topic: Form Builder Preparation – Create ZCI Library
• Create or import the required ZCI library within the Form Builder for HCM Processes and Forms
1.
For internal use by CSC only
For internal use by CSC only
At the conclusion of this exercise, you will be able to:
Go to the Business Workplace (transaction SO01) in the back-end system and open the mail called ZCI Library with the attachment (ZCI Library).
© SAP AG
HR280
5-39
2.
Save the mail attachment in My Documents. Double-click the mail and switch to the Attachments tab page. Mark the attachment, right-click, and select Export attachment.
For internal use by CSC only
For internal use by CSC only
© SAP AG
HR280
5-40
3.
Navigate to the path My Documents and unzip the zip file that you have downloaded (choose Extract to ISR_Native_Controls):
For internal use by CSC only
For internal use by CSC only
© SAP AG
HR280
5-41
Go to the Form Builder and create the new library group ISR Library (which must be linked to the folder that you have just created):
Choose the symbol on the top-right of the palette (arrow) and choose Add Group… from the menu.
Enter ISR Library as the name of the new group.
© SAP AG
HR280
5-42
For internal use by CSC only
For internal use by CSC only
4.
For internal use by CSC only
For internal use by CSC only
Choose the symbol on the top-right of the new group (arrow) and choose Group Properties… from the menu.
Find the folder ISR_NativeControls_ERP2005…
© SAP AG
HR280
5-43
For internal use by CSC only
For internal use by CSC only
and select it.
Choose OK to confirm.
© SAP AG
HR280
5-44
Exercises (3) Unit: HCM Processes and Forms – Practical Part Topic: Design Time and Form Builder – Enhancing the Form Scenario and the Form to Include Additional Fields At the conclusion of this exercise, you will be able to: For internal use by CSC only
• Enhance an existing form
General description of this exercise: Enhance your group-specific process so that you can use your process and the form to adapt the following fields of the Addresses infotype: •
•
Fields that can be edited: •
Street
•
Postal Code
•
Location
Field to be displayed: •
Country key (this field should be displayed with the default value DE)
The entries for these form fields are to change/update the existing data record of infotype IT0006. The difference between the old and new processes is that additional fields are now shown and can also be saved to the back end. (Neither the number of process steps nor the roles responsible for the steps are changed.) To achieve this, you have to work through the following exercise which contains the following technical objects: •
Form scenario (add new fields)
•
Customizing for the SAP_AP service of your form scenario
•
Adobe form (form layout and interface update)
Use the slides contained in the unit as an aid. 1-1
Enhance your group-specific form scenario with the fields listed above.
1-2
Test the start step of your enhanced form scenario by starting the ZD## process using the existing test report in the back end. The start step should now show your 4 new fields, and the Country Key field should contain DE as a default value.
© SAP AG
HR280
5-45
For internal use by CSC only
• Enhance an existing form scenario
1-3
Add the fields to the form, link them with the new fields in the ISR/form scenario, and activate the form.
1-4
Test your process (for your employee) in the portal. Verify that the data has been written to the back end correctly (new data record in IT0015 and a modified/updated data record for IT0006/Subtype1).
For internal use by CSC only
For internal use by CSC only
© SAP AG
HR280
5-46
Solutions (3) Unit: HCM Processes and Forms – Practical Part
1-1
Enhance your group-specific process so that you can use your process and the form to adapt the following additional fields of the Addresses infotype: Street, Postal Code, City, and Country Key. Go to the Customizing activity for the Design Time for HCM Processes and Forms (transaction HRASR_DT). (Personnel Management → HR Administrative Services → Configuration of Forms/Processes → Design Time for Processes and Forms) In the dropdown list of available technical objects, select Form Scenario, then enter the ID of your scenario ZL##, and choose Display. Go to the Fields view. Choose the Service Fields pushbutton. Check that the following values are selected in the upper area of the dialog box: •
Back-End Service:
1 Infotypes for Personnel Administration
•
Infotype:
0006 (Addresses)
•
Screen Struct. Type:
MAIN
•
Infotype Vers.:
99 International
•
ScreenStruct:
HCMT_BSP_PA_XX_R0006
•
Operation:
Change
•
Subtype:
1 (Permanent Residence)
Choose the Determine Fields pushbutton. •
Choose the fields below by selecting the indicator in the Transfer field.
•
Overwrite the default name in the Field Name column with the information provided in the Name column.Copy the prefix "I0006_" to the name as shown below. Copy
© SAP AG
Field Name
Name
X
I0006_COUNTRY_KEY
Country Key
X
I0006_CITY
Street
X
I0006_POSTAL_CODE
Postal Code
X
I0006_STREET
Street Name HR280
5-47
For internal use by CSC only
For internal use by CSC only
Topic: Design Time and Form Builder – Enhancing the Form Scenario and the Form to Include Additional Fields
Choose Transfer. The Fields view should now appear as shown below: Field Name
Name
F…
I0006_COUNTRY_KEY
Country Key
I0006_CITY
Street
I0006_POSTAL_CODE
Postal Code
I0006_STREET
Street Name
F…
Default Value
For internal use by CSC only
Choose the Manually option in the Default Value Determination for Field I0006_COUNTRY_KEY dialog box and enter DE in the Data Binding in Service/Default Value column. Choose Transfer. The Fields view should now appear as shown below: Field Name
Name
F…
I0006_COUNTRY_KEY
Country Key
I0006_CITY
Street
I0006_POSTAL_CODE
Postal Code
I0006_STREET
Street Name
F…
Default Value Manual Default Value: DE
Save your entries.
© SAP AG
HR280
5-48
For internal use by CSC only
In the I0006_COUNTRY_KEY row, double-click on the Default Value column.
1-2
Test the start of the step in the enhanced form scenario using the back-end test report for the ZD## process. Go to the Customizing activity for the Design Time for HCM Processes and Forms (transaction HRASR_DT). (Personnel Management → HR Administrative Services → Configuration of Forms/Processes → Design Time for Processes and Forms)
Go to the highest level of the tree structure where the name of the process is displayed. Choose Process → Test. Enter the ID of your process and your personnel number 460##. Choose Execute (F8). 1-3
Add the new fields to the form and link them to the new fields in the ISR/form scenario. Go to the Customizing activity for the Design Time for HCM Processes and Forms (transaction HRASR_DT). (Personnel Management → HR Administrative Services → Configuration of Forms/Processes → Design Time for Processes and Forms) In the dropdown list of available technical objects, select Form Scenario, then enter the ID of your form scenario ZD##, and choose Display. Go to the Form view. Choose the Activate pushbutton. (The interface has now been updated with the form scenario and ISR scenario fields.) Choose the Change Form pushbutton. Change the name of the form from Request for Removal Bonus to HR280 Request for Removal Bonus/Address Change. In the Form Builder, navigate to the Library palette and choose the tab page of the ISR library you created. Check that you are using the right library. Your instructor provided you with instructions on how to include the correct library earlier.
Use drag & drop to place 4 fields in the area of the form in which Amount has already been placed (below the existing Amount field). Use the following elements from the library: •
ISR Text Edit (3x)
•
ISR Text Display (1x)
© SAP AG
HR280
5-49
For internal use by CSC only
For internal use by CSC only
In the dropdown list of available technical objects, select Process, then enter the ID of your process ZD##, and choose Display.
Select the Street field on the form. In the lower right area, select the Object tab page and then the Binding tab page on it. Click on the arrow to the right of the Default Binding (Open, Save, Submit) field: Select your form ZD##. Choose Street → Data → Field. Repeat these steps for the Postal Code, City, and Country Key fields.
Elements from ISR Library
Text After Positioning the Field on the Form
Overwrite Text With
ISR Text Edit Field
Text Label
Street
ISR Text Edit Field
Text Label
Postal code
ISR Text Edit Field
Text Label
Location
ISR Text Display Field
Dsp. Label
Country Key
For internal use by CSC only
For internal use by CSC only
Now overwrite the field labels as follows:
Click on the PDF Preview tab page to see how your layout looks. Save the form. Activate the form. 1-4
Test your process (for your employee) in the portal. Check whether the default value for the Country Key field is displayed correctly on the form. Test whether the data is saved correctly to the back end. Use the solutions in the "Execute Process" unit to run through and test the modified process in its entirety.
© SAP AG
HR280
5-50
Adobe Interactive Forms in SAP ERP 6.0 Practical Part: Unit Overview Diagram
Adobe Interactive Forms in SAP ERP 6.0 – Practical Part Lesson 1: Step-by-Step: Create/Edit Processes and Forms
For internal use by CSC only
For internal use by CSC only
Lesson 2: The New Design Time Lesson 3: The Form Builder Lesson 4: Workflow and Process Lesson 5: Further Customizing
© SAP AG 2008
© SAP AG
HR280
5-51
Workflow Builder - Unit Objectives
Use the basic functions in the Workflow Builder
Make simple adjustments to the workflow of a process
Enhance a two-step (approval) process to include an extra process step and make the necessary Customizing settings
For internal use by CSC only
For internal use by CSC only
At the conclusion of this lesson, you will be able to
© SAP AG 2008
© SAP AG
HR280
5-52
Implementation: The Workflow Builder The aim is to turn a two-step process into a three-step process at the end of this chapter Process 1 In the portal – INITIATOR (start application)
1
In the portal – INITIATOR (start application)
Select employee and process
Select employee and process
Form appears: Edit and send
Form appears: Edit and send
2
For internal use by CSC only
For internal use by CSC only
1
Process 2
Next processor's UWL inbox: Select work item Form appears: Edit (approve) and send
2
Next processor's UWL inbox: Select work item
3
Next processor's UWL inbox: Select work item
Form appears: Edit (approve) and send
End
Form appears: Edit (approve) and send
End
Save in the back end
Save in the back end
© SAP AG 2008
The Workflow Builder for creating the workflow template: Define process steps Specific container elements Specific start events Specific exit Link WF template with form scenario Steps with specific tasks Assign agents Activate event triggering
© SAP AG
HR280
5-53
Process Example 1: Process Flow and Workflow Process 1
1
In the portal – INITIATOR (start application)
Start = 1 Step 1 of the business process
Select employee and process
2
For internal use by CSC only
For internal use by CSC only
Form appears: Edit and send
= Step 2 of the business process
Next processor's UWL inbox: Select work item
2
Form appears: Edit (approve) and send
End
Save in the back end
© SAP AG 2008
© SAP AG
HR280
5-54
Process Example 2: Process Flow and Workflow Process 2
1
In the portal – INITIATOR (start application)
Start = 1 Step 1 of the business process
Select employee and process
Next processor's UWL inbox: Select work item
2
Form appears: Edit (approve) and send
2
3
= Step 2 of the business process
For internal use by CSC only
For internal use by CSC only
Form appears: Edit and send
= Step 3 of the business process
Next processor's UWL inbox: Select work item
3
Form appears: Edit (approve) and send
End
Save in the back end
© SAP AG 2008
© SAP AG
HR280
5-55
The Workflow Builder: Overview Customizing step
Header data
For internal use by CSC only
For internal use by CSC only
Graphical model
Overview area Navigation area
Area to display: WF containers My WFs and tasks …
Information area © SAP AG 2008
© SAP AG
HR280
5-56
For internal use by CSC only
For internal use by CSC only
The Workflow Builder: Settings for HCM Processes and Forms
© SAP AG 2008
To make the standard components for form scenarios available in the Workflow Builder, go to the Workflow Builder and choose My Workflows and Tasks in the lower left screen area. The view changes. Choose "". A dialog box appears. Enter the TG17900001 task group and start the search by choosing the green checkmark. The standard component repository for form scenarios is now available in your modeling environment.
© SAP AG
HR280
5-57
For internal use by CSC only
For internal use by CSC only
Creating a WF Template: Create a Container Element for the Process Object (1)
© SAP AG 2008
You now have to create a container element for the process object of the workflow template that you have created. When a user initiates a process in the portal, the following occurs in the back-end system: The TRIGGERED event is triggered for the persistent process object (class CL_HRASR00_WF_PROCESS_OBJECT) to which the workflow template reacts. The persistent process object is transferred to the workflow container so that data can be accessed while the process is being executed. To create a container element, proceed as follows: • Select Workflow Container from the dropdown list in the lower left area of the Workflow Designer for your template. • The elements for the workflow container are displayed. A few standard container elements will already exist. • To create a new entry in the container, choose Double-click for new entry. • A dialog box appears in which you can define the container element.
© SAP AG
HR280
5-58
For internal use by CSC only
For internal use by CSC only
Creating a WF Template: Create a Container Element for the Process Object (2)
© SAP AG 2008
The name of this container element, "PROCESS_OBJECT", must be entered exactly as "PROCESS_OBJECT" because the program logic expects the container element called "PROCESS_OBJECT". If you enter a different name, the workflow will not work. Choose the D. Type tab page. Select the ABAP Class option as the object type and enter the following name for the class: CL_HRASR00_WF_PROCESS_OBJECT. In the same dialog box, choose the Attributes tab page. Set the parameter settings for "PROCESS_OBJECT" as an element to be imported (set the indicator). This element is to be received by means of the event TRIGGERED.
© SAP AG
HR280
5-59
Creating a WF Template: Define Start Events for the Workflow Basic data
For internal use by CSC only
For internal use by CSC only
Navigate to event control for the WF template
Activate event control in the WF template © SAP AG 2008
You now have to define the start event for the workflow. The workflow should react to the TRIGGERED event of the CL_HRASR00_WF_PROCESS_OBJECT class. You define this in the header data (basic data) of the workflow. Choose the Basic Data pushbutton in the upper area of the toolbar. This takes you to the event control settings for a process. On the "Version-INdependent (Task)" tab page, choose the "Start Events" tab. Define "CL" as the category in the first line, "CL_HRASR00_WF_PROCESS_OBJECT" as the object type, and "TRIGGERED" as the event of the object, then confirm these entries with the return key. Note that the two small boxes (in the Binding column – only the letter "B" is visible here) and the diamond (in the Active column – only the letter "A" is visible here) are not depicted in color, but are grayed out. This indicates that binding does not yet exist and that the start event has not been activated. Click on the button with the two small boxes (within this line). Here, you define the data binding from the event container to the workflow container.
© SAP AG
HR280
5-60
For internal use by CSC only
For internal use by CSC only
Creating a WF Template: Define Start Events for the Workflow (2)
Define the binding between the event container and workflow container
© SAP AG 2008
A dialog box displays the binding between the event container and workflow container. The elements in the event container are listed on the left-hand side, while on the right-hand side you can see the elements of the workflow container. The lower screen area shows the actual binding between the two containers. The Workflow Designer proposes some bindings here, which you can accept as they are. &EVT_CREATOR&
&_WF_INITIATOR&
&EVT_OBJECT&
&PROCESS_OBJECT&
Close the dialog box by choosing the green checkmark.
© SAP AG
HR280
5-61
Creating a WF Template: Define Start Events for the Workflow (3)
For internal use by CSC only
For internal use by CSC only
Now appears in color
Æ Start event has been defined
© SAP AG 2008
Note that the two small boxes that you clicked on previously when they were grayed out are now green. This means that the data binding between the event container and the workflow container has been defined. To activate the start event, click on the grayed out diamond in the Active column. The diamond will also turn green to indicate that it is active.
© SAP AG
HR280
5-62
For internal use by CSC only
For internal use by CSC only
Create WF Template: Define Program Exits for the Workflow
© SAP AG 2008
To ensure the process flows smoothly with the process object, you have to define a specific class in the program exit of the workflow. To do so, go into the basic data of the workflow. On the Version-Dependent (Current Workflow Version) tab page, select the Program Exits tab page. Define class CL_HRASR00_POBJ_WF_EXIT for the program exit. Choose Enter. You will notice that the display turns green. This confirms that a correct program exit exists.
© SAP AG
HR280
5-63
For internal use by CSC only
For internal use by CSC only
Create WF Template: Define Process Flow
© SAP AG 2008
Tip: Save the workflow template at this stage because you have now completed the mandatory entries and basic configuration options. You now want to add an extra step (edit form) to the workflow template.
© SAP AG
HR280
5-64
For internal use by CSC only
For internal use by CSC only
Create WF Template: Define Process Flow – Insert Process Step
2) An additional step now appears in the overall workflow process. 1) Position it using drag and drop
3) Double-click to open the settings for the process step
© SAP AG 2008
In the My Workflows and Tasks area, navigate to the folder under Components for HCM Processes and Forms → Task Groups→ TG17900002 → Process Form (Process Form). Choose Process Form and move it to the right place in the workflow using drag and drop. An additional step now appears in the overall workflow process (see the screenshot above) To make process-step-specific Customizing settings, double-click on the workflow step you have just created.
© SAP AG
HR280
5-65
Enter the new name of the workflow or process step. For example, from Process Form to Step 1 in WF.
For internal use by CSC only
For internal use by CSC only
Create WF Template: Define Process Step Name
© SAP AG 2008
The workflow template now appears as shown above. To change the step name, rename the Step Name field (from Process Form to Step 1 in WF).
© SAP AG
HR280
5-66
For internal use by CSC only
For internal use by CSC only
Create WF Template: Remove Unused Steps
© SAP AG 2008
The next task is to remove unused steps from from the workflow. Select the "undefined" step, click on the right mouse button, and choose Delete. Confirm deletion in the popup. The workflow then looks the way it does on the next page.
© SAP AG
HR280
5-67
For internal use by CSC only
For internal use by CSC only
Create WF Template: Container Elements for Step
© SAP AG 2008
Check the workflow container elements. You will see that additional container elements are now available. The workflow modeler created these automatically when the additional workflow step was added (using Process Form). The elements correspond to the imported and exported elements in the task container.
© SAP AG
HR280
5-68
For internal use by CSC only
For internal use by CSC only
Create WF Template: Main Container Element
© SAP AG 2008
You must specify for the Form container element which form scenario and/or form scenario version is to be used. To do so, double-click on the Form container element. The right data type has been created already. Now enter the form that you want to be used. Switch to the Initial Value tab page and enter the name of the form scenario.
© SAP AG
HR280
5-69
Technical Overview: Step-Specific Customizing Process 1
1
In the portal – INITIATOR (start application) Select employee and process
Next processor's UWL inbox: Select work item
2
Workflow Builder
Form appears: Edit (approve) and send
End
For internal use by CSC only
For internal use by CSC only
Form appears: Edit and send
Save in the back end
Design Time
1
2
© SAP AG 2008
Diagram on the left-hand side: Step 1 of the workflow is the second business step in the process. Right-hand side: Customizing settings for step 1 (definition of the step in the workflow template) You are provided with the attributes from the Customizing settings for the step at runtime The business step of a process is controlled by the following: • the workflow step Customizing entity (above right) • the form scenario entity (below right)
© SAP AG
HR280
5-70
For internal use by CSC only
For internal use by CSC only
Create WF Template: Configure Step
© SAP AG 2008
You now have to configure the Step 1 in WF step. To do so, double-click on Step 1 in WF in the overview.
© SAP AG
HR280
5-71
For internal use by CSC only
For internal use by CSC only
Create WF Template: Step – Define Processor
Result:
√
© SAP AG 2008
You define the processor (initiator of the workflow instance) on the Control tab page in the Processor area. Click the field beside Expression. A popup appears. Choose WF_INITIATOR as the processor under the Container folder.
© SAP AG
HR280
5-72
For internal use by CSC only
For internal use by CSC only
Create WF Template: Step – Binding
© SAP AG 2008
© SAP AG
HR280
5-73
For internal use by CSC only
For internal use by CSC only
Create WF Template: Step – Binding (Container)
Before
After
Workflow container
Task container
© SAP AG 2008
The objective now is to define the binding for the workflow step To do this, go to the Control tab page for the workflow step and choose the Binding (Exists) pushbutton The popup displays the automatically generated workflow bindings to/from the workflow container to/from the task container. These are the detailed container elements that contain the precise Customizing settings for the workflow and workflow steps Change the value for the &Send_VARIATION& container element to A. This means that data is saved to the back end in this step when the user chooses the Send pushbutton. Change the value for the &FORM& container element to ZF## (## = your group number). ZF## represents the name of the form scenario to be used Change the value for the &FORM_SCENARIO_STAGE container element to FSS_1. The container elements that are available through the HRAS task define which Customizing settings for the workflow can be made at step level.
© SAP AG
HR280
5-74
The different container elements have the following meaning: • &BACK_BUTTON_VISIBLE& = visibility of the back button • &FORM& = form used • &FORM_SCENARIO_STAGE& = form scenario step • &SAVE_DRAFT_BUTTON_VISIBLE& = visibility of Save Draft button • &SEND_EXPERT_IF_INCONSISTENT_DATA& = behavior of Send to Expert button • &WITHDRAW_PROCESS_BUTTON_VISIBLE& = prevent process button from being visible
© SAP AG
HR280
For internal use by CSC only
For internal use by CSC only
• &SEND_VARIATION& = Behavior when sending (save to back end)
5-75
Create WF Template: Complete and Activate WF Template
For internal use by CSC only
For internal use by CSC only
Activate
© SAP AG 2008
You have now defined all of the fundamental aspects of the workflow. The next step is to activate it. To do so, choose the Create and Activate Runtime Version pushbutton.
© SAP AG
HR280
5-76
Create WF Template: Syntax Check and Activation
For internal use by CSC only
For internal use by CSC only
Syntax check
© SAP AG 2008
Once you have activated the workflow, check its syntax. To do so, choose the Syntax Check pushbutton. In the message area (choose Result of Syntax Check in the lower area), you can obtain a host of information, for instance that some of the container elements are not being used. Since these container elements may be of use at a later point in time and do not have a detrimental effect, you do not need to delete them.
© SAP AG
HR280
5-77
Architecture: Components in a Process P R O C E S S (consists of...) Form scenario: Definition for fields, attachments, links
Form scenario step 1 : Definition for fields, attachments, links
For internal use by CSC only
For internal use by CSC only
Form scenario step...: Definition for fields, attachments, links
ISR scenario: Form and interface definition Interface Form
Workflow template: Definition of the process flow Æ definition of the process steps and which form scenario step is to be used
© SAP AG 2008
© SAP AG
HR280
5-78
Architecture: Design Entities and Front-End Components/Applications – Overview Implementation of a process: Summary after the WF template has been completed
Form scenario:
Field definition
ISR scenario:
Interface definition and form
Workflow template:
Definition of process flow (SAP Business WF)
Start application:
Runtime application (portal iView)
Form application:
Runtime application (portal iView)
Digital personnel file:
Runtime application (portal iView)
For internal use by CSC only
For internal use by CSC only
Process (Design Time)/Process Object (Runtime)
© SAP AG 2008
© SAP AG
HR280
5-79
Architecture: Step Level/Form Application and Control Process
Step 2
Step 1 Select WI
Step 3
Edit and send form
Form application
For internal use by CSC only
View: Edit
View: Check and send Org. reassignment
Org. reassignment Employee: …
1
View: Finished
For internal use by CSC only
Process execution
Data sent
Employee: …
2
Save draft
Save draft
Check and send
Send
3
WS-Template with HRAS-specific components WF step for process step 2 Process control
- task: Process form - Form_Scen: SOC1 - Save_Draft: X - Withdraw: -
© SAP AG 2008
1) The task that is used in the workflow step controls: - which and how many views are displayed in the form application. The process form task has been used in this example, which means that the Edit, Send and Check, and Finished views are shown. If you use the approve form task, only the Approve/Reject and Finished views are shown. 2) The form scenario that is used in the workflow step controls: -
which form is to be displayed. The org. reassignment form (ID: SOC1) has been used in this example.
-
which categories of attachment can be added/displayed
-
which additional information is provided in this step (not shown in the graphic above)
3) The Save_Draft container element controls: -
whether the save draft function is available in this step or not. In this example, the container element has been activated (value X), which means that the Save Draft pushbutton appears in the form application.
© SAP AG
HR280
5-80
Architecture: Process Example Process 1 (switch for position) Form scenario/ISR scenario 1
Form scenario/ISR scenario 2
Adobe form (layout) 1
Adobe form (layout) 2
Form 1
Form 1
Form 1
Form 2
Form 2
Form 2
Step 1
Step 2
Step 3
Step 4
Step 5
Step 6
Start application
UWL
UWL
UWL
UWL
UWL
Role 1
Role 2
Role 3
Role 4
Role 5
For internal use by CSC only
For internal use by CSC only
Data transfer
Role 6
ERP
Workflow template (WS) 1 © SAP AG 2008
© SAP AG
HR280
5-81
For internal use by CSC only
For internal use by CSC only
Processes – Creating a New Process
© SAP AG 2008
To create a new process form scenario, choose Process from the dropdown list and enter a (new) object name in the field below. If the object does not yet exist, the system asks if you would like to create it. Next, you can make the following settings • Process description • Validity period • Corresponding form scenario • Initiator role Note: Some process attributes are time-dependent. You can define more than one validity period for a process. You can create a new validity period for a process as follows: • Go to Process → Validity Period in the menu and change the attributes for the process.
© SAP AG
HR280
5-82
For internal use by CSC only
For internal use by CSC only
Process Definition – Overview with Administrative Information
© SAP AG 2008
The system displays an overview of administrative data, the validity of which is dependent on the version, with the following options: Process name and description Permit a parallel run for a process Determine if an expert can withdraw a process if errors occur. You can define a role that is informed if errors occur. You can group processes for authorization purposes. Process groups are useful, for example, if you have two different HR Administrator teams and each team is to call up a process for its own area only. One team might, for instance, only be able to start and execute processes for the USA, while the other can only do so for Germany.
© SAP AG
HR280
5-83
For internal use by CSC only
For internal use by CSC only
Process Definition – Settings for Start
© SAP AG 2008
In this configuration option, you determine the validity of processes. You can also define whether the Forward to Expert pushbutton is visible in the start application. Define whether the processor is also able to send the form if an error message appears (in an errortolerant process) or whether error messages are not to be tolerated. In addition, you can define whether the process can also be started without a start object (for example, to be set up).
© SAP AG
HR280
5-84
For internal use by CSC only
For internal use by CSC only
Process Definition – Workflow and Event Type Linkage
© SAP AG 2008
You define the workflow using the Workflow Builder (transaction SWDD). You can specify the corresponding workflow for the process in this step. The event type linkage is generated automatically, also in this view. You can deactivate the event type linkage. The required function module for checking, HR_ASR_CHECK_EVENT, is automatically created in the Event Type Linkage table (transaction SWETYPV).
© SAP AG
HR280
5-85
Process Definition – Role Assignment
For internal use by CSC only
For internal use by CSC only
Which role is a process to be visible for in the portal? You determine here which initiators can execute the process. The process only appears in the portal for this group.
© SAP AG 2008
In the Role Assignment configuration option, you determine which initiator roles (HR Administrator, manager, employee, XI inbound, EIC agents) can start a process in the portal. You can define further restrictions, such as particular object groups (DE processes, US processes). Using feature maintenance for PASRG (transaction PE03), you can define who is assigned to this object group.
© SAP AG
HR280
5-86
Overview of All Processes Depending on the Role or Initiator (1)
IMG: Æ HR Administrative Services Æ Configuration of Forms/Processes Æ Process Configuration Æ Set Up Processes Æ Validity for Process Start Æ Specify Valid Processes for Start Applications
For internal use by CSC only
For internal use by CSC only
Definition of the processes that should be displayed for each initiator/role.
© SAP AG 2008
The Specify Valid Processes for Start Applications Customizing activity provides an overview of the roles (initiators) that valid start processes have been assigned to (HR Administrative Services → Configuration of Forms/Processes → Process Configuration → Set Up Processes → Validity for Process Start → Specify Valid Processes for Start Applications). Choose a work area, for example HR Administrator.
© SAP AG
HR280
5-87
For internal use by CSC only
For internal use by CSC only
Overview of All Processes Depending on the Role or Initiator (2)
Form display in the portal
Form is selected in the back end as valid (to be displayed)
© SAP AG 2008
The Valid Processes for Start Applications view, offers an overview of all processes with their process descriptions. The validity periods are entered in the Start Date and End Date columns. The Valid column indicates whether a particular process is to be displayed for the role selected (in this case HR Administrator). If the indicator is set, the process and corresponding forms are displayed in the portal for this role and can be used.
© SAP AG
HR280
5-88
Process Definition – Assignment to Process Groups
For internal use by CSC only
For internal use by CSC only
Process Process group group to to be be assigned assigned to to the process the process
Overview Overview of of processes processes assigned assigned to to the the process process group group
© SAP AG 2008
In the Assignment to Process Groups configuration option, you define which process the system is to make available depending on the process group assigned. When you set up the process group, the system only displays those processes as user interfaces that have been assigned to the group and are valid. Example: • Processes without objects are executed with a particular application in which the Select Employees step is skipped. • It makes sense to assign those processes that can start without an object to a process group so that you can then assign the process group to the respective start application. • Process groups are also used for EIC integration. Processes that are processed by EIC agents of a particular category or subcategory should be assigned to a process group. The process group is then assigned to the category/subcategory.
© SAP AG
HR280
5-89
For internal use by CSC only
For internal use by CSC only
Process Definition – Collision Definition
© SAP AG 2008
In the Collision Definition configuration option, you define which processes you want to be subject to a collision check. The system uses the collision check to ensure that certain processes cannot be started or particular messages appear in the following circumstances: • Another particular process (within the collision group) has already been started. • Another particular process has already been completed. You use the collision group to group together processes so that they can be checked against each other for collisions. You determine what kind of message (information, warning, error message) you want to be displayed in the event of a collision.
© SAP AG
HR280
5-90
For internal use by CSC only
For internal use by CSC only
Process Definition – Transfer Field Values and Attachments
© SAP AG 2008
In the Change Transfer of Field Values configuration option, you can define which field values you want to be transferred between the different form scenarios in a process that contains several form scenarios. You also define here which attachment types you want to be transferred between the form scenarios in a process.
© SAP AG
HR280
5-91
Test/Check
In the Event of a Problem
Process in start application?
IMG: Process Customizing activities (define process, configure start application, validity for start application)
Does the form appear in the Edit view?
IMG: Check consistency for form scenarios
Can the form be sent? Does the work item appear in the next processor's UWL?
SCASE: Process object created?
Adobe Reader: Correct version?
For internal use by CSC only
For internal use by CSC only
Test Process
Workflow Builder: Instance created? Status? Processor? UWL Customizing OK? IMG: Check consistency for process IMG: Test process execution
Is data saved to the back end after the save to back end step?
WF Builder: Verify the step (&SEND_VARIATION&) at which the data is to be saved to the back end
© SAP AG 2008
© SAP AG
HR280
5-92
Workflow Builder – Summary
Use the basic functions in the Workflow Builder
Make simple adjustments to the workflow of a process
Enhance a two-step (approval) process to include an extra process step and make the necessary Customizing settings
For internal use by CSC only
For internal use by CSC only
You are now able to:
© SAP AG 2008
© SAP AG
HR280
5-93
For internal use by CSC only
For internal use by CSC only
5-94
HR280
© SAP AG
Exercises (4) Unit: HCM Processes and Forms – Practical Part Topic: Workflow Builder – Enhancing the Process to Include an Additional Step (Enhance the Workflow Template) • Enhance a workflow template for HCM Processes and Forms
General description of this exercise: Enhance your group-specific process to include a third role. •
This role should receive the form after the start step and before the actual original step.
•
This role should receive exactly the same form that is already used in the process.
The difference between the old and new processes is that you have to adapt the workflow template for your process. Complete the following exercise for this: 1-1
Prepare your Workflow Builder so that you are able to work with the components of HCM Processes and Forms.
1-2
Add a new step to your workflow template. You must add this step before the existing step. It should be based on the "Process Form" task (TS17900100). (Use the slides contained in the unit as an aid.) Add the new step to the workflow. Adjust the binding between the Workflow container and Task container by entering values for Form and Form_Scenario_Stage. Determine the program exit. Define the agent: Choose WF Initiator as the agent. Check and activate your workflow template.
1-3
Test the adapted process (for your employee) in the portal. After the process has been started, you should receive two work items (one after the other) in your UWL inbox.
© SAP AG
HR280
5-95
For internal use by CSC only
For internal use by CSC only
At the conclusion of this exercise, you will be able to:
For internal use by CSC only
For internal use by CSC only
5-96
HR280
© SAP AG
Solutions (4) Unit: HCM Processes and Forms – Practical Part
1-1
Prepare your Workflow Builder so that you are able to work with the components of HCM Processes and Forms. Start the Workflow Builder (transaction SWDD). Select the My Workflows and Tasks view in the list (in the lower left screen area). Choose . Go to the Task groups tab page. Enter TG17900001 (Components for HCM Processes and Forms). Confirm your entry.
1-2
Add a new step to your workflow template. You must add this step before the existing step. It should be based on the "Process Form" task (TS17900100). Start the Workflow Builder (transaction SWDD). Enter the ID of your workflow in the Workflow field or use the abbreviation (ZE##) to search. Verify that YOUR workflow is displayed (ID and abbreviation). Switch from the display mode to change mode. Select the My Workflows and Tasks option from the list (in the lower left screen area). Open the Components for HCM Processes and Forms folder. Open the Task Groups folder. Open the Interact. Components in HRASR (TG17900002) folder. Locate the Process Form (TS17900100) task. Position this task above the existing step by drag and drop. Double-click on the step you have just created in the workflow. (You should now see the Control tab page. If not, go to the Control tab page.) Rename the step (Step Name field) from Process Form to Step 1 in WF.
© SAP AG
HR280
5-97
For internal use by CSC only
For internal use by CSC only
Topic: Workflow Builder – Enhancing the Process to Include an Additional Step (Enhance the Workflow Template)
In the Agent area, choose the Workflow Initiator (Expression) option from the dropdown list. Go to the Program Exits tab page. In the Class field, enter: CL_HRASR00_POBJ_WF_EXIT. Return to the Control tab page. Choose the Binding (Exists) pushbutton.
For internal use by CSC only
Change the binding for the container elements as follows: •
FSS_1 for &FORM_SCENARIO_STAGE &
•
ZE## and Version 0000 for &FORM&
Confirm all of your entries for the new step by clicking on the green confirm pushbutton (you should now be back on the overview page of the workflow). Activate your workflow definition by choosing the Activate pushbutton or CTRL+F3. 1-3
Test the modified process (for your employee) in the portal. After the process has been started, you should receive two work items (one after the other) in your UWL inbox. Test the process using the Process Browser (Search Processes).
© SAP AG
HR280
5-98
For internal use by CSC only
A dialog box appears showing the binding between the workflow container and step container.
Adobe Interactive Forms in SAP ERP 6.0 Practical Part: Unit Overview Diagram
Adobe Interactive Forms in SAP ERP 6.0 – Practical Part Lesson 1: Step-by-Step: Create/Edit Processes and Forms
For internal use by CSC only
For internal use by CSC only
Lesson 2: The New Design Time Lesson 3: The Form Builder Lesson 4: Workflow and Process Lesson 5: Further Customizing
© SAP AG 2009
© SAP AG
HR280
5-99
Further Customizing – Unit Objectives
At the end of this lesson, you will be able to Make further Customizing settings for z
Attachment types, additional information (links), and form scenario steps
z
Business statuses
Adjust your workflow template to achieve behavior specific to each scenario step
Set up a process start without an object
Create fast data entry and mass processes
For internal use by CSC only
For internal use by CSC only
© SAP AG 2009
© SAP AG
HR280
5-100
For internal use by CSC only
For internal use by CSC only
Customizing Settings for Attachment Types
© SAP AG 2009
The Attachment Types Customizing option under Other Attributes allows you to define whether attachments can/must be added to a given form scenario step. To defnine an attachment type, click the Attachment Types field and choose Z_MOV_EXP here. The attachment type is then available for the specific form scenario step.
© SAP AG
HR280
5-101
For internal use by CSC only
For internal use by CSC only
Customizing Settings for Additional Information (Links)
© SAP AG 2009
The Additional Information Customizing option under Other Attributes allows you to define whether additional information can/must be added to a given form scenario step in the form of links. To define additional information, click the Addnl Information field and choose REMOVE_INFO_1 and REMOVE_INFO_2 here. These two additional sources of information are then made available as links in the particular form scenario step.
© SAP AG
HR280
5-102
For internal use by CSC only
For internal use by CSC only
Customizing Settings for Form Scenario Steps (1)
© SAP AG 2009
At least one form scenario step must be defined. Prior to EhP3, you had to create this step manually.
© SAP AG
HR280
5-103
For internal use by CSC only
For internal use by CSC only
Customizing Settings for Form Scenario Steps (2)
© SAP AG 2009
FSS_2 and FSS_3 are the newly defined form scenario steps. To obtain a good overview, you should always set up form scenario steps to correspond to your business steps. The form scenario steps are linked to one another by making binding settings in the Workflow Builder for each step. Go to the binding settings and make an entry there for the binding between workflow container and step container, for example &FORM_SCANRIO_STAGE& = FSS_2.
© SAP AG
HR280
5-104
Adjust Your Workflow Template to Achieve Behavior Specific to Each Scenario Step (1)
For internal use by CSC only
For internal use by CSC only
= Start Step 1 of the business process
= Step 2 of the business process
= Step 3 of the business process
© SAP AG 2009
© SAP AG
HR280
5-105
For internal use by CSC only
For internal use by CSC only
Adjust Your Workflow Template to Achieve Behavior Specific to Each Scenario Step (2)
© SAP AG 2009
© SAP AG
HR280
5-106
For internal use by CSC only
For internal use by CSC only
Adjust Your Workflow Template to Achieve Behavior Specific to Each Scenario Step (3)
© SAP AG 2009
© SAP AG
HR280
5-107
For internal use by CSC only
For internal use by CSC only
Adjust Your Workflow Template to Achieve Behavior Specific to Each Scenario Step (4)
© SAP AG 2009
© SAP AG
HR280
5-108
WF Template: Complete Once you have made all settings, do not forget to activate your workflow in the final step
For more information, see the slide:
For internal use by CSC only
For internal use by CSC only
(and to carry out a syntax check)
"Create WF Template: Complete and Activate WF Template"
© SAP AG 2009
© SAP AG
HR280
5-109
Process Start without Object - Options Process Design Option 1:
Step 1
Step 2
Step 3
Form
Form
Form
Update of POBJ and EE
Defaults and Checks against different Objects (User, PD Object ...)
Process Design Option 2: The object is not assigned at any stage of the process. Form data is saved only in the process object.
For internal use by CSC only
For internal use by CSC only
The assignment of an employee takes place before saving, not at the start of a process
Assigned Employee
Step 1
Step 2
Step 3
Form
Form
Form
Update of POBJ
Defaults and Checks against different Objects (User, PD Object ...)
POBJ
© SAP AG 2009
In the former process design, the employee was selected in the first process step (except in hiring processes). With EhP4, you can now start a process without having to select an employee beforehand. The employee can be now assigned at a later stage of the process. However, he/she must be assigned before the data is saved in the back-end system (option 1). Depending on the process definition, it is also possible to start and run a process without any object assignment. In this case, the data cannot be saved in the infotype of the back-end system, rather it is saved in the process object of Case Management (option 2).
© SAP AG
HR280
5-110
Process Start without Personnel No. – Customizing (1) The The object object type type "Job" "Job" is is marked marked as as used used and and therefore therefore appears appears in in the the start start application application in in the the input input help help
For internal use by CSC only
For internal use by CSC only
Define Define Properties Properties of of Object Object Types Types
© SAP AG 2009
To enable the process start without an object, go to the IMG activity: Personnel Management Æ HR Administrative Services Æ Configuration of Forms/Processes Æ Process Configuration Æ Set Up Processes Æ Validity for Process Start Æ Define Properties of Object Types In the first step of this IMG activity, specify the object types available in the application. If you deselect the object type "Job", then it is not available in the start application in the input help.
© SAP AG
HR280
5-111
Process Start without Personnel No. – Customizing (2) Define Define Properties Properties of of Object Object Types Types
For internal use by CSC only
For internal use by CSC only
Specify Specify whether whether ‘Skip ‘Skip Object Object Selection’ Selection’ is is visible visible or or not not
© SAP AG 2009
In the second step of this IMG activity, you specify whether the optionSkip Employee Selection is visible in the application for the different roles (manager, HR Administrator Role). If this is required for the personnel number, then create a new entry for object type P in the object attributes dialog structure.
© SAP AG
HR280
5-112
For internal use by CSC only
For internal use by CSC only
Process Start without Personnel No. – Workflow (1)
© SAP AG 2009
If you want to assign an employee (or object) to the process in a later step, specify using the Customizing step in the workflow in which process step the object/employee assignment is possible. Call the Workflow Builder (transaction SWDD). Select the corresponding workflow there and doubleclick the workflow step that you want to release for object/employee assignment. Choose Binding (Exists).
© SAP AG
HR280
5-113
For internal use by CSC only
For internal use by CSC only
Process Start without Personnel No. – Workflow (2)
Agent Agent can can find find and and assign assign personnel personnel number number
© SAP AG 2009
If this container element is not in the binding list, just drag and drop it from the area on the top-right to the right side of the binding area. For the container element &ASSIGN_OBJECT&, select the parameter ‘‘X’ = Pushbutton is Visible and Active. The agent of this workflow step is now able to search for a personnel number and assign it to the process.
© SAP AG
HR280
5-114
Fast Data Entry and Mass Start of Processes Fast Data Entry or Mass Start of an Employee Process 1
3
Edit Data
Edit Data
Edit Data The first agent starts the process - one step or multi-step. You enter the data for multiple employees.
Edit Data
Edit Data
Edit Data
If it is a multi-step process, a process instance is generated for each employee selected.
Each employee’s form is sent to the next relevant agent.
For internal use by CSC only
For internal use by CSC only
Start process
2
© SAP AG 2009
It is possible to start a process for more than one employee at the same time. This can be a single-step process where you want to change specific data for a number of employees. This can also be a multi-level process where individual process instances are generated for each employee selected in the request step, for example Special Payment for Mass Start.
© SAP AG
HR280
5-115
Fast Data Entry/Mass Process
Fast Data Entry Execution
Design A fast data entry scenario is set up just like a form scenario; however, it requires some additional definitions: defined columns, sequence of columns, and so on
Portal Role HR Administrator Selection of Employees
For internal use by CSC only
For internal use by CSC only
Fast Data Entry Design
Web Dynpro changed
Update
Employee 1 Employee 2 Employee n
© SAP AG 2009
This function is used to enter data for more than one employee at the same time. An HR Administrator can search for employees using the search function, and a manager can select employees within his/her area of responsibility. No workflow is involved in the one-step fast data entry process. This is a Web Dynpro application that does not use a form. You can use the same application for fast data entry as you do for mass processing. Fast data entry and mass processing processes are called using the same link.
© SAP AG
HR280
5-116
For internal use by CSC only
For internal use by CSC only
Fast Data Entry – Form Scenario Customizing
© SAP AG 2009
The form scenario of a fast data entry process has no major differences from the processes for individual persons. In the last column Field Sequence, you define the sequence of the fields. In the column Field Attribute, you define the field attributes. We recommend that you select the personnel number as the first field and the name of the employee as the second field. You should also maintain the field names beside them.
© SAP AG
HR280
5-117
For internal use by CSC only
For internal use by CSC only
Fast Data Entry – Process Customizing
© SAP AG 2009
You must define the process type at process level. Here choose Enable Mass Start of Processes.
© SAP AG
HR280
5-118
Mass Process: Process Design and Process Instance Process Design
Step 1
Step 2
Step 3
"Mass Start"
Form
Form
Process Instance
Step 2
Step 1 Selection of Employees
Form Empl.Form 1 Empl.Form 2 Empl. n
Web Dynpro
Step 3
For internal use by CSC only
For internal use by CSC only
Update
Form Empl.Form 1 Empl.Form 2 Empl. n
Update
Process Instance 1 Employee 1 Process Instance 2 Employee 2 Process Instance n Employee n
© SAP AG 2009
You use the same link to call mass processing processes and fast data entry processes. A mass processing process starts a process for multiple empoyees at the same time that contains a workflow. If the first agent starts the process, a process object is created and a workflow instance is opened for each selected employee. The agents of the following process steps receive a workflow item in their universal worklist (UWL) for each employee.
© SAP AG
HR280
5-119
For internal use by CSC only
For internal use by CSC only
Mass Process: Form Scenario Customizing
© SAP AG 2009
The form scenario of a mass process has no major differences from the processes for individual persons. In the last column Field Sequence, you define the sequence of the fields. We recommend that you select the personnel number as the first field and the name of the employee as the second field.
© SAP AG
HR280
5-120
For internal use by CSC only
For internal use by CSC only
Mass Process: Process Customizing
© SAP AG 2009
You must define the process type at process level. Here choose Enable Mass Start of Processes.
© SAP AG
HR280
5-121
For internal use by CSC only
For internal use by CSC only
Business Status Customizing
© SAP AG 2009
To maintain the business status, go to the IMG activity: Personnel Management Æ HR Administrative Services Æ Configuration of Forms/Processes Æ Process Configuration Æ Set Up Processes Æ Maintain Business Status The business status is based on the processing status. Therefore, you must first select a processing status.
© SAP AG
HR280
5-122
For internal use by CSC only
For internal use by CSC only
Maintain Business Status
© SAP AG 2009
Choose "New Entries" and enter the business status and the new business ID. The business status text is then displayed in the process browser.
© SAP AG
HR280
5-123
For internal use by CSC only
For internal use by CSC only
Maintain Business Status for Request Step
© SAP AG 2009
In this view, maintain the business status for the first process step; that is, before the workflow is started. You make settings in Customizing for the other process steps in the Workflow Builder.
© SAP AG
HR280
5-124
Maintain Business Status in the Workflow
2. Select input help
For internal use by CSC only
For internal use by CSC only
1. Drag node down
3. Maintain business status
© SAP AG 2009
Call the Workflow Builder (transaction SWDD) and enter the name of the workflow. Double-click to select the workflow step whose business status you want to maintain: Go to the Control tab page and choose Binding. If the container element &BUSINESS_STATUS& is not in the list, use Drag&Drop to move it from the area on the top-right to the list. Then go to the related field on the left to display the input help button. Choose this button and choose Enter Constant in the window that is displayed. Now assign the business status to the processing status.
© SAP AG
HR280
5-125
Further Customizing – Summary
Make further Customizing settings for Attachment types, business status, additional information (links), and form scenario steps
Adjust your workflow template to achieve behavior specific to each scenario step
Set up a process start without an object
Create fast data entry and mass processes
For internal use by CSC only
For internal use by CSC only
You are now able to:
© SAP AG 2009
© SAP AG
HR280
5-126
Exercises (5) Unit: HCM Processes and Forms – Practical Part Topic: Further Customizing – Additional Process Enhancements At the conclusion of this exercise, you will be able to: For internal use by CSC only
For internal use by CSC only
• Configure the way in which attachments are handled for your process • Configure additional links for your process • Configure the form scenario steps • Configure the functions in the form application (save draft, back to author, and so on)
General description of this exercise: Enhance your group-specific process as follows: Step 1 (Start)
Step 2
Step 3
Enhancements
Enhancements
Enhancements
• Additional link
• Additional link
•
Additional link
• Add attachments
• Add attachments
•
Add attachments
1-1
Enhance the process so that additional links appear and you can add attachments. The links that have been defined already, namely: •
REMOVE_INFO_1 ( HR280 Process Information) and
•
REMOVE_INFO_2 (HR280 Process Information)
should be available. In addition, it should be possible to add the following attachment category: • 1-2
Z_MOV_EXP
Test the modified process (for your employee) in the portal.
© SAP AG
HR280
5-127
1-4
Enhance your process in such a way that the added functions (see above) appear in the stepspecific form. In addition, the Save Draft function should be available in step 3. Step 1 (Start)
Step 2
Step 3
Enhancements
Enhancements
Enhancements
• Additional link
• NO additional link
•
NO additional link
• Add attachments
• Attachments are display ONLY
•
Add attachments
•
Save draft For internal use by CSC only
For internal use by CSC only
1-3
Test the modified process (for your employee) in the portal.
© SAP AG
HR280
5-128
Solutions (5) Unit: HCM Processes and Forms Topic: Further Customizing – Additional Process Enhancements Enhance your group-specific process with additional links and the possibility of handling attachments. Go to the Customizing activity for the Design Time for HCM Processes and Forms (transaction HRASR_DT). (Personnel Management → HR Administrative Services → Configuration of Forms/Processes → Design Time for Processes and Forms) In the dropdown list of available technical objects, select Form Scenario, then enter the ID of your form scenario ZF##, and choose Display. Customizing for attachment types: Go to the Attachment Types view (Other Attributes → Attachment Types). Select attachment type Z_MOV_EXP: Confirm your entry (by pressing Enter). Save your entry. Customizing for additional information: Go to the Additional Information view (Other Attributes → Additional Information). Select the following types of additional information: REMOVE_INFO_1 and REMOVE_INFO_2 . Confirm your entries (by pressing Enter). Save your entries. Execute your process and check whether: •
Attachments can be added, displayed, and deleted in every step
•
Additional links are available in every step
Search for the process in the process browser (Search Processes) and view the details (step information, form, attachments).
© SAP AG
HR280
5-129
For internal use by CSC only
For internal use by CSC only
1-1
1-2
Test the modified process (for your employee) in the portal. Execute your process and check whether: •
Attachments can be added, displayed, and deleted in every step
•
Additional links are available in every step
Search for the process in the process browser (Search Processes) and view the details (step information, form, attachments). Enhance your process in such a way that the added functions (see above) appear in the stepspecific form. In addition, the Save Draft function should be available in step 3. Go to the Customizing activity for the Design Time for HCM Processes and Forms (transaction HRASR_DT). (Personnel Management → HR Administrative Services → Configuration of Forms/Processes → Design Time for Processes and Forms) In the dropdown list of available technical objects, select Form Scenario, then enter the ID of your form scenario ZF##, and choose Display. Customizing Settings for Form Scenario Steps: Go to the Scenario Steps view (form scenario step FSS_1 already exists). Create two new entries (FSS_2/step 2 and FSS_3/step 3) and confirm them. (Your table should now appear like the table below. For example, default values should appear for the two new scenario steps.) N
Scenario Step
Name
Attach.Types
Addnl Information
Fields
1
FSS_1
START
Create & Change
Available
…
2
FSS_2
STEP 2
Create & Change
Invisible
…
3
FSS_3
STEP 3
Create & Change
Invisible
….
Double-click in the second row (for FSS_2) in the Attach.Types column and select Display Allowed. Your table should now appear as follows: N
Scenario Step
Name
Attach.Types
Addnl Information
Fields
1
FSS_1
START
Create & Change
Available
…
2
FSS_2
STEP 2
Display Allowed
Invisible
…
3
FSS_3
STEP 3
Create & Change
Invisible
….
Save your entries. Adjust your workflow template to achieve behavior specific to each scenario step: Start the Workflow Builder (transaction SWDD). Enter the ID of your workflow in the Workflow field or use the abbreviation (ZF##) to search.
© SAP AG
HR280
5-130
For internal use by CSC only
For internal use by CSC only
1-3
Verify that your workflow is displayed (ID and abbreviation). Switch from the display mode to change mode. On the graphical overview page, double-click on Step 1 in WF (which represents step 2 in the business process). Change the name of the step to Step 1 in WF. On the Control tab page, choose the Binding (Exists) pushbutton.A popup appears showing the binding that exists between the workflow container and step container (see also the slides in the WF Template and Process unit). For internal use by CSC only
Workflow
Step "Process Form"
FSS_2
&FORM_SCENARIO_STAGE&
Confirm your entry. Return to the graphical overview of your workflow template. On the graphical overview page, double-click on Step 2 in WF (which represents step 3 in the business process). Change the name of the step to Step 2 in WF. On the Control tab page, choose the Binding (Exists) pushbutton. Change the binding as follows: Workflow
Step 'Process Form'
FSS_3
&FORM_SCENARIO_STAGE&
X
&SAVE_DRAFT_BUTTON_VISIBLE&
Confirm your entry. Return to the graphical overview of your workflow template. Activate the workflow you have defined using the Activate pushbutton or CTRL+F3. 1-4
Test the modified process (for your employee) in the portal. Verify that the new functions are available in all steps. Add attachments. Use the exercise in the Execute Process unit (for process 4) as a checklist.
© SAP AG
HR280
5-131
For internal use by CSC only
Change the binding for &FORM_SCENARIO_STAGE& as follows:
For internal use by CSC only
For internal use by CSC only
5-132
HR280
© SAP AG
For internal use by CSC only
For internal use by CSC only
Appendix
© SAP AG 2009
© SAP AG
HR280
A-1
Processes in Personnel Development Execute a personnel development process
Start Process with HCM Processes and Forms
The first agent starts the process; however, he selects an object type instead of an employee.
2
3
Edit Data
A second agent edits the data and sends the form.
Edit Data
For internal use by CSC only
For internal use by CSC only
1
A third agent edits the data and saves the form.
You can also start the process and then assign an object later (or leave object unassigned).
© SAP AG 2009
As of EhP4, you can start a process for the object types – job, position, and organizational unit. The process then takes the same format as if you were choosing an employee. You choose the object type, then select a process for the object type, enter and save the data, and forward it to the next agent if necessary. You can also select a process without specifying an object type; this is allowed for certain processes.
© SAP AG
HR280
A-2
Example Processes for Organizational Management
Change business attributes of job
- HR_PD_CHANGE_JOB_ATTRIBUTES
Change name and description of job
- HR_PD_CHANGE_JOB_NAME
Change attributes of organizational unit
- HR_PD_CHANGE_ORG_UNIT_ATTRIBUTES
Change name and description of organizational unit
- HR_PD_CHANGE_ORG_UNIT_NAME
Change name and description of position
- HR_PD_CHANGE_POSITION_NAME
Change business attributes of position
- HR_PD_CHANGE_POS_ATTRIBUTES
Create organizational unit
- HR_PD_CREATE_ORGANIZATION_UNIT
Create position
- HR_PD_CREATE_POSITION
Delete position
- HR_PD_DELETE_POSITION
For internal use by CSC only
For internal use by CSC only
Processes for Organizational Management Objects:
Delimit assignment of position for organizational unit - HR_PD_DELIMIT_POS_ASSIGNMENT Move an unoccupied position
- HR_PD_MOVE_POSITION
© SAP AG 2009
© SAP AG
HR280
A-3
For internal use by CSC only
For internal use by CSC only
Create PD Process: Assign Back-end Service
Use Use the the input input help help
© SAP AG 2009
Call transaction HRASR_DT and select the view Form Scenario. Enter the name of the new scenario and choose Display. In the windowCreate Form Scenario, enter the required specifications.
© SAP AG
HR280
A-4
For internal use by CSC only
For internal use by CSC only
Create PD Process: Leading Object Type
© SAP AG 2009
In the object hierarchy area, navigate to Back-End Services and open the tree. In this example, you want to change the name of an organizational unit. Therefore, specify the Organizational Unit object type as leading (LEAD_OBJECT_ID). Specify a field name in the column Object Abbr. Fieldname and another one in the column Object Text Fieldname. Select the required operation and specify a rule, if necessary. Choose Continue and confirm the message informing you that the fields of instance 001 of the back-end service SAP_PD have been added.
© SAP AG
HR280
A-5
For internal use by CSC only
For internal use by CSC only
Create PD Process: Process Properties
© SAP AG 2009
To create a single-step process for the Organizational Unit object type, make the settings displayed above for the start step of the process. As the workflow template, specify NO_WORKFLOW.
© SAP AG
HR280
A-6
For internal use by CSC only
For internal use by CSC only
Create PD Process: Other Object Types
© SAP AG 2009
In the object hierarchy area, navigate to Back-End Services and open the tree. In this example, you want to link a position to an organizational unit. Therefore, specify the Organizational Unit object type as leading (LEAD_OBJECT_ID). Specify a field name in the column Object Abbr. Fieldname and another one in the column Object Text Fieldname. You can choose the name of your choice for the form field of the dependent object type (in the example POSITION). The operation for object type S is Create; no specification is required for object O since the object is not changed. Choose Continue and confirm the message informing you that the fields of instance 001 of the back-end service SAP_PD have been added. A node with one of the field names that you chose is added to the tree in the object hierarchy area.
© SAP AG
HR280
A-7
For internal use by CSC only
For internal use by CSC only
Create PD Process: Relationships
Create Create relationship relationship between between leading leading object object and and dependent dependent object object
© SAP AG 2009
In this example, you want to link a position to an organizational unit. The dependent Position object type should be linked to the leading Organizational Unit object type. Choose Relations in the object hierarchy area and enter the relationship and the specification of the relationship. Since you want to create the relationship, select the operation Create.
© SAP AG
HR280
A-8
Create PD Process: Form Scenario Fields
For internal use by CSC only
For internal use by CSC only
Leading Leading object object type type O O
Use Use wizard wizard to to create create fields fields for for each each object object type type
Dependent Dependent object object type type S S
© SAP AG 2009
You can use the wizard to define fields that you want to display in the form. The Adobe form and the workflow are created in the same way as the processes of Personnel Administration.
© SAP AG
HR280
A-9
Copy a Standard Process with All Related Objects: Procedure/Overview To copy a standard process with all related objects, proceed as follows:
2. Open Design Time, select a process, and choose Copy with Dependent Objects.
For internal use by CSC only
For internal use by CSC only
1. Note all relevant IDs of the process (source and target; ensure that the target IDs are not in use/do not exist already).
3. Go to the Workflow Builder (SWDD) and copy the workflow template for the source process. 4. Go to the new workflow template and adapt the workflow as required (in particular container elements form, form scenario step in WF, and step container).
© SAP AG 2009
Even though you don‘t need this technically it helps you a lot to control the copying process to get an overview about all involved objects and also to have plan for the IDs your new object shall get.
© SAP AG
HR280
A-10
Copy Process (1): Note All Relevant Process IDs Target (Example)
Process ID:
ZD00
ZG00
Form Scenario ID:
ZD00
ZG00
ISR Scenario ID:
ZD00
ZG00
Form ID:
ZD00
ZG00
Interface ID:
ZD00
Is assigned automatically
WS99700296
Is assigned automatically
WF ID:
For internal use by CSC only
For internal use by CSC only
Source (Example)
© SAP AG 2009
Even though you don‘t need this technically it helps you a lot to control the copying process to get an overview about all involved objects and also to have plan for the IDs your new object shall get.
© SAP AG
HR280
A-11
Copy Process (2): Perform "Copy with Dependent Objects" Choose the following function: Copy with Dependent Objects. This function will copy the following objects: Process (including the relation to the Workflow Template)
2)
Form Scenario
3)
ISR Scenario
4)
Form
5)
Interface
6)
Workflow Template
For internal use by CSC only
For internal use by CSC only
1)
This copying functions thus really copies all dependent object, the only thing you have still to take care of, is the relation to the workflow template. This is the workflow template of the source process. Thus you still have to copy the WF-Template and do the necessary changes in the WF-Template and in the process
© SAP AG 2009
© SAP AG
HR280
A-12
For internal use by CSC only
For internal use by CSC only
Copy Process (3): Enter New IDs and Alter Description
© SAP AG 2009
© SAP AG
HR280
A-13
For internal use by CSC only
For internal use by CSC only
Copy Process (4): Select Both Objects for Activation (Preselection Only)
© SAP AG 2009
© SAP AG
HR280
A-14
For internal use by CSC only
For internal use by CSC only
Copy Process (5): Copy the Workflow Template
© SAP AG 2009
© SAP AG
HR280
A-15
Copy Process (6): Adjust the WF Template (References for Form Scenario (WF and Step Containers)); Activate
2)
For internal use by CSC only
For internal use by CSC only
5)
4)
c
1)
3)
© SAP AG 2009
© SAP AG
HR280
A-16
For internal use by CSC only
For internal use by CSC only
Copy Process (7): Assign New WF Template to Process; Generate Event Type Linkage
© SAP AG 2009
© SAP AG
HR280
A-17
For internal use by CSC only
For internal use by CSC only
Copy Process (8): Check Process Start and Parallel Run
© SAP AG 2009
© SAP AG
HR280
A-18
Activate and Run Sample Process (with All Related Objects): Procedure To activate and run a standard process or sample process (with all related objects), proceed as follows: 2. Activate Web Dynpro services and applications
For internal use by CSC only
For internal use by CSC only
1. Copy client (000) according to piece list 3. Activate event type linkage 4. Check the validity of the process 5. Ensure that HR Administrator IT 0001 has been maintained 6. Troubleshooting
© SAP AG 2009
© SAP AG
HR280
A-19
(1) Copy Client (000) According to Piece List – (1)
For internal use by CSC only
For internal use by CSC only
F4 help
Enter 'HRASR*' and choose the F4 help
© SAP AG 2009
© SAP AG
HR280
A-20
(1) Copy Client (000) According to Piece List – (2)
For internal use by CSC only
For internal use by CSC only
Select the request type
Select piece list
© SAP AG 2009
© SAP AG
HR280
A-21
For internal use by CSC only
For internal use by CSC only
(1) Copy Client (000) According to Piece List – (3)
2
1
3 © SAP AG 2009
© SAP AG
HR280
A-22
(1) Copy Client (000) According to Piece List – (4) 2
1
4
For internal use by CSC only
For internal use by CSC only
1
3
5
© SAP AG 2009
© SAP AG
HR280
A-23
(1) Copy Client (000) According to Piece List – (5)
For internal use by CSC only
For internal use by CSC only
Result of test session
© SAP AG 2009
© SAP AG
HR280
A-24
(2) Activate Web Dynpro Services – Transaction SICF
For internal use by CSC only
For internal use by CSC only
Transaction SICF
© SAP AG 2009
Enter transaction SICF and go to default_host SAP → BC → Web Dynpro → SAP. The following HCM Processes and Forms Applications must be activated: asr_form_display asr_keyword_search asr_lauchpad asr_personnel_file asr_processes_display asr_process_execute asr_process_select asr_profiles_show
© SAP AG
HR280
A-25
(2) Activate Web Dynpro Services
For internal use by CSC only
For internal use by CSC only
Service must be activated
© SAP AG 2009
© SAP AG
HR280
A-26
For internal use by CSC only
For internal use by CSC only
(3) Activate Event Type Linkage for WF
Result Æ
© SAP AG 2009
Choose IMG → Personnel Management → HR Administrative Services → Configuration of Forms /Processes → Design Time for Processes and Forms. You can also use transaction HRASR_DT to open the Design Time of HCM Processes and Forms. Choose Workflow in the structure on the left side. As you can see the workflow of the standard process ‘Membership Fees’ is entered and available, but the Event Type Linkage is not active (incomplete). Activate the Event Type Linkage by choosing the generate button next to the field ‘Event Type Linkage’.
© SAP AG
HR280
A-27
For internal use by CSC only
For internal use by CSC only
(4) Check the Validity of the Start Process
© SAP AG 2009
Go to IMG Æ Personnel Management Æ HR Administrative Services Æ Configuration of Forms /Processes ÆProcess Configuration Æ Set Up Processes --< Validity for Process Start Æ Specify Valid Processes for Start Application. Ensure that the example process you want to use is entered and marked as valid in this table for each role: Choose a role (employee, manager, HR admin etc.) from the list. You need to activate the process start only for those roles who should be able to start a process. If the role is only involved in the process (2nd, 3rd, … process step) and not starting the process, you do not need to activate the process for this role. In our example the process should be activated for the HR administrator.
© SAP AG
HR280
A-28
For internal use by CSC only
For internal use by CSC only
(4) Check the Validity of the Sample Start Process
Mark the process as valid
© SAP AG 2009
The process ‘Membership Fees’ is entered in the table but not marked as active (last column). Mark the process as active. Also check the validity period (start and end date) of this process. If the end date is in the past go to the Design Time and change the End date of the process.
© SAP AG
HR280
A-29
For internal use by CSC only
For internal use by CSC only
(5) Check Infotype 0001 – HR Administrator Entry
© SAP AG 2009
Most of the example processes use rules for HR Admin (rule 17900016), HR Time Admin (rule 17900017), HR Payroll Admin (rule17900018). The rule resolution uses the administrators entered in IT0001 Organizational Assignment of the employee for which the process is to be executed. The administrators can be maintained in table T526. Ensure that a user is also maintained. Description of rule 17900016 If an 'Organizational Assignment' infotype exists and a personnel administrator is defined there for the persons/users affected by the process or the person/users transferred using the container elements RULE_BASIS_OTYPE/RULE_BASIS_OBJID, then the user assigned to this identifier (see table T526) is the agent.
© SAP AG
HR280
A-30
(6) Troubleshooting – (1) The ADS must be installed and connected to the ECC system. If the form in the portal does not work check SAP Note 944221 for ‘ADS Trouble Shooting’. Check the Adobe Reader version which is installed on your client For internal use by CSC only
For internal use by CSC only
Copy Case Types and Profiles for Case Search from delivery client 000
When you start a process, the process object is created, but the workflow is not started you may need to check the workflow RFC customizing
© SAP AG 2009
For Case Types Go to IMG Æ Personnel Management Æ HR Administrative Services Æ Configuration of Forms /Processes ÆProcess Configuration Æ Technical Settings Æ Set Up Process Object SAP delivers the following default case types that are assigned to the Records Management System ID ASR_POBJ: Process (H_PO) Scenario (H_FO) Step (H_SO) SAP delivers the following profiles for the so-called case search for the default case types H_PO, H_FO, and H_SO. Process Search (ASR_POBJ) Scenario Search (ASR_FOBJ) Step Search (ASR_SOBJ) Copy the delivered case types (IMG activity Copy Case Types) from the delivery clients. It is important that you transfer the case types unchanged. Read IMG documentation!!!
© SAP AG
HR280
A-31
For internal use by CSC only
For internal use by CSC only
(6) Troubleshooting – (2) Locked Workflow Batch User
Transaction SWU3 Æ RFC destination information
© SAP AG 2009
When you start a process, the process object is created, but the workflow is not started; you may need to check workflow RFC Customizing. Go to transaction SWU3. If the ‘Configure RFC Destination’ has a red light, then the user ‘WF-Batch’ is locked Æ unlock the user.
© SAP AG
HR280
A-32
(6) Useful Transactions
SWI1
Æ Work item selection (has the work item been generated?)
SWI2_ADM1
Æ Work Items Without Agents
SWI2_DIAG
Æ Diagnosis of Work Items Containing Errors
SWPR
Æ Workflow Restart After Error
PFTC
Æ Copy workflow template
For internal use by CSC only
For internal use by CSC only
Workflow
Case Management SCASE
Æ Find cases of HCM Processes and Forms Æ Choose RMS ID = ASR_POBJ
© SAP AG 2009
© SAP AG
HR280
A-33
For internal use by CSC only
For internal use by CSC only
Miscellaneous
Miscellaneous
© SAP AG 2008 2009
© SAP AG
HR280
A-34
For internal use by CSC only
For internal use by CSC only
Implementation: Define Role for Start Applications (1)
Indicates that the process is visible for and can be executed by the HR Administrator initiator role in the portal
© SAP AG 2009
In this Customizing step, you define the processes that are valid for start applications, that is to say, which processes can be started by a particular (portal) role within the portal. In addition, you can specify the validity period for a process by entering a start date (valid from) and end date (valid to). Once you have defined the process as "valid" (by selecting the checkbox), the selected role can see and execute the process in the portal.
© SAP AG
HR280
A-35
For internal use by CSC only
For internal use by CSC only
Implementation: Define Role for Start Applications (2)
© SAP AG 2009
You also have to define the role assignment in the Design Time for the process. To do so, go to the Customizing option Role Assignment
© SAP AG
HR280
A-36
View more...
Comments
