HCM_PF_Std_Documentation_EHP4 by venkatvanga

VIEWS: 1,417 PAGES: 376

									HR Administrative Services
        (PA-AS)




                       HELP.PAAS




        Release 6956
SAP Online Help                                                                        22.04.2009



Copyright
© Copyright 2009 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in any form or for any purpose
without the express permission of SAP AG. The information contained herein may be
changed without prior notice.
Some 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, System i, System i5, System p, System p5, System x,
System z, System z10, System z9, z10, z9, iSeries, pSeries, xSeries, zSeries, eServer, z/VM,
z/OS, i5/OS, S/390, OS/390, OS/400, AS/400, S/390 Parallel Enterprise Server, PowerVM,
Power Architecture, POWER6+, POWER6, POWER5+, POWER5, POWER, OpenPower,
PowerPC, BatchPipes, BladeCenter, System Storage, GPFS, HACMP, RETAIN, DB2
Connect, RACF, Redbooks, OS/2, Parallel Sysplex, MVS/ESA, AIX, Intelligent Miner,
WebSphere, Netfinity, Tivoli and Informix are trademarks or registered trademarks of IBM
Corporation.

Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.

Adobe, the Adobe logo, Acrobat, PostScript, and Reader are either trademarks or registered
trademarks of Adobe Systems Incorporated in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of the 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.

JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for
technology invented and implemented by Netscape.

SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP Business ByDesign, 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 other countries.

Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal
Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services
mentioned herein as well as their respective logos are trademarks or registered trademarks of
Business Objects S.A. in the United States and in other countries. Business Objects is an
SAP company.

All other product and service names mentioned are the trademarks of their respective
companies. Data contained in this document serves informational purposes only. National
product specifications may vary.

These materials are subject to change without notice. These materials are provided by SAP
AG and its affiliated companies ("SAP Group") for informational purposes only, without
representation or warranty of any kind, and SAP Group shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP Group products and


HR Administrative Services (PA-AS)           6956                                              2
SAP Online Help                                                                  22.04.2009


services are those that are set forth in the express warranty statements accompanying such
products and services, if any. Nothing herein should be construed as constituting an
additional warranty.




HR Administrative Services (PA-AS)         6956                                              3
SAP Online Help                                                                   22.04.2009



Icons in Body Text

   Icon                      Meaning
                             Caution
                             Example
                             Note
                             Recommendation
                             Syntax


Additional icons are used in SAP Library documentation to help you identify different types of
information at a glance. For more information, see Help on Help   General Information
Classes and Information Classes for Business Information Warehouse on the first page of any
version of SAP Library.



Typographic Conventions

  Type Style                Description
  Example text              Words or characters quoted from the screen. These include field
                            names, screen titles, pushbuttons labels, menu names, menu paths,
                            and menu options.
                            Cross-references to other documentation.
  Example text              Emphasized words or phrases in body text, graphic titles, and table
                            titles.
  EXAMPLE TEXT              Technical names of system objects. These include report names,
                            program names, transaction codes, table names, and key concepts of a
                            programming language when they are surrounded by body text, for
                            example, SELECT and INCLUDE.
  Example text              Output on the screen. This includes file and directory names and their
                            paths, messages, names of variables and parameters, source text, and
                            names of installation, upgrade and database tools.
  Example text              Exact user entry. These are words or characters that you enter in the
                            system exactly as they appear in the documentation.
  <Example text>            Variable user entry. Angle brackets indicate that you replace these
                            words and characters with appropriate entries to make entries in the
                            system.
  EXAMPLE TEXT              Keys on the keyboard, for example, F2 or ENTER.




HR Administrative Services (PA-AS)          6956                                            4
SAP Online Help                                                                                                       22.04.2009




HR Administrative Services (PA-AS).................................................................................... 10
  HCM Processes and Forms ............................................................................................. 14
     HCM Processes and Forms (Technical Overview) ........................................................ 19
        Process Flow with One Form Scenario...................................................................... 26
        Process Flow with Two Form Scenarios.................................................................... 29
        Overview: Data Processing in HCM Processes and Forms........................................ 30
     Process........................................................................................................................ 32
     Process Object............................................................................................................. 35
     ISR Scenario................................................................................................................ 36
     Form Scenario.............................................................................................................. 37
     Start Application ........................................................................................................... 38
     Form Application .......................................................................................................... 42
     Universal Worklist (UWL).............................................................................................. 45
     Process Browser .......................................................................................................... 45
     E-Mail Notification ........................................................................................................ 47
     Business Status ........................................................................................................... 47
        Creating and Assigning Business Statuses ............................................................... 48
     Creating and Editing Interactive Forms ......................................................................... 50
        Creating Form Fields with Data Binding .................................................................... 52
        Using Form Fields to Enter Agent Notes.................................................................... 53
        Creating a Dropdown List Box................................................................................... 54
        Creating Pushbuttons ............................................................................................... 55
     Message Mapping ........................................................................................................ 56
     Message Mapping Based on Form Scenarios............................................................... 58
     Business Workflow for HCM Processes and Forms ...................................................... 60
        Technical Basics for Business Workflow for HCM Processes & Forms ...................... 61
           Special Features of the Workflow Templates ......................................................... 63
           Special Features of the Standard Tasks ................................................................ 66
           Agent Determination Rules.................................................................................... 68
           Workflow Templates for Sample Processes ........................................................... 71
        Standard Tasks......................................................................................................... 73
           Task Group TG17900001: Components for HCM Processes & Forms ................... 73
           Task Group TG17900002: Interactive Components ............................................... 73
              Standard Task TS17900100: Edit Form.............................................................. 73
              Standard Task TS17900101: Approve Form....................................................... 81
              Standard Task TS17900102: Form Is Edited Again by Author ............................ 84
              Standard Task TS04000018: Process PD Form ................................................. 86
              Standard Task TS04000019: Approve PD Form................................................. 94
              Standard Task TS04000020: PD Form Is Edited Again by Author....................... 97


HR Administrative Services (PA-AS)                             6956                                                                  5
SAP Online Help                                                                                                    22.04.2009


             Workflow Template WS17900260: Save Form with Error Handling..................... 99
             Workflow Template WS17900404: Draft for Process Start ................................ 104
             Workflow Template WS17900418: Forward: Process Start with Errors ............. 105
          Task Group TG17900003: Background Components........................................... 107
             Standard Task TS17900106: Check Existence of PA Infotype .......................... 108
             Standard Task TS17900107: Check Form Data ............................................... 109
             Standard Task TS17900108: Save Form Data ................................................. 110
             Standard Task TS17900110: Import Field Value to WF Cont. Element ............. 111
       Restrictions When Modeling Workflows................................................................... 113
    Authorization Concept of HCM Processes and Forms................................................. 118
       Contexts for Checking Authorizations...................................................................... 120
       Methods for Checking Authorizations ...................................................................... 121
    Error Handling ............................................................................................................ 124
    Design Time for Processes and Forms ....................................................................... 127
       Changing the Initial Screen for Design Time............................................................ 129
       Creation and Configuration of Processes ................................................................ 129
          Validity-Period-Independent Settings for a Process.............................................. 131
             Settings for Withdrawing a Process .................................................................. 132
             Transfer of Field Values Between Form Scenarios of a Process ....................... 132
             Transfer of Attachments Between Form Scenarios of a Process....................... 134
          Validity-Period-Dependent Settings for a Process................................................ 134
             Assignment of a Workflow Template to the Process ......................................... 135
             Assignment of Roles to a Process.................................................................... 137
             Grouping Processes in Groups ........................................................................ 138
             Restrictions for Starting a Process ................................................................... 139
                Collision Checks for a Process ..................................................................... 141
                Frequency Restrictions for a Process............................................................ 142
             Assignment of Form Scenarios to a Process .................................................... 143
       Creation and Configuration of Form Scenarios ........................................................ 144
          Definition of Form Scenarios................................................................................ 145
          Definition of Form Fields...................................................................................... 146
          Editing the Form Layout....................................................................................... 147
          Definition of Scenario Steps................................................................................. 150
          Configuration of Back-End Services..................................................................... 151
             Settings for Back-End Service SAP_PA ........................................................... 153
             Settings for Back-End Service SAP_PT............................................................ 157
             Settings for Back-End Service SAP_PD ........................................................... 160
             Settings for Generic Services ........................................................................... 166
          Definition of Attachment Types ............................................................................ 167
          Creation of Links for Additional Information.......................................................... 168


HR Administrative Services (PA-AS)                          6956                                                                 6
SAP Online Help                                                                                                    22.04.2009


         Definition of Rules ............................................................................................... 168
         Definition of User Events ..................................................................................... 169
         Settings for Message Mapping ............................................................................ 170
      Mass Processes and Fast Data Entry...................................................................... 171
         Configuring a Process for Fast Data Entry ........................................................... 173
         Starting a Fast Data Entry Process...................................................................... 174
         Configuring a Process as a Mass Process ........................................................... 176
         Starting a Mass Process...................................................................................... 178
      Organizational Management Processes .................................................................. 180
         Creation and Configuration of Organizational Processes ..................................... 181
         Creating an OM Process (Exercise 1).................................................................. 184
         Creating an OM Process (Exercise 2).................................................................. 191
         Creating an OM Process (Exercise 3).................................................................. 200
      Process Start without Employee Selection .............................................................. 207
         Configuring and Starting Processes without Employee Selection ......................... 209
      Checks and Utilities for Processes and Forms......................................................... 211
         Check the Configuration of a Process.................................................................. 211
         Test a Process .................................................................................................... 212
         Check Objects for Inconsistencies ....................................................................... 213
         Compare and Reconcile Objects ......................................................................... 213
         Export and Import of Objects As XML File............................................................ 215
    Sample Processes in HCM Processes and Forms ...................................................... 216
      Hiring, Permanent (Germany) ................................................................................. 217
      Hiring (US).............................................................................................................. 220
      Rehire (Germany) ................................................................................................... 224
      Rehire (US)............................................................................................................. 228
      Transfer (International)............................................................................................ 232
      Transfer including Previous Position Update (International) ..................................... 234
      Transfer, Initiated by E-Recruiting (International)..................................................... 236
      Maternity Leave (Germany)..................................................................................... 239
      Birth of a Child (Germany)....................................................................................... 241
      Birth of Child (US)................................................................................................... 243
      Salary Change Using Annual Salary (International) ................................................. 245
      Salary Change Using Pay Scale Wage Group and Level (International) .................. 247
      Special Payment (International) .............................................................................. 250
      Special Payment Without Personnel Department (International) .............................. 253
      Change to Working Time (International) .................................................................. 256
      Change of Address (US) ......................................................................................... 259
      Company Loan (International) ................................................................................. 261
      Membership Fees Sports Club (International).......................................................... 263


HR Administrative Services (PA-AS)                          6956                                                                 7
SAP Online Help                                                                                                     22.04.2009


       Termination (Germany)........................................................................................... 265
       Termination (US) .................................................................................................... 268
       Special Payment for Mass Start (Multi-Step Process).............................................. 272
       Address Change (Single-Step Process) .................................................................. 274
       Create Position ....................................................................................................... 276
       Change Position Name ........................................................................................... 278
       Change Position Attributes...................................................................................... 279
       Move Position ......................................................................................................... 282
       Delete Position........................................................................................................ 284
       Delimit Position Assignment.................................................................................... 285
       Create Organizational Unit ...................................................................................... 287
       Change Organizational Unit Name .......................................................................... 290
       Change Organizational Unit Attributes..................................................................... 291
       Change Job Name.................................................................................................. 294
       Change Job Attributes............................................................................................. 295
       Special Payment (Process Start Without Employee Selection) ................................ 298
       Country-Specific Processes .................................................................................... 300
    Integration of EIC and HCM Processes and Forms ..................................................... 300
    Integration of E-Recruiting and HCM Processes and Forms........................................ 301
       XI Content for HCM Processes and Forms.............................................................. 302
          NewHire .............................................................................................................. 304
             New Hire Request from E-Recruiting (NEWHIREREQUEST) ........................... 306
             Rehire Request from E-Recruiting (REHIREREQUEST)................................... 306
             Transfer Request from E-Recruiting (TRANSFERREQUEST) .......................... 307
    Tutorial: Create a Process .......................................................................................... 307
       Sample Process for the Tutorial .............................................................................. 310
       Unit 1: Create Form, Workflow, and Process ........................................................... 313
          1.1 Configuring a Form Scenario and an ISR Scenario ........................................ 313
             1.1.1 Creating a Form and Editing the Layout................................................... 318
          1.2 Creating a Workflow Template with the Process Form Workflow Step ............ 322
             1.2.1 Retrieving Task Groups for HCM Processes and Forms .......................... 323
             1.2.2 Creating a Workflow Template................................................................. 323
             1.2.3 Creating a Container Element for the Process Object .............................. 324
             1.2.4 Defining a Triggering Event for the Workflow ........................................... 325
             1.2.5 Defining the Programming Exit at the Workflow Template Level............... 325
             1.2.6 Activating the Start Event and Setting Up Type Linkage for the Process .. 326
             1.2.7 Adding Process Form W/F Step (HR Admin) to W/F Template................. 328
             1.2.8: Defining Process Form W/F Step (HR Administrator).............................. 328
             1.2.9 Determining the Form Scenario in the Workflow Container ...................... 331
          1.3 Creating a Process ........................................................................................ 332


HR Administrative Services (PA-AS)                           6956                                                                 8
SAP Online Help                                                                                                          22.04.2009


           1.4 Checking Process Consistency...................................................................... 333
           1.5 Testing a Process (Back End)........................................................................ 334
           1.6 Testing a Process (Portal) ............................................................................. 334
        Unit 2: Enhance Existing Objects ............................................................................ 336
           2.1 Changing a Form Scenario ............................................................................ 336
              2.1.3 Checking Consistency of the Changed Form Scenario ............................ 338
           2.2 Changing a Form........................................................................................... 338
           2.3 Adding the Process Form W/F Step (Superior) in W/F Template .................... 340
           2.4 Making Further Changes to the Form Scenario .............................................. 342
              2.4.1 Using Attachment Types in the Form Scenario ........................................ 342
              2.4.2 Inserting Links for Additional Information ................................................. 343
        Unit 3: Inserting an Approval Loop .......................................................................... 344
           3.1 Adding Approve Form W/F Step in Workflow Template .................................. 346
           3.2 Defining Approve Form W/F Step .................................................................. 346
           3.3 Adding a Branch (Multiple Condition) in the Workflow Template..................... 348
           3.4 Adding Form Is Edited Again by Author Workflow Step in the Workflow Template
           ........................................................................................................................... 351
           3.5 Defining Form Is Edited Again by Author Workflow Step ................................ 351
           3.6 Inserting Loop for Running Approval Process Again....................................... 354
           3.7 Adjusting Workflow Process Flow After Inserting Approval Loop .................... 357
        Unit 4: Making Additional Enhancements ................................................................ 359
           4.1 Enabling Employees to Start the Process ...................................................... 359
           4.2 Determining Agents Using Rules ................................................................... 360
           4.3 Sending a Confirmation E-Mail....................................................................... 362
        Appendix: Tips & Tricks for Processing Workflow Templates................................... 365
           Checking the First Version of the Workflow Template .......................................... 365
           Deleting Unused Workflow Container Elements ................................................... 365
           Copying Workflow Templates .............................................................................. 367
           Determining Events That Are Triggered By a Workflow Template ........................ 368
           Checking of Workflow Template Instances........................................................... 369
  HR Administrator ........................................................................................................... 370
     Portal Role: HR Administrator..................................................................................... 370
     Editing of Employee Data ........................................................................................... 371
  Digital Personnel File (DPF)........................................................................................... 375




HR Administrative Services (PA-AS)                              6956                                                                    9
SAP Online Help                                                                     22.04.2009




      HR Administrative Services (PA-AS)
Purpose
You can use this component to execute HR activities such as an employee's hiring or leaving
completely within the SAP NetWeaver Portal. From selecting an activity to storing the
associated document, the system supports you in performing these process flows.
The component uses the HR Administrator portal role to support the central processing of
personnel data. It also encourages decentralized execution of HR activities by including
managers and employees (where necessary) directly in the process flow and thus reducing
the workload for the HR department.
The following aspects can increase the effectiveness and optimize the costs of your process
flows:

      Exclusive use of the portal to execute the activities enables all persons involved to
      have easy access to the required data. As the portal is the only medium that permits
      the input of data, multiple entry of data is avoided, thus reducing the error percentage.

      The automatic inclusion of all required persons and roles – from the request to the
      approval – simplifies the communication paths.

      The option of monitoring and including process flows that are currently running down to
      the individual processing steps reduces the processing time.
HR Administrative Services depicts HR activities using processes. The focus is on those
processes that pertain to an event in the personal life of an employee or in the work place and
require the involvement of several people, such as hiring, transfer, or maternity leave.
You enter the data required for a process in interactive forms that are customized for each
process step and for each agent. The system then forwards these forms automatically to the
relevant agents, for example, for review or for approval. When a process has been
completed, the system can store the corresponding documents in the personnel file of the
relevant employee. In each process step, you enter only the data that is required for this
particular step, enabling you to make contact with the relevant decision maker or store of
information in each case.

Integration
If you want to use this component, the following components are obligatory:

Obligatory mySAP ERP Components

Component                        Function Provided                  Remarks
Personnel Administration         Storage of HR master data          You can also use Personnel
                                 that you process using HR          Administration functions (such
                                 Administrative Services            as Maintain HR Master Data
                                 processes and forms                (PA30) or Personnel Actions
                                                                    (PA40)) directly in the back-
                                                                    end system as an alternative
                                                                    to the HR Administrative
                                                                    Services.
Time Management                  Storage of time management         This component is obligatory if
                                 data that you process using        you want to process Time
                                 HR Administrative Services         Management using HR
                                 processes and forms                Administrative Services.
Internal Service Request (ISR)   Communication between              This component ensures, for
                                 interactive forms and the back-    example, that a value help is



HR Administrative Services (PA-AS)           6956                                            10
SAP Online Help                                                                   22.04.2009


                                end system                       also offered for form fields as
                                                                 well as for fields in the back-
                                                                 end system.

Obligatory SAP NetWeaver Components

Component                       Function Provided                Remarks
SAP NetWeaver Portal            User interfaces for the portal   The HR Administrator portal
                                roles involved in HR             role (in other words, the
                                Administrative Services          Business Package for HR
                                                                 Administrator) is obligatory .
                                                                 In addition, further roles
                                                                 (Manager and Employee in the
                                                                 standard delivery) can be
                                                                 involved in the processing of
                                                                 processes. You can also
                                                                 integrate customer-specific
                                                                 portal roles.
SAP Interactive Forms by        Interactive forms                Interactive forms represent the
Adobe                                                            electronic equivalent of paper
                                                                 forms. The processor uses
                                                                 them for data entry and
                                                                 processing.
SAP Business Workflow           Implementation of the process    You use this component to
                                flow                             define the flow of processes,
                                                                 for example, the number and
                                                                 sequence of process steps or
                                                                 approval loops. This
                                                                 component also ensures agent
                                                                 determination for the relevant
                                                                 process step at process
                                                                 runtime.
Case Management                 Storage of the process object    See Process Object [Page 35]
The following components are optional:

Optional mySAP ERP Components

Component                       Function Provided                Remarks
Organizational Management       Agent determination using        You can use this component
                                rules that are based on the      to ensure, for example, that a
                                organizational structure of      process step goes to an
                                your company                     employee's direct manager for
                                                                 approval.
                                                                 Alternatively, you can
                                                                 implement agent
                                                                 determination using rules from
                                                                 the Responsibility category, by
                                                                 defining a specific list of users
                                                                 as processors.
Manager Self-Service            Involvement of managers in       You must implement the
                                HR Administrative Services       Business Package for
                                processes                        Manager Self-Service for this
                                                                 purpose.
Employee Self-Service           Involvement of employees in      You must implement the
                                HR Administrative Services       Business Package for


HR Administrative Services (PA-AS)         6956                                            11
SAP Online Help                                                                     22.04.2009


                                processes                          Employee Self-Service for this
                                                                   purpose.
Employee Interaction Center     Initiation of processes by EIC
                                agents
SAP E-Recruiting                Hiring, rehiring, or transfer of   Alternatively, you can also
                                employees through E-               hire, rehire, or transfer
                                Recruiting initiatives,            employees without using SAP
                                                                   E-Recruiting.

Optional SAP NetWeaver Components

Component                       Function Provided                  Remarks
SAP Records Management          Storage of the digital             You require this component if
                                personnel file                     you want to store forms in the
                                                                   digital personnel file and if the
                                                                   digital personnel file must be
                                                                   available in the portal for
                                                                   display or processing
                                                                   purposes.
SAP NetWeaver Exchange          Integration between SAP E-         You use the XI content of HR
Infrastructure                  Recruiting and HR                  Administrative Services
                                Administrative Services            (integration scenario NewHire)
                                                                   for this purpose.
SAP NetWeaver Business          Detailed reports, for example,     You must implement the
Intelligence                    about the frequency of             business intelligence content
                                process execution, processing      of the Shared Services
                                and execution times, or            InfoArea for this purpose.
                                process error rates
The following graphic gives an overview of these components:




HR Administrative Services (PA-AS)          6956                                              12
SAP Online Help                                                                                       22.04.2009


      NetWeaver                                           ERP                                   Portal Content
 SAP Interactive Forms                 HR Administrative Services                  Business Package for HR Administrator
       by Adobe
                                          HCM Processes and Forms                   Worklist
      SAP Business                        Processes
        Workflow                                                                    Start Processes
                                             Start Application
                                             Form Application                       Start Hiring Process
  SAP NetWeaver Portal
                                                                                    Display Processes
    SAP Records                        Digital Personnel File
                      Case                                                          Edit Employee Data
    Management        Mgmt.            HR Administrator                      ISR
    SAP NetWeaver                                                                   Process Personnel File
                                             Personnel             Time
  Business Intelligence                    Administration       Management          …
    SAP NetWeaver                                      Organizational
 Exchange Infrastructure                                Management
                                                                                   Business Package for Manager Self-Service

                                                                                    Universal Worklist
     XI Content                             Employee Interaction Center
                                                                                    Start Processes
        NewHire
                                                      E-Recruiting                  …
      BI Content
                                                                                   Business Package for Employee Self-Service
    Shared Services
                                                                                    Life & Work Events
                                                                                     Birth of a Child (= Start Process)

                                                                                     …
      obligatory          nn   Application component
      optional
                          nn   Integration scenario

                          nn   InfoArea

                          nn   iView




For more information about the integration of the components, see HCM Processes and
Forms (Technical Overview) [Page 19].

Features
The component is made up of the following subcomponents:

       HCM Processes and Forms
       This subcomponent contains the HCM Processes and Forms framework with which you
       can set up and execute your processes and the corresponding forms.

       HR Administrator
       This subcomponent contains the HR Administrator portal role that provides all tasks
       and functions for the HR department in the portal. The HR Administrator role is
       delivered with the Business Package for HR Administrator. The role is integrated
       optimally in the HCM Processes and Forms framework: The system automatically
       forwards the processing steps of a process that are to be performed by an HR
       administrator to the portal role.
       You can also edit employee data in this role. This function is based on the HR master
       data maintenance. The HR administrator can call the master data maintenance directly
       using the Employee Data Maintenance in the portal or through the backend system
       (transaction PA30). The HR administrator can also change master data without using
       the HCM Processes and Forms framework.

       Digital Personnel File (DPF)
       This subcomponent contains the personnel file in which all data entered for an
       employee is grouped together. The DPF is optimized for use with the HCM Processes
       and Forms framework: The system can automatically store forms and attachments of a




HR Administrative Services (PA-AS)                           6956                                                 13
SAP Online Help                                                                      22.04.2009


      process in the DPF of the relevant employee immediately after the process has been
      completed.
In addition, you can run reports for this component using the Shared Services [External]
business intelligence content.




      HCM Processes and Forms
Purpose
You can use this component to execute HR processes in which changes are to be made to
HR master data. You can use interactive forms to integrate all involved roles directly in the
process.
Using the component has the following advantages:

       Media bridges (such as paper/PC, fax/PC) and the ensuing multiple entry of data are
       avoided.

       Reduction of the incorrect entries by using the system to integrate all involved roles

       Reduction of the processing time for HR processes

Implementation Considerations
Business Prerequisites
Before you can set up the component, yuo must know the business flow of HR processes in
your enterprise. We recommend you create process descriptions that contain the following
information in particular:

       Overview of all users involved in the process and their roles

       Overview of HR master data relevant for the process

       Description of the process flow comprising the sequence of process steps, the role
       assigned to the process step, and the master data relevant for the process step.

Technical Prerequisites
To be able to use the processes, the Additional Actions infotype (0302) must be actively used
in your ERP system.



             To activate the Additional Actions infotype and to create the corresponding
             infotype records for your employees, see Customizing for Personnel
             Administration and choose the Activation ‘Additional Actions’ step in
             Customizing Procedures      Actions      Set Up Personnel Action Types.
For more information about the technical settings of the component, see HCM Processes and
Forms (Technical Overview) [Page 19].

Features
Cross-Role Implementation of Processes
You use SAP Business Workflow to define process flows. You can use all the functions of
SAP Business Workflow (including branching and approval steps within a process). The
Workflow Template [Page 71] is used to display and execute processes and enables you to
integrate all the roles required for a process.



HR Administrative Services (PA-AS)            6956                                              14
SAP Online Help                                                                     22.04.2009


Interactive Forms
You use interactive forms to enable data entry through forms and to provide the user with the
precise fields and information he or she requires to execute the particular process. The forms
are integrated with the backend system and therefore HR master data is updated
automatically.
If you use several forms within one process, the data can be transferred between the various
forms.
In Customizing, you can define customer- and industry-specific forms that are tailored to suit
the requirements of the particular process.



             In the Marriage of Employee process, you can edit in a form not only the data
             from the Personal Data infotype (0002), but also the address data from the
             Addresses infotype (0006), for example. The same principle applies to more
             complex processes that were previously performed using personnel actions
             (transaction PA40).



             The SAP system includes a variety of sample processes that you can use as a
             template when you configure your own processes. For more information, see
             Sample Processes in HCM Processes and Forms [Page 216].

Functions
The component provides you with the following functions for implementing and executing
processes:

      Saving the form entries as a draft

      Entering notes

      Managing attachments

      Transferring process documents (forms and attachments to a process) automatically to
      an employee's Digital Personnel File (DPF).

      Setting up error tolerance for entries made in the form
      In this way, you can also permit the user to save incorrect entries without these entries
      being saved directly in the backend system. In this case, the data has to be corrected
      by a subsequent user.

      Overview of processes and search for processes for users in the HR Administrator role

      Tracing all those involved in the process (person who created the request, approver,
      and so on)

Example: Features for a Transfer Process
The following uses a possible transfer process as an example to describe the business
functions provided by HCM Processes and Forms.
Features of the Transfer process (from a business point of view)




HR Administrative Services (PA-AS)           6956                                            15
SAP Online Help                                                                   22.04.2009



                                                 Process

                  Step 1                             Step 2                            Step 3
      Select         Edit and send        Select       Edit and send        Select       Edit and send
      process             form           work item          form           work item          form




    Process              Transfer        Universal        Transfer         Universal         Transfer
    selection:                            Worklist                          Worklist
    - Transfer       Emplo yee:                        Emplo yee:                        Emplo yee:
                     Date:                             Date:                             Date:
    - Maternity
    protection                                         Position:                         Position:
    - Parental
     leave …


                      Rev iew     Send                  Rev iew     Send                  Rev iew     Send




              Sending Manager                   Receiving Manager                HR Administrator




In this example, the Transfer process has the following properties:

      The process comprises three business steps that are performed by a sending
      manager, a receiving manager, and a HR administrator.

      The data from the form is not saved to the database of the backend system until step
      3. No data is saved in steps 1 or 2.

Description of Process Steps
Step 1

      User
      The sending manager opens the Start Processes application. The system shows the
      manager a list of the processes he or she can start based on his or her authorizations.
      The manager starts the Transfer process and the system displays the relevant form for
      processing.
      The manager enters the required data in the form. He or she uses the Review function
      to check the entries.



              You can set up the behavior of the Review function in Customizing. For
              example, you can allow the manager to save incorrect data temporarily. You can
              define the error tolerance for each step.
      After the check has been executed, the manager chooses the Send function to send
      the form.

      System
      Based on the user who started the process or the affected employee, the system
      determines which manager is responsible for performing the second process step.



HR Administrative Services (PA-AS)           6956                                           16
SAP Online Help                                                                        22.04.2009


       Result
      The user's entries are saved as a draft. The system sends a work item with the form to
      the Universal Worklist [Page 45] (UWL) of the receiving manager. This manager can
      perform the second process step.
Step 2

       User
      The receiving manager navigates to his or her UWL and selects the relevant work item.
      The system displays the form, together with the data from step 1, for processing. The
      manager makes his or her entries, checks them, and then submits the form.

       System
      Based on the user who started the process or the affected employee, the system
      determines which user is responsible for performing the third process step.

       Result
      The entries made by the receiving manager and the sending manager are saved as a
      draft. The system sends a work item with the form to the UWL of the HR administrator
      responsible. The HR administrator can perform the third process step.
Step 3

       User
      The HR administrator responsible navigates to his or her UWL and selects the relevant
      work item. The system displays the form, together with the data from steps 1 and 2, for
      processing. The HR administrator makes his or her entries, checks them, and then
      chooses Send.

       System
      In contrast to the previous two steps, the Send function triggers two activities:

                The system ends the processing of the form.

                The system saves the data from the form to the database of the backend
                system.

       Result
      The employee’s HR master data is updated according to the data entered in the form.
      The process is complete.
The above graphic displays a simplified version of the process steps on the user interface.
This simplified version is valid in particular for the processing of forms as used by the user in
HCM Processes and Forms. This application provides the user with different views in which
he or she can process the form.
Using step 2 in the Transfer process (see above) as an example, the following graphic shows
the views provided for the user by the form application.
Form Application Views




HR Administrative Services (PA-AS)            6956                                              17
SAP Online Help                                                                    22.04.2009



                                               Process

               Step ...                           Step 2                            Step ...
                                      Sele ct        Edit and send
                                     work item            form




    View : Edit                      View : Review and Send               View : Completed


        Users Involved                    Users Involved
        Attachments                       Attachments
                                                                              Data was sent
             Transfer                          Transfer
         Emplo yee: ...                    Emplo yee: ...
         Date: 08/01/05                    Date: 08/01/05
         Position:                         Position:




          Save Draft      Rev iew                           Send




For more information about these views, see Form Application [Page 42].




HR Administrative Services (PA-AS)         6956                                               18
SAP Online Help                                                                      22.04.2009



      HCM Processes and Forms (Technical Overview)
Use
Architecture

                                            Process


                                       ISR Scenario(s)


                                      Form Scenario(s )

                                   Workflow Template (WS)

                                       Process Object


                                       Start Application


                                      Form Application


                                 Digital Personnel File (DPF)




The component is made up of the following architectural elements:

      Process
      The process groups together the following elements: ISR scenario, form scenario, and
      workflow template. A process can include one or more form scenarios.
For more information, see Process [Page 32].

      ISR Scenario
      The ISR scenario is used to select the form and to define the form layout. It is part of
      the cross-application Internal Service Request [External] function.
For more information, see ISR Scenario [Page 36].

      Form scenario
      The form scenario answers the following questions regarding the following properties:

             Which fields are used in a form?

             How are these fields linked with the infotype fields in the back-end system?

             Which scenario steps exist?

             Which types of attachments can be uploaded?

             Which services are used?
             The services determine the logic used to process form fields in the back-end
             system. The following types of service are available:




HR Administrative Services (PA-AS)           6956                                                19
SAP Online Help                                                                      22.04.2009


                    PA Service (enables Personnel Administration infotypes to be created,
                    changed, and deleted)

                    PT Service (enables Time Management infotypes to be created,
                    changed, and deleted)

                    PD Service (enables Personnel Development infotypes to be created,
                    changed, and deleted)

                    Generic Services Framework
                    The standard system includes the generic service S_MGR_POSITIONS
                    (Positions in Manager’s Area of Responsibility), for example. You can
                    use this service to ensure that a manager is offered only those jobs for
                    selection in the Positions form field that belong to his or her area of
                    responsibility.
      Each form scenario has exactly one ISR scenario.
      For more information, see Form Scenario [Page 37].

      Workflow template
      You use a workflow template to define the process flow, define agent determination,
      and to control the form application [Page 42] in a process.
      For each process there is a workflow template that defines the process flow.
      For more information, see Business Workflow for HCM Processes and Forms [Page
      60].

      Process Object
      The process object represents the persistence layer of runtime data that results from
      the execution of a form-based process.
      The system creates a process object if the user triggers the process in the start
      application. The system saves the following data and elements in this process object:

             Data that a user entered in the form (for each process step)

             Attachments that a user included in the process while the process was being
             executed
      The process object is created and the data is saved using the Case Management
      [External] component.
For more information, see Process Object [Page 35].

      Start Application
      The start application enables processes to be started. Depending on the portal role, the
      start application can be structured differently. It displays the processes to be executed
      and the steps required to start a process (for example, displaying the Employee
      Selection function on the user interface of the start application).
      For more information, see Start Application [Page 38].

      Form Application
      The form application enables forms to be called in different scenario steps that are
      modeled in the workflow template.
      For more information, see Form Application [Page 42].

      Digital Personnel File (DPF)




HR Administrative Services (PA-AS)           6956                                             20
SAP Online Help                                                                     22.04.2009


     You can use the DPF together with HCM Processes and Forms. If you integrate the
     personnel file, the system automatically saves any forms and attachments in the
     employee's Digital Personnel File that are created when the process is executed.



            The permanent saving of processes is fulfilled using the process object;
            however, the DPF provides an optional enhancement to the HCM Processes
            and Forms functions.

Integration
HCM Processes and Forms uses the following components and their technologies:

      Internal Service Request [External] (ISR)
     The ISR Framework (including Interactive Forms based on Adobe software [External] /
     Adobe Document Services) provides the technical basis for defining an ISR scenario
     [Page 36] and defining the graphical layout of the forms.

      HR Master Data (PA-PA) and Data from Time Management (PA-PT)
     The fields of forms in HCM Processes and Forms can be linked with the fields in
     Personnel Administration (PA) infotypes, Personnel Development (PA), or Time
     Management (PT) infotypes. When the process is executed, the system updates the
     data in the infotypes with the entries made in the form fields.

      SAP Business Workflow [External]
     SAP Business Workflow provides the technical basis for modeling the process steps
     that depict the process flow after the process is started.
     In the workflow, you specify the following information for the individual process steps:

             The order of the individual process steps

             The functions that are provided to the users in the form application

             The users that are to execute a process step

             How and where the data is to be saved

      SAP Enterprise Portal
     The portal provides all users integrated in a process with the iViews needed to execute
     the process on the user interface:

             Start Application
            The start application enables the user to start processes.

             Universal Worklist (UWL)
            The UWL provides the work items with which the user can call the forms for
            which he or she is the intended agent.

      Manager Self-Service (MSS)
     The manager obtains access to the HCM Processes and Forms functions intended for
     him or her using the Manager Self-Service [External].

      Employee Self-Service (ESS)
     The employee obtains access to the HCM Processes and Forms functions intended for
     him or her using the Employee Self-Service [External].

      Records and Case Management



HR Administrative Services (PA-AS)          6956                                                21
SAP Online Help                                                                       22.04.2009


      Records and Case Management [External] provides the following underlying
      technology:

              Storage of process instances (for more information, see Process Object [Page
              35])

              The interface and data storage for the Digital Personnel File (DPF) and the
              process documents (forms and attachments) stored there.

Features
There are several different process types that can be started in HCM Processes and Forms:

       Start Process for Employee
      You start a process for a single employee, editing data for that employee in a form.

       Start Process Without Employee Selection
      You start a process without first selecting an employee, you can assign the employee
      at a later stage in the process.

       Perform Hiring Process
      You start the hiring process; the employee personnel number is automatically created
      after the start step is completed.

       Start Process for Multiple Employees
      You start a process for multiple employees at the same time, editing data for those
      employees in a table.

       Start Organizational Process
      You start a process for object types job, position, or organizational unit. You edit data in
      a form for that object type.
The standard process for HCM Processes and Forms involves the following steps:
  1. Select the object type - employee (or Skip Employee Selection checkbox), job, position,
     or organizational unit - that you want to execute the process for.
  2. Select a process (in Start Process for Multiple Employees, you choose process before
     choosing employees).
  3. Edit the form (or data in a table for Start Process for Multiple Employees).
  4. Save data for the employee(s) or object.
  5. For more information on process steps, see HCM Processes and Forms [Page 14].

Process Types
Start Process for Employee involves selecting one employee, selecting a process, editing a
form and saving data for that employee. This data can be forwarded to one or more further
agents in the process for input, or you can have a one-step process, which is finished when
the first agent selects Completed. It is also possible for an employee to start a process from
ESS using a link. For a sample process, see Birth of a Child (Germany) [Page 241].
Start Process for Employee




HR Administrative Services (PA-AS)            6956                                               22
SAP Online Help                                                                     22.04.2009




                          1                      2                     3


                       Start
                     Process
                    with HCM                 Edit Data              Edit Data
                    Processes
                    and Forms




                  First agent starts     Second agent             Third agent
                  process, it can be a   edits data and           edits data and
                  one-step process       sends form               saves form



       Or employee can start
       process using a link from
       ESS




It is possible to perform Start Proces for Employee process without first selecting an
employee, for example, the Special Payment process. You can assign the employee at a later
stage in the process, for example, the third agent involved in the process assigns the
employee. You enter data and send the form to the next agent, he or she reviews the data
and sends the form to the final agent in the process who assigns the employee and saves the
data. For a sample process, see Special Payment (Process Start Without Employee
Selection) [Page 298].
Start Process Without Employee Selection




                          1                      2                    3


                       Start
                     Process
                    with HCM                 Edit Data              Edit Data
                    Processes
                    and Forms




                 First agent starts        Second agent          Third agent
                 process, without          edits data and        assigns employee
                 selecting an employee     sends form            and saves form




                                           No employee             Employee
                                           assigned here         assigned here




HR Administrative Services (PA-AS)                        6956                             23
SAP Online Help                                                                    22.04.2009


Perform Hiring Process allows you to start a process without first selecting an employee. You
enter employee data, and the employee personnel number is assigned after the first process
step. The rest of the process continues like a multi-step employee process. You enter data
and send the form (the personnel number is automatically created), the next agent reviews
the data and sends the form to the final agent, who saves the data. For a sample process,
see Hiring (US) [Page 220].
Perform Hiring Process




                      1                    2                     3


                     Start
                   Process
                  with HCM              Edit Data              Edit Data
                  Processes
                  and Forms




              First agent starts      Second agent         Third agent edits
              process, without        edits data and       data and saves
              selecting an employee   sends form           form




                  Employee is
               assigned after this
                     step




Start Process for Multiple Employees allows you 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 a
specific piece of data for a number of employees, for example, country of residence.
Alternatively, it can be a multi-step process where individual process instances are generated
for each employee selected in the request step, for example, Special Payment process. You
enter data in a table for all the employees, when you send, separate process instances are
generated for each employee, the next agent (can be different for each employee) reviews
data in a form, the final agent saves the data. For a sample process, see Special Payment for
Mass Start (Multi-Step Process) [Page 272].
Start Process for Multiple Employees




HR Administrative Services (PA-AS)                  6956                                    24
SAP Online Help                                                                                                22.04.2009




                           1                       2                                        3


                        Start
                      Process                  Edit Data                                   Edit Data
                     with HCM
                     Processes
                                                        Edit Data
                     and Forms                                                                  Edit Data



                                                                Edit Data                         Edit Data
                 First agent starts
                 process; it can be a
                 one-step process; you
                 can enter data for
                 multiple employees
                                               If it is a multi-step
                                               process, a process
                                               instance is                                 Each employee’s
                                               generated for each                          form is sent to
                                               employee selected                           the next relevant
                                                                                           agent




Start Organizational Process - As well as starting a process for an employee, 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 select the object type, select a
process for that object type, edit data and save, forwarding to the next agent if workflow is
involved (you can also have a single-step process). The next agent reviews the data and
sends the form, the final agent saves the data. For a sample process, see Create Position
[Page 276].
Start Organizational Process




                           1                       2                         3


                        Start
                      Process
                     with HCM                   Edit Data                  Edit Data
                     Processes
                     and Forms




                First agent starts        Second agent                 Third agent edits
                process, but instead of   edits data and               data and saves
                selecting an employee,    sends form                   form
                the agent selects an
                object type



                       Job

     Position                       Org Unit




HR Administrative Services (PA-AS)                         6956                                                       25
SAP Online Help                                                                        22.04.2009



          Process Flow with One Form Scenario
Purpose
During a process flow, database entries are created and updated in the various HCM
Processes and Forms components. The following process flow description illustrates how the
various components work together using the example of a transfer process. This process
uses one form scenario.

Process Flow
The following assumptions have been made in the description of the process:

          Role 1: User in the role of Manager (sending manager)

          Role 2: User in the role of Manager (receiving manager)

          Role 3: User in the role of HR Administrator

          When setting up the workflow template, you specify that the entries in the form are
          saved to the backend system only after the third process step has been performed.
          The Send function triggers the data storage.

Process step 1 – Starting the process with the start application
      1. In the portal, the sending manager navigates to the start application [Page 38] that is
         set up for his or her role.
          The start application offers managers the relevant processes for which they have
          authorization.
      2. The manager selects the required employee.
      3. The manager selects the transfer process.
          The system calls the relevant form for processing.
      4. The manager enters the relevant data in the form fields.
          Depending on the Customizing settings, the system provides input help for certain input
          fields.
      5. The manager chooses the Review and Send function.
          The system checks the entries against data in the backend system. If necessary, the
          manager corrects any data that was entered incorrectly.
          Once the data is correct, the Review and Send view appears.
      6. The sending manager checks the entered data once again and chooses the Send
         function.
          A confirmation view appears in which the manager is informed that the data entry was
          successfully completed. The process reference number is specified in the confirmation
          view.
          When the Send function is executed, the system creates the following technical objects
          for the process in the specified order:
...




             a. The system creates a range of objects in Case Management for the process
                object [Page 35].
                 These include files that are referenced by the process object, such as
                 attachments or data containers for the form data.
             b. The system saves the data entered as a draft in the process object.

                        The process object is assigned the status Processed.



HR Administrative Services (PA-AS)               6956                                              26
SAP Online Help                                                                          22.04.2009


                         You can now view the process in the Process Browser [Page 45] and
                         trace its status.
             c. The system creates the instance of the workflow template that is assigned to the
                process and the instance of the first workflow template step that is executed.
      7. The workflow runtime environment determines the required agent for the first workflow
         step based on the agent determination rules stored in the workflow template for this
         step. In our transfer process example, this is the receiving manager.
      8. The system enters a work item in the Universal Worklist [Page 45] (UWL) of the
         receiving manager.

Process step 2 – Approval of the requested transfer
...




      1. In the portal, the receiving manager navigates to his or her UWL and calls the relevant
         work item.
      2. The system displays the form. The system dynamically merges the form layout that you
         stored in the Customizing settings for the ISR scenario [Page 36] and the form data
         from the process object that was specified by the sending manager.



                 At this time, the form does not yet exist as a PDF [External] file.
      3. The receiving manager checks the data entered and chooses Approve.
      4. In the following view, the manager receives confirmation that the approval was
         executed successfully.
      5. The system updates the technical instances of the process.

                 The system updates the process object. Based on the information specified in
                 the workflow step for saving data, the system saves the data at the end of
                 process step 2 not only in the infotypes of the application database, but also as
                 a draft in the process object.

                 The system updates the workflow instance. The system sets the status of the
                 work item to Completed and performs the agent determination as described in
                 process step 1.
      6. The system enters a work item in the UWL of the responsible HR administrator.

Process step 3 – Further processing and saving of data by the HR administrator
...




      1. In the portal, the HR administrator navigates to his or her UWL and calls the relevant
         work item.
      2. As in process step 2, the system combines the layout of the form to be displayed and
         the data.
      3. The HR administrator edits the form.
          He or she enters additional data that is required for a transfer. More fields are provided
          in addition to the fields that were available to the receiving manager in the form.



                 The availability of the form fields in the various process steps depends on the
                 assignments of the fields to the scenario steps in Customizing. For more
                 information, see Form Scenario [Page 37] under Scenario Steps.
      4. The HR administrator chooses Continue.
      5. The system checks the data entered.

                 Once the data is correct, the Review and Send view appears.



HR Administrative Services (PA-AS)               6956                                              27
SAP Online Help                                                                     22.04.2009


             If the system finds errors, the HR administrator must first check the data that
             was entered incorrectly.
             The HR administrator is an expert in the processing of employee data.
             Therefore, the data entered by the HR administrator can be saved in the
             infotypes of the application database. For this reason, the HR administrator must
             correct any entries that have triggered an error message. Only after the HR
             administrator has corrected any errors can the processing of the form be
             completed.
  6. The HR administrator checks the data entered and chooses the Send function.
      A confirmation view appears informing the HR administrator that the data was entered
      successfully.
  7. The system ends the process.

             The system updates the infotypes.

             The system sends an information e-mail to the employee who is to be
             transferred.

             The system sets the status of the work item of the HR administrator and the
             workflow template to Completed.

             If you use the Digital Personnel File (DPF), the system creates a PDF file with
             the data contained in the form.


The following graphic illustrates the described process flow for the transfer process example
using one form scenario.




HR Administrative Services (PA-AS)           6956                                              28
SAP Online Help                                                                     22.04.2009



                                                 Process


            Form scenario/ISR scenario 1
                                                           Transfer
                  Adobe Form (Layout) 1                      Scenario step 1: Visible in process step1, 2, & 3

     Form 1             Form 1            Form 1           Employee:         Gary Harvey
    (scenario          (scenario          (scenario        Personnel No.:    00001000
      step 1)            step 1)            step 1
                                                           Old Positio n:    Developer
                                             & 2)
                                                           New Position:     Development Architect
    Process            Process            Process
                                                           Transfer Date:    06/01/2005
     step 1             step 2             step 3
                                                                Scenario step 2: Visible in process step 3

       Start             UW L                UW L
                                                            Salary Group:                 5
    application
                                                            Bonus Plan:                   High


    Role               Role               Role
     1                  2                  3


                          ERP


                                     Workflow template (WS) 1




      Process Flow with Two Form Scenarios
Purpose
Architecture of HCM Processes and Forms when using two form scenarios




HR Administrative Services (PA-AS)         6956                                                  29
SAP Online Help                                                                     22.04.2009



                                                   Process


            Form scenario/ISR scenario 1                          Form scenario/ISR scenario 1
                   Adobe Form (Layout) 1                              Adobe Form (Layout) 2

     Form 1              Form 1            Form 1            Form 2          Form 2                  Form 2

                                               Data transfer

    Process             Process            Process        Process           Process                 Process
     step 1              step 2             step 3         step 4            step 5                  step 6

        Start              UWL                UWL             UWL              UWL                    UWL
     application



    Role                Role               Role            Role              Role                   Role
     1                   2                  3               4                 1                      3


                                                    ERP


                                       Workflow template (WS) 1




The graphic shows the structure of a process in which two form scenarios are used.



Process Flow
The process flow is essentially the same as for a process with one form scenario [Page 26].
The system can transfer the field values and attachments from the first form scenario to the
second form scenario. In Customizing for the form scenarios, you can define how and
whether data is to be transferred.
For more information, see the Implementation Guide (IMG) for HR Administrative Services
under Configuration of Forms/Processes     Configuration of Forms  Specify Data Transfer
Between Form Scenarios of Process.




   Overview: Data Processing in HCM Processes and
Forms
Use
Several components of the HCM Processes and Forms application are involved in processing
the data. The following overview shows you how the individual components work together to
check and save the data.




HR Administrative Services (PA-AS)          6956                                               30
SAP Online Help                                                                      22.04.2009


Features
Link between form data and infotype fields in Customizing
In order for the system to be able to process the data in the application database of the
infotypes, you must make the appropriate Customizing settings to link the fields that are
included in the form application [Page 42] with the infotype fields of the application.
...




      In Customizing, you enter for each form scenario [Page 37] the Personnel
      Administration. Time Management, and Personnel Development infotypes that are
      affected by operations such as Change, Create, and so on.
      You specify which field in the form scenario represents a specific field in the relevant
      infotype. In other words, you specify the relationships between form fields of the form
      application and the infotype fields.

      When setting up the form scenario, you specify which fields in the form are relevant for
      which form scenario step, that is, which data is relevant in which step for checking or
      saving.

      When setting up the workflow, you specify which form scenario step is executed for a
      specific workflow step.
For more detailed information, see the Implementation Guide for HR Administrative Services
under Configuration of Forms/Processes and Business Workflow for HCM Processes and
Forms [Page 60].

Processing of data when executing a process

      If a user uses the Check function in the form application or navigates to the Check and
      Send view, the system checks the plausibility of the values in the fields that were
      specified for the relevant form scenario step. This applies to the start application [Page
      38] and all other process steps.

              The backend layer for the form scenarios determines the relationships based on
              the data specified in Customizing for the form.

              The backend layer calls the business logic of the application for the infotypes
              and checks the entered data depending on the operation that is to be executed
              (Change, Create, and so on).

      If a user executes the Send function in the form application, the system saves all data
      changed, deleted, or created by the user in the form data container of the process
      object. This also happens when the start application is used and when executing
      individual process steps.
      The system performs an update of the infotypes only if it is specified in the workflow for
      a workflow step that the data is to be saved in the infotypes of the application database.



             If you have a process that consists solely of a start application, the data can be
             saved in the infotypes only if you created a workflow template with a workflow
             step with which the data is saved in the infotypes.
             A standard task, with which the data is automatically saved, is provided for this.
             An additional form scenario step in which the data is saved by the user is
             therefore not required. For an example, see the demo workflow template
             WS17900037.


The following diagram provides an overview of how the components work together, as
described above.




HR Administrative Services (PA-AS)           6956                                                31
SAP Online Help                                                                   22.04.2009




                                      Process Object



                                              Workflow Template
               Start of
                                             Workf low        Workf low
               Process                        Step              Step
                                             Approve          Edit For m
                                              For m


              Form                       Form                  Form
               Name:                      Name:                Name:
               Personnel no. :            Personnel no. :      Pers onnel no. :
               Amoun t:                   Amoun t:             Amoun t:
               Reason:                    Reason:              Reas on:


                  Send                        Send                 Send




                            Form Scenario - Backend Layer




                                      Application

                                 Business Logic of Application




                                      Application Database
                                        (Infotype Tables)




      Process
Definition
Depiction of a business process flow in Personnel Administration and Personnel Development
using elements from HCM Processes and Forms.




HR Administrative Services (PA-AS)          6956                                         32
SAP Online Help                                                                       22.04.2009


The process primarily represents a grouping of the ISR scenarios and form scenarios used
and the link with a workflow template. For each process, there is a workflow template that
defines the process flow.



             The process can be viewed in different ways and can mean the following:

                             From a business point of view, the process is the basis for
                             implementing a process. Therefore, the business flow should
                             exist as a process description at the start of the implementation.

                             From an implementation point of view, the process is the
                             technical representation of the business point of view, using
                             Customizing and using elements from HCM Processes and
                             Forms.

                             From a user point of view, the process is the user performing an
                             implemented process, for a specific employee and a specific
                             validity date. When performing the process, the system creates a
                             process object [Page 35]. As a result, the system makes the
                             master data changes defined in the process for the employee
                             concerned.
             SAP provides a range of sample processes. For more information, see Sample
             Processes in HCM Processes and Forms [Page 216].

Use
You use the Process object to depict a business process flow, using components from HR
Administrative Services. Note that many properties of the business process flow cannot be
set directly in the process; you set them indirectly in Customizing of the following components
involved:

       ISR Scenario

       Form Scenario

       Workflow Template (in the workflow steps)

       Start Application

       Form Application
For the process itself, the following information is entered in Customizing:

       Name of the process

       Validity period of the process

       Workflow template that is used when starting the process
Other Customizing settings for which the process is important:

       Grouping processes in process groups.
      You can assign process groups to the start applications, and use them to control
      authorizations. Assigning process groups to start applications enables you to provide
      various processes for different portal roles (manager, employee, HR Administrator).

       Settings for the collision check, parallel run, and restricting the frequency of processes

       Options for withdrawing processes if errors occur




HR Administrative Services (PA-AS)            6956                                             33
SAP Online Help                                                                  22.04.2009


Structure
Structure of a process

                                                Process

                                           ISR Scenario(s)
                                          Adobe Form (Layout)

                                     Interface Form/Back-End System

                                           Use of ISR Library


                                          Form Scenario(s)
                                          Features/Form Fields

                                            Scenario Steps

                                           Attachment Types

                                                Services


                                       Workflow Template (WS)
                  Use of specific workflow tasks and agent determination
                                           rules

          Process-specific Customizing of the start application and form application


          Process-specific Customizing for the transfer of forms and attachments to
                                 the Digital Personnel File




The graphic shows the elements that structure a process, and which process-specific settings
are necessary in Customizing.

Elements of the Process
      ISR scenario and form scenario
      For more information about the functions of the ISR scenario and form scenario, see
      the relevant documentation for the ISR scenario [Page 36] and form scenario [Page
      37].
      When using several forms within a process, the data transfer from form to form can be
      determined using Customizing.

      Workflow template
      In the workflow template, you model the workflow steps for which you configure the
      specific workflow tasks and rules for determining agents, and to which you assign
      appropriate form scenarios.

      Start application
      In the process-specific Customizing of the start applications, you determine which
      users can start a process and which start application (for the Employee, Manager, or
      HR Administrator role) is available to a process at the start.



HR Administrative Services (PA-AS)          6956                                             34
SAP Online Help                                                                      22.04.2009


       Digital Personnel File (DPF)
      In the process-specific Customizing for the transfer to the DPF, it is determined if forms
      and attachments of the process are transferred to the DPF. When using multiple forms
      and/or attachment types, a partial transfer is also possible.

Customizing for Processes
You make the settings for the different elements and functions in Customizing for HR
Administrative Services under HCM Processes and Forms         Configuration of
Forms/Processes      Design Time and under Configuration of Forms/Processes        Process
Configuration.
For more information about Design Time, see Design Time for Processes and Forms [Page
127].

Example
The following table lists the elements of a process based on an example.
The information for the following example corresponds to the provided Transfer sample
process.
Elements of the Transfer sample process

Element                                             Example (Name and ID)
Process                                             Transfer (ORG_CHANGE)
ISR Scenario                                        Transfer (SOC1)
Form Scenario                                       Transfer (SOC1)
Workflow Template                                   Transfer (WS17900427)




      Process Object
Definition
Object that represents the persistence layer of runtime data that results from the execution of
a form-based process [Page 32].
The system creates a process object if a user triggers the process in the start application
[Page 38]. The system saves the following data and elements in this process object:

       Data that a user entered in the form (for each process step)

       Attachments that a user included in the process while the process was being run
The process object is created and the data is saved using the Case Management [External]
component.

Use
The process object forms the basis for the following HR Administrative Services functions:

       Executing the form application [Page 42] within a process
      To be able to run a process step correctly, the form application requires both the data
      stored in the workflow and data such as the information that was entered in the form or
      the reference number of a process. The form application receives this data from the
      process object.


HR Administrative Services (PA-AS)           6956                                             35
SAP Online Help                                                                    22.04.2009


       Searching and displaying processes using the Process Browser
      The Process Browser is used to search for processes and for detailed information for
      the processes, such as status, employees involved, or times of execution. In the
      Process Browser, you can search using attributes of the process object and display the
      found processes in various degrees of detail (attributes for a process, attributes for
      steps of a process). The process object thus forms the technical basis for searching
      and displaying in the Process Browser.

Structure
The process object is structured hierarchically with the following levels:

       Top level: Has attributes for the process, such as process name or process reference
       number

       Middle level: Has attributes for the form scenarios used in the process, such as name
       and version of the form scenario

       Bottom level: Has data about the process step, that is, the data entered in the form and
       the administrative data such as the person executing the process or the status of the
       process step.
The examples for the individual levels come from HR Processes and Forms.
The case type [External] is of the most importance in Case Management. For each of the
named levels of a process object, a specific case type is predefined that you must implement
in the Customizing of the process modeling.
For more information about configuring the process object in Case Management, see the
Implementation Guide (IMG) for HR Administrative Services under Configuration of
Forms/Processes     Process Configuration     Technical Settings   Set Up Process Object.




      ISR Scenario
Definition
Used to call up an interactive form in a form-based process within HR Administrative
Services. The ISR has a 1:1 relationship with the form scenario [Page 37].

Use
In HR Administrative Services, ISR scenarios are used only to control the user interface in the
form of interactive forms as part of a form-based process. In other applications, an ISR
scenario is used to model an entire process. HR Administrative Services therefore uses only
a part of the functionality available for ISR scenarios. The Customizing environment for ISR
scenarios was modified accordingly.
We recommend that you use Design Time for Processes and Forms. Design Time replaces
a multitude of individual IMG activities, views and view clusters. You create the ISR scenario
when you create the form scenario. When you create a form scenario in Design Time, a
dialog box appears in which you enter the form scenario name and description. Additionally,
you should enter the ISR scenario and the form (the user must enter at least the ISR scenario
as this is a required field). The system then automatically creates the ISR scenario, the form
and the interface.


When the user adds infotype fields to the form scenario and saves the form scenario, the ISR
scenario is updated automatically with the new fields (characteristics).




HR Administrative Services (PA-AS)            6956                                          36
SAP Online Help                                                                      22.04.2009




              If the user enters only the ISR scenario in the dialog box, but not the Form, then
              neither the interface nor the form are created. This must be done separately in
              Design Time via Form Scenario in the object hierarchy area. In the Form area,
              the Create button allows you to create both the interface and the form.
When you create the form scenario, including the ISR scenario, via Design Time, the
following data is created:
ISR Scenario

Field                     Purpose
Scenario                  Four-character alphanumeric ID for the ISR scenario entered by the
                          user
Description               Business-related label for the ISR scenario automatically provided by
                          the system
Application               Application H (HCM Processes and Forms) indicates that the ISR
                          scenario is used in HR Administrative Services. This is automatically
                          provided by the system.
Version                   Numeric ID of the instance of the ISR scenario. The version of the ISR
                          scenario and that of the form scenario to be linked must be identical.
                          This is automatically provided by the system.
Input Type in Web         Input with Adobe PDF
                          The input type is a default value that you are not allowed to change.
                          Other input types are not currently supported. This is automatically
                          provided by the system.
Form                      Name of the form for the ISR scenario. If you do not enter a form name,
                          it is created automatically when the form is generated, and named
                          Z_ISR_FORM_<ISR scenario> (where "ISR scenario" is replaced with
                          the technical name of the scenario).
Interface                 Used for calling the interactive form. The interface is generated
                          automatically.
Characteristics           The fields of the form that are generated automatically during the
                          comparison to the linked form scenario. This is done automatically
                          when you save the form scenario.
Active                    Indicator that is automatically set for all newly created versions. You
                          specify when configuring a process which version is actually used. This
                          is automatically done by the system.




         Form Scenario
Definition
Together with the assigned ISR scenario [Page 36], the form scenario provides the basis for a
form-based process [Page 32] such as ‘Transfer’.
This type of process runs through several roles that are integrated using interactive forms,
and ends by modifying the HR master data.
A form scenario comprises one interactive form and is assigned to one ISR scenario.



HR Administrative Services (PA-AS)            6956                                             37
SAP Online Help                                                                       22.04.2009


Use
The form scenario is used to configure the interactive form:

       It determines the basic set of form fields that can be changed in a process.

       It configures the default values and input help for the form fields.

       It defines which HR master data fields are relevant for an assigned process step, and
       which changes to the data are to be performed on the database.

       It defines the use of attachments and links for additional information.
Form scenarios are version-dependent. Since processes can vary, it is important that you are
able to adjust the corresponding form scenarios. To be able to provide different forms for
process variants, you create versions. Each form scenario has at least one version, which you
link with the relevant process.
You can define scenario steps if the form configuration is not to be processed as a whole at
the runtime of the process; in other words, when different parts of the form configuration are
relevant depending on the process step involved.
You configure the form scenario in Customizing for HR Administrative Services by choosing
Configuration of Forms/Processes     Design Time for Processes and Forms.
To use a form scenario in a process, you must also use the corresponding ISR scenario in
parallel. The form scenario and the linked ISR scenario must have exactly the same version
number. Form scenarios are synchronized with ISR scenarios. When you create a form
scenario, you are asked to create the corresponding ISR scenario at the same time. When
the form scenario is later saved, the ISR scenario is also updated and saved. You assign the
ISR scenario to the form scenario in Customizing for HR Administrative Services by choosing
Configuration of Forms/Processes       Design Time for Processes and Forms..
Form scenarios are required for the start configuration of processes and must therefore be
linked with a process. A process can be assigned several form scenarios. You make the
assignment in Customizing for HR Administrative Services by choosing Configuration of
Forms/Processes Design Time for Processes and Forms.




      Start Application
Definition
Application to trigger a process [Page 32] within the framework of HR Administrative Services.
The start application consists of several views in which the user can perform the start of the
process. In these views, the user can select the employee or object that is to be involved in
the process and the process that the system is to start (depending on the portal role in each
case). The user can also edit the form assigned to this process. By sending this data, the user
ends the start application and triggers the process that the system maps from this point in
time using the form application [Page 42].

Use
The start application, which runs in the portal, is used to prepare the start of the process. You
make these preparatory settings in different views. When the start application ends, you
trigger the selected process; this means that the system creates a workflow instance for the
workflow template of the process. The execution of the start application is therefore the
triggering event for the workflow of the process.
For more information about the relationship between workflow and processes, see Special
Features of the Workflow for HCM Processes and Forms [Page 61].



HR Administrative Services (PA-AS)            6956                                             38
SAP Online Help                                                                               22.04.2009


Within the framework of HR Administrative Services, the standard system includes the
following start applications:

        Start application for HR Administrator

        Start application for Manager
These two applications differ only in terms of the Select Employee view: In the start
application for the HR Administrator, this view includes a simple search and an enhanced
search. The HR Administrator can select the employees to whom he or she is assigned. In
the start application for managers, the manager can select the employees for whom he or she
is responsible through the organizational assignment.
The start application for the Employee role is also executable. However, employees cannot
see the Select Employee view or the Select Process view. An employee can only trigger
processes for himself or herself. The processes that are available are entered in the
Employee portal role in the Life and Work Events area. Once a process has been selected,
the employee is brought directly to the Edit view.
For more information about setting up the start application for employees, see the IMG for HR
Administrative Services under Relationships to Other Roles       Employee Self-Service.

Structure
The following graphic simplifies the structure of the start application:


                        Start Application: Overview of Start Application Views

 View:             View:             View:                            View:                       View:
 Select            Select            Edit                             Review and Send             Completed
 Employee          Process
 Joe Miller        Process 1         Show Link List                   Show Link List              Data was sent
 Jack Smith        Process 2         Attachments                      Attachments
 …                 Process 3
                   …                          Transfer                      Transfer
                                        Employee: …                   Employee: …
                                        Date: 01/08/05                Date: 01/08/05
                                        Job:                          Job:




      Select             Edit            Save Draft      Review and                    Send
     Process                                               Send




In the different views of the start application, cross-view and view-specific functions are
available in each case. Examples of cross-view functions are Show User Involved or Show
Link List. They are available in several views. View-specific functions, such as Select Process
or Review and Send, are each available in one specific view only.


Overview of the start application views and their functions

Views                     Functions




HR Administrative Services (PA-AS)               6956                                                 39
SAP Online Help                                                                     22.04.2009


Select Employee        Used to select the employee on which the process that is to be started is
                       to be based. It is dependent on the initiator role and is only available to
                       HR administrators and managers, not to employees.
                       Functions:

                              Start (Search) (enables the search for employees)

                              Select employee from hit list or employee list
                       When the employee has been selected

                              Select Process (leads to the next view)
Select Process         Used to select the process that the user wants to start for the selected
                       employee.
                       Which processes are available for selection here depends on the
                       following factors at runtime:

                              Role dependency – It is specified in Customizing which processes
                              are available for selection for which initiator role.

                              Dependency on the selected employee – It is specified in
                              Customizing which processes are valid for which employee (for
                              example, using the personnel area to which the employee is
                              assigned). Only these processes are then available for selection.
                       Functions:

                              Previous Step (returns to preceding view Select Employee)

                              Select Process

                              Edit (leads to the next view)
Edit                   Used for editing a form assigned to a given process and for checking the
                       data entered.
                       The user enters data in the form. The system supports the user with
                       various functions in the form, default values, and value help.
                       Functions:

                              Show Link List

                              Previous Step (returns to preceding view Select Process)

                              Review and Send (checks the entries made and displays any
                              error messages – this function is available until all entries are
                              correct and no further errors are detected)
                       Optional function:

                              Save Draft




HR Administrative Services (PA-AS)          6956                                             40
SAP Online Help                                                                     22.04.2009


Review and Send          As a result of the check, this displays error messages if the user made
                         incorrect or invalid entries.
                         The user can correct any errors. After correction, a second check is
                         required. When all errors have been corrected, the user can send the
                         form and the system navigates to the next view.
                         Functions:

                                Show Link List

                                Previous Step (returns to preceding view Edit)

                                Send (ends form editing and navigates to the next step)
Completed                Outputs a message that the data was sent successfully. With appropriate
                         Customizing, the user can display a reference number for the process
                         started.
                         Functions:

                                Start Additional Process
You make the settings in Customizing for the views and functions of the start application in
the IMG for HR Administrative Services under Configuration of Forms/Processes        Process
Configuration     Set Up Processes   Validity for Process Start and under HR Administrator
   Start Application for Processes.

Integration
You access the start application as follows:

       Start application for HR Administrator: iView Start Processes for the portal role HR
       Administrator

       Start application for Manager: iView Start Processes for the portal role Manager
In Customizing, you can specify that the system provides different processes for different
areas of responsibility. In this way, administrators for HR master data can select processes
different to those available to administrators for time recording. For more information about
this topic, see the IMG for HR Administrative Services under HR Administrator         Start
Application for Processes       Create Start Applications for Different Users in Portal.

Example
The user is an HR Administrator. It is specified in Customizing that the processes 1 to 10 are
available for selection for the HR Administrator portal role. It is also specified that the
processes 1 to 5 are valid for employees of the personnel area 100 and the processes 6 to 10
are valid for employees of the personnel area 200.
Execution of the start application

View                     Example
Select Employee          The HR Administrator selects employee 1 who belongs to the personnel
                         area 100. The administrator then chooses Select Process and the
                         system navigates to the following view.
Select Process           The system displays the processes 1 to 5 for selection by the HR
                         Administrator. The HR Administrator selects process 1, chooses Edit,
                         and the system navigates to the following view.




HR Administrative Services (PA-AS)             6956                                             41
SAP Online Help                                                                     22.04.2009


Edit                     The system displays the form for processing that is assigned to process
                         1. The HR Administrator makes the desired entries in the form. The
                         administrator then chooses Review and Send and the system navigates
                         to the following view.
Review and Send          All entries were correct. The HR Administrator chooses Send and the
                         system navigates to the following view.
Completed                The HR Administrator receives the information that the system has sent
                         the data successfully. The HR Administrator closes the start application.




       Form Application
Definition
An application used in the context of HR Administrative Services for editing the forms of a
process [Page 32] in all of the steps following the initial step.



Use
You use the form application to edit forms during a process. You call the form application from
the universal worklist (UWL) [Page 45]: The system launches the form application when a
user executes a work item in the UWL that is based on a workflow step that was set up in
HCM Processes and Forms. You generally set up such a workflow using workflow tasks
predefined for HCM Processes and Forms. The following tasks are of relevance:

       Process Form (TS17900100)

       Approve Form (TS17900101)

       Form Is Edited Again by Author (TS17900102)
For more information about workflow, see Business Workflow for HCM Processes and Forms
[Page 60].
In addition, you can launch the form application from a mail. You use this method of launching
the application typically if the agent responsible for processing a work item does not have a
UWL. In the standard system, this applies to the portal role Employee. In this case, the
system generates a mail containing a hyperlink, with which the user can launch the form
application.
For more information, see the Implementation Guide (IMG) for HR Administrative Services
under Configuration of Forms/Processes     Process Configuration  Enhanced Messages.



Structure
The following graphic illustrates a simple structure of the form application:




HR Administrative Services (PA-AS)            6956                                            42
SAP Online Help                                                                             22.04.2009


                                          Form Application Views
                              Views when using the tasks "Process Form"/"Form Is Edited Again By Author"

  Start of form application   View:                             View:                             View:
  The Manager and HR
                              Edit                              Review and Send                   Completed
  Administrator roles start   Agents Involved                   Agents Involved                   Data was sent
  the form application from   Attachments                       Attachments
  the universal worklist
  (UWL)                                 Transfer                         Transfer
  The Employee role starts
                               Employee: ...                     Employee: ...
  the form application from
                               Date: 08/01/05                    Date: 08/01/05
  an e-mail that contains a
                               Position:                         Position:
  link to start the form
  application
                               Back to Author     Review and      Previous Step     Send
                                                    Send


                                   Views when using the task "Approve Form"


                              View:                             View:
                              Approve                           Completed
                              Agents Involved                   Data was sent
                              Attachments

                                        Transfer
                               Employee: ...
                               Date: 08/01/05
                               Position:

                              Approve    Reject     Back to
                                                    Author




The form application is made up of a number of different views that contain view-specific and
cross-view functions.
You determine which views are available by means of the workflow tasks predefined for HCM
Processes and Forms. In other words, the form application views displayed depend on the
workflow tasks you use when implementing a workflow step. Most of the functions are also
provided through the workflow tasks.
For more information about setting up the workflow, see the Implementation Guide for HR
Administrative Services under Configuration of Forms/Processes     Process Configuration
Workflow Modeling     Include Components for HCM Processes and Forms in Workflow
Builder.


The following two tables provide an overview of the views of the form application using the
three most important workflow tasks:

       Form application using the workflow tasks Edit Form [Page 73] or using Form Is Edited
       Again by Author [Page 84] (identical behavior of form application)

       Form application using the workflow task Approve Form [Page 81]


Overview of the form application views using the workflow tasks Edit Form or Review
Form
View                                                     Functions




HR Administrative Services (PA-AS)                6956                                                 43
SAP Online Help                                                                22.04.2009


Edit                                          Used for editing a form assigned to a given
                                              process and for checking the data entered.
                                              The user enters data in the form. The system
                                              supports the user with various functions in the
                                              form, default values, and value help.
                                              Functions:

                                                     Review and Send (checks the data
                                                     entered and navigates to the next view)
                                              Optional function:

                                                     Save Draft

                                                     Back to Author

                                                     Withdraw Process
Review and Send                               As a result of the check, this displays error
                                              messages if the user made incorrect or invalid
                                              entries.
                                              The user can correct any errors. After
                                              correction, a second check is required. When
                                              all errors have been corrected, the user can
                                              send the form and the system navigates to the
                                              next view.
                                              Functions:

                                                     Previous Step (returns to preceding view
                                                     Edit)

                                                     Send (ends form editing and navigates
                                                     to the next step)
Completed                                     Outputs a message that the data was sent
                                              successfully.


Overview of the form application views using the workflow task Approve Form
View                                          Functions
Approve                                       Used for approving or rejecting a form.
                                              Functions:

                                                     Approve

                                                     Reject
                                              Optional function:

                                                     Save Draft

                                                     Back to Author

                                                     Withdraw Process
Completed                                     Displays successfully approved or rejected
                                              form.




HR Administrative Services (PA-AS)     6956                                             44
SAP Online Help                                                                      22.04.2009



      Universal Worklist (UWL)
Definition
SAP Enterprise Portal element that users can personalize as their central point of access to
their tasks.
In HR Administrative Services, the universal worklist provides users with the current work
items generated by the system when running a process within HCM Processes and Forms.
For more information, see Universal Worklist [External].



Use
You have to use the universal worklist for all portal roles that you want to be involved in
processes in HCM Processes and Forms. It is not necessary to set up a universal worklist for
roles that only trigger the process start but that are not involved in other process steps. The
SAP Business Workflow [Page 60] enters the current processing steps as work items in the
relevant user's universal worklist.
The universal worklist is already integrated in the Manager and HR Administrator portal roles.
It is set up to enable the system to display work items from HCM Processes and Forms.
If you want to set up additional portal roles to use HCM Processes and Forms, you must
configure the universal worklist accordingly when integrating the portal roles.
For more information, see the Implementation Guide for HR Administrative Services under
HR Administrator -> Set Up Display in Universal Worklist.



Integration
When calling up a work item in the universal worklist, the system starts the form application
[Page 42].




      Process Browser
Use
The HR Administrator can use this function to obtain an overview of processes and
associated process steps. The administrator can also display data such as personnel number,
date of birth, and contact details for the employee affected by the process, and for the
process initiator. Additionally, the administrator can display the forms that are assigned to the
individual process steps of a process.

Integration
The process browser is available to the HR Administrator in the portal, in the following iViews:

       Open Employee Processes [External] and Open Employee Processes [External]
       iViews
      The process browser here has predefined search criteria. Therefore, the iViews do not
      display the process browser’s search fields. Instead, they directly shows a list of all
      processes in which the HR Administrator is involved, and that are not yet completed.




HR Administrative Services (PA-AS)            6956                                              45
SAP Online Help                                                                     22.04.2009


       Search Employee Processes [External] and Search Organizational Processes
       [External] iViews
      These iViews comprises all of the process browser’s functions. The iViews first shows
      the search fields for a simple search for processes. You can use the Advanced Search
      function to show additional search criteria. The system displays the search results in a
      list, below the search criteria.

       Display Processes [External] iView
      The process browser here has the name of the affected employee as preset selection
      criteria. Therefore, the iView does not display the process browser’s search fields. The
      HR Administrator first selects an employee in the Employee Information workset. This
      iView then displays all the processes in which the employee selected is involved.

       Open processes in Display Employee Profile [External] iView
      The process browser is the same as that in the Open Processes iView. However, the
      name of the employee previously selected by the HR Administrator in the Employee
      Information workset is predefined as an additional selection criteria, in the same way as
      it is for the Display Processes iView.
The Details function is available to the HR Administrator in all of these iViews.

Features
The process browser provides the following functions:

       Search fields for searching for processes
      Here you enter your search criteria and start the search.

       Hit list
      Below the search fields, the system displays the list of processes that match the search
      criteria. In the list, you can view the data for the employee that is affected by the
      relevant process, and the data for the person who started the process.

       Dialog box with details on the processes
      After selecting a process from the search results, you can use the Details function to
      access a dialog box with further information. The dialog box shows the general data of
      the process that you previously selected in the results list of the process search, and a
      list of all process steps executed for the process thus far. By selecting a process step,
      you open the associated form in the display mode. The form contains all data and
      attachments that existed when the relevant process step was completed.

       Business Status of process step
      Along with the processing status, APPROVED, PROCESSED, and so on, you can
      customize text for individual processes to appear in the Business Status column. This
      text gives more detailed, personalized input on the status of the process. For more
      information, see Business Status [Page 47].
Depending on how the process browser is used, all or some of these functions are available.
For example, in some iViews, only the hit list and the process details are available, and not
the search.
See also:
Process Object [Page 35]




HR Administrative Services (PA-AS)            6956                                            46
SAP Online Help                                                                     22.04.2009



     E-Mail Notification

An e-mail which arrives in the e-mail inbox, advising an agent that there is a work item to be
executed.



Extended Notification is used to inform recipients by e-mail that a workflow work item is
waiting to be processed.

This e-mail notification makes sense if the recipient does not have a UWL in the portal (for
example, this can be the case for the portal role Employee) or if the recipient does not
frequently check his or her R/3 inbox. The work item does not appear in the UWL, but arrives
in an e-mail as a link instead. This ensures that agents involved in a workflow process receive
notification of a work item to be executed as soon as possible, meaning that the process can
be completed without unnecessary delays. A link is provided in the e-mail body from which
you can generate the work item to be executed. Alternatively, you can choose not to send the
e-mail so that the recipient instead receives the work item in the worklist.

For more information, see Customizing for Personnel Management under HR
Administrative Services Configuration of Forms/Processes Process Configuration
  Enhanced Messages Enhanced Notifications of SAP Business Workflow .



     Business Status

The business status is the customized status value of a particular process step.

The business status appears in the process browser for individual work items, so that the user
can see what status the process is at. For a processing status such as Approved, you can
enter a customized text for the business status, for example, Approved by Manager, so that it
is easier to identify the specific step that has been completed. You can create several
different business status texts for each processing status. Depending on the individual
process, you can choose one of these business statuses to appear in the process browser for
the request step.

To see the business status of a process step, open the process browser. For more
information, see Process Browser.

Features
        You can create several different business status texts for each process step status.

        You can create a business status for the request step in a process (the first step,
        when he workflow has not been started).

        If no business statuses are created by the user, the system provides default settings
        for business statuses as detailed in the following table:

   Process Step Status                          Business Status Description

APPROVED                       Approved

REJECTED                       Rejected



HR Administrative Services (PA-AS)           6956                                              47
SAP Online Help                                                                      22.04.2009



   Process Step Status                           Business Status Description

PROCESSED                      Processed

RESENT                         Sent Again

WITHDRAWN                      Canceled

BACK                           Sent back to Author

DRAFT                          Saved as Draft

ERROR                          Errors Occurred

FORWARDED                      Forwarded to Expert

BACKTOUSER                     Returned to Original User after Resolving Error

SELECTED                       Process Selected after XI Inbound

XI_REJECTED                    XI Message Rejected

For more information, see Customizing HR Administrative Services Configuration of
Forms/Processes Process Configuration Maintain Business Status .

Activities
You create business statuses and make them available to processes in Customizing.
However, it is at the individual workflow step level that you control which business status to
display in the process browser and process overview.

In the Customizing activity HR Administrative Services Configuration of Forms/Processes
  Process Configuration Maintain Business Status you can perform the following
activities:

        Create business statuses for each process.

        Assign particular business statuses to individual processes.

In the Customizing activity: HR Administrative Services Configuration of
Forms/Processes Process Configuration Maintain Business Status for Request Step
  you can perform the following activity:

        Assign a business status to the first step of a process (when the workflow has not
        been started)

In the Workflow Builder (transaction SWDD) you perform the following activity:

        Choose business statuses to assign to individual process workflow steps.

For more information on all the activities described above, see Creating and Assigning
Business Statuses.



     Creating and Assigning Business Statuses


HR Administrative Services (PA-AS)            6956                                               48
SAP Online Help                                                                      22.04.2009


You create and assign business statuses to processes to provide the end user with more
detailed information about the stage a process is at.

Procedure
Creating Business Statuses
Before you can assign customized business statuses, you must create them in Customizing.
To do this, complete the following steps:

    1. Choose Personnel Management HR Administrative Services Configuration of
       Forms/Processes Process Configuration Set Up Processes Maintain Business
       Status .

    2. In the Choose Activity dialog box, choose Maintain Business Status.

        The Determine Work Area: Entry dialog box appears.

    3. Enter the workflow step status which you want to customize and choose Continue.


             Recommendation

        If a list of customized business statuses already exist, make a note of the last ID in
        the list. When you create a new business status, the system does not automatically
        provide IDs.


    4. Choose New Entries.

    5. Enter a new ID and business status.

        The text you write here for the business status appears in the process browser and
        process overview. Do not enter an ID that already exists for the step status type.

    6. Choose Save.

        Choose Back to see your new business status.

Once you create a business status, you may assign it to processes and workflow steps.

Assigning Business Statuses to Request Steps (First Process Steps)
To assign a business status to the first step in a process (which is outside of the workflow),
complete the following steps:

    1. Choose Personnel Management HR Administrative Services Configuration of
       Forms/Processes Process Configuration Set Up Processes Maintain Business
       Status .

    2. In the Choose Activity dialog box, choose Maintain Business Status for Request Step.

        The Determine Work Area: Entry dialog box appears.

    3. Enter the process to which you want to assign a business process and choose
       Continue.

    4. In the Step Status After Action field, enter the step status you wish to assign to the
       first process step (outside the workflow).

        Once you do this, all the business statuses that you have created for this step status
        are available to you.



HR Administrative Services (PA-AS)            6956                                               49
SAP Online Help                                                                        22.04.2009


    5. Enter a business status ID and choose Save.

The business status now appears in the process browser and process overview when the
process is started in the Portal.

Assigning Business Statuses to Individual Process Workflow Steps
Once you create business statuses, you assign them to the individual workflow steps of a
particular process. To do this, complete the following steps:

    1. Open the Workflow Builder (transaction SWDD).

    2. Choose the workflow containing the workflow steps, to which you wish to assign a
       business status.

    3. Double-click a workflow step.

        The basic details for the workflow step appear.

    4. Choose Binding Exists.

        The Change Binding For Step dialog box appears.

    5. Choose the dropdown list in the &Business_Status& workflow container element.

        The Enter Constant dialog box appears.


             Note

        If the &Business_Status& workflow container element does not appear in the bottom
        half of the screen, search for it in the top right window and drag it into the bottom right
        window.


    6. Choose Enter Constant.

        Fields appear for each of the step status types.

    7. Enter a business status for the step status types you wish to customize and choose
       Exiting Binding Editor.

When the process is started and the individual workflow step has been completed, the
process browser and process overview display the business status you have assigned to the
workflow step.



      Creating and Editing Interactive Forms
Use
To support your form-based business processes, you create and edit interactive forms using
the Adobe LiveCycle Designer (Form Builder). The Adobe LiveCycle Designer is software
from the company Adobe Systems Inc. that is integrated in the SAP environment. For more
information about the Adobe LiveCycle Designer, see the Procedure tab page under More
Help.
The Adobe LiveCycle Designer covers two areas:

      The left side contains a window with the tab page Data View.




HR Administrative Services (PA-AS)            6956                                              50
SAP Online Help                                                                        22.04.2009


      This area contains all form fields that you have defined in the form scenario or that you
      have transferred to the ISR scenario as characteristics using the comparison with the
      form scenario.



             The following fields and structures also appear:
             ISR_LONG_TEXT
             ISR_NEW_LONG_TEXT
             ISR_AUTOMATIC_UPDATE
             GENERAL_DATA
             CONTROL_PARAM
             You should not use these fields or structures in HR Administrative Services
             since their behavior can change at any time.

      The right side contains a window with the tab page Library.
      This area contains all interface elements that you can use to structure the form. Use
      drag and drop to drag the interface elements to the form. SAP provides an own library
      of interface elements under the name ISR Native Controls. This library is specially
      adjusted for use in ISR scenarios.
      SAP has made all interface elements necessary for use within the HR Administrative
      Services framework available in a library contained in SAP Note 973170. Elements in
      this library also contain the scripting necessary for UI attributes.



             If possible, use only interface elements from this Library.
             These interface elements contain special scripting that is adjusted for use in the
             HR Administrative Services ISR environment.
             To view (and edit if necessary) this scripting, in Adobe LiveCycle Designer,
             choose Pallets     Script Editor. In the dialog box that opens, in the dropdown list
             choose Display      Events with Scripts.

Features
The Adobe LiveCycle Designer provides you with the following functions for editing interactive
forms:

      Creation of form fields with data binding
      For detailed information, see Creating Form Fields with Data Binding [Page 52].

      Entry of agent (processor) notes
      A standard function is provided for entering agent notes in the form. To use this form,
      the automatically generated fields HRASR_PREVIOUS_NOTES and
      HRASR_CURRENT_NOTE must be used. The field HRASR_CURRENT_NOTE
      enables the current agent of the form to enter notes when he runs the process. The
      field HRASR_PREVIOUS_NOTES shows the current agent all notes entered in
      previous processing steps. For detailed information, see Using Form Fields to Enter
      Agent Notes [Page 53].

      Creation of dropdown list boxes
      In contrast to the SAP GUI, in an interactive form, it is currently not possible to provide
      input help (F4 help) for an input field. However, it is possible to use dropdown list boxes
      and thus define the set of valid entries uniquely. The prerequisite for this is that, for the
      field in the form scenario, you have either defined a manual value help or configured


HR Administrative Services (PA-AS)            6956                                              51
SAP Online Help                                                                             22.04.2009


          the value help such that it is provided by means of a backend service. For detailed
          information, see Creating Dropdown List Boxes [Page 54].

          Creation of pushbuttons
          In a form, you can create pushbuttons with which the user can trigger actions at
          runtime. The following actions are supported:

                 Initialization of the entire form
                 The pushbutton for initializing the entire form resets the form to its initial status.
                 The content of all fields is deleted and default values are redetermined (if
                 defined). The field Effective Date (EFFECTIVE_DATE) is particularly important
                 here. This field is not reset. The current date entered is used to calculate the
                 (time-dependent) default values.

                 Triggering of a roundtrip to check the data entered and to calculate dependent
                 fields
                 For detailed information, see Creating Pushbuttons [Page 55].

Activities
You access the Adobe LiveCycle Designer (Form Builder) through the Customizing for HR
Administrative Services:
You can access the functions for creating or editing interactive forms under Configuration of
Forms/Processes     Cross-Form Settings       Create ISR Scenario:

          Choose Version in the dialog structure.
          The Change Version view appears.

          Choose Generate to create the form or Change Adobe Form to edit the form.




          Creating Form Fields with Data Binding
Use
In Adobe LiveCycle Designer (Form Builder), you specify the layout of an interactive form. In
a library, you select the UI elements that you use to specify how a field is displayed in the
form. You link the UI element to one of the form fields that you defined in the associated form
scenario. In this way, the form field is automatically filled with data at the process runtime.

Procedure
...




You access the Adobe LiveCycle Designer (Form Builder) through the Customizing for HR
Administrative Services:

          Choose Configuration of Forms/Processes           Configuration of Forms       Create ISR
          Scenario.

          Choose Version in the dialog structure.
          The Change Version view appears.

          Choose Generate to create the form or Change Adobe Form to edit an existing form.
Proceed as follows:
      1. Select a suitable UI element from the Library and move it to the form using drag and
         drop.




HR Administrative Services (PA-AS)                   6956                                             52
SAP Online Help                                                                            22.04.2009


      2. Select the UI element and change the properties such as size, position, description,
         and so on.
      3. In the area on the left of the Adobe LiveCycle Designer, choose the Data Overview tab
         page.
      4. Select the desired form field and expand it down to the FIELD subelement.
      5. Select the FIELD element and use drag and drop to place it exactly on the UI element
         in the form.
      6. In the next dialog screen, select the Do Not Update Related Properties option.
          In this way, the UI element is automatically linked to the form field and is filled with data
          automatically at the process runtime.
      7. If necessary, check that the link to the form field is correct by choosing the Object tab
         page.
      8. Select the Binding tab page and check the value entered for Standard Binding. This
         value must have the format $record.<Field Name>.DATA[*].FIELD, where <Field
         Name> is the name of the form field.




          Using Form Fields to Enter Agent Notes
Use
A standard function is available to enter agent notes in the form. To use this function, you
must use the following automatically generated fields:

          HRASR_CURRENT_NOTE
          In this field, the current agent (processor) of a form can enter any number of notes at
          the process runtime.

          HRASR_PREVIOUS_NOTES
          In this field, all notes entered in previous processing steps are displayed to the current
          agent.

Procedure
...




You access the Adobe LiveCycle Designer (Form Builder) through the Customizing for HR
Administrative Services:

          Choose Configuration of Forms/Processes          Configuration of Forms       Create ISR
          Scenario.

          Choose Version in the dialog structure.
          The Change Version view appears.

          Choose Generate to create the form or Change Adobe Form to edit an existing form.
Proceed as follows:
      1. Select the element with the name HR Admin – Comments from the Library and move it
         to the form using drag and drop.
      2. Change the field names in accordance with your requirements.
      3. Leave the technical settings and data binding unchanged.




HR Administrative Services (PA-AS)                6956                                               53
SAP Online Help                                                                              22.04.2009



          Creating a Dropdown List Box
Use
For an input field on an interactive form, you can create a dropdown list box that contains the
range of valid input values for this field.

Prerequisites
For the field in the form scenario, you have either defined a manual value help or configured
the value help such that it is provided by means of a backend service.

Procedure
You access the Adobe LiveCycle Designer (Form Builder) through the Customizing for HR
Administrative Services:

          Choose Configuration of Forms/Processes         Configuration of Forms      Create ISR
          Scenario.

          Choose Version in the dialog structure.
          The Change Version view appears.

          Choose Generate to create the form or Change Adobe Form to edit an existing form.
Proceed as follows:
...




      1. Select the element with the name HR Admin – Drop Down List Box from the library and
         move the element to the form using drag and drop.
      2. Link the subelement FIELD to the dropdown list box. To do this, proceed as described
         in Creating Form Fields with Data Binding [Page 52].
      3. Choose the Binding tab page and then Element Values.
          The Dynamic Properties dialog box is opened.
      4. Enter the following value in the Objects field: $record.sap-vhlist.<Field
         name>\.DATA\.FIELD.item[*], whereby <Field name> is the name of the form field.

      5. Decide if the dropdown list box is to trigger a roundtrip at runtime when you select an
         entry.
          A roundtrip must be triggered if there are other fields or other dropdown list boxes
          whose values are dependent on the selected value and therefore must be recalculated
          accordingly.



                 If you have a dropdown list box for both Personnel Area and Personnel
                 Subarea, the possible entries for the Personnel Subarea are dependent on the
                 entry you select for Personnel Area. This means that the dropdown list box for
                 the Personnel Area must trigger a roundtrip so that the possible entries for the
                 Personnel Subarea can be redetermined. In contrast, the dropdown list box for
                 the Personnel Subarea does not have to trigger a roundtrip.

                 If the dropdown list box is not to trigger a roundtrip, the processing is
                 completed.

                 If the dropdown list box is to trigger a roundtrip, you must adjust the coding of
                 the dropdown list box as follows:

                        Select the dropdown list box on the form and choose Pallets           Script
                        Editor in the Adobe LiveCycle Designer.


HR Administrative Services (PA-AS)               6956                                                  54
SAP Online Help                                                                         22.04.2009


                         In the next window that appears, select the *exit entry in the Display
                         dropdown list. Find the following coding:
                         // xfa.record.CONTROL_PARAM.ISR_EVENT.value = "CHECK";
                         // app.eval("event.target.SAPSubmit(false);");
                         With the prefixed comment signs "//", the coding is deactivated.

                         Remove the comment signs "//".

                         Replace the CHECK string with USER EVENT CHECK.
                         The coding must then be as follows:
                         xfa.record.CONTROL_PARAM.ISR_EVENT.value =
                         "USER_EVENT_CHECK";
                         ContainerFoundation_JS.SendMessageToContainer(event.target,
                         "submit", "", "", "", "");
                         The coding is now activated and triggers a roundtrip at runtime so that
                         dependent fields and dropdown list boxes can be calculated.



         Creating Pushbuttons
Use
In an interactive form, you can create pushbuttons with which the user can trigger actions at
the process runtime.
The following actions are supported:

          Initialization of the entire form

          Partial initialization of the form

          Triggering of a roundtrip to check the data entered and to calculate dependent fields
For more information, see Creation and Editing of an Interactive Form [Page 50].

Creating Pushbuttons to Initialize Forms
When the form is initialized, the system provides default values and input helps based on the
field contents of the form fields.
To set up a pushbutton to initialize the form, proceed as follows:
You access the Adobe LiveCycle Designer (Form Builder) through the Customizing for HR
Administrative Services:
...




      1. Choose Configuration of Forms/Processes         Configuration of Forms     Create ISR
         Scenario.
      2. Choose Version in the dialog structure.
          The Change Version view appears.
      3. Choose Generate to create the form or Change Adobe Form to edit an existing form.
      4. Select the HR Admin – Button element and move it to the form using drag and drop.
      5. Select the pushbutton and change the size and description to suit your requirements.
      6. Choose Pallets       Script Editor.
      7. In the next dialog screen, select the *mouseDown entry in the Display dropdown box.
      8. Find the following coding:


HR Administrative Services (PA-AS)               6956                                              55
SAP Online Help                                                                         22.04.2009


          $record.CONTROL_PARAM.ISR_EVENT = "CUSTOM_EVENT"
      9. Replace the "CUSTOM_EVENT" string with "USER_EVENT_INITIALIZE".

Creating Pushbuttons to Partially Initialize Forms
If you have defined several areas in a form that each correspond to one field group with
several fields, you can offer a pushbutton in each of these areas that will trigger an operation.
The operation checks, for example, the field contents of the area and simultaneously
initializes the fields of the subsequent area.
During the initialization, based on the field contents of the previous area(s), the system
provides information for the subsequent area, such as default values and input help.
You define the operations for the subsets of form fields in Customizing under Configuration of
Forms/Processes     Configuration of Forms      Create Operations for Groups of Form Fields.
To set up a pushbutton to partially initialize the form, proceed as follows:
...




      1. Perform steps 1 to 8 as described in the “Creating a pushbutton to initialize the form”
         section.
      2. Replace the “CUSTOM_EVENT“ string with an operation defined in the IMG under
         Configuration of Forms/Processes Configuration of Forms    Create Operations for
         Groups of Form Fields.

Creating Pushbuttons to Trigger Roundtrips
If you want to create a pushbutton to check the entered data and calculate derived data,
proceed as follows:
...




      1. Perform steps 1 to 8 as described in the “Creating a pushbutton to initialize the form”
         section.
      2. Replace the "CUSTOM_EVENT" string with "USER_EVENT_CHECK".




          Message Mapping
With the help of this tool, you can substitute non-applicable or non-specific system messages
(such as information, error messages, warnings, success messages, cancellation messages,
and exit messages) with appropriate messages. You can make the required settings in
Customizing for HR Administrative Services under Tools        Message Mapping.
Alongside this general kind of message mapping, you have the ability to define a specific kind
of message mapping according to the form scenario. For more information, see Message
Mapping Based on Form Scenarios [Page 58].
You have several options for defining the message mapping:

          Message mapping according to message type, message ID, and message number

          Message mapping according to error category and message type
The following graphic gives you an overview of how the individual customer and standard
customizing settings are read through the system.




HR Administrative Services (PA-AS)               6956                                              56
SAP Online Help                                                                   22.04.2009


                   Start


                  ………


                 C Table 1                    C Table 1                        S Table 1                    S
            CONTEXTID                     CONTEXTID                       CONTEXTID                     CONTEX
            PROCESSOR_ROLE                PROCESSOR_ROLE empty            PROCESSOR_ROLE                PROCE
            MSGTY                         MSGTY                           MSGTY                         MSGTY
            MSGID                         MSGID          empty            MSGID                         MSGID
            MSGNO                         MSGNO          empty            MSGNO                         MSGNO



          Yes    Message                         Message      No                 Message      Yes       No
     x           mapping                         with error                      mapping            x
                  found?                         category?                        found?

                           No                           Yes                           No

               C Table 1                       C Table 2                      S Table 1
           CONTEXTID                       CONTEXTID                      CONTEXTID                          CON
           PROCESSOR_ROLE                  PROCESSOR_ROLE                 PROCESSOR_ROLE                     PRO
           MSGTY                           ERRORCAT                       MSGTY                              ERR
           MSGID         empty             MSGTY                          MSGID          empty               MSG
           MSGNO         empty                                            MSGNO          empty



          Yes    Message                         Message      Yes                Message      Yes
     x           mapping                         mapping            x            mapping            x
                  found?                          found?                          found?

                           No                           No                            No

              C Table 1                       C Table 2                        S Table 1                     S
          CONTEXTID                       CONTEXTID                       CONTEXTID                      CONTE
          PROCESSOR_ROLE empty            PROCESSOR_ROLE empty            PROCESSOR_ROLE empty           PROCE
          MSGTY                           ERRORCAT                        MSGTY                          ERROR
          MSGID                           MSGTY                           MSGID                          MSGTY
          MSGNO                                                           MSGNO



          Yes    Message                         Message      Yes                Message      Yes
     x           mapping                         mapping            x            mapping            x
                  found?                          found?                          found?


                       No                               No                            No




The table descriptions in the graphic should be read as follows:

         C Table 1 stands for the table for the view Customer: Message Mapping According to
         Message Type

         C Table 2 stands for the table for the view V_T5ASRMSGMAP2C Customer: Message
         Mapping According to Error Category

         S Table 1 stands for the table for the view V_T5ASRMSGMAP1S SAP: Message
         Mapping According to Message Type

         S Table 2 stands for the table for the view V_T5ASRMSGMAP2S SAP: Message
         Mapping According to Error Category




HR Administrative Services (PA-AS)           6956                                          57
SAP Online Help                                                                  22.04.2009




                    C Table 1
                CONTEXTID
                PROCESSOR_ROLE
                MSGTY
                MSGID         empty
                MSGNO         empty

             This excerpt from the flow chart should be read as follows:
             The system reads the customer settings in the Customizing view
             V_T5ASRMSGMAP1C (Customer: Message Mapping According to Message
             Type) for the entered context, the entered processor role, and the entered
             message type. No values are specified for message ID and message number.


                    This means that the message mapping for the value entered is read.

                    Empty
                    This means that the message mapping will be applied to every message
                    ID and message number.




      Message Mapping Based on Form Scenarios
Use
With the help of this tool, you can replace non-applicable or non-specific system messages
(for example: information, error messages, warnings, success messages, cancellation
messages, and exit messages) with appropriate messages for each scenario. You make the
required settings in Customizing for HR Administrative Services by choosing Configuration of
Forms/Processes        Configuration of Forms    Message Mapping Based on Form Scenarios.
You can find information on general (not form scenario-specific) message mapping under
Message Mapping [Page 56].
Just as in general message mapping, you have several options for message mapping based
on form scenarios:
    Message mapping according to message type, message ID, and message number
    Message mapping according to error category and message type
If no specific discrepant message has been found for a certain form scenarios, then the
system reads the setting for general message mapping. Since form scenarios are only used
within HR Administrative Services, the context HRASR has been pre-defined and does not
need to be entered explicitly.
The following graphic gives you an overview of how the individual customer and standard
customizing settings are read through the system.




HR Administrative Services (PA-AS)          6956                                           58
SAP Online Help                                                                            22.04.2009


                    Start


                   ………


               FSCN Table 1                                      FSCN Table 1
            FORM_SCENARIO                                   FORM_SCENARIO
            PROCESSOR_ROLE                                  PROCESSOR_ROLE empty
            MSGTY                                           MSGTY
            MSGID                                           MSGID             empty
            MSGNO                                           MSGNO             empty



           Yes    Message                                          Message            No
     x            mapping                                          with error
                   found?                                          category?

                            No                                            Yes

               FSCN Table 1                                      FSCN Table 2
            FORM_SCENARIO                                     FORM_SCENARIO
            PROCESSOR_ROLE                                    PROCESSOR_ROLE
            MSGTY                                             ERRORCAT
            MSGID           empty                             MSGTY
            MSGNO           empty



           Yes    Message                                           Message     Yes
     x            mapping                                           mapping                x
                   found?                                            found?

                            No                                            No

               FSCN Table 1                                     FSCN Table 2
          FORM_SCENARIO                                     FORM_SCENARIO
          PROCESSOR_ROLE empty                              PROCESSOR_ROLE empty
          MSGTY                                             ERRORCAT
          MSGID                                             MSGTY
          MSGNO



           Yes    Message                                   Yes     Message           No
     x            Mapping                              x            mapping
                   found?                                            found?


                        No                     Return discrepant                  Call up general
                                                   message                       message mapping




The table descriptions in the graphic should be read as follows:

         FSCN table 1 stands for the table for the view V_T5ASRMSGMAPFS1 Message
         Mapping According to Message Type

         FSCN table 2 stands for the table for the view V_T5ASRMSGMAPFS2 Message
         Mapping According to Error Category




HR Administrative Services (PA-AS)           6956                                                 59
SAP Online Help                                                                    22.04.2009




                   FSCN Table 1
                FORM_SCENARIO
                PROCESSOR_ROLE
                MSGTY
                MSGID           empty
                MSGNO           empty


             This excerpt from the flow chart should be read as follows:
             The system reads the customer settings in the Customizing view
             V_T5ASRMSGMAPFS1 (Message Mapping According to Message Type) for the
             entered form scenario, processor role, and message type. No values are
             specified for message ID and message number.



             This means that the message mapping for the value entered is read.
                Empty
             This means that the message mapping will be applied to every message ID and
             message number.




      Business Workflow for HCM Processes and Forms
Purpose
SAP Business Workflow is the central tool for controlling processes for HCM Processes and
Forms. You use it to specify which process steps should follow in HR processes such as an
employee's hiring, leaving, or organizational reassignment. In addition, you define which
users are to execute each process step, which forms they can edit in the individual steps, and
which interface functions they can execute in the corresponding form application [Page 42].

Features
      The SAP Business Workflow has been designed for HCM Processes and Forms in
      such a way as to minimize the effort involved in setting up your processes in the
      system. For more information, see Special Features of the Workflow for HCM
      Processes and Forms [Page 61].

      A workflow template is provided for each sample process for HCM Processes and
      Forms.
      The workflow templates for depicting HR processes such as hiring or leaving are simply
      examples of how you can map the processes in your enterprise. You should copy them
      and adapt them for your customer-specific workflow templates so that you have all the
      functions related to the application. You can make a few simple changes to depict
      additional processes.



             You should never use the templates that are delivered in the standard system in
             a production system; if you do so, SAP cannot assume responsibility for the
             function and data. We strongly recommend that you use these workflow




HR Administrative Services (PA-AS)          6956                                            60
SAP Online Help                                                                    22.04.2009


             templates only as templates, and that you adjust your copies to suit your
             requirements.
             You can use the workflow templates depicting technical processes, however, in
             the production system.

      Multiple standard workflow objects are provided for setting up your workflow templates;
      these objects fulfill the most popular requirements for processing HR processes:

             Workflow templates with which you can execute purely technical process steps

             Standard tasks that depict editing, approving, and saving the data entered

             Standard tasks that control system actions such as automatically saving data,
             sending e-mails, or sending system messages for the Exchange Infrastructure

             Rules for agent determination with which the suitable processors for a process
             step are determined dynamically



             If you want to change a workflow template, and have already executed a
             process that is based on this workflow template, you must create a new version
             of the workflow template in the Workflow Builder by choosing Workflow
             Generate Version before you change the template. Processes that have already
             been executed thus remained based on the original version of the workflow
             template. Processes that you execute after changing the workflow template use
             the new version of the workflow template.
See also:
HCM Processes and Forms [Page 14]




   Technical Basics for Business Workflow for HCM
Processes & Forms
Use
The tasks involved in the administration of HR master data can be simplified and streamlined
with an appropriate, automated process control. SAP Business Workflow provides a range of
possibilities to refer tasks (such as the creation of special HR master data) to those
employees who are most familiar with this data.
For this reason, SAP Business Workflow is the central component for HCM Processes and
Forms to depict and structure the HR processes. The special architecture of the workflow
objects provided and their relation to the other HCM Processes and Forms components
enable you to set up process variants and new processes quickly and easily.

Features
The SAP Business Workflow controls the following functions in conjunction with the other
HCM Processes and Forms components:

      Workflow Template
      You use workflow templates and form scenarios [Page 37] to map your processes in
      Personnel Administration. In addition to sample form scenarios, predefined demo
      workflow templates are also provided for the most important Personnel Administration
      processes, such as hiring, organizational reassignment, and leaving. These are closely
      linked to the processes and form scenarios also provided in the standard system.



HR Administrative Services (PA-AS)          6956                                           61
SAP Online Help                                                                    22.04.2009


      In addition to the demo workflow templates depicting business processes in the
      enterprise and the agents involved, there are also workflow templates that you can use
      to control technical processes such as handling errors or automatically saving data.

      Standard Tasks
      Specific standard tasks for HCM Processes and Forms are available to map the
      individual business or technical steps in the workflow. You can use them to control the
      work performed in the form application and the functions that are available in each
      process step.

      Agent Assignment
      With the agent assignment rules specific to HCM Process and Forms, you can
      determine the appropriate user for each process step.
      The agent determination rules specify how the system is to determine the agent
      (processor) of a workflow step. These agents then receive a work item in their
      Universal Worklist.



             Alternatively, you can also send an e-mail to an agent. This technique is
             particularly suitable if the agent of a workflow step seldom works with the portal
             or if you cannot provide a universal worklist for the agent. For additional
             information, see the Implementation Guide for HR Administrative Services under
             Configuration of Forms/Processes         Process Configuration    Enhanced
             Messages.
      The standard system already contains some agent determination rules [Page 68].
      You can also use the rules for agent determination to run the authorization checks. The
      authorization checks are run using the authorization objects of HR master data
      authorizations. For more information, see Authorization Concept of HCM Processes
      and Forms [Page 118].


The following diagram illustrates the interaction of the individual SAP Business Workflow
objects with the other HCM Processes and Forms Customizing objects.
Relationship Between Process Steps and Workflow Templates




HR Administrative Services (PA-AS)          6956                                            62
SAP Online Help                                                                    22.04.2009


                                                    Process

                    Process step 1              Process step 2             Process step 3
                   Select     Edit and        Select     Edit and        Select      Edit and
                  process    send form        work      send form        work       send form
   Process                                     item                       item
  execution
                   Start Application            Universal Worklist and Form Application



                                  Custom izing HCM Processes and Forms

   Process
   control         Custom izing for the       Workflow template linked with specific HCM
                    start application            Processes and Forms components




      Special Features of the Workflow Templates
Use
Workflow templates for HCM Processes and Forms have the same meaning as workflow
templates for other applications. You use them to define the flow of a process. In the workflow
steps, you specify what happens when a step is executed, and how the system determines
the agent responsible for a process step. The advantage of the workflow templates for HCM
Processes and Forms is that you create a close link to other HCM Processes and Forms
objects in the workflow objects.

Features
In the workflow templates for HCM Processes and Forms, you must create a close link with
the objects specific to HCM Processes and Forms, such as the form scenario or the process
object, when setting up the workflow.



              If you set up the workflow templates for HCM Processes and Forms to depict the
              processes in your company, you should always take note of how a workflow
              template is linked to other objects, and the subobjects (steps, tasks, agent
              assignment rules, and so on) of the workflow template that are involved.
To facilitate the creation of these links, a wide range of standard workflow objects are
available in which these relationships with other HCM Processes and Forms objects are
already depicted:

      Either exemplary, such as in the demo workflow templates,


HR Administrative Services (PA-AS)           6956                                           63
SAP Online Help                                                                     22.04.2009


      Or as directly usable for your processes in the form of technical workflow templates
      and standard tasks
The workflow templates in HCM Processes and Forms have the following special features:

      Process control
      You use the workflow templates to specify which steps are to be processed by users or
      by the system, and the conditions under which they are processed. In addition, the
      workflow template is integrated with the Start Application [Page 38] and the Form
      Application [Page 42].
      The start application triggers the event that then starts the workflow. The form
      application is called when an interactive workflow step is executed.

      Control of the execution of the workflow steps
      When defining the workflow steps, you specify which functions are to be available in
      the form application. By using certain standard tasks, you specify which views are
      provided in the form application.



                    The Approve Form standard task provides two views: an approval view
                    and a confirmation view.

                    The Edit Form standard task provides three views: a processing view, a
                    check view, and a confirmation view.
      You also specify for each workflow step which functions the user can execute.



             For a workflow step Edit Form, you can decide, for example, whether the
             following buttons can be seen on the form application:

                    Save Draft

                    Back to Author

                    Withdraw Process

                    Send to Expert
      When setting up the workflow steps, you specify which form scenario is used in the
      workflow step. In assigning the form scenario, you have the following options:

             If you run the process using a start application, you specify the required form
             scenario in the Customizing settings for the start application. If you want to
             retain the form scenario of the start application throughout the entire workflow,
             you transfer the form scenario with the container element FORM into the
             workflow container and the individual workflow steps.

             If you want to use more than one form scenario in a process, you can specify
             the required form scenario at the relevant workflow step with the container
             element FORM.

      Control of the agent determination
      The agent determination rules developed especially for HCM Processes and Forms
      enable you not only to determine the correct agent for a process step, but also to run
      authorization checks.
The following graphic shows the elements of the workflow templates to which you can create
links to other HCM Processes and Forms objects.




HR Administrative Services (PA-AS)           6956                                              64
SAP Online Help                                                                 22.04.2009


Links in the Workflow Template to Other HCM Processes and Forms Objects

Name                                        Relationship
Identifier
Name
Workflow Step                               You can use the standard tasks to map the
                                            interactive steps in the process and the
                                            background activities in the system, such as
                                            the processing of data in the backend system.
Workflow Container                          The following container elements are
                                            especially important:

                                                  PROCESS_OBJECT (process object)

                                                  FORM_SCENARIO_STAGE (form
                                                  scenario step)

                                                  PROCSTATE (processing status)

                                                  FORM (form scenario)
                                            For a description of these and other important
                                            container elements, see the documentation for
                                            the standard tasks.
Start Events                                As the start event for all workflow templates,
                                            you use the triggering event TRIGGERED of
                                            the object type
                                            CL_HRASR00_WF_PROCESS_OBJECT.
                                            This event is triggered by the Process Object
                                            [Page 35]. The process object is automatically
                                            created by the system if the user starts the
                                            process using the Start Application [Page 38].
                                            Using the TRIGGERED event, you ensure
                                            that the workflow instances receive the correct
                                            information from the Customizing settings and
                                            the start application.
The following graphic illustrates how the various HCM Processes and Forms components
work together when a process is run, from the point of view of SAP Business Workflow.




HR Administrative Services (PA-AS)        6956                                           65
SAP Online Help                                                                                               22.04.2009


                                                                           Process

                                   P. step 1                           Process step 2                         P. step 3
                                    Edit and          Select                          Edit form                Edit and
                                   send form          work                                                    send form
                                                       item
 Process Execution




                                                                     Form Application
                       Form Application          View :              View :                       View :
                       Views                     Edit                                             Completed
                                                                     Review and Send
                                                  Transfer                                        Data was
                                                                              Transfer
                                                                                                  sent
                                                 Emplo yee: ...      Emplo yee: ...

                       Functions in the form        Save Draft
                       application               Rev iew and Send      Back             Send




                                  Custom izing         Workflow template
     Process Control




                                  of the start
                                  application          WF step for process step 2
                                                        -   Standard task: Edit Form
                                                        - Container elements: Save_Draft: X




See also:
Agent Determination Rules [Page 68]
Authorization Concept of HCM Processes and Forms [Page 118]




                       Special Features of the Standard Tasks
Use
The standard tasks for HCM Processes and Forms are closely linked to the other objects in
HCM Processes and Forms. This means that they can be used to control more functions than
most other standard tasks can.

Features
                       In the standard tasks, all links are already included that the system requires for
                       communicating with the other HCM Processes and Forms components. It is therefore
                       highly recommended that you use these standard tasks when setting up your workflow
                       template.

                       The standard tasks are deliberately of a general nature. This enables you to use
                       identical steps in your workflow templates without having to copy and change the
                       standard tasks for each individual workflow template. This means that you can reuse
                       the same standard tasks for various processes, thereby saving a lot of effort when
                       changes are required.

                       You can use the following task groups to create your own workflow templates:

                             Interactive Components (task group TG17900002)


HR Administrative Services (PA-AS)                                  6956                                              66
SAP Online Help                                                                     22.04.2009


            You can use the tasks in this task group to set up process steps that are
            executed by employees in your enterprise.
            In the relevant standard tasks is stored which views are to be provided in the
            form application.



                   The Approve Form standard task provides two views: an approval view
                   and a confirmation view.

                   The Edit Form standard task provides three views: a processing view, a
                   check view, and a confirmation view.
            The standard tasks already provide in their container all links that you require for
            HCM Processes and Forms. These container elements are transferred to the
            dataflow container of the workflow step when setting up the workflow template.
            In the workflow step, you enter your own values or step-related values. This
            includes the following information, for example:

                   Are special buttons, such as Forward to Expert, displayed in the form
                   application for this process step?

                   Does the system save the data entered in this step to the infotypes?
            The system uses the programming exit CL_HRASR00_POBJ_WF_EXIT
            entered in the workflow step to keep the process object synchronous with the
            workflow and writes the data entered with the interactive components to the
            process object. The programming exit represents the communication between
            the process object and the workflow. You must specify the programming exit for
            all workflow steps in which an agent interactively processes a form.

            Background Components (task group TG17900003)
            You can use the tasks in this task group to set up process steps that the system
            executes in the background. You must use the WF Batch user for this and
            ensure that this user has the necessary authorizations, for example, the
            authorization to update the Personnel Administration and Time Management
            infotypes.



            You can use the background components to execute system activities such as:

                           Check whether the relevant infotype records exist

                           Creation of results that you can use for process modeling



            You are not allowed to specify the programming exit
            CL_HRASR00_POBJ_WF_EXIT for the background components.

      The two task groups are grouped together with the task group TG17900001
      (Components for HCM Processes and Forms). If you transfer this task group into your
      workflow builder, you can access the standard tasks of both groups when creating your
      workflow templates. You can then select the standard tasks in the Workflow Builder
      and drag and drop them to the graphical modeling interface.
See also:

      Task Group TG17900001: Components for HCM Processes and Forms [Page 73]

      Task Group TG17900002: Interactive Components [Page 73]




HR Administrative Services (PA-AS)          6956                                             67
SAP Online Help                                                                    22.04.2009


      Task Group TG17900003: Background Components [Page 107]




      Agent Determination Rules
Definition
The agent determination rules specify for HCM Processes and Forms how the system
determines the agents (processors) of each interactive workflow step at runtime of SAP
Business Workflow.

Use
In the standard system, a range of agent determination rules is available for HCM Processes
and Forms that already fulfill important requirements for the application:

      Determination of the next agent based on HR selection criteria

      Determination of the suitable agent by first checking the agent’s authorizations



              SAP recommends you use the agent determination rules included in the
              standard system for your HCM Processes and Forms workflow templates.

Structure
HCM Processes and Forms provides two types of agent determination rules that you can use
to map your processes:

      Rules that determine the next agent for a process step
      The next agent is determined with these rules based as usual on organizational criteria.
      The standard system contains some rules that determine the next agent using objects
      from SAP Organizational Management or SAP Personnel Administration.

      Rules that run an authorization check
      You can use the ASRAgent rule to initiate an authorization check that ensures that only
      users who have authorization to edit or approve a particular process step receive the
      work item in their worklist. This ensures that users do not receive any work items for
      process steps in which they would have to edit data, for example, and for which they do
      not have change authorization.



                    The authorization checks are based only on authorizations that are
                    checkable at the time the work item was initialized. When processing the
                    work item, it may be necessary to check other authorizations.

      Combination of both types of rules
      If you use the ASRAgent rule on the workflow step in the data flow for the agent
      determination, you can combine the advantages of both types of rules. To do this, you
      enter a rule that determines the next agent for a process step as a subrule of the
      ASRAgent rule. The subrule first determines all potential agents of a process step, for
      example, on the basis of the organizational structure and the data specified in the data
      flow. The ASRAgent rule then filters the agents that have the required authorizations.
Agent Determination Rules for HCM Processes and Forms

  3. Identi      4. Name             5. Function Module                  6. Description



HR Administrative Services (PA-AS)            6956                                          68
SAP Online Help                                                         22.04.2009


     fier
  7. 1790      8. ASRAgent           9. HR_ASR_AGENTFINDER   10. Agent determination
     0012                                                        with authorization
                                                                 check
11. 1790      12. ASROrgOb       13. HR_ASR_ORGANIZATIO      14. Employees
    0013          ject               NAL_OBJECT                  belonging to a
                                                                 specified
                                                                 organizational object
                                                                 type.
                                                             15. This rule delivers all
                                                                 users (object type
                                                                 US) that are
                                                                 assigned to an
                                                                 object type from
                                                                 SAP Organizational
                                                                 Management. The
                                                                 rule processes all
                                                                 object types that are
                                                                 used for agent
                                                                 determination within
                                                                 the framework of the
                                                                 workflow.
                                                             16. SAP Organizational
                                                                 Management is
                                                                 used to determine
                                                                 the users.
17. 1790      18. ASRManag       19. HR_ASR_MANAGER          20. Manager
    0014          er
                                                             21. This rule delivers the
                                                                 manager for a
                                                                 person. The rule
                                                                 processes the object
                                                                 types P (Person). S
                                                                 (Position), O
                                                                 (Organizational
                                                                 Unit), C (Job), and
                                                                 US (User).
                                                             22. SAP Organizational
                                                                 Management is
                                                                 used to determine
                                                                 the users.
23. 1790      24. ASRGrpAd       25. HR_ASR_GROUP_ADMI       26. Administrator Group
    0015          min                NS
                                                             27. This rule delivers the
                                                                 users (object type
                                                                 US) for the
                                                                 administrator group
                                                                 of the relevant
                                                                 person. The rule
                                                                 processes the object
                                                                 types P (Person)
                                                                 and US (User).
                                                             28. SAP Personnel
                                                                 Administration
                                                                 objects are used to
                                                                 determine the users.



HR Administrative Services (PA-AS)        6956                                   69
SAP Online Help                                                     22.04.2009


29. 1790      30. ASRPersA       31. HR_ASR_PERSONNEL_   32. Personnel
    0016          dmin               ADMIN                   Administrator
                                                         33. This rule delivers the
                                                             user (object type
                                                             US) for the
                                                             personnel
                                                             administrator of the
                                                             relevant person. The
                                                             rule processes the
                                                             object types P
                                                             (Person) and US
                                                             (User).
                                                         34. SAP Personnel
                                                             Administration
                                                             objects are used to
                                                             determine the users.
35. 1790      36. ASRTimeA       37. HR_ASR_TIME_ADMIN   38. Time Recording
    0017          dmin                                       Administrator
                                                         39. This rule delivers the
                                                             user (object type
                                                             US) for the time
                                                             recording
                                                             administrator of the
                                                             relevant person. The
                                                             rule processes the
                                                             object types P
                                                             (Person) and US
                                                             (User).
                                                         40. SAP Personnel
                                                             Administration
                                                             objects are used to
                                                             determine the users.
41. 1790      42. ASRPayrA       43. HR_ASR_PAYROLL_AD   44. Payroll Administrator
    0018          dmin               MIN
                                                         45. This rule delivers the
                                                             user (object type
                                                             US) for the payroll
                                                             administrator of the
                                                             relevant person. The
                                                             rule processes the
                                                             object types P
                                                             (Person) and US
                                                             (User).
                                                         46. SAP Personnel
                                                             Administration
                                                             objects are used to
                                                             determine the users.
47. 0400      48. ASR_PD_        49. Responsibilities    50. PD Administrator
    0007          Admin
                                                         51. The processes are
                                                             determined using
                                                             the areas of
                                                             responsibility.
                                                         52. The container
                                                             element
                                                             PROCESS_GROUP


HR Administrative Services (PA-AS)       6956                                70
SAP Online Help                                                                     22.04.2009


                                                                              is available for this.
                                                                         53. SAP Organizational
                                                                             Management is
                                                                             used to determine
                                                                             the users.



             For more information about the individual rules, see the individual objects in the
             Maintain Rules transaction (PFAC) in the system.
             For general information about rule resolution, see the SAP Library and choose
             SAP NetWeaver -> Application Platform -> Business Services -> SAP Business
             Workflow -> Reference Documentation -> Rule Resolution.




      Workflow Templates for Sample Processes
Use
Below is an overview of the workflow templates that we deliver for sample processes in the
standard release. The workflow templates are models, which you can copy and then adjust
the copy to represent your own processes.



             You must never use the originals of the workflow templates in your own
             processes. We accept no responsibility for the completeness and reliability of
             these workflow objects.

Integration
The listed workflow templates are intended for Sample Processes in HCM Processes and
Forms [Page 216].

Prerequisites
You can find the prerequisites for using the sample processes and the underlying workflow
templates in the description of the individual processes.

Features
The following workflow templates (WF templates) are available in the standard system for the
following sample processes:
WF Template             Name of WF              Related WF               Sample Process
                        Template                Template
WS17900011              Hiring an Employee      WS17900415 (Start        Hiring, Permanent
                        (DE)                    Process for XI Data)     (Germany) [Page
                                                                         217]
                                                WS17900015
                                                (Follow-Up Activities
                                                after Process with XI
                                                Scenario)
WS18900008              New Hire,               WS17900415 (Start        Hiring (US) [Page
                        Permanent (US)          Process for XI Data)     220]
                                                WS17900015
                                                (Follow-Up Activities
                                                after Process with XI


HR Administrative Services (PA-AS)           6956                                             71
SAP Online Help                                                                 22.04.2009


                                              Scenario)
WS61000081            Rehire DE (HRASR        WS17900415 (Start      Rehire (Germany)
                      Rehire, SRD)            Process for XI Data)   [Page 224]
WS61000091            Rehire US Forms         WS17900415 (Start      Rehire (US) [Page
                      and Processes           Process for XI Data)   228]
WS17900427            Transfer                                       Transfer
                                                                     (International) [Page
                                                                     232]
WS61000088            Transfer 2              WS17900415 (Start      Transfer, Initiated by
                                              Process for XI Data)   E-Recruiting
                                                                     (International) [Page
                                                                     236]
WS17900366            Maternity Leave                                Maternity Leave
                                                                     (Germany) [Page
                                                                     239]
WS17900367            Birth of a Child                               Birth of a Child
                                                                     (Germany) [Page
                                                                     241]
WS17900013            Birth of Child (US)                            Birth of Child (US)
                                                                     [Page 243]
WS61000080            Change Salary 1                                Salary Change Using
                                                                     Annual Salary
                                                                     (International) [Page
                                                                     245]
WS61000079            Change Salary 2                                Salary Change Using
                                                                     Pay Scale Wage
                                                                     Group and Level
                                                                     (International) [Page
                                                                     247]
WS61000073            Special Payment -1                             Special Payment
                      (XX)                                           (International) [Page
                                                                     250]
WS61000078            Special Payment -2                             Special Payment
                      (XX)                                           Without Personnel
                                                                     Department
                                                                     (International) [Page
                                                                     253]
WS61000074            Change to Working                              Change to Working
                      Time (XX)                                      Time (International)
                                                                     [Page 256]
WS61000075            Change to                                      Change of Address
                      Permanent                                      (US) [Page 259]
                      Residence (US)
WS61000077            Company Loan (XX)                              Company Loan
                                                                     (International) [Page
                                                                     261]
WS61000076            Membership Fees                                Membership Fees
                      (XX)                                           Sports Club
                                                                     (International) [Page
                                                                     263]




HR Administrative Services (PA-AS)          6956                                           72
SAP Online Help                                                                       22.04.2009


WS17900391               Termination (DE)                                  Termination
                                                                           (Germany) [Page
                                                                           265]
WS18900010               Termination (US)                                  Termination (US)
                                                                           [Page 268]




      Standard Tasks
The following section describes the standard tasks and agent determination rules that you
can use to create your own workflow templates.
You can use the originals of the following objects.




   Task Group TG17900001: Components for HCM
Processes & Forms
This task group contains all the tasks groups for HCM Processes and Forms. You can use it
so that you have all standard tasks for HCM Processes and Forms available when creating
your workflow templates.
This task group does not have any standard tasks of its own. It contains the following task
groups:

       Task group TG17900002: Interactive Components

       Task group TG17900003: Background Components




      Task Group TG17900002: Interactive Components
Use
The standard tasks of the TG17900002 task group (Interactive Components) create work
items while a process is running. These work items notify an HR administrator, manager, or
employee that he or she has a task that requires processing. They are made available to
users in the universal worklist in the portal. When a user executes a work item, the system
calls up the relevant form application in the portal, in which the user can edit or approve the
required form.




      Standard Task TS17900100: Edit Form
Definition
You can use this standard task to create a workflow step to enable users to edit a form, for
example, a workflow step to create or correct data. Executing a work item calls up a form
application [Page 42] in which users can edit the form of a form scenario in the portal. You
can additionally define the following:


HR Administrative Services (PA-AS)            6956                                                73
SAP Online Help                                                                    22.04.2009


       Provide functions such as Save Draft or Withdraw Process. They are optional
       elements that you can have in the form application.

       Specify where data is to be saved. You can decide whether the data is to be saved
       directly to the database of the backend system (to update infotypes, for example) as
       well as in the process object.


Standard Task: 17900100
ID: Edit
Name: Edit Form



Structure
Authorization Check
For the authorization object P_ASRCONT, the activity P (Process) is used for the
authorization check.
For more information, see Authorization Concept of HCM Processes and Forms [Page 118].

User Interface Control
When a user accesses a work item that is executed with this task, a form application is called.
It has the following three views:

       Edit
      In this view, the users can display, enter, and change data in the form. They can carry
      out the following actions, provided that you specify in this (Personnel Administration)
      PA-specific task that the relevant buttons are made available:

              Save Draft

              Back to Author

              Withdraw Process

              Send to Expert

              Next
      Depending on the settings, the agent will be able to see the Review and Send button or
      the Next button. By choosing either of these buttons, the user goes to the next view.
      The system first checks the data. Depending on your settings in the container elements
      SEND_VARIATION and SEND_EXPERT_IF_INCONSTENT, the user can, for
      example, complete the work item even if the data is incorrect or send the data to an
      expert for error handling.

       Review and Send
      In this view, the user can check the data entered and complete the editing of the form
      by choosing the Send button. The system sends the data entered asynchronously to
      the backend system. It sets the status of the work item to Completed and continues
      with the next step in the workflow.

       Completed
      The user receives a confirmation that the data has been sent successfully. The work
      item disappears from the user's universal worklist.
The following graphic illustrates these user interface elements:



HR Administrative Services (PA-AS)           6956                                              74
SAP Online Help                                                                         22.04.2009




         Edit                         Rev iew and Send          Completed

    Show Ag ents Inv olv ed                    Show Link List


         Process Reference Number 000000002635                  Phase




            Valid from


        Personn el
        number


         First Name      Paul



         Last Name       Schneider




      Sav eeDraft
       Sav Draft                     Back to Author
                                      Back to Author            Withdraw Process
                                                                Withdraw Process


         Back
          Back                       Rev iew and Send
                                      Rev iew and Send             Next
                                                                    Next




Process Control
In the container definition, you can define the following types of container elements:

       Container elements that control which form scenario is used with which scenario step
       when the task is executed

       Container elements that control which of the optional functions are made available
       when the task is executed
If you use this task, you must also do the following tasks in the relevant workflow step:

       Data flow of task container

       Rule for agent determination with respective data flow to rule container

       Programming exit CL_HRASR00_POBJ_WF_EXIT


Data Flow: Import Elements

       Form (FORM) – Mandatory
      This element specifies which form scenario is used when the workflow step is
      executed. It consists of a structure with the following fields, which you have to define for
      use with this task:

                     Form Scenario (FORM_SCENARIO)
                 Enter the form scenario that is to be used within the workflow step.


HR Administrative Services (PA-AS)                       6956                                  75
SAP Online Help                                                                    22.04.2009


            FormScenario Version (FORM_SCENARIO_VERSION)
            Enter the version of the form scenario that you want to use.

            Do Not Save Directly (SUPPRESS_SAVE)
            You can use this field to override the value of the SEND_VARIATION element.
            You can use this field to control subworkflows, for example.

                   Enter an X if you do not want the data to be written to the infotypes in
                   the database of the backend system. This setting is valid even if the
                   value A (Check and Save) has been set in the SEND_VARIATION
                   element.

                   Enter nothing if the data is to be saved according to the settings in the
                   SEND_VARIATION element.
     Data type (type name on the Data Type tab page in the ABAP Dictionary Data Type
     field): HRASR00_FORM_KEY_ELEMENT

      Form Scenario View (FORM_SCENARIO_STAGE) – Mandatory
     Enter the scenario step that is to be used for the workflow step. You must have already
     defined the step in the Create Form Scenario IMG activity (view cluster
     HRASR00FSCN).
     When defining the data flow in the workflow container, you can use a value help (F4)
     for the FORM_SCENARIO_STAGE field. This allows you to access your Customizing
     entries. You can use the value help in the Workflow column and, in the subsequent
     dialog box, the value help for the field in the Temporary Check Results of Table
     column. If the column is not visible, you can use the Enter Constant function.
     Data type (Data Type tab page, ABAP Dictionary Reference field): Structure
     HRASR00_PROCESS_MODELLING and Field FORM_SCENARIO_STAGE
      Processor role (PROCESSOR_ROLE) – Optional
     Here you enter the role of the processor who generally executes the workflow step. If
     you do not specify a processor role, the HR Administrator (HRASRA) processor role is
     assigned in the standard release. It is necessary to enter the processor role, for
     example, for Data Tracking [External] at the process-step level and for Message
     Mapping [Page 56].
     For more information, see the Implementation Guide (IMG) for HR Administrative
     Services under Configuration of Forms/Processes    Process Configuration     Set Up
     Processes     Determine Processor Roles.
     Data type (Data Type tab page, ABAP Dictionary Reference field): Structure
     HRASR00_PROCESS_MODELLING and Field PROCESSOR_ROLE
      Send Variant (SEND_VARIATION) – Optional
     You can use this element to specify how you want the system to proceed when
     executing the Review and Send or Send functions. The element specifies:

            Whether the data is saved in the infotypes in the backend system

            Whether the user processing the work item can complete the work item, even if
            error messages were issued in the backend system due to inconsistent data



            When a user executes a work item, the system checks the data in the form
            against the business logic for the fields that you have linked to the form fields
            when configuring the form. These checks can cause error messages in various
            categories, such as insufficient authorization, collisions between data records, or


HR Administrative Services (PA-AS)          6956                                               76
SAP Online Help                                                                   22.04.2009


            incorrect or inconsistent data. For more information, see Error Handling [Page
            124].
     The following values are possible:

            BLANK = Do not save (do not tolerate errors)
            This is the default parameter. The system checks the data against the business
            logic in the backend system, meaning it checks the data entered. The user must
            resolve the error before he or she can complete the work item. To do this, the
            user can request the help from an expert who then returns the work item to the
            user. When the user has completed the work item, the data is not written to the
            backend system's database.

            B = Do not save (tolerate errors)
            The data is checked in the backend system. If error messages occur due to
            inconsistent data, the system can tolerate these messages and dynamically
            provide the user with the Next function. When the user has completed the work
            item, the data is not written to the backend system's database. The work item is
            sent to the next agent.
            This setting is useful if an expert, such as an HR administrator, performs a
            workflow step following this step. The user can complete the work item even if
            the entered data is inconsistent.



            Errors that did not occur due to inconsistent data are not tolerated in this
            procedure (for example, missing authorizations). When theses errors occur, the
            system dynamically shows the Send to Expert button in the form application and
            automatically controls the further processing through an expert.
            Note the interaction of the SEND_VARIATION and
            SEND_EXPERT_IF_INCONSISTENT elements here.

            A = Save (do not tolerate errors)
            The data is checked against the business logic in the backend system and
            written to the infotypes in the backend system. Error messages are not
            tolerated; users have to have entered all data correctly before they can continue
            editing the form. The user can request an expert's help for this.



            If a work item is completed with SEND_VARIATION = A, the system also saves
            any process steps that were entered in previous steps but not yet saved in the
            backend system. If this setting is made, you therefore have to ensure that the
            user in a particular step is also able to correct incorrect data entered by other
            users. The corresponding fields must therefore be visible and modifiable in the
            form.


     Data type (Data Type tab page, ABAP Dictionary Reference field): Structure
     HRASR00_PROCESS_MODELLING and Field SEND_VARIATION


      Save Draft button (SAVE_DRAFT_BUTTON_VISIBLE) – Optional
     You use this element to specify whether a button is provided to the user to temporarily
     save the entries in the form. Once the user has temporarily saved the data and the step
     is not yet completed, the corresponding work item continues to be available to the user
     in the universal worklist for processing with all previously entered data.

            X = Save Draft button is visible


HR Administrative Services (PA-AS)         6956                                              77
SAP Online Help                                                                     22.04.2009


            The user can save the current processing status of the form using the Save
            Draft button.

            BLANK = Not visible
            The Save Draft button is not visible and is therefore not available to the user
            (default setting).
     Data type (Data Type tab page, ABAP Dictionary Reference field): Structure
     HRASR00_PROCESS_MODELLING and Field BUTTON_IS_ENABLED
      Back to Author button (BACK_BUTTON_VISIBLE) – Optional
     You use this element to specify whether a button is provided to the user to return a
     form to the initiator of a process.

            X = Back to Author button is visible
            The user can return the form to the initiator by choosing the Back to Author
            button. In this case, the processing status (PROCSTATE, see below) receives
            the value BACK.
            Note that you must take account of this behavior in subsequent modeling of the
            workflow.

            BLANK = Not visible
            The Back to Author button is not visible and is therefore not available to the user
            (default setting).
     Data type (Data Type tab page, ABAP Dictionary Reference field): Structure
     HRASR00_PROCESS_MODELLING and field BUTTON_IS_ENABLED
      Process Cancelation button (WITHDRAW_PROCESS_BUTTON_VISIBLE) – Optional
     You use this element to specify whether a user can withdraw a process. Withdrawing a
     process has the following effects:

            The entire process is stopped.

            All work items in the relevant workflow steps and workflow template that are not
            completed receive the status Cancelled.

            The process object is assigned the status Withdrawn.

            All open work items disappear from the universal worklists of all involved in the
            process.



            The withdrawal of a process triggers a workflow of its own. For more
            information, see the Implementation Guide (IMG) for HR Administrative Services
            under Configuration of Forms/Processes      Process Configuration     Technical
            Settings    Settings for Standard Components and Workflows       Activate
            Workflow After Withdrawing Process.
     The element can have the following properties:

            BLANK = Not visible (button not visible)
            The Process Cancelation button is not visible and is therefore not available to
            the user (default setting).

            ALWAYS = Visible (button visible and active, even after saving to backend
            system)




HR Administrative Services (PA-AS)           6956                                             78
SAP Online Help                                                                   22.04.2009


            The Process Cancelation button is always available. The user can cancel the
            entire process.



            You can use this setting to cancel a process even if data has already been
            saved in the infotypes. Note that this can affect your dataset.

            IF_NO_SAVE = Visible before save (button is visible and active until saving to
            the backend system)
            The Process Cancelation button is only available to users while the recorded
            data has not yet been saved in the backend system.
     Data type (Data Type tab page, ABAP Dictionary Reference field): Structure
     HRASR00_PROCESS_MODELLING and Field
     WITHDRAW_BUTTON_VISIBLE
      Expert button (SEND_EXPERT_IF_INCONSISTENT) – Optional
     Users who are not experts at entering personnel data can encounter insolvable
     problems if error messages occur due to inconsistent data. For this reason, you should
     allow the system to dynamically show the Send to Expert button in the form application
     when such errors occur and if no suitable agent can correct the errors in the workflow
     step that follows.



            Note the description of the SEND_VARIATION element. For more information,
            see Error Handling [Page 124].

            X = Send to Expert button is visible
            The Send to Expert button is dynamically displayed if error messages occur due
            to inconsistent data.



            If you specify SEND_EXPERT_IF_INCONSISTENT = X together with
            SEND_VARIATION (Send Variant) = B, the behavior of
            SEND_EXPERT_IF_INCONSISTENT overrides that of SEND_VARIATION.
            This means that if the agent receives error messages due to inconsistent data,
            he or she cannot complete the work item. The agent must either correct the
            entered data or send the work item to an expert.
            The interaction between SEND_EXPERT_IF_INCONSISTENT and
            SEND_VARIATION is only relevant for errors in the Inconsistent Data error
            category. The system always provides the Send to Expert pushbutton for errors
            of the following error categories, even if you have set
            SEND_EXPERT_IF_INCONSISTENT = BLANK:

                   Data Collision

                   No Authorization

                   Object Is Locked (for background steps only)

                   Incorrect Customizing
            For this reason, a user who receives error messages due to inconsistent data
            can only complete the work item under the following conditions:

                   He or she corrects the data entered.

                   He or she forwards the work item to an expert.



HR Administrative Services (PA-AS)         6956                                            79
SAP Online Help                                                                    22.04.2009


            BLANK = Not visible
            The Send to Expert button is not visible and is therefore not available to the user
            (default setting).


     Data type (Data Type tab page, ABAP Dictionary Reference field): Structure
     HRASR00_PROCESS_MODELLING and Field BUTTON_IS_ENABLED


Container Definition: Export Elements

      Processing Status (PROCSTATE) – Optional
     You can use this element to specify that the processing status is to be transferred from
     the workflow step to the workflow container once the work item is completed (data flow:
     workflow <- Edit Form step). If the processing status is known in the workflow
     container, you can process the other workflow steps in accordance with the processing
     status.




            A workflow step for editing a form can be completed with the processing status
            PROCESSED or BACK.

                          If the work item is completed with the PROCESSED status, the
                          next workflow step should be carried out by an HR administrator.

                          If the work item is completed with the BACK status, the next
                          workflow step should be carried out by the person who initiated
                          the process.
            You model the following workflow steps depending on the processing status.


     To transfer the processing status to the workflow container, you must have previously
     created a suitable container element in the workflow container:

            For example, element = PROCSTATE

            For example, name = processing status

            Data type (Data Type tab page, ABAP Dictionary Reference field): Structure
            HRASR00_PROCESS_MODELLING and Field PROCESSING_STATUS
     The processing status can have the following values:

            PROCESSED
            The work item was processed successfully. The user has chosen the Send
            function in the view of the form application Review and Send.

            BACK
            The user has chosen the Back to Author function.

            ERROR
            An error occurred in executing the work item. This status is possible only if you
            entered B for the SEND_VARIATION element.




HR Administrative Services (PA-AS)          6956                                            80
SAP Online Help                                                                      22.04.2009




             For withdrawn processes, you no longer have to react to a processing status in
             the workflow. There is therefore no processing status for Withdrawn.

      Container element notify_via_e-mail - Optional
      You use this container element to specify whether an e-mail notification is sent to the
      next agent involved in a process. If e-mail notification is set to “X” = TRUE, an e-mail is
      sent to the agent, advising them that there is a work item waiting to be processed. They
      can access the work item directly from the body of the e-mail. If it is set to “_” = FALSE,
      no e-mail is sent; the agent can access work items to be processed in the UWL.

      Container element BUSINESS_STATUS - Optional
      You use this container element to specify whether the business status is visible to the
      user in the process browser. If business status is set to “X” = TRUE, you can see the
      business status for the request step. If it is set to “_” = FALSE, only the processing
      status is displayed; the business status cannot be seen.




      Standard Task TS17900101: Approve Form
Definition
You use this standard task to send a form to a user for approval. The approver can execute
the following functions in the relevant form application:

      Approve or reject the content of the form. The approver cannot change the content of
      the form.

      Return the form to the process initiator (optional)

      Save a draft (optional)



             When a user executes this (Personnel Administration) PA-specific task, the data
             is not saved in the back-end system.


Standard Task: 17900101
ID: Approve
Name: Approve Form



Structure

Processor Assignment
You can use this PA-specific task for all HCM Processes and Forms workflow templates, and
store a corresponding agent assignment rule for the workflow steps.
For more information, see Agent Assignment Rules [Page 68].




HR Administrative Services (PA-AS)           6956                                             81
SAP Online Help                                                                       22.04.2009


Authorization Check
The A (Approve) activity is used for the P_ASRCONT authorization object.
For more information, see Authorization Concept of HCM Processes and Forms [Page 118].

User Interface Control
When you initiate a work item with this task, a form application with the following views is
available:

       Approve

       Completed
When the corresponding work item is executed, the following elements are available on the
user interface:

       A form in which the user can check data. The user cannot edit the data.

       Approve and Reject buttons, which the user can choose to complete the processing of
       the form. The data is then sent to the workflow environment and the system continues
       with the next step in the workflow.

       Save Draft and Back to Author buttons (optional)

Process Control
If you use this task, you must also do the following tasks in the relevant workflow step:

       Data flow of task container

       Rule for agent determination with respective data flow to rule container

       Programming exit CL_HRASR00_POBJ_WF_EXIT


Container Definition: Import Elements

       Form (FORM) – Mandatory
      This element specifies which form scenario is used when the workflow step is
      executed. It consists of a structure with the following fields, which you have to define for
      use with this task:

              Form Scenario (FORM_SCENARIO) – Mandatory
             Enter the form scenario that is to be used within the workflow step.

              FormScenario Version (FORM_SCENARIO_VERSION) – Mandatory
             Enter the version of the form scenario that you want to be used.

              Do Not Save Directly (SUPPRESS_SAVE) - Mandatory
             You can use this field to override the entries in the SEND_VARIATION element.

                     Enter an X if the data is not to be written to the database even if the
                     value A (Save (Do Not Tolerate Errors)) is set in the SEND_VARIATION
                     element.

                     Enter nothing if the data is to be saved according to the settings in the
                     SEND_VARIATION element.
      Data type (Data Type tab page in the ABAP Dictionary Data Type field): Type name
      HRASR00_FORM_KEY_ELEMENT
       Form Scenario View (FORM_SCENARIO_STAGE) - Mandatory


HR Administrative Services (PA-AS)            6956                                               82
SAP Online Help                                                                     22.04.2009


     Enter the scenario step that is to be used for the workflow step. You must have already
     defined the step in the Create Form Scenario IMG activity (view cluster
     HRASR00FSCN).
     When defining the data flow in the workflow container, you can use a value help (F4)
     for the FORM_SCENARIO_STAGE field. This allows you to access your Customizing
     entries. You can use the value help in the Workflow column and, in the subsequent
     dialog box, the value help for the field in the Temporary Check Results of Table
     column. If the column is not visible, you can use the Enter Constant function.
     Data type (Data Type tab page, ABAP Dictionary Reference field): Structure
     HRASR00_PROCESS_MODELLING and field FORM_SCENARIO_STAGE
      Processor role (PROCESSOR_ROLE) – Optional
     Here you enter the role of the processor who generally executes the workflow step. If
     you do not specify a processor role, the HR Administrator (HRASRA) processor role is
     assigned in the standard release. It is necessary to enter the processor role, for
     example, for Data Tracking [External] at the process-step level and for Message
     Mapping [Page 56].
     For more information, see the Implementation Guide (IMG) for HR Administrative
     Services under Configuration of Forms/Processes    Process Configuration     Set Up
     Processes     Determine Processor Roles.
     Data type (Data Type tab page, ABAP Dictionary Reference field): Structure
     HRASR00_PROCESS_MODELLING and field PROCESSOR_ROLE
      Save Draft button (SAVE_DRAFT_BUTTON_VISIBLE) – Optional
     You use this element to specify whether a button is provided to the user to temporarily
     save the entries in the form. Once the user has temporarily saved the data and the step
     is not yet completed, the corresponding work item continues to be available to the user
     in the universal worklist for processing with all previously entered data.

            X = Save Draft button is visible
            The user can save the current processing status of the form using the Save
            Draft button.

            " " = Not visible
            The Save Draft button is not visible and is therefore not available to the user
            (default setting).
     Data type (Data Type tab page, ABAP Dictionary Reference field): Structure
     HRASR00_PROCESS_MODELLING and Field BUTTON_IS_ENABLED
      Back button (BACK_BUTTON_VISIBLE) – Optional
     You use this element to specify whether a button is provided to the user to return a
     form to the initiator of a process.

            X = Back to Author button is visible
            The user can return the form to the initiator by choosing the Back to Author
            button. In this case, the processing status (PROCSTATE, see below) receives
            the value BACK.
            Note that you must take account of this behavior in subsequent modeling of the
            workflow.

            BLANK = Not visible
            The Back to Author button is not visible and is therefore not available to the user
            (default setting).




HR Administrative Services (PA-AS)          6956                                              83
SAP Online Help                                                                      22.04.2009


      Data type (Data Type tab page, ABAP Dictionary Reference field): Structure
      HRASR00_PROCESS_MODELLING and field BUTTON_IS_ENABLED
Container Definition: Export Elements

      Processing Status (PROCSTATE) – Optional
      You can use this element to specify that the processing status is to be transferred from
      the workflow step to the workflow container once the work item is completed (data flow:
      workflow <- Edit Form step). If the processing status is known in the workflow
      container, you can process the other workflow steps in accordance with the processing
      status.
      The processing status can have the following values:

             APPROVED
             This value is set when the user has chosen the Approve function.

             REJECTED
             This value is set when the user has chosen the Reject function.

             BACK
             This value is set when the user has chosen the Back to Author function.
      To transfer the processing status to the workflow container, you must have previously
      created a suitable container element in the workflow container:

             For example, element = PROCSTATE

             For example, name = processing status

             Data type (Data Type tab page, ABAP Dictionary Reference field): Structure
             HRASR00_PROCESS_MODELLING and field PROCESSING_STATUS


      Container element notify_via_e-mail - Optional
      You use this container element to specify whether an e-mail notification is sent to the
      next agent involved in a process. If e-mail notification is set to “X” = TRUE, an e-mail is
      sent to the agent, advising them that there is a work item waiting to be processed. They
      can access the work item directly from the body of the e-mail. If it is set to “_” = FALSE,
      no e-mail is sent; the agent can access work items to be processed in the UWL.

      Container element BUSINESS_STATUS - Optional
      You use this container element to specify whether the business status is visible to the
      user in the process browser. If business status is set to “X” = TRUE, you can see the
      business status for the request step. If it is set to “_” = FALSE, only the processing
      status is displayed; the business status cannot be seen.




   Standard Task TS17900102: Form Is Edited Again
by Author
Definition
You can use this standard task to return a form to a user to edit another time. With this
standard task, the user receives a returned form that he or she has already edited. This task
is triggered in the following conditions:



HR Administrative Services (PA-AS)           6956                                             84
SAP Online Help                                                                    22.04.2009


      When a user of the form chooses the Back to Author function in the form application

      If the workflow is modeled according to the related workflow step for the processing
      status (PROCSTATE) BACK.
This (Personnel Administration) PA-specific task generally corresponds to the Edit Form task.
The differences are:

      The values of the processing statuses that are output are different (see below).

      The Back to Author function is not available in the form application.
For more information, see the documentation on Standard Task TS17900100: Edit Form
[Page 73].


Standard Task: 17900102
ID: Return Form
Name: Form Is Edited Again by Author



Structure
Processor Assignment
You can use this PA-specific task for all HCM Processes and Forms workflow templates, and
store a corresponding agent assignment rule for the workflow steps. When using this task,
make sure that the same user who first edited the form receives the work item.
For more information, see Agent Assignment Rules [Page 68].

Authorization Check
The P (Process) activity is used for the P_ASRCONT authorization object.
For more information, see Authorization Concept of HCM Processes and Forms [Page 118].

User Interface Control
See the documentation for the PA-specific task Edit Form.

Process Control
Container Definition: Import Elements

      Processor role (PROCESSOR_ROLE) – Optional
      Here you enter the role of the processor who generally executes the workflow step. If
      you do not specify a processor role, the HR Administrator (HRASRA) processor role is
      assigned in the standard release. It is necessary to enter the processor role, for
      example, for Data Tracking [External] at the process-step level and for Message
      Mapping [Page 56].
      For more information, see the Implementation Guide (IMG) for HR Administrative
      Services under Configuration of Forms/Processes    Process Configuration     Set Up
      Processes     Determine Processor Roles.
      Data type (Data Type tab page, ABAP Dictionary Reference field): Structure
      HRASR00_PROCESS_MODELLING and field PROCESSOR_ROLE
Container Definition: Export Elements




HR Administrative Services (PA-AS)          6956                                             85
SAP Online Help                                                                      22.04.2009




             The configuration options in the binding editor are identical to the task
             TS17900100: Edit Form. Only the PROCSTATE element returns different
             values.

       Processing Status (PROCSTATE) – Optional
      You can use this element to specify that the processing status is to be transferred from
      the workflow step to the workflow container once the work item is completed (workflow
      binding <- Form Is Edited Again by Author step). If the processing status is known in
      the workflow container, you can process the other workflow steps in accordance with
      the processing status.
      The processing status can have the following value:

              RESENT
             The work item was processed successfully. The user has chosen the Send
             function in the Review and Send view of the form application.



             Note that you control the subsequent workflow steps, such as those for
             approving the form, on the basis of the Sent Back processing status. This is
             necessary so that you can differentiate subsequent process steps from those
             resulting from the first editing.
      Data type (Data Type tab page, ABAP Dictionary Reference field): Structure
      HRASR00_PROCESS_MODELLING and Field PROCESSING_STATUS


       Container element notify_via_e-mail - Optional
      You use this container element to specify whether an e-mail notification is sent to the
      next agent involved in a process. If e-mail notification is set to “X” = TRUE, an e-mail is
      sent to the agent, advising them that there is a work item waiting to be processed. They
      can access the work item directly from the body of the e-mail. If it is set to “_” = FALSE,
      no e-mail is sent; the agent can access work items to be processed in the UWL.

       Container element BUSINESS_STATUS - Optional
      You use this container element to specify whether the business status is visible to the
      user in the process browser. If business status is set to “X” = TRUE, you can see the
      business status for the request step. If it is set to “_” = FALSE, only the processing
      status is displayed; the business status cannot be seen.




     Standard Task TS04000018: Process PD Form

You can use this standard task to create a workflow step to enable users to edit a form in an
organizational process, for example, a workflow step to create or correct data. Executing a
work item calls up a form application in which users can edit the form of a form scenario in the
portal. You can additionally define the following:

        Provide functions such as Save Draft or Forward to Expert. They are optional
        elements that you can have in the form application.




HR Administrative Services (PA-AS)           6956                                             86
SAP Online Help                                                                      22.04.2009


        Specify where data is to be saved. You can decide whether the data is to be saved
        directly to the database of the back-end system (to update infotypes, for example) as
        well as in the process object.

Standard Task: 04000018

ID: Process

Name: Process PD (Personnel Development) Form

Structure
Authorization Check
For the authorization object P_ASRCONT, the activity P (Process) is used for the
authorization check. For more information, see Authorization Concept of HCM Processes and
Forms.

User Interface Control
When a user accesses a work item that is executed with this task, a form application is called.
It has the following three views:

        Edit

        In this view, the users can display, enter, and change data in the form. They can carry
        out the following actions, provided that you specify in this standard task that the
        relevant buttons are made available:

               o   Save Draft

               o   Back to Author

               o   Withdraw Process

               o   Send to Expert

               o   Next

        Depending on the settings, the agent can see the Review and Send button or the
        Next button. By choosing either of these buttons, the user goes to the next view. The
        system first checks the data. Depending on your settings in the container elements
        SEND_VARIATION and SEND_EXPERT_IF_INCONSTENT, the user can, for
        example, complete the work item even if the data is incorrect or send the data to an
        expert for error handling.

        Review and Send

        In this view, the user can check the data entered and complete the editing of the form
        by choosing the Send button. The system sends the data entered asynchronously to
        the back-end system. It sets the status of the work item to Completed and continues
        with the next step in the workflow.

        Completed

        The user receives a confirmation that the data has been sent successfully. The work
        item disappears from the user's Universal Worklist.

Process Control
In the container definition, you can define the following types of container elements:




HR Administrative Services (PA-AS)            6956                                          87
SAP Online Help                                                                        22.04.2009


        Container elements that control which form scenario is used with which scenario step
        when the task is executed

        Container elements that control which of the optional functions are made available
        when the task is executed

If you use this task, you must also do the following tasks in the relevant workflow step:

        Data flow of task container

        Rule for agent determination with respective data flow to rule container

        Programming exit CL_HRASR00_POBJ_WF_EXIT

Data Flow: Import Elements

        Form (FORM) – Mandatory

        This element specifies which form scenario is used when the workflow step is
        executed. It consists of a structure with the following fields, which you have to define
        for use with this task:

            o   Form Scenario (FORM_SCENARIO)

                Enter the form scenario that is to be used within the workflow step.

            o   Form Scenario Version (FORM_SCENARIO_VERSION)

                Enter the version of the form scenario that you want to use.

            o   Do Not Save Directly (SUPPRESS_SAVE)

                You can use this field to override the value of the SEND_VARIATION
                element. You can use this field to control subworkflows, for example:

                         Enter an X if you do not want the data to be written to the infotypes in
                         the database of the back-end system. This setting is valid even if the
                         value A (Check and Save) has been set in the SEND_VARIATION
                         element.

                         Enter nothing if the data is to be saved according to the settings in
                         the SEND_VARIATION element.

        Data type (type name on the Data Type tab page in the ABAP Dictionary Data Type
        field): HRASR00_FORM_KEY_ELEMENT

        Form Scenario View (FORM_SCENARIO_STAGE) – Mandatory

        Enter the scenario step that is to be used for the workflow step. You must have
        already defined the step in the Create Form Scenario Customizing activity (view
        cluster HRASR00FSCN).

        When defining the data flow in the workflow container, you can use a value help (F4)
        for the FORM_SCENARIO_STAGE field. This allows you to access your Customizing
        entries. You can use the value help in the Workflow column and, in the subsequent
        dialog box, the value help for the field in the Temporary Check Results of Table
        column. If the column is not visible, you can use the Enter Constant function.

        Data type (Data Type tab page, ABAP Dictionary Reference field): Structure
        HRASR00_PROCESS_MODELLING and Field FORM_SCENARIO_STAGE

        Processor role (PROCESSOR_ROLE) – Optional Here you enter the role of the
        processor who executes the workflow step. If you do not specify a processor role, the


HR Administrative Services (PA-AS)            6956                                               88
SAP Online Help                                                                      22.04.2009


       HR Administrator (HRASRA) processor role is assigned in the standard release. It is
       necessary to enter the processor role, for example, for Data Tracking at the process-
       step level and for Message Mapping.

       For more information, see Customizing for Personnel Management under HR
       Administrative Services Configuration of Forms/Processes Process Configuration
         Set Up Processes Determine Processor Roles. .

       Data type (Data Type tab page, ABAP Dictionary Reference field): Structure
       HRASR00_PROCESS_MODELLING and Field PROCESSOR_ROLE

       Send Variant (SEND_VARIATION) – Optional

       You can use this element to specify how you want the system to proceed when
       executing the Review and Send or Send functions. The element specifies:

           o   Whether the data is saved in the infotypes in the back-end system

           o   Whether the user processing the work item can complete the work item, even
               if error messages were issued in the back-end system due to inconsistent
               data

                   Note

               When a user executes a work item, the system checks the data in the form
               against the business logic for the fields that you have linked to the form fields
               when configuring the form. These checks can cause error messages in
               various categories, such as insufficient authorization, collisions between data
               records, or incorrect or inconsistent data. For more information, see Error
               Handling.


       The following values are possible:

           o   BLANK = Do not save (do not tolerate errors)

               This is the default parameter. The system checks the data against the
               business logic in the back-end system, meaning it checks the data entered.
               The user must resolve the error before he or she can complete the work item.
               To do this, the user can request the help from an expert who then returns the
               work item to the user. When the user has completed the work item, the data
               is not written to the back-end system's database.

           o   B = Do not save (tolerate errors)

               The data is checked automatically in the back-end system. If error messages
               occur due to inconsistent data, the system can tolerate these messages and
               dynamically provide the user with the Next function. When the user has
               completed the work item, the data is not written to the back-end system's
               database. The work item is sent to the next agent.

               This setting is useful if an expert, such as an HR administrator, performs a
               workflow step following this step. The user can complete the work item even
               if the entered data is inconsistent.

                   Note

               Only errors that occur due to inconsistent data are tolerated in this procedure
               (for example, missing authorizations). When theses errors occur, the system




HR Administrative Services (PA-AS)          6956                                              89
SAP Online Help                                                                      22.04.2009


               dynamically shows the Send to Expert button in the form application and
               automatically controls the further processing through an expert.

               Note the interaction of the SEND_VARIATION and
               SEND_EXPERT_IF_INCONSISTENT elements here.


           o   A = Save (do not tolerate errors)

               The data is automatically checked against the business logic in the back-end
               system and written to the infotypes in the back-end system. Error messages
               are not tolerated; users must enter all data correctly before they can continue
               editing the form. The user can request an expert's help for this.


                    Caution

               If a work item is completed with SEND_VARIATION = A, the system also
               saves any process steps that were entered in previous steps but not yet
               saved in the back-end system. If this setting is made, you therefore have to
               ensure that the user in a particular step is also able to correct incorrect data
               entered by other users. The corresponding fields must therefore be visible
               and modifiable in the form.


       Data type (Data Type tab page, ABAP Dictionary Reference field): Structure
       HRASR00_PROCESS_MODELLING and Field SEND_VARIATION.

       Save Draft button (SAVE_DRAFT_BUTTON_VISIBLE) – Optional

       You use this element to specify whether a button is provided to the user to
       temporarily save the entries in the form. Once the user has temporarily saved the
       data and the step is not yet completed, the corresponding work item continues to be
       available to the user in the Universal Worklist for processing with all previously
       entered data.

           o   X = Save Draft button is visible

               The user can save the current processing status of the form using the Save
               Draft button.

           o   BLANK = Not visible

               The Save Draft button is not visible and is therefore not available to the user
               (default setting).

       Data type (Data Type tab page, ABAP Dictionary Reference field): Structure
       HRASR00_PROCESS_MODELLING and Field BUTTON_IS_ENABLED.

       Back to Author button (BACK_BUTTON_VISIBLE) – Optional

       You use this element to specify whether a button is provided to the user to return a
       form to the initiator of a process.

           o   X = Back to Author button is visible

               The user can return the form to the initiator by choosing the Back to Author
               button. In this case, the processing status (PROCSTATE, see below)
               receives the value BACK. Note that you must take account of this behavior in
               subsequent modeling of the workflow.

           o   BLANK = Not visible


HR Administrative Services (PA-AS)          6956                                              90
SAP Online Help                                                                     22.04.2009


               The Back to Author button is not visible and is therefore not available to the
               user (default setting). Data type (Data Type tab page, ABAP Dictionary
               Reference field): Structure HRASR00_PROCESS_MODELLING and field
               BUTTON_IS_ENABLED

       Data type (Data Type tab page, ABAP Dictionary Reference field): Structure
       HRASR00_PROCESS_MODELLING and Field BUTTON_IS_ENABLED.

       Process Cancellation button (WITHDRAW_PROCESS_BUTTON_VISIBLE) –
       Optional

       You use this element to specify whether a user can withdraw a process. Withdrawing
       a process has the following effects:

           o   The entire process is stopped.

           o   All work items in the relevant workflow steps and workflow template that are
               not completed receive the status Cancelled.

           o   The process object is assigned the status Withdrawn.

           o   All open work items disappear from the universal worklists of all involved in
               the process.


                   Note

               The withdrawal of a process triggers a workflow of its own. For more
               information, see Customizing for Personnel Management under HR
               Administrative Services Configuration of Forms/Processes Process
               Configuration Technical Settings Settings for Standard Components and
               Workflows Activate Workflow After Withdrawing Process .


       The element can have the following properties:

           o   BLANK = Not visible (button not visible)

               The Process Cancellation button is not visible and is therefore not available
               to the user (default setting).

           o   ALWAYS = Visible (button visible and active, even after saving to back-end
               system) The Process Cancellation button is always available. The user can
               cancel the entire process.


                   Caution

               You can use this setting to cancel a process even if data has already been
               saved in the infotypes. Note that this can affect your dataset.


           o   IF_NO_SAVE = Visible before save (button is visible and active until saving
               to the back-end system)

               The Process Cancellation button is only available to users while the recorded
               data has not yet been saved in the back-end system.

       Data type (Data Type tab page, ABAP Dictionary Reference field): Structure
       HRASR00_PROCESS_MODELLING and Field WITHDRAW_BUTTON_VISIBLE.

       Expert button (SEND_EXPERT_IF_INCONSISTENT) – Optional


HR Administrative Services (PA-AS)          6956                                                91
SAP Online Help                                                                    22.04.2009


       Users who are not experts at entering personnel data can encounter insolvable
       problems if error messages occur due to inconsistent data. For this reason, you
       should allow the system to dynamically show the Send to Expert button in the form
       application when such errors occur and if no suitable agent can correct the errors in
       the workflow step that follows.

            Note

       Note the description of the SEND_VARIATION element. For more information, see
       Error Handling.


           o   X = Send to Expert button is visible

               The Send to Expert button is dynamically displayed if error messages occur
               due to inconsistent data.

                    Caution

               If you specify SEND_EXPERT_IF_INCONSISTENT = X together with
               SEND_VARIATION (Send Variant) = B, the behavior of
               SEND_EXPERT_IF_INCONSISTENT overrides that of SEND_VARIATION.
               This means that if the agent receives error messages due to inconsistent
               data, he or she cannot complete the work item. The agent must either correct
               the entered data or send the work item to an expert.


               The interaction between SEND_EXPERT_IF_INCONSISTENT and
               SEND_VARIATION is only relevant for errors in the Inconsistent Data error
               category. The system always provides the Send to Expert pushbutton for
               errors of the following error categories, even if you have set
               SEND_EXPERT_IF_INCONSISTENT = BLANK:

                       Data Collision

                       No Authorization

                       Object Is Locked (for background steps only)

                       Incorrect Customizing

               For this reason, a user who receives error messages due to inconsistent data
               can only complete the work item under the following conditions:

                       He or she corrects the data entered.

                       He or she forwards the work item to an expert.

           o   BLANK = Not visible

               The Send to Expert button is not visible and is therefore not available to the
               user (default setting).

       Data type (Data Type tab page, ABAP Dictionary Reference field): Structure
       HRASR00_PROCESS_MODELLING and Field BUTTON_IS_ENABLED.

Container Definition: Export Elements

       Processing Status (PROCSTATE) – Optional




HR Administrative Services (PA-AS)          6956                                            92
SAP Online Help                                                                     22.04.2009


       You can use this element to specify that the processing status is to be transferred
       from the workflow step to the workflow container once the work item is completed
       (data flow: workflow <- Edit Form step). If the processing status is known in the
       workflow container, you can process the other workflow steps in accordance with the
       processing status.

            Example

       A workflow step for editing a form can be completed with the processing status
       PROCESSED or BACK.

           o   If the work item is completed with the PROCESSED status, the next workflow
               step should be carried out by an HR administrator.

           o   If the work item is completed with the BACK status, the next workflow step
               should be carried out by the person who initiated the process.

       You model the following workflow steps depending on the processing status.


       To transfer the processing status to the workflow container, you must have previously
       created a suitable container element in the workflow container:

           o   For example, element = PROCSTATE

           o   For example, name = processing status

           o   Data type (Data Type tab page, ABAP Dictionary Reference field): Structure
               HRASR00_PROCESS_MODELLING and Field PROCESSING_STATUS

       The processing status can have the following values:

           o   PROCESSED

               The work item was processed successfully. The user has chosen the Send
               function in the view of the form application Review and Send.

           o   BACK

               The user has chosen the Back to Author function.

           o   ERROR

               An error occurred in executing the work item. This status is possible only if
               you entered B for the SEND_VARIATION element.


            Note

       For withdrawn processes, you no longer have to react to a processing status in the
       workflow. There is therefore no processing status for Withdrawn.


       Container element notify_via_e-mail - Optional

       You use this container element to specify whether an e-mail notification is sent to the
       next agent involved in a process. If e-mail notification is set to X = TRUE, an e-mail is
       sent to the agent, advising them that there is a work item waiting to be processed.
       They can access the work item directly from the body of the e-mail. If it is set to _ =
       FALSE, no e-mail is sent; the agent can access work items to be processed in the
       UWL.



HR Administrative Services (PA-AS)           6956                                              93
SAP Online Help                                                                      22.04.2009


        Container element BUSINESS_STATUS - Optional

        You use this container element to specify whether the business status is visible to the
        user in the process browser. If business status is set to X = TRUE, you can see the
        business status for the request step. If it is set to _ = FALSE, only the processing
        status is displayed; the business status cannot be seen.



     Standard Task TS04000019: Approve PD Form

You use this standard task to send a form to a user for approval. The approver can execute
the following functions in the relevant form application:

        Approve or reject the content of the form. The approver cannot change the content of
        the form.

        Return the form to the process initiator (optional)

        Save a draft (optional)


              Caution

        When a user executes this standard task, the data is not saved in the back-end
        system.


Standard Task: 04000019

ID: Approve

Name: Approve PD (Personnel Development) Form

Structure
Processor Assignment
You can use this standard task for HCM Processes and Forms workflow templates for
organizational processes, and store a corresponding agent assignment rule for the workflow
steps.

For more information, see Agent Assignment Rules.

Authorization Check
The A (Approve) activity is used for the P_ASRCONT authorization object.

For more information, see Authorization Concept of HCM Processes and Forms.

User Interface Control
When you initiate a work item with this standard task, a form application with the following
views is available:

        Approve

        Completed




HR Administrative Services (PA-AS)            6956                                             94
SAP Online Help                                                                        22.04.2009


        The user receives a confirmation that the data has been sent successfully. The work
        item disappears from the user's Universal Worklist.

When the corresponding work item is executed, the following elements are available on the
user interface:

        A form in which the user can check data. The user cannot edit the data.

        Approve and Reject buttons, which the user can choose to complete the processing
        of the form. The data is then sent to the workflow environment and the system
        continues with the next step in the workflow.

        Save Draft and Back to Author buttons (optional)

Process Control
If you use this task, you must also do the following tasks in the relevant workflow step:

        Data flow of task container

        Rule for agent determination with respective data flow to rule container

        Programming exit CL_HRASR00_POBJ_WF_EXIT

Container Definition: Import Elements

        Form (FORM) – Mandatory

        This element specifies which form scenario is used when the workflow step is
        executed. It consists of a structure with the following fields, which you have to define
        for use with this task:

            o   Form Scenario (FORM_SCENARIO) – Mandatory

                Enter the form scenario that is to be used within the workflow step.

            o   Form Scenario Version (FORM_SCENARIO_VERSION) – Mandatory

                Enter the version of the form scenario that you want to be used.

            o   Do Not Save Directly (SUPPRESS_SAVE) - Mandatory

                You can use this field to override the entries in the SEND_VARIATION
                element.

                         Enter an X if the data is not to be written to the database even if the
                         value A (Save (Do Not Tolerate Errors)) is set in the
                         SEND_VARIATION element.

                         Enter nothing if the data is to be saved according to the settings in
                         the SEND_VARIATION element.

        Data type (Data Type tab page in the ABAP Dictionary Data Type field): Type name
        HRASR00_FORM_KEY_ELEMENT

        Form Scenario View (FORM_SCENARIO_STAGE) - Mandatory

        Enter the scenario step that is to be used for the workflow step. You must have
        already defined the step in the Create Form Scenario Customizing activity (view
        cluster HRASR00FSCN).

        When defining the data flow in the workflow container, you can use a value help (F4)
        for the FORM_SCENARIO_STAGE field. This allows you to access your Customizing


HR Administrative Services (PA-AS)            6956                                               95
SAP Online Help                                                                      22.04.2009


       entries. You can use the value help in the Workflow column and, in the subsequent
       dialog box, the value help for the field in the Temporary Check Results of Table
       column. If the column is not visible, you can use the Enter Constant function.

       Data type (Data Type tab page, ABAP Dictionary Reference field): Structure
       HRASR00_PROCESS_MODELLING and field FORM_SCENARIO_STAGE

       Processor role (PROCESSOR_ROLE) – Optional

       Here you enter the role of the processor who generally executes the workflow step. If
       you do not specify a processor role, the HR Administrator (HRASRA) processor role
       is assigned in the standard release. It is necessary to enter the processor role, for
       example, for Data Tracking at the process-step level and for Message Mapping.

       For more information, see Customizing for Personnel Management under HR
       Administrative Services Configuration of Forms/Processes Process Configuration
         Set Up Processes Determine Processor Roles .

       Data type (Data Type tab page, ABAP Dictionary Reference field): Structure
       HRASR00_PROCESS_MODELLING and field PROCESSOR_ROLE

       Save Draft button (SAVE_DRAFT_BUTTON_VISIBLE) – Optional

       You use this element to specify whether a button is provided to the user to
       temporarily save the entries in the form. Once the user has temporarily saved the
       data and the step is not yet completed, the corresponding work item continues to be
       available to the user in the universal worklist for processing with all previously entered
       data.

           o   X = Save Draft button is visible

               The user can save the current processing status of the form using the Save
               Draft button.

           o   " " = Not visible

               The Save Draft button is not visible and is therefore not available to the user
               (default setting).

       Data type (Data Type tab page, ABAP Dictionary Reference field): Structure
       HRASR00_PROCESS_MODELLING and Field BUTTON_IS_ENABLED

       Back button (BACK_BUTTON_VISIBLE) – Optional

       You use this element to specify whether a button is provided to the user to return a
       form to the initiator of a process.

           o   X = Back to Author button is visible

               The user can return the form to the initiator by choosing the Back to Author
               button. In this case, the processing status (PROCSTATE, see below)
               receives the value BACK. Note that you must take account of this behavior in
               subsequent modeling of the workflow.

           o   BLANK = Not visible

               The Back to Author button is not visible and is therefore not available to the
               user (default setting).

       Data type (Data Type tab page, ABAP Dictionary Reference field): Structure
       HRASR00_PROCESS_MODELLING and Field BUTTON_IS_ENABLED

Container Definition: Export Elements


HR Administrative Services (PA-AS)           6956                                               96
SAP Online Help                                                                      22.04.2009


        Processing Status (PROCSTATE) – Optional

        You can use this element to specify that the processing status is to be transferred
        from the workflow step to the workflow container once the work item is completed
        (data flow: workflow <- Edit Form step). If the processing status is known in the
        workflow container, you can process the other workflow steps in accordance with the
        processing status.

        The processing status can have the following values:

            o   APPROVED

                This value is set when the user has chosen the Approve function.

            o   REJECTED

                This value is set when the user has chosen the Reject function.

            o   BACK

                This value is set when the user has chosen the Back to Author function.

        To transfer the processing status to the workflow container, you must have previously
        created a suitable container element in the workflow container:

            o   For example, element = PROCSTATE

            o   For example, name = processing status

            o   Data type (Data Type tab page, ABAP Dictionary Reference field): Structure
                HRASR00_PROCESS_MODELLING and field PROCESSING_STATUS

        Container element notify_via_e-mail - Optional

        You use this container element to specify whether an e-mail notification is sent to the
        next agent involved in a process. If e-mail notification is set to X = TRUE, an e-mail is
        sent to the agent, advising them that there is a work item waiting to be processed.
        They can access the work item directly from the body of the e-mail. If it is set to _ =
        FALSE, no e-mail is sent; the agent can access work items to be processed in the
        UWL.

        Container element BUSINESS_STATUS - Optional

        You use this container element to specify whether the business status is visible to the
        user in the process browser. If business status is set to X = TRUE, you can see the
        business status for the request step. If it is set to _ = FALSE, only the processing
        status is displayed; the business status cannot be seen.



  Standard Task TS04000020: PD Form Is Edited
Again by Author

You can use this standard task to return a form to a user to edit another time. With this
standard task, the user receives a returned form that he or she has already edited. This task
is triggered in the following conditions:

        When a user of the form chooses the Back to Author function in the form application




HR Administrative Services (PA-AS)            6956                                             97
SAP Online Help                                                                    22.04.2009


        If the workflow is modeled according to the related workflow step for the processing
        status (PROCSTATE) BACK.

This task corresponds to the Process PD Form standard task. The differences are:

        The values of the processing statuses that are output are different (see below).

        The Back to Author function is not available in the form application.

For more information, see the documentation on Standard Task TS04000018: Process PD
Form.

Standard Task: 04000020

ID: Return Form

Name: PD (Personnel Development) Form Is Edited Again by Author

Structure
Processor Assignment
You can use this standard task for all HCM Processes and Forms workflow templates, and
store a corresponding agent assignment rule for the workflow steps. When using this
standard task, make sure that the same user who first edited the form receives the work item.

For more information, see Agent Assignment Rules.

Authorization Check
The P (Process) activity is used for the P_ASRCONT authorization object.

For more information, see Authorization Concept of HCM Processes and Forms.

User Interface Control
See the documentation for the task Process PD Form.

Process Control
Container Definition: Import Elements

        Processor role (PROCESSOR_ROLE) – Optional

        Here you enter the role of the processor who executes the workflow step. If you do
        not specify a processor role, the HR Administrator (HRASRA) processor role is
        assigned in the standard release. It is necessary to enter the processor role, for
        example, for Data Tracking at the process-step level and for Message Mapping.

        For more information, see Customizing for Personnel Management under HR
        Administrative Services Configuration of Forms/Processes Process Configuration
          Set Up Processes Determine Processor Roles .

        Data type (Data Type tab page, ABAP Dictionary Reference field): Structure
        HRASR00_PROCESS_MODELLING and field PROCESSOR_ROLE

Container Definition: Export Elements


    Note

The configuration options in the binding editor are identical to the task TS04000018: Process
PD Form. Only the PROCSTATE element returns different values.


HR Administrative Services (PA-AS)           6956                                              98
SAP Online Help                                                                      22.04.2009




        Processing Status (PROCSTATE) – Optional

        You can use this element to specify that the processing status is to be transferred
        from the workflow step to the workflow container once the work item is completed
        (workflow binding <- Form Is Edited Again by Author step). If the processing status is
        known in the workflow container, you can process the other workflow steps in
        accordance with the processing status.

        The processing status can have the following value:

            o   RESENT

                The work item was processed successfully. The user has chosen the Send
                function in the Review and Send view of the form application.


                     Note

                You control the subsequent workflow steps, such as those for approving the
                form, on the basis of the Sent Back processing status. This is necessary so
                that you can differentiate subsequent process steps from those resulting from
                the first editing.


        Data type (Data Type tab page, ABAP Dictionary Reference field): Structure
        HRASR00_PROCESS_MODELLING and Field PROCESSING_STATUS

        Container element notify_via_e-mail - Optional

        You use this container element to specify whether an e-mail notification is sent to the
        next agent involved in a process. If e-mail notification is set to X = TRUE, an e-mail is
        sent to the agent, advising them that there is a work item waiting to be processed.
        They can access the work item directly from the body of the e-mail. If it is set to _ =
        FALSE, no e-mail is sent; the agent can access work items to be processed in the
        UWL.

        Container element BUSINESS_STATUS - Optional

        You use this container element to specify whether the business status is visible to the
        user in the process browser. If business status is set to X = TRUE, you can see the
        business status for the request step. If it is set to _ = FALSE, only the processing
        status is displayed; the business status cannot be seen.



    Workflow Template WS17900260: Save Form with
Error Handling
Use
You can use this workflow template to have the data of a form automatically saved in the
infotypes in the backend system, without a human user initiating the save.
You can use the workflow template if you do not want to give the last person to process the
form data the extensive authorizations required to save the data securely on the database. If
error messages arise in the backend system during automatic processing, you can have the
data processed by an authorized expert.




HR Administrative Services (PA-AS)            6956                                             99
SAP Online Help                                                                        22.04.2009




                This workflow template is intended for use only within a surrounding workflow
                template as a multistep task. You can use it without adjusting the standard
                version. If the standard version does not meet your requirements, you can copy
                it and adjust the copy.


Workflow Template: 17900260
ID: Sichern_Beh
Name: Save Form with Error Handling

Standard Tasks Used

          Standard Task: TS17900107: Check Form Data [Page 109]

          Standard Task: Wait Step

          Standard Task TS04200007: Find and Lock Employee

          Standard Task: TS17900160: Forwarded Because of Errors

          Standard Task: TS17900108: Save Form Data [Page 110]

          Standard Task: TS17900110: Import Form Field Value to Workflow Container Element
          [Page 111]

          Standard Task: TS17900112: Instantiate BOR EMPLOYEET

          Standard Task: TS04200008: Unlock Employee

          Standard Task: TS17900106: Check Existence of PA Infotype [Page 108]



Process Flow
...
...




      1. The system attempts to save the data.
         If the system is able to save the data, the workflow template is completed. If the system
         is not able to save the data, it reacts as follows, depending on the cause:
            a. Errors or warnings arise during the data check by the business logic. The
               system enters a work item in the expert's worklist for processing.



                The default settings is that only serious errors (type ERROR) cause the save to
                fail. However, you can specify that an expert receives an interactive work item
                also in the case of warnings. You can also specify whether the system is to save
                the data first, despite the warnings.
            b. The employee's data is locked for processing because the payroll is being run.
                In this case, the logic of the workflow template is such that the system attempts
                each hour to lock the personnel number itself to be able to save the data. You
                can set how often the system repeats the attempts in the workflow container.

                       Once the maximum number of attempts is reached, an expert receives a
                       work item for processing.

                       If the system is able to lock the personnel number and then the save
                       fails, due to inconsistent data, for example, an expert receives a work
                       item to process the relevant form.


HR Administrative Services (PA-AS)               6956                                            100
SAP Online Help                                                                       22.04.2009


         c. The employee's data is locked for maintenance because it is being processed in
            another application.
             In this case, the system attempts to lock the personnel number itself until the
             lock is lifted by the other application.
  2. The expert processes the data that the system was unable to save automatically.
      You can specify that a particular expert receives the work item depending on the type
      of error.
For more information, see Error Handling [Page 124].

Structure
Agent Assignment
Data is saved in the background by the user workflow batch.
If the system was unable to save the data, it determines the expert responsible on the basis
of the type of error. You specify which agents receive the work item for which errors in the
Implementation Guide for HR Administrative Services under Configuration of
Forms/Processes        Process Configuration    Error Handling.

Authorization Check
Make sure that the WF Batch user and the experts have the required authorizations:

      Authorization object P_ASRCONT: The activity R (Read) is used for the authorization
      check.

      The relevant Personnel Administration authorization objects, such as P_ORGIN to
      check authorization for HR infotypes.
For more information, see Authorization Concept for HCM Processes and Forms [Page 118].

Process Control
If you want to use this workflow template in a workflow step of a workflow template, you have
to define a binding for the mandatory container elements of the WS17900260 template. If you
do not assign any values in the binding for the optional importing container elements, the
system uses the default value.
When you define the binding, you have the following options:

      You can specify the values directly in the binding of this workflow template.

      You can assign the container element of the workflow template the value of the
      corresponding container element of the surrounding workflow template. In the latter
      case, you have to create the element in the same data type in the surrounding
      workflow container. For information about the data type, you can double-click the
      corresponding element of the sub-workflow.
Binding: Import Elements
Container elements to control the logic implemented by the workflow template

      Form (FORM) – Mandatory
      You can use this element to specify the form scenario whose data you want to
      automatically save in the background. Note that all other form scenarios that have been
      processed but not yet saved are also saved at the same time.
      This element consists of a structure with the following three fields:

             Form Scenario (FORM_SCENARIO) – Mandatory
             Enter the form scenario that is to be used within the workflow step



HR Administrative Services (PA-AS)            6956                                             101
SAP Online Help                                                                       22.04.2009


              Form Scenario Version (FORM_SCENARIO_VERSION) – Mandatory
             Enter the version of the form scenario that you want to be used.

              Do Not Save Directly (SUPPRESS_SAVE) – Optional
             You can use this field to override the settings in the SEND_VARIATION
             element.

                     Enter an X here if the data is not to be written to the infotypes even if the
                     value A (Check and Save) is set in the SEND_VARIATION element.

                     Enter nothing if the data is to be saved according to the settings in the
                     SEND_VARIATION element.
      Data type (Data Type tab page in the ABAP Dictionary Data Type field): Type name
      HRASR00_FORM_KEY_ELEMENT
       Mode in which manual processing is carried out (HANDLING_MANUALLY) – Optional
      You can use this element to control the conditions under which an expert receives a
      work item for processing. The following values are possible:

              ERROR (default setting)
             If errors occur when the form data is saved, an expert receives a work item.



             In the case of errors, the form data is not saved on the application database.

              WARN_PREV
             If errors or warnings occur when the form data is saved, an expert receives a
             work item. The system does not save the data to the application database, even
             if only warnings occur.

              WARN_AFTER
             If errors or warnings occur when the form data is saved, an expert receives a
             work item. If warnings occur, the system saves the data directly to the
             application database before the expert processes the work item.
      Data type (Data Type tab page, ABAP Dictionary Reference field): Structure
      HRASR00_PROCESS_MODELLING and Field HANDLING_MANUALLY
       Maximum number of save attempts (COUNTER_MAX_PAYROLL) – Optional
      If the personnel numbers are locked by a current payroll run, the data cannot be saved.
      The system can then attempt to lock the personnel numbers itself every hour and to
      save the data.
      You can use this element to specify the maximum number of times the system should
      attempt to lock the personnel numbers. The default limit is 26 (hours).
      Data type (Data Type tab page, ABAP Dictionary data type): Type name INTEGER.


Container elements to control the behavior of the interactive step for the expert.

       Scenario step (FORM_SCENARIO_STAGE) – Mandatory
      You specify the scenario step for the workflow step at which the form has to be
      processed by an expert if errors or warnings occurred on saving. You must have
      configured the scenario step in Customizing for the form scenario.
      When defining the binding in the workflow container, you can use a value help (F4) for
      the FORM_SCENARIO_STAGE field, which enables you to access your Customizing


HR Administrative Services (PA-AS)            6956                                            102
SAP Online Help                                                                   22.04.2009


     entries. You can use the value help in the Workflow column and, in the subsequent
     dialog box, the value help for the field in the Temporary Check Results of Table.
     Data type (Data Type tab page, ABAP Dictionary Reference field): Structure
     HRASR00_PROCESS_MODELLING and Field FORM_SCENARIO_STAGE
      Send Variant (SEND_VARIATION) – Optional and Save Draft button
      (SAVE_DRAFT_BUTTON_VISIBLE) – Optional
For more information about these container elements, see the Standard Task TS17900100:
Edit Form [Page 73] documentation.


Container Definition: Export Elements



            You will not usually have to use these export elements. You can however, add
            customer-specific implementations of functions and logic.

      Processing Status (PROCSTATE) – Optional
     Once the workflow template is completed, the PROCSTATE element contains the
     processing status of the last workflow step executed. This may be a different step,
     depending on the process flow within the workflow template.



                          The form data can be saved to the infotypes without problems.
                          After the workflow template is completed, the PROCSTATE
                          container element has the processing status of the step used to
                          save the data in the background. It has the value PROCESSED.

                          Warnings occur when data is saved in the background. You
                          specified in the Mode in which manual processing is carried out
                          container element (HANDLING_MANUALLY) that an expert is to
                          receive a work item to postprocess data only in the case of errors
                          (ERROR). After the workflow template is completed, the
                          PROCSTATE container element has the processing status of the
                          step used to save the data in the background. It has the value
                          WARNING.
     Data type (Data Type tab page, ABAP Dictionary Reference field): Structure
     HRASR00_PROCESS_MODELLING and Field PROCESSING_STATUS
      Form field EFFECTIVE_DATE – Optional
     The EFFECTIVE_DATE element contains the value of the form field of the same name
     of the form scenario you specified for the FORM container element.
     Data type (Data Type tab page, ABAP Dictionary data type): Type name DATUM.

      Error category (ERROR_CATEGORY) – Optional
     If messages arise when the form data is saved, this container element contains the
     highest-priority error category.
     For more information about prioritizing error categories, see the Implementation Guide
     for HR Administrative Services and choose Configuration of Forms/Processes
     Process Configuration    Error Handling.
     Data type (Data Type tab page in the ABAP Dictionary Data Type field): Type name
     ASR_ERROR_CATEGORY
      Error messages (ERROR_MESSAGS) – Optional



HR Administrative Services (PA-AS)         6956                                            103
SAP Online Help                                                                           22.04.2009


      If messages arise when the form data is saved, this container element contains the
      messages that arose for the ERROR_CATEGORY category (see above).
      Data type (Data Type tab page in the ABAP Dictionary Data Type field): Type name
      HRASR00ERROR_INFO_TAB




   Workflow Template WS17900404: Draft for Process
Start

You can use this workflow template to trigger a workflow for a draft version in the start step of
process for the process initiator.

This workflow is triggered only the first time you choose the Save Draft button in the start step
of the process.

Workflow Template: 17900404

ID: ASRDRAFT

Name: Draft for Process Start

Standard Tasks Used

        Standard Task: TS04000025: Get Status of Switch

        If the switch is on, you can use the new functions for SAP enhancement package 4
        for SAP ERP 6.0. If the switch is off, these new functions are not available.

        Standard Task: TS04000024: Get Application of Process

        If you choose an employee-related process, the application type is Personnel
        Administration (PA); you are brought to Draft for Process Start - task TS17900121.

        If you choose an organization-related process, the application type is Personnel
        Development (PD); you are brought to Draft for PD Process Start - task TS04000021.

        Standard Task: TS17900121: Draft for Process Start

        Standard Task: TS04000021: Draft for PD Process Start

Structure
Agent Assignment
If you activate the event linkage, the workflow for draft version is available for use.

Authorization Check
Make sure that the WF Batch user has the required authorizations:

        Authorization object P_ASRCONT: The activity S (Start) is used for the authorization
        check.




HR Administrative Services (PA-AS)             6956                                             104
SAP Online Help                                                                      22.04.2009


        The relevant Personnel Administration authorization objects, such as P_ORGIN to
        check authorizations.

For more information, see Authorization Concept of HCM Processes and Forms.

Process Control
If you want to use this workflow template in a workflow step of a workflow template, you have
to define a binding for the mandatory container elements of the WS17900404 template. If you
do not assign any values in the binding for the optional importing container elements, the
system uses the default value.

When you define the binding, you have the following options:

        You can specify the values directly in the binding of this workflow template.

        You can assign the container element of the workflow template the value of the
        corresponding container element of the surrounding workflow template. In the latter
        case, you have to create the element in the same data type in the surrounding
        workflow container. For information about the data type, you can double-click the
        corresponding element of the sub-workflow.

Process
    1. Perform the activity Workflow: Draft for Process Start in Customizing for Personnel
       Management under HR Administrative Services Configuration of
       Forms/Processes Process Configuration Technical Settings Settings for
       Standard Components and Workflows Workflow: Draft for Process Start .

        Choose Activate Event Linkage to link to event DRAFT_CREATED. Ensure status
        Activated is displayed for the workflow.

        This ensures that you can use this workflow in your processes.

    2. When you choose the Save Draft button in the start step of the process, a work item
       appears in the process initiator's worklist with any changes made before saving the
       draft. You can open this draft version from the work item and make further changes.

        If you choose Save Draft again, no separate work item is generated, but the changes
        you have made are updated in the original work item.

        When you choose Check and Send, the work item gets sent to the next agent in the
        process, and the draft work item is no longer found in the UWL.

    3. If you choose Delete Draft, the draft work item is deleted.



   Workflow Template WS17900418: Forward:
Process Start with Errors

You can use this workflow template to trigger a workflow for forward to expert function in start
step of the process.

This workflow is triggered only the first time you choose the Forward to Expert button in the
start step of the process.

Workflow Template: 17900418

ID: ASRDraftErr


HR Administrative Services (PA-AS)           6956                                            105
SAP Online Help                                                                     22.04.2009


Name: Forward: Process Start with Errors

Standard Tasks Used

        Standard Task: TS04000025: Get Status of Switch

        If the switch is on, you can use the new functions for SAP enhancement package 4
        for SAP ERP 6.0. If the switch is off, these new functions are not available.

        Standard Task: TS04000024: Get Application of Process

        If you choose an employee-related process, the application type is Personnel
        Administration (PA); you are brought to Forward to Expert: Process Start with Errors -
        task TS17900160.

        If you choose an organization-related process, the application type is Personnel
        Development (PD); you are brought to Forwarded Because of Errors in PD Form -
        task TS04000022.

        Standard Task: TS17900160: Forward to Expert: Process Start with Errors

        PD-Specific Task: TS04000022: Forwarded Because of Errors in PD Form

Structure
Agent Assignment
You specify which agents receive the work item for which error categories in Customizing for
Personnel Management under HR Administrative Services Configuration of
Forms/Processes Process Configuration Error Handling Assign Possible Processors to
Error Categories .

Authorization Check
Make sure that the WF Batch user and the experts have the required authorizations:

        Authorization object P_ASRCONT: The activity P (Process Form) is used for the
        authorization check.

        The relevant Personnel Administration authorization objects, such as P_ORGIN to
        check authorizations.

For more information, see Authorization Concept of HCM Processes and Forms.

Process Control
If you want to use this workflow template in a workflow step of a workflow template, you have
to define a binding for the mandatory container elements of the WS17900418 template. If you
do not assign any values in the binding for the optional importing container elements, the
system uses the default value.

When you define the binding, you have the following options:

        You can specify the values directly in the binding of this workflow template.

        You can assign the container element of the workflow template the value of the
        corresponding container element of the surrounding workflow template. In the latter
        case, you have to create the element in the same data type in the surrounding
        workflow container. For information about the data type, you can double-click the
        corresponding element of the sub-workflow.




HR Administrative Services (PA-AS)           6956                                          106
SAP Online Help                                                                      22.04.2009


Process
    1. Perform the activity Workflow: Draft for Process Start (Error Case) in Customizing for
       Personnel Management under HR Administrative Services Configuration of
       Forms/Processes Process Configuration Technical Settings Settings for
       Standard Components and Workflows Workflow: Draft for Process Start (Error
       Case) .

        Choose Activate Event Linkage to link to event DRAFT_TO_ERROR_AGENT. Ensure
        status Activated is displayed for the workflow.

        This ensures that you can use this workflow in your processes.

    2. In Customizing for Personnel Management under HR Administrative Services
         Configuration of Forms/Processes Process Configuration Set Up Processes
         Configure Process Start , choose the process in which you want to enable the
       Forward to Expert button.

        Select the Show 'Forward to Expert' button for Inconsistent Data checkbox.

    3. You can choose the Forward to Expert button in the start step of a process if there
       are errors occurring that you are unable to solve. The relevant expert for the error
       category receives the work item in his or her worklist including the message that there
       are errors to be solved.

        The expert has several options:

            o   Save Draft

                The expert can enter changes and save those changes to update the work
                item in his or her worklist.

            o   Back to Agent

                The expert enters a comment and sends the form back to the initiator. The
                initiator receives the work item with comments in his or her worklist, and tries
                to solve the errors before sending the form to the next agent in the process.

            o   Withdraw Process

                If the expert chooses this button, the process gets cancelled. To enable a
                process to be withdrawn, you must perform the activity Enable Withdrawal of
                Processes in Customizing for Personnel Management under HR
                Administrative Services Configuration of Forms/Processes Process
                Configuration Error Handling Enable Withdrawal of Processes .

        If the expert can solve the errors, he or she can choose Check and Send to start the
        process on behalf of the initiator; the work item gets sent to the next agent in the
        process.



  Task Group TG17900003: Background
Components
Use
The standard tasks of the TG17900003 task group (Background Components) trigger system
activities at runtime that are executed without user interaction. They create results in the
workflow container. You can use these results for process modeling.




HR Administrative Services (PA-AS)           6956                                            107
SAP Online Help                                                                     22.04.2009



   Standard Task TS17900106: Check Existence of
PA Infotype
Definition
The system uses this standard task to check whether a particular infotype record has been
saved on the database for a particular personnel number for a particular period. This standard
task comprises an action to be executed by the system. No human users are involved.


Standard task: 17900106
ID: Exist.PA IT
Name: Check Existence of PA Infotype



Structure
Referenced Object Method, Properties:
Object Type: CL_HRASR00_WF_COMPONENTS
Method: CHECK_EXISTENCE_OF_PA_IT


Agent Assignment


Authorization Check
Make sure that the WF Batch user has the required authorizations.

User Interface Control
-

Process Control


Container Definition: Import Elements

      Start/End Date (BEGDA/ENDDA) – Mandatory
      Start and end dates of the period for which the specified infotype record is sought.
      Data type (Data Type tab page, ABAP Dictionary Reference field): Structure PSKEY
      and Field BEGDA or ENDDA

      Personnel Number (PERNR) – Mandatory
      The personnel number of the employee whose data is being processed. You should
      link this to PROCESS_OBJECT.OBJECT_KEY.
      ABAP Dictionary data type: PERNR_D

      Infotype (INFTY) – Mandatory
      Four-digit number of the infotype that is being sought.
      ABAP Dictionary Reference: Structure PSKEY, Field INFTY

      Subtype (SUBTY) – Mandatory



HR Administrative Services (PA-AS)           6956                                            108
SAP Online Help                                                                    22.04.2009


      Number of the subtype that is being sought.
      ABAP Dictionary Reference: Structure PSKEY, Field SUBTY
Container Definition: Export Elements

      Processing Status (PROCSTATE) – Optional
      You can use this element to specify that the processing status is to be transferred from
      the workflow step to the workflow container once the work item is completed (data flow:
      workflow <- Edit Form step). If the processing status is known in the workflow
      container, you can process the other workflow steps in accordance with the processing
      status.
      The processing status can have the following values:

             PROCESSED = At least one infotype record was found for this person.

             ERROR = No records were found for the specified infotype for this person.




      Standard Task TS17900107: Check Form Data
Definition
You can use this standard task to run a background check of the form data against the
databases in the backend system. The result of the check is available at workflow level for
further processing.


Standard task: 17900107
ID: Check Form D
Name: Check Form Data



Structure
Referenced Object Method, Properties:
Object Type: CL_HRASR00_WF_COMPONENTS
Method: CHECK_FORM_DATA


Agent Assignment
-

Authorization Check
Make sure that the WF Batch user has the required authorizations:

      Authorization object P_ASRCONT: The activity R (Read) is used for the authorization
      check.

      Authorization object P_ORGIN to check authorization for HR infotypes
For more information, see Authorization Concept of HCM Processes and Forms [Page 118].

User Interface Control
-


HR Administrative Services (PA-AS)           6956                                             109
SAP Online Help                                                                       22.04.2009


Process Control


Container Definition: Import Elements

       Form (FORM) – Mandatory
      You use this element to specify which form scenario is used when the workflow step is
      executed. This element consists of a structure with the following three fields:

              Form Scenario (FORM_SCENARIO) – Mandatory
             Enter the form scenario that is to be used within the workflow step.

              FormScenario Version (FORM_SCENARIO_VERSION) – Mandatory
             Enter the version of the form scenario that you want to be used.

              Do Not Save Directly (SUPPRESS_SAVE) – Mandatory
             You can use this field to override the settings in the SEND_VARIATION
             element. This field is not relevant for this task.
Container Definition: Export Elements

       Processing Status (PROCSTATE) – Optional
      You can use this element to provide business-related information about the current
      processing status of the work item. This element is declared for the reverse data flow
      (back to workflow).
      The processing status can have the following values:

              PROCESSED = No errors and no warnings occurred during the check of the
              form data container.

              WARNING = A warning occurred during the check.

              ERROR = An error occurred during the check.




      Standard Task TS17900108: Save Form Data
Definition
You can use this standard task to run a background check on the data entered in the form
and subsequently save it in the back-end system. This task corresponds to a user executing
the Review and Send functions in an interactive step where the data is saved in the back-end
system by the Send function.
The result of the check or save is available on the workflow level for further processing. If the
check is successful, the system attempts to save the form data. For more information, see the
description of the Processing Status container element.



             You can use this standard task in the following scenario, for example:
             You want the data to be saved in the back-end system when a supervisor has
             approved a form. If the data cannot be saved in the back-end system as a result
             of errors, you want the HR administrator to postprocess the incorrect data. This
             means that the supervisor does not receive error messages that he or she is
             unable to process.




HR Administrative Services (PA-AS)            6956                                           110
SAP Online Help                                                                     22.04.2009


Standard task: 17900108
ID: Save Form
Name: Save Form Data



Structure
Referenced Object Method, Properties:
Object Type: CL_HRASR00_WF_COMPONENTS
Method: SAVE_FORM_DATA_TO_DB


Agent Assignment
-

Authorization Check
Make sure that the WF Batch user has the required authorizations.

      Authorization object P_ASRCONT: The activity X (Saved to Database) is used for the
      authorization check.

      Authorization object P_ORGIN to check authorization for Human Resources infotypes
For more information, see Authorization Concept for HCM Processes and Forms [Page 118].

User Interface Control
-

Process Control
The setting options in the binding editor and the evaluations are the same as those for the
standard task TS17900107: Check Form Data [Page 109].



             The system saves the data if it has the processing status PROCESSED or
             WARNING. Data cannot be saved if it has the processing status ERROR.




   Standard Task TS17900110: Import Field Value to
WF Cont. Element
Definition
You can use this standard task to transfer values from fields in a form to elements of the
workflow container. The system accesses the current dataset of the form scenario that is
specified in the task binding.



             You cannot use this standard task to import fields from infotypes with a
             repetition structure (such as the Basic Pay infotype (0008)).




HR Administrative Services (PA-AS)           6956                                             111
SAP Online Help                                                                      22.04.2009


Standard task: 17900110
ID: Elementimp
Name: Import Form Container -> WF Container



Structure
Referenced Object Method, Properties:
Object Type: CL_HRASR00_WF_COMPONENTS
Method: DATAMAPPING



Agent Assignment
-

Authorization Check
Make sure that the WF Batch user has the required authorizations.

      Authorization object P_ASRCONT: The activity R (Read) is used for the authorization
      check.

      Authorization object P_ORGIN to check authorization for HR infotypes
For more information, see Authorization Concept for HCM Processes and Forms [Page 118].

User Interface Control
-

Process Control


Container Definition: Import Elements

      Form (FORM) – Mandatory
      You use this element to specify which form scenario is used when the workflow step is
      executed. This element consists of a structure with the following three fields:

             Form Scenario (FORM_SCENARIO) – Mandatory
             Enter the form scenario that is to be used within the workflow step

             Form Scenario Version (FORM_SCENARIO_VERSION) - Mandatory
             This field specifies the version of the form scenario that you want to use.

             Suppress Save (SUPRESS_SAVE)
             You can use this field to override the settings in the SEND_VARIATION
             element. This field is not relevant for this task.
      Data type (Data Type tab page in the ABAP Dictionary Data Type field): Type name
      HRASR00_FORM_KEY_ELEMENT.
      Form Field Name x (FORM_FIELD_NAME_x)
      This element contains the name of the form field whose value is to be imported. Enter
      the name in exactly the same format as you defined when setting up the form scenario.

             Since the element does not contain any workflow elements, the specified name
             should not contain the identifier of a workflow element &.


HR Administrative Services (PA-AS)           6956                                          112
SAP Online Help                                                                        22.04.2009


             You can use the task to read the values of a maximum of three fields. To
             number the imported form fields, use _x.
Container Definition: Export Elements

      Value x (FORM_FIELD_VALUE_x)
      This element contains the value of the form field that you entered for
      FORM_FIELD_NAME_x. In the definition of the dataflow, specify the receiving
      workflow element, for example, &Name&.




      Restrictions When Modeling Workflows
Use
Modeling workflow templates for HCM Processes and Forms is subject to certain restrictions.
This affects, for example, the following workflow templates:

      Workflow templates in which you insert branches so that several form scenarios can
      be edited simultaneously in the same workflow

      Workflow templates that contain loops with which processors can reject a form or send
      it back to another processor as a result of a query

Features
Workflow Templates with Branches
If you want to create workflow templates with parallel branches, you must observe the
following rules:

      The branch must not be between two workflow steps that process the same form
      scenario.
      Therefore, if several workflow steps process the same form scenario, you can only
      insert the branch after the last of these steps.
      Reason: The next workflow step with a new form scenario always accesses the last
      data container of the first form scenario. If you insert a branch for the first form scenario
      before the last workflow step, the content of the last data container of the first form
      scenario depends on how far the process has progressed. The system then uses any
      of the first form scenario’s data containers. The data that is processed in the new form
      scenario is therefore not current.

      The workflow template can only immediately begin with a branch if you do not use the
      same form scenario that is used in the start application in any of the workflow steps.
      The start application is located outside the workflow template. Therefore, you do not
      see the initial step when editing the workflow template. However, the system processes
      the initial step in exactly the same way as the actual workflow steps. If you insert a
      branch directly after the initial step and use the same form scenario that you used in
      the initial step in one of the workflow steps, the same situation that is described in the
      first rule occurs.

      Form scenarios that are processed in parallel branches of a workflow template are not
      allowed to access the same data.
      This means, for example, that if you provide a field from a particular infotype in a form
      scenario for editing, you cannot provide this field in a second form scenario that you are
      using in a parallel branch of the same workflow template either for processing or
      displaying.



HR Administrative Services (PA-AS)            6956                                             113
SAP Online Help                                                                       22.04.2009


      Reason: If two processors are processing the same field simultaneously, the system
      cannot evaluate whose changes are valid. If a processor is processing a field and a
      second processor displays the field at the same time, it is possible that the second
      processor will see obsolete information.

Workflow Templates with Loops
If you want to create workflow templates with loops, you must fulfill the following conditions:

       Loops can occur in a workflow template in the following cases:

              A processor has a query for a previous processor and therefore sends the form
              back to that processor.

              A processor does not approve a request. The form is thus sent back to the
              original processor for further processing.
      In the workflow template, the processing status PROCSTATE is displayed in the
      workflow step container using the BACK value for a query and the REJECTED value
      for a rejection.

       After a processing status of BACK or REJECTED is set in a workflow step, the
       following applies:

              If the following workflow step is an interactive step that has a form scenario
              assigned to it that has already been processed once, the form is displayed to
              the processor in the same way as it was originally sent. If the content of the
              form fields being processed in this step has been changed in other process
              steps, the changed data is displayed.

              All following form scenarios and form scenario steps are initialized again. This
              means that the processor sees them as if they have never been processed
              before. Comments and attachments are retained however.
             Reinitialization means in this case that the default values for the form are
             recalculated and field values from other form scenarios are transferred again if
             necessary. Entries that a processor has undertaken in a form scenario that is to
             be reinitialized are lost when the reinitialization occurs.

              If a form scenario or form scenario step that has not yet been processed follows
              a step with a processing status of BACK or REJECTED, it is initialized as usual.

       This logic has no influence on steps that do not change the content of form data
       containers, such as the sending of an e-mail.

       Between triggering a loop and the next interactive step, you must not use any standard
       tasks that can change the data container (for example, the standard task TS17900108
       for saving in the background). The use of such standard tasks can lead to errors during
       reinitialization.

Example
Workflow Templates with Branches
Permitted Branch
The figure below shows an example of a workflow template with a branch that is permitted:




HR Administrative Services (PA-AS)            6956                                            114
SAP Online Help                                                                               22.04.2009



                                                 Start Application

                                         Form Scenario                 A
                                         Form Scenario Step            A1
                                         Data Container                A1
                                         Field                         a
Workflow Template




                                                 Workflow Step 1

                                         Form Scenario                 A
                                         Form Scenario Step            A2
                                         Data Container                A2
                                         Field                         c




                        Workflow Step 2 a                            Workflow Step 2 b

                    Form Scenario                B             Form Scenario             C
                    Form Scenario Step           B1            Form Scenario Step        C1
                    Data Container               B1            Data Container            C1
                    Field                        e             Field                     b


Branches That Are Not Permitted
The figures below show examples of workflow templates with branches that are not
permitted. In both cases, the branches are not possible because it is not clearly defined which
data container the system must use to process workflow step 2 a (Example 1) or 1 a
(Example 2). When processing the B1 data container, the system can use either the A1 data
container or the A2 data container, depending on whether workflow step 2 b (Example 1) or 1
b (Example 2) has already been executed or not.
Branches That Are Not Permitted – Example 1




HR Administrative Services (PA-AS)                                   6956                           115
SAP Online Help                                                                               22.04.2009



                                                 Start Application

                                         Form Scenario                 A
                                         Form Scenario Step            A1
                                         Data Container                A1
                                         Field                         a
Workflow Template




                                                 Workflow Step 1

                                         Form Scenario                 A
                                         Form Scenario Step            A2
                                         Data Container                A2
                                         Field                         c




                        Workflow Step 2 a                            Workflow Step 2 b

                    Form Scenario                B             Form Scenario             A
                    Form Scenario Step           B1            Form Scenario Step        A3
                    Data Container               B1            Data Container            A3
                    Field                        e             Field                     b


Branches That Are Not Permitted – Example 2

                                                 Start Application

                                         Form Scenario                 A
                                         Form Scenario Step            A1
                                         Data Container                A1
                                         Field                         a
Workflow
Template




                        Workflow Step 1 a                            Workflow Step 1 b

                    Form Scenario                B             Form Scenario             A
                    Form Scenario Step           B1            Form Scenario Step        A2
                    Data Container               B1            Data Container            A2
                    Field                        e             Field                     b



Workflow Templates with Loops
Permitted Loops

Permitted Loop – Example 1



HR Administrative Services (PA-AS)                                   6956                           116
SAP Online Help                                                                    22.04.2009


In this example, form scenario B is sent back to processor 1 after being rejected by processor
2. Processor 1 receives form scenario A in the form in which it was originally sent. Form
scenario B belonging to processor 2 is then reinitialized.

      Request Step                       Approval Step                             …
                            Send                                  Approve
    Form Scenario A                      Form Scenario B                           …


          Processor 1                         Reject       Processor 2



                                          Process Step

                                         Form Scenario A

                                                           Processor 1




Permitted Loop – Example 2

In this example, form scenario B is sent back to processor 1 after being rejected by processor
2. Before processor 1 receives form scenario A again for processing, an e-mail is sent. After
this, processor 1 receives form scenario A in the form in which it was originally sent. Form
scenario B belonging to processor 2 is then reinitialized.

      Request Step                        Approval Step                             …
                             Send                                  Approve
     Form Scenario A                     Form Scenario B                            …


           Processor 1                        Reject       Processor 2




                                        Background Step
                             Send
                                           Send E-Mail


                                              Send




                                          Process Step

                                         Form Scenario A

                                                           Processor 1




Loop That Is Not Permitted
In this example, form scenario B is sent back to processor 1 after being rejected by processor
2. Before processing the form again however, processor 1 processes form scenario C. Form
scenario A is therefore reinitialized by processor 1.




HR Administrative Services (PA-AS)          6956                                          117
SAP Online Help                                                                    22.04.2009


      Request Step                        Approval Step                             …
                             Send                                 Approve
     Form Scenario A                     Form Scenario B                            …


           Processor 1                        Reject       Processor 2




                                           Process Step
                             Send
                                         Form Scenario C


                                               Send




                                           Process Step

                                         Form Scenario A

                                                           Processor 1




   Authorization Concept of HCM Processes and
Forms
Use
Protection of personal data is an important aspect of IT-supported HR tasks. For this reason,
authorizations in SAP Personnel Management can be defined down to the smallest detail to
prevent unauthorized access to person-specific data.
On the other hand, the aim of HCM Processes and Forms is to involve as many users as
possible in the performance of routine HR tasks and thus to enable more efficient processing.
For this purpose, a special authorization concept was developed for HCM Processes and
Forms with which you can involve all employees in these processes without having to assign
them all of the relevant HR authorizations. This enables shorter implementation times and
reduces the risk of assigning employees incorrect authorizations.
The authorization concept of HCM Processes and Forms separates users’ authorizations to
access specific forms, processes, and attachments from the users’ authorizations to access
HR data in the infotypes of the backend system.

Features
      There are three methods available for checking authorizations. They are defined
      according to the authorization objects that are used in the authorization check:

              Use of the authorization object for HCM Processes and Forms: P_ASRCONT

              Use of the traditional HR authorization objects

              Combination of both methods



             For more information, see Methods for Checking Authorizations [Page 121].




HR Administrative Services (PA-AS)           6956                                         118
SAP Online Help                                                                     22.04.2009


      You specify the required method for checking authorizations in Customizing for HCM
      Processes and Forms. This has the following advantages:

             If you want to use the traditional HR authorization objects, you only need to
             change the existing authorizations for employees, managers, and HR
             administrators if authorizations to read (manager, employee) or change (HR
             administrator) are included for additional infotypes.

             If you use the authorization object P_ASRCONT, you must include the
             authorization object in the profile but you do not need to adjust the previous
             authorizations.

      The authorization checks distinguish between the various activities the user can
      perform. You can assign a method for checking authorizations to each activity.



            Some examples of activities are:

                    Launch Process / Form

                    Read

                    Approve Form

                    Save Application Data



            You set up these authorizations using the traditional HR authorization objects.

                    A – Approve Form

                    P – Process Form

                    X – Save Application Data

      You can assign the methods for checking authorizations to their activities on various
      levels in Customizing. You can thus greatly simplify the assignment of required
      authorization checks and benefit from even greater flexibility when protecting
      especially sensitive data.

             You can specify the method for checking authorizations that is used in the
             process for an activity (see above) that is to be performed.

             You can refine the specified data on the process level. You can group individual
             processes into process groups if necessary. You can then assign a method for
             checking authorizations to these process groups for each activity. This enables
             you to perform a simplified or a strict authorization check for individual
             processes.

             You can group form scenarios into form scenario groups. You can specify the
             activities for which users can be assigned authorizations for these groups in the
             authorization object P_ASRCONT.

             You can also specify the activities for which users can be assigned
             authorizations for attachment types in the authorization object P_ASRCONT.
See also:

      The Implementation Guide (IMG) for Personnel Management under Personnel
      Administration -> Tools -> Authorization Management




HR Administrative Services (PA-AS)          6956                                              119
SAP Online Help                                                                     22.04.2009


      SAP Library under Human Resources          HR Tools     Authorizations for Human
      Resources [External].

      The documentation for the authorization object P_ASRCONT.




      Contexts for Checking Authorizations
Use
You can assign methods for checking authorizations for HCM Processes and Forms to
different contexts. The following overview explains what data you can protect in which
location or at what time if you use the third method of combining traditional HR authorization
objects with the authorization object P_ASRCONT. For more information, see Methods for
Checking Authorizations [Page 121].

Features
When processes are executed or the Process Browser and the Digital Personnel File are
used, the system performs authorization checks during the execution of certain functions. The
functions in question are as follows:

      Process runtime/execution of processes

              Calling a start application

                     Calling a process

                     Calling a form

              Resolution of rules for agent assignment

              Calling a form from a work item

              Saving data from a form to the back-end system

              Approving a form

              Withdrawing a process

      Process Browser:

              Searching for processes

              Displaying the processes found

              Displaying forms for processes found

      Digital Personnel File

              Displaying documents in the Digital Personnel File

              Case Management (in this case you also use the relevant authorization objects
              from Case Management)

      HR Administrative Services: Administrator Workbench (Transaction
      HRASPROCESS_UTILITY)
The following table gives you an overview of the Activities for Checking Authorizations in the
various HCM Processes and Forms contexts



HR Administrative Services (PA-AS)           6956                                           120
SAP Online Help                                                                     22.04.2009


Activities for Checking Authorizations in the various contexts

Application/       Description                         Pro-     Form            Attachment
Trigger                                                cess     Scenario
Select             Selection of a process that can     S
Process            be started
Start Process      Start of a certain process          S        S
Processing         Start of a processing step from              P
Step               the universal worklist
Approval Step      Start of an approval step from               A
                   the universal worklist
Cancellation       Cancellation of a process during    D
Step               a process step
Save               Saving of application data during   X        X
Application        a processing step or background
Data               step
Process            Search for processes and            R        R               R
Browser            displays of step details, forms,
                   and attachments
Digital            Display of forms and                         R               R
Personnel          attachments
File
Case               Display and changing of process     R        R               R
Management         and process step properties,
                   form data containers, and
                   attachments
Administrator      Display of processes, deletion of   R, D     R
Workbench          related objects such as
                   attachments, notes, form data
                   containers



                The authorization checks are not carried out if a work item is transferred or
                delegated to another user. The system will only run an authorization check when
                the new user wants to execute the work item.




      Methods for Checking Authorizations
Use
The following section provides you with an overview of the three methods for checking
authorizations that you can use to protect personal data in HCM Processes and Forms.

Features
For all the methods described below, the system calls the method
CHECK_MIN_PERNR_AUTHORIZATION of the BAdI HRPAD00AUTH_CHECK from the
function module HR_CHECK_AUTHORITY_PERNR, which ensures at least one minimum
check of personal data. The method checks whether access to at least one data record for
the personnel number is possible. The system does not check whether the user is authorized




HR Administrative Services (PA-AS)              6956                                       121
SAP Online Help                                                                      22.04.2009


to access an existing infotype record. It only checks whether the user is authorized to access
any infotype, even if there is no data record for an infotype in the system.
In addition, this method checks the settings you made in the authorization main switches for
HR. The scope of these authorization checks depends on how you have set up the
authorization main switches.



             For more information, see the Implementation Guide for Personnel Management
             under Personnel Administration    Tools    Authorization Management
             Maintain Authorization Main Switches.
             Note: If you have implemented the BAdI HRPAD00AUTH_CHECK (IMG Activity
             BAdI: Set Up Customer-Specific Authorization Check) it is run for HCM
             Processes and Forms.



             Note also that changes made to the authorization main switches have
             implications for the authorization checks in all HR applications. It is strongly
             recommended that you only change the settings after careful consideration of
             the consequences for other applications in SAP Human Capital Management.

Method 1: Exclusive Use of the Authorization Object P_ASRCONT (Authorization for
Process Content)
You can use this method to check access to various process contents. Examples of such
contents are certain forms that are used in processes. You can use the authorization object at
the level of the following process types to specify which activities a user is allowed to perform
on the objects:

       Processes

       Attachments that the system displays through the Digital Personnel File (DPF) or the
       Process Browser

       Form scenarios
      For more information, see Contexts for Checking Authorizations [Page 120].
The authorization object contains a simplified check for personnel numbers that are
accessible by users. You therefore do not need to specify which personnel numbers or
organizational units need to be assigned authorizations to read, write, and so on. Only the
following options are possible:

       Authorization only for the user's own personnel number

       Authorization for all personnel numbers, excluding the user's own number

       Authorizations for all personnel numbers



             For more information, see the documentation for the authorization object
             P_ASRCONT.
             Note that these authorizations for personnel numbers can only be processed in
             connection with the processes in HCM Processes and Forms. They have no
             effect on the access authorizations for employee data in the backend system.
Advantages of the Method

       You can control access to the process contents.

       You do not need to change the existing HR authorizations.



HR Administrative Services (PA-AS)            6956                                            122
SAP Online Help                                                                       22.04.2009


      If you create new processes, forms and so on, you only need to adjust the
      authorization objects if you have set them up for the new process or form groups
      (content types) in Customizing.
Disadvantages of the Method

      You must add the authorization object to the profiles of the roles or users .

Method 2: Exclusive Use of HR Authorizations
In this method you use the traditional HR authorizations that you can activate using the HR
authorization main switches. You can also use this method to check the authorizations for the
forms that the system uses in the processes. The forms are linked to the authorization checks
for the HR infotypes. If the user has no authorization for the data displayed in the form, the
form is displayed without content and with an appropriate error message.
Advantages of the Method

      You do not have to change the existing authorization profiles for the users or roles.

      You can use the HR authorization profiles to control access to the data and personnel
      numbers used in the process.
Disadvantages of the Method

      You cannot control access to the following objects with these authorizations:

             Start application

             Process data

             Forms

             Attachments
      These missing checks can result in users being able to gain unauthorized access to
      process data and attachments at the start of an application if they have the specified
      authorizations for the personnel number and the transaction.

      You must adjust the authorization profile for every new process that you set up if new
      infotypes have been introduced that you did not list previously in the profiles.

      The authorizations that you assign here also apply to access to data in the backend
      system. It can therefore occur that employees with a user in the backend system can
      gain unauthorized access to data in the backend system (in Reporting, for example).

Method 3: Using a Combination of Both Methods
This is the safest method that you can use. It is therefore recommended that you use this
method. In this way, you can combine the advantages of the authorization object
P_ASRCONT with those of the traditional HR authorizations.
Advantages of the Method

      The system checks access to the application objects as well as the contents contained
      in them. You can thus fully protect the data and avoid users accessing processes and
      data for which they have no authorization.
Disadvantage of the Method

      You must add the authorization object P_ASRCONT and the traditional HR
      authorizations to the authorization profiles of the users and roles for the employees
      that use HR Administrative Services .




HR Administrative Services (PA-AS)           6956                                             123
SAP Online Help                                                                    22.04.2009




             Note that you can protect the infotype data in the backend system with settings
             in the workflow. You can specify in the individual workflow steps who can save
             data in the infotypes of the backend system.
      You can avoid this disadvantage by setting up your authorizations and processes in the
      following way:

             Only HR administrators receive authorizations for reading and updating
             backend data. You set up these authorizations using the traditional HR
             authorization objects.
             Other persons involved in the processes, such as employees and managers,
             only receive authorization for processes and forms using the authorization
             object P_ASRCONT.

             When setting up the workflow, you use a standard task that saves data in the
             backend system. You assign a (virtual) processor that has the relevant HR
             authorizations to this standard task.
             The system saves the data in a background step in the backend system. HR
             administrators only receive work items for postprocessing data if an error
             occurs.
      For more information, see Standard Task TS17900100: Edit Form [Page 73] and
      Standard Task TS17900108: Save Form Data [Page 110].
The following settings are recommended:

      Use the authorization object P_ASRCONT to protect process and attachment data
      from unauthorized access. Use the following Activities characteristics in the
      authorization object P_ASRCONT for your employees:

             S – Start Process/Form

             R – Read

             P – Process Form

             D – Withdraw Process
      In addition, add the activity A - Approve Form for your managers and the activity X -
      Save Application Data During a Process for your HR administrators.

      Set up further authorization checks for processes that process particularly sensitive
      data.




      Error Handling
Purpose
This process describes the system behavior when the agent (processor) has executed the
Review and Send function after entering data in a form when executing a process step and
errors occur when the data is subsequently checked. The process flow can differ depending
on the settings in Customizing and in the workflow:

      The agent cannot send the data and complete the work item until he or she has
      resolved the incorrect entries.




HR Administrative Services (PA-AS)          6956                                              124
SAP Online Help                                                                    22.04.2009


      The agent can send the data and complete the work item although errors still exist.

      The agent can forward the work item with the incorrect data to an expert who either
      resolves the errors and returns the work item to the agent, or resolves the errors and
      sends the data, thus completing the work item.

Prerequisites
Workflow Modeling
When modeling the workflow that underlies the relevant process, you have used the standard
task TS17900100 Edit Form. There you can use the SEND_VARIATION and
SEND_EXPERT_IF_INCONSISTENT elements to determine how the system is to behave
when a user has generated error messages due to inconsistent data.
For more information, see the documentation on Standard Task TS17900100: Edit Form
[Page 73].

Customizing
You have performed the IMG activity Assign Possible Processors to Error Categories and
assigned possible experts to the following error categories that can occur:

      Error categories of errors that occurred when saving data synchronously

             Data Collision

             No Authorization

             Inconsistent Data

             Object Is Locked (for background steps only)

             Incorrect Customizing

             All Other Categories

      Error categories of errors that occurred in background steps and when saving data
      asynchronously

             Exception when updating the process object

             Exception when updating the application database

             Exception when forwarding to the expert
For more detailed information, see the Implementation Guide (IMG) for HR Administrative
Services under Configuration of Forms/Processes     Process Configuration   Error Handling
  Assign Possible Processors to Error Categories.


You have performed the IMG activity Enable Withdrawal of Processes if required to do so,
and have specified for the relevant process that the expert can withdraw this process. The
Withdraw Process pushbutton is provided for the expert to do this. For more detailed
information, see the Implementation Guide (IMG) for HR Administrative Services under
Configuration of Forms/Processes      Process Configuration     Error Handling    Enable
Withdrawal of Processes.

Process Flow
  3. The agent navigates to his or her universal worklist (UWL) in the portal and opens a
     work item.
  4. The system opens the corresponding form.



HR Administrative Services (PA-AS)          6956                                             125
SAP Online Help                                                                    22.04.2009


  5. The agent enters the required data in the form.
  6. The agent chooses the Review and Send function.
  7. The system checks the entries against the business logic in the backend system.
  8. The system identifies errors and informs the user of these errors by means of an
     appropriate message. Depending on the error category to which the error is assigned,
     the following process flows are possible:

             Inconsistent Data error category
             Depending on the system settings, the following process flows are possible:

                    The agent corrects the data and chooses Review and Send again. The
                    system checks the entries and sends the work item, for example, to the
                    next agent.

                    The system displays the Continue pushbutton on the user interface. The
                    agent does not correct the data and closes the work item with the
                    incorrect data.

                    The system displays the Forward to Expert pushbutton on the user
                    interface. The agent does not correct the inconsistent data and chooses
                    Forward to Expert. The system forwards the work item to the expert
                    defined in Customizing. This expert corrects the entries. The expert
                    returns the work item to the previous agent by choosing Back to Agent,
                    or sends the work item to the next agent by choosing Review and Send.
                    Depending on the Customizing settings, the expert can also withdraw the
                    process.

             All other error categories for saving data synchronously

                    The agent is unable to resolve the error. The system displays the
                    Forward to Expert pushbutton.

                    The agent chooses Forward to Expert.

                    The system forwards the work item to the expert who is defined in
                    Customizing for the processing of errors for the relevant error category.

                    The expert resolves the error and returns the work item to the agent.
                    Depending on the Customizing settings, the expert can also withdraw the
                    process.

             Error categories of errors that occur in background processes and when saving
             data asynchronously

                    The agent sends the work item and the data is updated asynchronously.
                    If an error occurs, then – depending on the error category – the defined
                    expert is informed of the problem by e-mail.

                    The system saves the data of the process object in the programming exit
                    of the workflow. The data is then saved in the background. If an error
                    occurs, the expert defined for the Exception when updating to the
                    process object error category is informed of the problem by e-mail.




HR Administrative Services (PA-AS)          6956                                           126
SAP Online Help                                                                      22.04.2009



      Design Time for Processes and Forms
Use
You use this tool to create processes and the related objects, for example, workflow template,
form scenarios, and forms, and make the required settings for them.

Features
The following graphic is a schematic representation of the screen areas that Design Time for
processes and forms is subdivided into:


        Object selection area                                   Object processing area




         Object hierarchy area



Object Selection Area
This area contains a dropdown list box that you can use to select the following objects:

       Process
      For more information, see Creation and Configuration of Processes [Page 129].

       Form Scenario
      For more information, see Creation and Configuration of Form Scenarios [Page 144].

Object Hierarchy Area
This area gives an overview of the configuration options for the selected object, in a tree
structure.

Object Processing Area
This area displays the detailed configuration options for a node selected in the object
hierarchy area.

Activities
You can navigate within Design Time in the following ways:



HR Administrative Services (PA-AS)            6956                                            127
SAP Online Help                                                                      22.04.2009


Object Selection Area
      In the dropdown list box, choose Process or Form Scenario.
     The system displays the object that you last displayed or changed, below the dropdown
     list box. In the object hierarchy area, the system displays the related tree structure.
     To adjust the display in the object processing area and the menu for the selected
     object, choose Display or Enter.

      To display a different object, use the input help in the field below the dropdown list box
      to select it, or enter the name of the object and then choose Display or Enter.

      To create a new object, enter a new object name in the field below the dropdown list
      box, and then choose Display or Enter.
     If no object exists with the specified name, the system suggests creating it.

Object Hierarchy Area
      You can access the options for an object in the object processing area from the object
      hierarchy area and adjust the menu for the selected object in the following ways:

             You position the cursor on the relevant node in the tree structure and choose
             Enter.

             You position the cursor on the relevant node in the tree structure and choose
             Display or Change in the context menu.

             You double-click the node in the tree structure.

      To adapt the tree structure in the object hierarchy area to the object that is displayed in
      the object processing area, choose Display Object List.



            You edit process P1. The form scenarios F1 and F2 are assigned to this
            process.
            In the object hierarchy area, you choose P1      <Validity Period> Form
            Scenarios -> F1, and double-click Form. In the object processing area, the
            relevant settings for the form for form scenario F1 are displayed.
            If you now choose Display Object List, in the object hierarchy area, the system
            displays the tree structure for form scenario F1.

      To navigate between the settings that you have made, choose the arrow keys
      (Previous Object or Next Object).



            First you make settings for the workflow template for your process. You then edit
            the role assignment.
            If you now choose       (Previous Object), you go back to the settings for the
            workflow template.       (Next Object) takes you back to role assignment.

Object Processing Area
      In many fields you can double-click to access the Customizing view for creating or
      editing an object.




HR Administrative Services (PA-AS)           6956                                            128
SAP Online Help                                                                        22.04.2009




                 Under <Process Name>       Reference Number for Process, double-clicking
                 takes you to the Template ID field in the Customizing view Defining Template for
                 Reference Numbers of Processes (V_T5ASRRFNUMPAID).

          You can use the structure symbol      to access the linked IMG activities.




          Changing the Initial Screen for Design Time
Use
When you open Design Time, an initial screen is displayed in the right-hand side of the
screen. In the standard system, the system displays the HRASR00_DT_START_PICTURE
image here. You can display your own image instead.

Procedure
...




      1. On your local hard drive, create the desired image in an image format that is configured
         in your ERP system in SAP Web Repository (transaction SMW0).
      2. Import the image as a binary data object into SAP Web Repository in your ERP system.
          Enter ZHRASR00_DT_START_PICTURE as the object name.
For more information, see Web Object Maintenance [External].

Result
When the system finds an image with the name ZHRASR00_DT_START_PICTURE, it
displays this as the initial screen of Design Time. If it does not find an image with this name, it
shows the standard image HRASR00_DT_START_PICTURE.




          Creation and Configuration of Processes
Use
You can use Design Time for processes and forms to create processes [Page 32] and to
make the necessary settings.

Features
Creating a Process
You have the following options for creating a new process:

          You create the process from the beginning.

          You copy an existing process.
          The system copies all settings that you made for the existing process. The assignment
          of the form scenarios to the existing process is transferred for the new process.
          Meaning that you do not create any new form scenarios for the process with this
          option.

          You copy an existing process, including all related objects.



HR Administrative Services (PA-AS)              6956                                           129
SAP Online Help                                                                          22.04.2009


          The system copies all settings that you made for the existing process. In addition, you
          can copy all or individual form scenarios for the existing process and the related forms.
          Meaning that you can simultaneously create new form scenarios and forms for the new
          process with this option.

Editing Validity Periods for a Process
          When creating a new process, you determine a validity period for the process.

          You can create an additional validity period for the same process.
          All time-dependent properties are initial to start with.
          Depending on your entries, the system delimits the existing validity period, or divides it
          into more than one period.

          You can copy an existing validity period.
          This also copies all time-dependent properties of the process.

          You can delete an existing validity period.
          The system deletes all settings for the process that you made dependent on this
          validity period.

Determining Process Properties
          You determine certain process properties depending on the validity period. You can
          create more than one validity period for the same process, and make different settings
          for them.

          Other process properties are independent of the validity period and apply for the entire
          lifetime of the process in the system, without changing.



                 In addition, instead of determining many of the properties of the business
                 process flow directly on the process, you determine them indirectly using the
                 following involved components:

                                 Form scenario [Page 37]

                                 Workflow template (in the workflow steps; see Business Workflow
                                 for HCM Processes and Forms [Page 60])

                                 Start application [Page 38]

                                 Form application [Page 42]

Activities
Creating a Process Using the Object Selection Area
...
...




      1. In the object selection area, in the dropdown list box, choose Process.
      2. Enter a technical name for the process, and choose Enter.

Creating a Process Using Menu or Context Menu
...




      1. Double-click <process name> in the object hierarchy area to select an existing process.
      2. In the menu, choose Process         Create, or in the context menu Create.

Editing Validity Periods Using Menu or Context Menu
...




HR Administrative Services (PA-AS)                 6956                                          130
SAP Online Help                                                                      22.04.2009


  1. Double-click <validity period> in the object hierarchy area to select an existing validity
     period.
  2. In the menu, choose Process, or in the context menu, choose the required option.

Determining Process Properties
For more information, see Validity-Period-Dependent Settings for a Process [Page 134] and
Validity-Period-Independent Settings for a Process [Page 131].




      Validity-Period-Independent Settings for a Process
Use
You use this function to determine all data for a process that is independent of a validity
period.

Features
You determine the following settings as independent of a validity period:

       Basic settings:

              Name and description of process

              Setting to permit the process to be run more than once in parallel

              Settings for withdrawing the process

              Process group for the authorization check

              Defaults for generating the reference numbers when running the process

       Transfer of field values between form scenarios of the process

       Transfer of attachments between form scenarios of the process

Activities
       To make the basic settings, in the object hierarchy area, choose <Process Name> and
       enter the following in the object processing area:

              Name of the process

              Description of the process

              Permit Parallel Run indicator (see Restrictions for Starting a Process [Page
              139])

              Settings for Withdrawing a Process [Page 132]

              Process group for the authorization check
             For more information, see Authorization Concept of HCM Processes and Forms
             [Page 118] and the Implementation Guide (IMG) for HR Administrative Services,
             under Authorizations.

              Pattern ID for generating the reference numbers when running the process
             For more information, see the IMG for HR Administrative Services under
             Configuration of Forms/Processes     Process Configuration    Set Up
             Processes     Reference Numbers for Processes.


HR Administrative Services (PA-AS)            6956                                            131
SAP Online Help                                                                     22.04.2009


      To make the settings for transferring the field values, choose <Process Name>
      Transfer of Field Values in the object hierarchy area.
      For more information, see Transfer of Field Values Between Form Scenarios of a
      Process [Page 132].

      To make the settings for transferring the attachments, choose <Process Name>
      Transfer of Attachments in the object hierarchy area.
      For more information, see Transfer of Attachments Between Form Scenarios of a
      Process [Page 134].




      Settings for Withdrawing a Process
Use
You use this function to set who is informed when a process is withdrawn. The process
initiator can always withdraw a process. Depending on the workflow settings, the other
process processors can also withdraw the process. If necessary, experts can also withdraw a
process.

Features
      You determine which process processors are informed when a process is withdrawn.

      You determine whether an expert can always withdraw the process to correct errors,
      regardless of the modeling of the individual workflow steps.

Activities
In the object hierarchy area, choose <Process Name> and make the following settings in the
object processing area.

      To determine whether only the process initiator and HR Administrator are informed, or
      whether other process processors are also informed, proceed as follows:
...




         a. Go to the IMG activity Activate Workflow After Withdrawing Process and activate
            the required workflow template.
         b. Go back to Design Time for processes and forms.
             The system displays your settings in the Notifications field.
         c. If you have activated the workflow template with which the additional processors
            can be informed, choose Additional Roles and enter the desired processor roles.

      If required, set the If Errors Occur Expert Can Withdraw Process indicator.




    Transfer of Field Values Between Form Scenarios
of a Process
Use
If you use more than one form scenario in a process, you use this function to determine for
which fields values are transferred between the form scenarios.




HR Administrative Services (PA-AS)           6956                                         132
SAP Online Help                                                                        22.04.2009


If more than one form scenario is assigned to a process, they are processed independently of
each other. If you want to transfer data from one form scenario into another, you must define
an appropriate assignment of the form fields of the source and target form scenarios.

Prerequisites
You use more than one form scenario in your process.

Features
      If the target form scenario is edited in the process, the system copies the values for the
      fields for which you have defined an assignment from the source form scenario. The
      source form scenario therefore provides default values for the target form scenario.

      If you have defined additional default values for the target form scenario manually, or
      using back-end services, these are not taken into account. The values copied from the
      source form scenario have precedence in all cases. This also applies to any initial
      values that are copied from the source form scenario.

      The field values are filled in the target form scenario when the fields become relevant
      for the first time. A field that is already relevant in the first step of the target form
      scenario is also filled with the value from the source form scenario when the target
      form scenario is called for the first time. A field that is not relevant until a subsequent
      step is not filled until the step is actually processed.



             In contrast to the target form scenario, it is not necessary to enter the version of
             the source form scenario. The version of the target form scenario is required
             because the field assignment can be version dependent.
             You do not need to specify the version of the source form scenario as it can only
             ever be used in one version at the process runtime. When copying the field
             values, the system simply copies the data from the existing version of the source
             form scenario.

Activities
In the object hierarchy area, choose <Process Name>         Transfer of Field Values, and enter
the following:

      Target form scenario

              Name of the form scenario

              Version of the form scenario

              Name of the field that is to accept the value from the source form scenario

      Source form scenario

              Name of the form scenario

              Name of the field that is to provide the value for the field of the target form
              scenario
Repeat for all form scenarios and fields within the process in which values are to be copied.




HR Administrative Services (PA-AS)            6956                                              133
SAP Online Help                                                                      22.04.2009



    Transfer of Attachments Between Form Scenarios
of a Process
Use
If you use more than one form scenario in a process, you use this function to determine which
attachment types are transferred between the form scenarios.
If more than one form scenario is assigned to a process, they are processed independently of
each other. If you want to transfer attachments from one form scenario into another, you must
define an appropriate assignment of the attachment types of the source and target form
scenarios.

Prerequisites
       You use more than one form scenario in your process.

       You use the same attachment types in these form scenarios.

Features
The features are the same as in Transfer of Field Values Between Form Scenarios of a
Process [Page 132].

Activities
In the object hierarchy area, choose <Process Name>        Transfer of Attachments, and enter
the following:

       Target form scenario

              Name of the form scenario

              Version of the form scenario

              Attachment type whose attachments are to be transferred from the source form
              scenario

       Source form scenario

              Name of the form scenario
Repeat the entries for all form scenarios for which attachment types are to be transferred.




      Validity-Period-Dependent Settings for a Process
Use
You use this function to determine all data for a process that is dependent on a validity period.

Features
You determine the following settings as dependent on a validity period:

       Settings for the start step of the process

              In the start step, you can show the Forward to Experts pushbutton.




HR Administrative Services (PA-AS)            6956                                            134
SAP Online Help                                                                     22.04.2009


             You can determine how the system reacts when the processor wants to close
             the start step but the entered data is not complete or is incorrect.

             You can determine whether the process can be run without a start object, for
             example, without specifying a personnel number.



             For example, this setting is useful for a process for hiring new employees. You
             determine the personnel number of the employee during the process, and not
             before the process start.



             If you set the No Start Object indicator for a process, you can only assign
             process groups to it that also have this indicator set. For more information, see
             Grouping Processes in Groups [Page 138].

      Assignment of a workflow template to the process

      Assignment of roles to the process

      Assignment of the process to one or more groups

      Restrictions for starting the process

      Assignment of form scenarios to the process

Activities
      To make the settings for the start step, choose <Process Name>        <Validity Period>
      in the object hierarchy area.

      To make the additional period-dependent settings, choose <Process Name>
      <Validity Period> in the object hierarchy area, and then the relevant node.
      For more information, see:

             Assignment of a Workflow Template to the Process [Page 135]

             Assignment of Roles to a Process [Page 137]

             Grouping Processes in Groups [Page 138]

             Restrictions for Starting a Process [Page 139]

             Assignment of Form Scenarios to a Process [Page 143]




   Assignment of a Workflow Template to the
Process
Use
You use the workflow template to make the following settings for your process:

      You use the workflow definition in the Workflow Builder to determine which process
      steps follow one other.

      You use the rules for determining processors to set which user receives which process
      step for processing.



HR Administrative Services (PA-AS)            6956                                          135
SAP Online Help                                                                          22.04.2009


          You use the standard tasks that the individual workflow steps are based on to
          determine the following:

                 which form is used in which process step

                 which interface functions (for example, pushbuttons Save Draft or Withdraw
                 Process) are available in the individual process steps

Prerequisites
          In Customizing for SAP NetWeaver, under Application Server   Business
          Management      SAP Business Workflow, you have set up the workflow runtime
          environment.

          You have made the settings for standard components and workflows in Customizing
          for HR Administrative Services under Configuration of Forms/Processes  Process
          Configuration.

Features
          You can assign an existing workflow template that you previously created in the
          Workflow Builder.

          You can create a new workflow template for your process.

          You can reconcile the form scenarios of the process with the form scenarios of the
          workflow template. For more information, see Assignment of Form Scenarios to a
          Process [Page 143].

Activities
To create a new workflow template, choose <Process Name>             <Validity Period>
Workflow in the object hierarchy area, and proceed as follows:
...




      1. Choose Create Workflow Template.
          From Design Time, the Workflow Builder appears.
      2. In the Workflow Builder, define your workflow template.
          You can use the following standard objects:

                 Standard workflow template [Page 71] as a copy template for your own
                 workflow template

                 Standard tasks [Page 73] for HCM Processes and Forms

                 Agent Determination Rules [Page 68] for HCM Processes and Forms
      3. Return to Design Time for processes and forms, and generate the event type linkage
         for your workflow template here.



                When creating your workflow template, note the restrictions when modeling
                workflows [Page 113] for HCM Processes and Forms.




HR Administrative Services (PA-AS)             6956                                            136
SAP Online Help                                                                             22.04.2009



      Assignment of Roles to a Process
Use
You use this function to determine the processes that are available to a user for the start on
the user interface, depending on his or her role.



              You do not explicitly determine the other processor roles for the remaining
              process steps for the process; this is done implicitly by the workflow template
              that you assign to the process. For more information, see Assignment of a
              Workflow Template to the Process [Page 135].

Features
       You can assign one or more initiator roles to your process. The processes defined in
       this way are then available to the user that is assigned this role.

       You can determine that the specified initiator role can only start the process for certain
       object groups, for example, certain groups of employees.
      You can control the display of the processes such that the user can perform only those
      processes for an employee that are relevant for the employee because the employee
      belongs to a certain grouping.



              Even if the user can run the process, you can set certain restrictions for the
              process start. For more information, see Restrictions for Starting a Process
              [Page 139].

Activities
       When creating a new process, you can directly determine an initiator role for the
       process.

       To set restrictions for this initiator role or to assign additional initiator roles to your
       process, choose <Process Name>              <Validity Period>    Process Start        Role
       Assignment, in the object hierarchy area, and enter the following:
...




         a. Enter the initiator role(s).
         b. Set a restriction to certain object groups for an initiator role, as required.
          c. If you want to set a restriction, click on the Object Groups field to enter the
             desired object group.
         d. If you want to create a new object group, proceed as follows:
                  i.    Double-click on the Object Group field in the Object Group Assignment
                        dialog box to go to the view for creating new object groups.
                 ii.    Create the object group here.
                 iii.   Return to the Change Object Group Assignment dialog box and branch to
                        the feature for determining the object group.
                iv.     Use the feature to determine which objects are included in the object
                        group.
      For more information about restricting to certain object groups, see Restrictions for
      Starting a Process [Page 139].




HR Administrative Services (PA-AS)               6956                                                137
SAP Online Help                                                                   22.04.2009



      Grouping Processes in Groups
Use
You can group more than one process that have the same conditions or that you want to
process together into a group.

Features
      Process groups
      You can use process groups to group processes that are displayed on the user
      interface. The processes that belong to the same process group are displayed together
      in the start application that this process group is assigned to.

      Collision groups
      You can use collision groups to group processes to check processes for collisions with
      the grouped processes.

      Groups for authorization checks
      You can group processes for which the same authorization checks are made into an
      authorization group.

Activities
      Process groups

             In the object hierarchy area, choose <Process Name>       <Validity Period>
             Process Start     Assignment to Process Groups

                    To assign your process to a process group for being displayed on the
                    user interface, enter the desired process group(s).

                    To create a new process group, double-click the Group field to go to the
                    view for creating process groups.



            The No Start Object indicator displays whether the processes from the specified
            process group can be run without specifying a start object. You do not make this
            setting in Design Time; you make it in Customizing for HR Administrative
            Services, under Configuration of Forms/Processes      Process Configuration
            Set Up Processes     Process Groups      Enable Process Start Without Start
            Object Selection.
            You can also set the indicator for an individual process. For more information,
            see Validity-Period-Dependent Settings for a Process [Page 134].
            If you have set the indicator for a process, you can only assign process groups
            to it that also have this indicator set.

      Collision groups
      For more information, see Collision Checks for a Process [Page 141].

      Groups for authorization checks
      For more information, see Validity-Period-Independent Settings for a Process [Page
      131].




HR Administrative Services (PA-AS)          6956                                           138
SAP Online Help                                                                      22.04.2009



      Restrictions for Starting a Process
Use
You use this function to determine that your process, depending on the situation, can only be
performed under certain conditions or not at all.

Features
      Restriction on initiator roles
      You can determine that only users that are assigned a particular initiator role, for
      example only managers, can run the process.

      Restriction on object groups
      You can determine that the initiator role can only run the process for certain groups of
      objects, for example, employees from a particular country.

      Parallel run of a process
      If you want to run a process that was already run for the same object, for example, the
      same employee, and this process is not yet completed, the system issues an error
      message by default. You can change this system response for your process and permit
      the process to be run more than once in parallel.



             It can be useful to permit a process to be run more than once in parallel, for
             example, a process that employees can use to request leave. This prevents
             employees from having to wait until their leave is approved and the process is
             completed before they can create their next leave request.

      Conditions for starting a process
      You can use the BAdI HRASR00PROCESS_START_RESTRICT to set conditions
      under which a process can be started.



             For example, for the Maternity Leave process, you can set the condition that
             only female employees can run this process.

      Frequency restriction
      You can determine how often a process can be run for the same object, for example,
      the same employee.

      Collision check
      You can determine that a process cannot be run while certain other processes are
      running for the same object.

Activities
Determining Restrictions
      Restriction on initiator roles
      For more information, see Assignment of Roles to a Process [Page 137].

      Restriction on object groups
      For more information, see Assignment of Roles to a Process [Page 137].



HR Administrative Services (PA-AS)           6956                                            139
SAP Online Help                                                                          22.04.2009


          Parallel run of a process
         To enable your process to be run more than once in parallel, in the object hierarchy
         area choose <Process Name> and under Executability of the Process, set the Permit
         Parallel Run indicator.

          Conditions for starting a process
         To set the conditions, choose <Process Name> in the object hierarchy area. Under
         Executability of the Process, branch to the editing of the BAdI
         HRASR00PROCESS_START_RESTRICT and create an implementation for the BAdI.
         For more information, see the documentation on the BAdI. To display the
         documentation, branch to the IMG activity Determine Restrictions for Starting
         Processes.

          Frequency restriction
         For more information, see Frequency Restrictions for a Process [Page 142].

          Collision check
         For more information, see Collision Checks for a Process [Page 141].

System Check of Determined Restrictions
When a user wants to run a process for a certain object, for example, a particular employee,
in the list of processes that can be run, the system displays only those processes for which
the following conditions apply:

          The processes can be run by the initiator role that is assigned to the user.

          The processes can be run for the object group (for example, country grouping) to
          which the object (for example, the employee) belongs.
         To determine the object group that the selected object belongs to, the system
         evaluates the feature for object group determination. For more information, see
         Assignment of Roles to a Process [Page 137].
The system then checks whether there are additional restrictions, in the following sequence:
...




      1. In the standard system, the system checks whether the same process was already
         started for the same object and is not yet completed.
         Depending on the result, the system proceeds as follows:

                 If the process was already started and is not yet completed, the system issues
                 an error message.

                 If the process was not started, the system continues with the check in step 2.



                If you have set the Permit Parallel Run indicator for the process, the system
                skips this check.
      2. The system checks whether the BAdI HRASR00PROCESS_START_RESTRICT has
         been implemented for the process.
         Depending on the result, the system proceeds as follows:

                 If the BAdI is implemented, the system opens the BAdI method. The method
                 returns the parameter IS_PROCESS_EXECUTABLE that determines whether
                 the process can be run or not.

                        If the process cannot be run, the system displays the error message
                        The conditions for starting the process are not met.



HR Administrative Services (PA-AS)               6956                                           140
SAP Online Help                                                                      22.04.2009


                      If the process can be run, the system continues with the check in step 3.

              If there is no implementation, the system continues with the check in step 3.
  3. The system checks whether there is a frequency restriction for the process.
      Depending on the result, the system proceeds as follows:

              If the process cannot be run, the system displays the error message The
              maximum number of instances for the process start has been reached.

              If the process can be run, the system continues with the check in step 4.
  4. The system checks whether the process would collide with another process.
      Depending on the result, the system proceeds as follows:

              If there is a collision, depending on your settings, the system displays an
              information, warning, or error message.

              If there is no collision, the system runs the process.




      Collision Checks for a Process
Use
You use this function to determine whether your process is part of a collision check. During
the collision check, the system checks whether the process is allowed to start after a different
process was started for the same object, for example, the same employee.

Features
       You can determine the running processes that a process may not collide with.

       You can determine the completed processes that a process may not collide with.

       You can determine whether the system displays an information, warning, or error
       message when there is a collision. The system reacts as follows:

              Information
              A message appears drawing the user’s attention to the collision. The process
              can still be run.

              Warning
              A message appears warning the user that he or she has called a process that is
              not permitted. The process can still be run.

              Error
              An error message appears. The process cannot be run.

       You can mark a process as relevant for the collision check. Meaning that you assign a
       collision group to the process. This allows you to check whether other processes
       collide with the process.

Activities
Determine Collision Checks for a Process
In the object hierarchy area, choose <Process Name>          <Validity Period>   Process Start
    Collision Definition, and make the following settings:


HR Administrative Services (PA-AS)             6956                                           141
SAP Online Help                                                                         22.04.2009

...




      1. Specify the collision group that contains the processes with which your process may not
         collide.
      2. Determine how the system reacts when there is a collision with the processes from the
         collision group.
      3. To also include completed processes in the collision check, set the Include Completed
         Processes indicator.

Define Process As Relevant for the Collision Check
In the object hierarchy area, choose <Process Name>     <Validity Period>           Process Start
   Assignment to Collision Groups, and make the following settings:

          Assign the desired collision group to your process.

          To create a new collision group, double-click the Collision Group field to go to the view
          for creating process groups.

Example
You want to stop more than one process for changing the organizational assignment of an
employee being run at the same time.
Create the collision group ORG. You assign all processes that change the organizational
assignment of an employee to the group ORG. This marks these processes as relevant for
the collision check.
Then you assign this group as a collision group to each individual process from the group
ORG. You determine that the system issues an error message if there is a collision with
running processes of the group.
If a user now wants to start a process from the ORG group, the system checks whether a
different process from the group is already running for the same employee. If this is the case,
the system displays an error message. The user cannot run the process until the other
process with which it collides is completed.




          Frequency Restrictions for a Process
Use
You use this function to determine how often a process can be run for the same object, for
example, the same employee.

Features
You can determine the following restrictions:

          The process can be run any number of times.

          The process cannot be run if it was run one or more times within a certain period that
          is before the desired process start.

          The process cannot be run if it was run one or more times within a certain period that
          contains the desired process start. The period is calculated as an interval that regularly
          repeats itself as of a set date.



                You set the interval as four weeks, the start date as January 1, 2007, and the
                frequency as 1 Time. You want to run the process on March 6. March 6 is in the



HR Administrative Services (PA-AS)               6956                                           142
SAP Online Help                                                                      22.04.2009


             third four-week interval since January 1. If this process was already run in this
             interval, for example on February 28, it cannot be run on March 6.

       The process cannot be run if it was run one or more times within a certain period from
       a fixed start date.

Activities
In the object hierarchy area, choose <Process Name>       <Validity Period>      Process Start
    Frequency Restriction, and make the required settings.
To transfer the entries that you made in a field to the area Result of the Selected Setting,
choose Enter.




      Assignment of Form Scenarios to a Process
Use
Each process must be assigned at least one form scenario.
You can, however, assign more than one form scenario to a process. A process is usually
based on more than one form scenario if the processor is to receive the specific steps of
different forms (that is, entry screens). A process can also consist of several separate units
that are realized through separate form scenarios.

Activities
Form Scenario for Process Start
...




To assign the start form scenario to the process, you can proceed as follows:

       Determine start form scenario when creating the process
      When you create a new process, in the dialog box you can directly assign the form
      scenario that is used when the process starts.
      This form scenario is then displayed in the object hierarchy area of the process, under
      <Process Name>       <Validity Period>    Form Scenarios. It is indicated by a symbol
      with a one (1).
      The start form scenario is also displayed in the object processing area in the group box
      Form Scenario for Process Start (Start Step).

       Determine start form scenario after creating the process
      If you did not assign a start form scenario when you created the process, in the object
      hierarchy area choose <Process Name>         <Validity Period>   Form Scenarios and
      enter the form scenario in the object processing area in the group box Form Scenario
      for Process Start (Start Step).

       Determine scenario step of start form scenario
      To also determine which scenario step of the start form scenario to use, choose
      <Process Name>        <Validity Period>   Form Scenarios and enter the scenario step
      in the object processing area in the group box Form Scenario for Process Start (Start
      Step).

Other Form Scenarios
To assign other form scenarios to the process, you can proceed as follows:

       Assign existing form scenarios



HR Administrative Services (PA-AS)            6956                                             143
SAP Online Help                                                                     22.04.2009


         a. In the object hierarchy area, choose <Process Name>         <Validity Period>
            Form Scenarios.
         b. In the object processing area, under Other Form Scenarios of Process, enter the
            desired form scenarios.

       Create and assign new form scenarios
...




         a. In the object hierarchy area, choose <Process Name>         <Validity Period>
            Form Scenarios.
         b. In the menu or context menu, choose the option Create and proceed as
            described under Definition of Form Scenarios [Page 145].



              Alternately, you can also choose Form Scenario in the object selection area and
              then create the form scenarios. Then, in the object selection area, choose
              Process to assign the form scenarios to the process.
          c. In the object processing area, under Other Form Scenarios of Process, enter the
             newly created form scenarios.

       Use form scenarios of workflow template
...




         a. In the object hierarchy area, choose <Process Name>         <Validity Period>
            Form Scenarios.
         b. In the object processing area, choose the Reconcile with Workflow pushbutton.
              The system adds all form scenarios to the process that were used in the
              workflow template of the process.




      Creation and Configuration of Form Scenarios
Use
The Design Time for Processes and Forms provides you with all functions for creating a new
form scenario [External] and editing the settings for an existing form scenario.
In the object selection area of Design Time, you have two options for creating or editing a
form scenario: either using the Process option, or directly using Form Scenario.

Integration
If you use Process in the object selection area to access Design Time for Processes and
Forms, you can display and edit the settings for the process and for the related form
scenarios. In the Form Scenario area you can directly display and edit the settings for form
scenarios and forms.

Features
You can make the following settings for the form scenario:

       Definition of form fields

       Creation and editing of form

       Definition of scenario steps

       Configuration of back-end services
You can also define the following additional properties for a form scenario:



HR Administrative Services (PA-AS)           6956                                             144
SAP Online Help                                                                     22.04.2009


      Attachment types

      Links for additional information

      Rules

      User events

      Message mapping

Activities
You have the following options for creating a form scenario:

      You create a fundamentally new form scenario.

      You copy an existing form scenario.
Proceed as described in the following sections.




      Definition of Form Scenarios
Use
You use this function to create the basic data for a form scenario [External]. Form scenarios
are version dependent, which means that there is at least one version of each form scenario.
You need this version for assigning a form scenario to a process.
Since processes can vary, you must also be able to adjust the associated form scenarios. In
this case, you can create a new version of the assigned form scenarios, to which you can also
assign new forms.



              As soon as a version is used for running a process, you should no longer
              change this version under any circumstance. Create a new version instead.
For technical reasons, it is necessary to create an ISR scenario that corresponds to the form
scenario, so that there is always a 1:1 relationship between a form scenario and an ISR
scenario. The ISR scenario is used to integrate the interactive form and to create the form
layout.

Activities


              When you create a completely new form scenario, the system first creates
              version 0. If you want to revise the form scenario later, you can either make
              these changes in the existing version, or create a new version. The system
              automatically creates the new version with the next free number.
              If you have already made extensive Customizing settings for the form scenario
              and want to create a new version based on these settings, you should copy this
              form scenario version.

      You create the form scenario with a name and a description.

      You enter a name for the ISR scenario.

      You enter a name for the form. If you choose Suggest Names (pushbutton), the
      system generates the name using the format Z_ISR_HRARS_<form scenario>. If you
      assign the name yourself, make sure that it is within the customer namespace.


HR Administrative Services (PA-AS)           6956                                             145
SAP Online Help                                                                        22.04.2009


       The system opens a dialog box. You can confirm whether to create the form and the
       interface.

       On the Change Form Scenario screen, make the following entries:

              You enter a form scenario group for the authorization check.

              You enter an anchor number for storing the form in the Digital Personnel File
              after running the process.

       The system displays the administration information for the form scenario.

       When you save the form scenario, the system automatically generates the ISR
       scenario.




      Definition of Form Fields
Use
You use this function to create all form fields [External] that are relevant for a form scenario
[External].
This includes fields that appear on the form for the input or output of data, as well as fields
that do not appear on the user interface and are used solely to transport data.
Some form fields are mandatory. Such mandatory form fields for processes that affect the HR
master data are, for example, PERNR (personnel number) and EFFECTIVE_DATE (effective
date). Depending on the back-end service used, there can be other mandatory form fields.
For an overview of the mandatory fields for the back-end services provided with the standard
system, see:
Settings for Back-End Service SAP_PA [Page 153]
Settings for Back-End Service SAP_PT [Page 157]
Settings for Back-End Service SAP_PD
[Page 160]



              If you no longer need a form field, remove it from the form and delete it from the
              form scenario version. Otherwise this field is still processed in the back-end
              system.

Features
The definition of a form field comprises the following settings:

       Field name

       Name

       Field attribute
      The field attribute determines the properties of a field.
      You can determine the field properties for each field that you use in an interactive form.
      You have many attributes available, such as Editable. This means that the field
      appears on the form and you can make entries in it.
      When processing the form layout, you must use the correct ISR control element for the
      form. The system checks whether this is the case, and displays the result of the check
      in the Form column.


HR Administrative Services (PA-AS)             6956                                               146
SAP Online Help                                                                        22.04.2009


       Default value
      Form fields can be filled with default values. You specify for each form field whether it
      has a default value. For fields with default values, you can decide whether the default
      value is defined manually or determined using a back-end service. You can use a radio
      button to select the sequence number of the back-end service under which you defined
      it in the form scenario.

       Input help
      For each form field, you enter whether there is an input help (type of input help). You
      can either enter the possible values of the input help manually, or they can be
      determined using one or more back-end services.

       Collision check
      Switching on the collision check for a form field means that suitable checks are made at
      the process runtime that ensure that the part of the back-end system linked with the
      form field remains unchanged.

       Data binding
      You specify the type of each form field using a data element. You can do this in one of
      two ways:

              Manually by entering a data element explicitly

              Automatically by linking the form field to a back-end service field
      You usually link the form fields to the fields of one or more back-end services. In this
      way, the data saved in the form field is forwarded to the back-end service where it can
      be processed. For more information, see "Configuration of Back-End Services".
      For form fields that are not linked to a field of a back-end service, you always have to
      enter the data element manually.



              You can use form fields as parameters in rules to control whether a back-end
              service is called or whether a specific operation of this service is called. For
              more information, see Definition of Rules.

Activities
       The system creates mandatory form fields for the back-end service.

       You create all specific form fields and define their properties.

       To define the user interface for the form, use controls (input fields, dropdown lists,
       radio buttons, and so on). You must link these controls to the form fields. For more
       information, see Editing the Form Layout [Page 147].




      Editing the Form Layout
Use
You use this function to create the interactive form with all fields that are to be available on
the form, and edit the layout in Adobe LiveCycle Designer. This Form Builder software is
integrated into the SAP environment and is provided by Adobe Systems Inc.
You can:


HR Administrative Services (PA-AS)             6956                                             147
SAP Online Help                                                                           22.04.2009


          Insert the control element Web Dynpro Script
          The element hides Adobe menu bars and sets the form fields so that they cannot be
          edited if the form is checked after processing.

          Create a header row for the form

          Create form fields with data binding

          Create form fields for displaying and editing agent notes

          Create date fields

          Create the Update Data pushbutton, which updates the data in the form according to
          the selected date

          Display a form preview
For basic information about working with Adobe LiveCycle Designer, see the Layout tab page
in the menu, under Help    Adobe Designer Help.
For specific information about creating an interactive form, also see Creating and Editing
Interactive Forms [Page 50].

Procedure


                 The following section lists the steps that you typically perform in the Form
                 Builder, but that you do not have to perform for each form.

Inserting the Control Element Web Dynpro Script
...




      1. At the right-hand side of the Form Builder, change from the Library tab page to the ISR
         Controls tab page.
      2. In the menu, choose Utilities     Insert Web Dynpro Script
      3. Save your entries.

Creating the Header Row
...




      1. Select the ISR Header element on the ISR Controls tab page and use drag and drop to
         drag it to the top of the form.
      2. Enter a text for the form header.
      3. Save your entries.

Creating Form Fields with Data Binding
Proceed as follows for each form field:
...




      1. At the right-hand side of the Library tab page, choose the appropriate HR control
         element and use drag and drop to drag it onto the form.
      2. In the left-hand area of the Form Builder, choose the Data Overview tab page.
          At the end of the structure, all form fields created in the form scenario are displayed.
      3. Select the desired form field and expand it to the FIELD subelement.
      4. Select the FIELD element and use drag and drop to place it exactly on the ISR text
         element in the form.
      5. In the Binding Properties dialog box, select the Do Not Update Related Properties
         option.




HR Administrative Services (PA-AS)                6956                                               148
SAP Online Help                                                                             22.04.2009


       6. In this way, the UI element is linked to the form field and is filled with data automatically
          at the process runtime.
       7. Enter a text for the form field.
       8. Check the correct binding to the form field as required.
              a. In the right-hand area, choose the Object tab page, and from there the Binding
                 tab page.
              b. Check the value entered for the standard binding. This value must have the
                 format $record.<Field Name>.DATA[*].FIELD, where <Field Name> is the name
                 of the form field.
       9. Repeat steps 1 through 8 until you have created all form fields.
      10. Save your entries.

Creating Form Fields for Agent Notes
...




       1. At the right-hand side of the Form Builder, change from the Library tab page to the
          Controls tab page.
       2. Use drag and drop to drag the HR Admin - Comments element onto the form and
          position it at the bottom of the page.
       3. Enter a text for the form field.
       4. Drag the form field on the form to the required size (height and width).
       5. Switch to the Data Overview tab page.
              a. Select the field HRASR_CURRENT_NOTE and expand it to the FIELD
                 subelement.
              b. Select the FIELD element and use drag and drop to move it onto the ISR control
                 element in the form.
              c. In the Binding Properties dialog box, choose the Do Not Update Related
                 Properties option.
                  In this way, the text area is linked to the field HRASR_CURRENT_NOTE and
                  the notes entered are automatically processed correctly at runtime.
       6. Perform steps 1 to 5 in the same way for the field HRASR_PREVIOUS_NOTES.
           The system automatically sets this field so that it cannot be edited.
       7. Save your entries.

Creating a Date Field
...




       1. At the right-hand side of the Form Builder, change from the Library tab page to the
          Controls tab page.
       2. Use drag and drop to drag the HR Admin - Date Field element onto the form and
          position it on the page.
       3. On the left-hand side of the Form Builder, on the Data Overview tab page, select the
          EFFECTIVE_DATE form field.
       4. Select the FIELD element and use drag and drop to place it exactly on the ISR control
          element in the form.
       5. In the Binding Properties dialog box, choose the Do Not Update Related Properties
          option.
           In this way, the UI element is linked to the form field and is filled with data automatically
           at the process runtime.
       6. Enter a text for the date field.




HR Administrative Services (PA-AS)                 6956                                             149
SAP Online Help                                                                          22.04.2009


      7. If required, check the correct binding to the form field as described in step 8 of the
         “Creating Form Fields with Data Binding” section.
      8. Save your entries.

Creating Pushbutton for Updating Data
...




      1. At the right-hand side of the Form Builder, change from the Library tab page to the
         Controls tab page.
      2. Use drag and drop to drag the HR Admin - Button element onto the form (for example,
         to the right of the date field).
      3. Enter the text Update Data for the pushbutton.
      4. Choose Pallets    Script Editor. In Script Editor, the scripting row relevant for the
         pushbutton is selected:
          $record.CONTROL_PARAM.ISR_EVENT = "CUSTOM_EVENT"
      5. Replace “CUSTOM_EVENT“ with “USER_EVENT_INITIALIZE“ or
         ”USER_EVENT_CHECK“, or another event.
      6. Save your entries.
      7. Activate the form:
          In the following dialog box, select the SFPF <Form> form and the SFPI <Interface>
          interface, and choose Activate.

Displaying a Form Preview
...




      1. Choose the PDF Preview tab page.
          You see a preview of the form in which you can see, for example, whether the display
          and processing fields were correctly defined.
      2. Complete the processing in the Form Builder.

Result
You have created the form with all necessary fields and elements, and have activated the
form and the interface.




          Definition of Scenario Steps
Use
You use this function to define scenario steps [External]. You need scenario steps if the form
configuration is not to be processed as a whole at the runtime of the process, rather that
depending on the process step involved, different parts of the form configuration are relevant.
You assign scenario steps to a workflow step when defining the process. Only the back-end
services and operations that belong to the scenario step, and all previously processed
scenario steps that were not saved are run at runtime.

Features
          A form scenario [External] can consist of several steps; however, at least one step
          must exist. You can use a number to determine the step sequence of the scenario
          steps.




HR Administrative Services (PA-AS)                6956                                            150
SAP Online Help                                                                        22.04.2009


      You can use attachments and links for additional information on the form depending on
      steps. This means that for each scenario step you can define which attachments and
      which links are available.

      Depending on the step, you can configure the properties of attachments.

      You assign the form fields [External] that are relevant for this step to scenario steps. A
      scenario step therefore represents a subset of the defined form fields. As the form
      fields are assigned to back-end services, a scenario step also represents a subset of
      the fields and operations defined for the back-end services.
      If you do not explicitly assign a form field to a step, all form fields are understood to be
      assigned and therefore relevant for the step.
      The assignment of form fields is relevant at runtime, but is also enhanced with the
      following mechanism:
      During the processing of the process, the form fields that were used in each step are
      internally documented for the step. Each form field that was used in a step is then
      automatically also used in all subsequent steps. This additive approach means that the
      following fields are relevant in a scenario step i:

              All form fields that are assigned to the scenario step i in the Customizing of the
              form scenario

              All form fields that were relevant at runtime in the previous scenario step i-1

      Depending on the step, you can configure the field properties of form fields.

      You can display an overview of the back-end operations that are run based on the field
      assignment.

Activities
      For each form scenario that you create, the system creates a default scenario step.

      You should use easily identifiable labels for the scenario steps, since they are used in
      the workflow to create the text of the work item and appear under this name in the
      universal worklist (UWL) of the next processor.

      You define the attachment types to use in the scenario step, and their properties.
      For more information, see Definition of Attachment Types [Page 167].

      You define links for additional information on the form.
      For more information, see Creation of Links for Additional Information [Page 168].

      You determine which form fields are relevant in the scenario step and define the field
      properties depending on the step.




      Configuration of Back-End Services
Use
Back-end services provide the business logic that can be used in the form scenarios. To have
data transferred to the back-end services, you link the form fields to the back-end services.
You use this function to determine which back-end services are used in the form scenario and
assign form fields to the back-end services.




HR Administrative Services (PA-AS)            6956                                              151
SAP Online Help                                                                       22.04.2009


Features
      Assigning back-end services
      You create a back-end service with a Sequence Number that uniquely identifies it. The
      number also specifies the sequence in which the services are called at runtime.
      By using sequence numbers when assigning the back-end services, you have the
      option of using the same service more than once in the form scenario. You assign
      different sequence numbers to the service for this purpose. You should only use this
      option if it is absolutely necessary to split up the processing of a back-end service into
      more than one block (for example, because there are dependencies between the
      individual blocks).
      Back-end services can also be assigned a Rule. In this case, the service is called only
      if the evaluation of the rule produces the value "true."

      Assigning form fields to back-end services
      A back-end service is only called if you have assigned at least one field to it. Only the
      values of the fields that are assigned to the back-end service are transferred to it. You
      determine how the form fields are processed by the back-end service by configuring
      the back-end service. For more information, see:
      Settings for Back-End Service SAP_PA [Page 153]
      Settings for Back-End Service SAP_PT [Page 157]
      Settings for Back-End Service SAP_PD [Page 160]
      Settings for Generic Services [Page 166]

Activities
      You assign the back-end scenarios that are used in the form scenario.

      You move and insert back-end services to determine the sequence in which they are
      called.

      You assign form fields to the back-end services.

Example
The following services are used for a form scenario:
The standard service SAP_PA, the standard service SAP_PT, and a generic service
S_MATLEAVE that is required in a Maternity Leave process for determining the time limits.

Back-End Services

No.                               Service                            Name
1                                 SAP_PA                             Personnel Administration
                                                                     infotypes
2                                 SAP_PT                             Time Management infotypes
3                                 S_MATLEAVE                         Maternity Leave (Determine
                                                                     absence types)




HR Administrative Services (PA-AS)            6956                                            152
SAP Online Help                                                                      22.04.2009



      Settings for Back-End Service SAP_PA
Use
You use this function to configure the SAP_PA back-end service for your form scenario. The
SAP_PA back-end service enables Personnel Administration infotypes to be created,
changed, and deleted in a form scenario.

Features
      Operations based on InfoObjects
      The SAP_PA service is based on InfoObjects. The infotypes can be restricted by
      specifying a subtype and an object identification. An InfoObject can be represented as
      follows: [infty, subty, objps].



             The following table contains some examples of InfoObjects:
              InfoObject                            Name
              [0002, space, space]                  Personal data
              [0006, space, space]                  Any address
              [0006, 1, space]                      Main address
              [0021, 1, space]                      Spouse
              [0279, N001, 01]                      Individual values for product 01 (= "Retirement
                                                    Scheme") of the pension fund N001
      You can use InfoObjects to establish the relationship between form fields and infotype
      fields. Each InfoObject can be assigned an operation that is used on this InfoObject at
      the runtime of the form scenario.
      The SAP_PA service supports the following operations:

             Create

             Change

             Change without delimiting

             Delete
      The effect of the operation depends on the time constraint of the InfoObject. The
      following three time constraints are used:

             Time constraint 1: Exactly one data record exists at each time.

             Time constraint 2: Exactly one or no data record exists at each time.

             Time constraint 3: Any number of data records exists at each time.
      For example, the Create operation always creates a new data record for an InfoObject
      with time constraint 3, without modifying the existing records. However, an existing data
      record is first delimited for an InfoObject with time constraint 1 or 2.
      You can only ever enter one operation for an InfoObject. It is not possible to execute
      multiple operations on the same InfoObject (for example, create and delete).

      Assigning form fields to InfoObjects, using screen structures
      Screen structures enable access from form fields to the InfoObjects. At least one
      screen structure exists for each infotype. There is usually more than one screen


HR Administrative Services (PA-AS)           6956                                           153
SAP Online Help                                                                         22.04.2009


     structure, particularly if the infotype is country-specific. In this case, there is a separate
     screen structure for each country version. Each screen structure contains all infotype
     fields that are relevant for the user interface. These can be input fields or output fields
     (for example, for related texts or calculated fields).
     When assigning the form fields to InfoObjects, you have to choose one of the possible
     country-specific screen structures of the infotype. This means that the entire form
     scenario is created for a particular country version.
     If do not use country-specific screen structures, only international ones, you define the
     entire form scenario as an international form scenario without any country-specific
     features.
     Because each InfoObject in a form scenario can be defined only once, you have to
     choose one screen structure for each InfoObject. You are not permitted to use the
     international screen structure and a country-specific screen structure simultaneously for
     the same InfoObject.
     The input help displays the available screen structures for you to select. You cannot
     use country versions and infotypes that do not have a screen structure. The majority of
     infotypes and country versions provided by SAP have corresponding screen structures.
     If you want to use customer infotypes, they must also have screen structures, meaning
     that you must have completely decoupled the Business Logic and UI of the infotypes.
     When you create new infotypes, create them using the new principle.
     SAP provides you with a tool that supports you when decoupling infotypes. The tool is
     in Customizing for Personnel Administration under Customizing Procedures
     Infotypes   Infotypes in the Decoupled Infotype Framework.



            Two types of screen structures are differentiated: type MAIN and type LINE. You
            usually use screen structures of the MAIN type. You require LINE screen
            structures if you want to process repeat fields in the form scenario.
     For more information, see:
     Developing an Infotype in Personnel Administration [External]
     Business Logic Guidelines for Creating and Migrating Infotypes [External]
     UI Programming Guidelines for Infotypes [External]

             Displaying and editing infotype texts in the form
            To display and edit infotype texts in the form, use the screen structure
            HCMT_BSP_PA_TEXT, and bind the form field to the TEXT field of this screen
            structure. Make sure when creating the form that you use a control element that
            permits the display of texts of more than one line.
            For more information, see Editing the Form Layout [Page 147].



            All screen structures contain the technical field OBJECT_KEY. This field is used
            for internally processing the data records. Never use the OBJECT_KEY field in
            your form scenario.

      Using default values for form fields
     You can fill form fields with default values from the SAP_PA service.
     The following default value types are available:

             Value for Effective Date
            You should use this type if the form field is an input field and you want the value
            that "currently" exists on the database to be entered in the field as a default. The


HR Administrative Services (PA-AS)            6956                                              154
SAP Online Help                                                                      22.04.2009


            user can then retain the value or overwrite it. You have usually linked the form
            field to an InfoObject for which you have set the Change operation or Change
            Without Delimiting, and assume that data exists on the database that the user
            changes when editing the form. The mandatory field Effective Date
            (EFFECTIVE_DATE) determines the date on which the change in data becomes
            effective. The existing value for this date is determined as a default value. If
            there is no data record on the database for the effective date, no default value is
            determined for the form field.

             Value for Day Before Effective Date
            You should use this type if the form field is a display-only field that displays the
            previously existing value on the database. You will usually have defined another
            form field as an input field for users to enter the newly changed value. For
            example, in a process to change an employee's organizational data (including
            the position), there may be a display field that displays the old position and an
            additional input field for entering the new position. The change is to take place
            as of the effective date. In this case, you would choose the Value for Day Before
            Effective Date type for the display field. For the field in which the new position is
            input, you would choose the Value for Effective Date type. This means that the
            existing position as at the effective date is specified in the field as the default
            value for the new position. In the case of both types, if there is no data record on
            the database on the day previous to the effective date (= EFFECTIVE_DATE -
            1), no default value is determined for the form field.

             Default Value of Business Logic
            You should use this type if the form field is assigned to an InfoObject for which
            you have set the Change operation. In this case, there is usually no data record
            on the database that could be used as a default value. If you use the Default
            Value of Business Logic type, the initial computation logic of the infotype is
            called and determines default values for the creation of a new data record. If the
            logic cannot determine a default value, no default value is entered in the form
            field.

      Activating input help for form fields
     The SAP_PA service provides input help for certain form fields. To gain an overview of
     the fields for which input help is available, you can use the tool for testing decoupled
     infotypes (see the “Activities” section).

      Mandatory form fields
     The SAP_PA service has a range of mandatory fields:
      Field Name                  Name                              Data Element
      PERNR                       Personnel Number                  PERNR_D
      EFFECTIVE_DATE              Effective Date                    ASR_EFFECTIVE_DATE
      MASSN                       Action                            MASSN
      MASSG                       Reason for Action                 MASSG
      CENTRAL_PERSON              Central Person                    OBJEKTID


     These fields must exist in each form scenario used by the SAP_PA service with the
     name exactly as specified and with the data element exactly as specified.




HR Administrative Services (PA-AS)            6956                                           155
SAP Online Help                                                                        22.04.2009


             Do not delete these mandatory form fields.

Activities
Under <Form Scenario>      <Version>     Back-End Services in the object hierarchy area of
Design Time, make the following settings:

      Definition of operations based on InfoObjects
      Specify the operations that you want to use and determine the sequence in which they
      are performed.
      If you only want to use an InfoObject to supply a form field with an input help or default
      value, do not enter an operation for the InfoObject. This is the case, for example, if you
      use the Personal Data infotype (0002) to output the employee's name on the form. You
      always enter an operation if you want to modify the InfoObject on the database (as a
      rule).

      Determining the time constraint of an infotype
      When defining the InfoObjects, you should always be aware of their time constraints as
      these affect the operations used. InfoObjects with time constraint 1 and 2 are usually
      no problem. However, there are restrictions for InfoObjects with time constraint 3.
      You determine the time constraint of an infotype in Customizing for Personnel
      Administration under Customizing Procedures        Infotypes   Infotypes. Double-click
      on the infotype to access the infotype properties. The time constraint is defined either
      for the infotype or the subtype:

              The Time Constraint field contains the time constraint of the infotype. The value
              "T" means that the time constraint depends on the subtype.

              The Time Constraint Table field contains the name of the table in which the time
              constraints of the subtype are defined.
      If the infotype has subtypes, but you do not restrict to a subtype in the InfoObject, the
      InfoObject is treated as if it had time constraint 3. You then have to link a form field to
      the Subtype field of the infotype that contains the required subtype at runtime.

      Determining the available input help
      To determine which fields of the SAP_PA service have input help, proceed as follows:

              Go to the PUIT_UI transaction.

              Enter a personnel number.

              Enter an infotype and, if required, a subtype.

              Choose Execute.
             An overview of all data records for the personnel number and the chosen
             infotype appears.

              To display the name of the screen structure, choose Technical Information. The
              following information about the available input help applies only to the displayed
              screen structure.

              Choose Edit     Create Data Record.

              In the dialog box that appears, enter any values or leave the fields blank.

              Choose Continue.
             A dialog box appears that displays all fields of the screen structure. The Input
             Help column displays whether input help is available for the field. In Customizing



HR Administrative Services (PA-AS)            6956                                             156
SAP Online Help                                                                      22.04.2009


             for the SAP_PA service, you can only activate the input help for fields that have
             input help.

      If you do not want the value of the form field to be included in the operation, set the
      Exclude from Operation indicator (OpAusschl).



             If you want an operation to be executed only in particular circumstances, you
             assign a rule to it. You must have previously defined the rule in the form
             scenario. You must have assigned all form fields that you use in the rule to the
             SAP_PA service. The assigned operation is executed only if the rule - based on
             the values of the form fields used - has the value "true."
             You are not permitted to use repeat fields (see below) in a rule, since they can
             contain multiple values, whereas a rule can only ever be defined on one field
             value.

      You enter the record index. You usually enter the value 1. The following exceptions
      apply:

             If you have set the Create operation for the InfoObject and the InfoObject has
             time constraint 3, it is possible to create more than one new data record.

                    If you only want to create one new data record, use the value 1.

                    If you want to create two data records, use the value 1 for the fields to
                    be included in the first data record, and 2 for the fields that are to be
                    included in the second data record. You cannot start with the value 2 or
                    higher.

                    If you want to create additional data records, raise the value of the data
                    index by one for each new record.

             If you have set the Delete operation for the InfoObject and the InfoObject has
             time constraint 3, it is possible to delete more than one data record. Use the
             value * (asterisk) as the data index for this purpose. The asterisk means that all
             data records in the relevant time interval are deleted.




      Settings for Back-End Service SAP_PT
Use
You use this function to configure the SAP_PT back-end service for your form scenario. The
SAP_PT back-end service enables Time Management infotypes to be created, changed, and
deleted.

Features
      Operations based on InfoObjects
      The SAP_PT service is based on InfoObjects. The infotypes can be restricted by
      specifying a subtype and an object identification. An InfoObject can be represented as
      follows: [infty, subty, objps].



             The following table contains some examples of InfoObjects:
              InfoObject                            Description


HR Administrative Services (PA-AS)           6956                                               157
SAP Online Help                                                                       22.04.2009


             [2001, space, space]                   Any absence
             [2001, 0190, space]                    Educational leave
             [2007, 01, space]                      Approved overtime
     You can use InfoObjects to establish the relationship between form fields and infotype
     fields. Each InfoObject can be assigned an operation that is used on this InfoObject at
     the runtime of the form scenario.
     If you only want to use an InfoObject to supply a form field with a default value, do not
     enter an operation for the InfoObject. You enter an operation if you want to modify the
     InfoObject on the database (as a rule).
     The SAP_PT service supports the following operations:

             Create
            You use this operation when you want to create a new data record.
            If you explicitly link the start and end date (BEGDA and ENDDA) of the
            InfoObject to form fields, the new data record is created with the same validity. If
            you do not link the start and end date, the data record is created with the validity
            of the mandatory fields EFFECTIVE_BEGDA and EFFECTIVE_ENDDA. If
            EFFECTIVE_BEGDA or EFFECTIVE_ENDDA is initial, the value from
            EFFECTIVE_DATE is used instead.

             Change (restricted)



            Restrict your use of this option. For Personnel Administration infotypes
            (SAP_PA service), this operation should not be used for infotypes with time
            constraint 3. Time Management infotypes usually also have the nature of time
            constraint 3; therefore you should not use the operation for them either. You
            should use the Change operation only if you are certain that the Time
            Management infotype behaves in a similar manner to time constraint 1 or 2.

             Delete
            You use the Delete operation to delete data records. It deletes all data records
            that are in the interval [EFFECTIVE_BEGDA - EFFECTIVE_ENDDA] or are
            valid on at least one day in the interval. If EFFECTIVE_BEGDA or
            EFFECTIVE_ENDDA is initial, the date specified in EFFECTIVE_DATE is used
            instead. If you want to delete data records in another period, you specify the
            period explicitly by linking form fields to the start and end date of the InfoObject.
            Note that you always have to link at least one field to the InfoObject for the
            operation to be executed on the InfoObject. You are advised to link the PERNR
            field for the Delete operation.
            As a result of the complex time constraint logic of time management infotypes, it
            can be assumed that more than one data record exists in the specified deletion
            interval. The Delete operation is therefore usually applied to a set of data
            records. For this reason, you must enter the value * for the data index when
            linking the form fields. This indicates that there are multiple data records, as
            opposed to just one.
     Whereas Personnel Administration infotypes can have a time constraint of 1, 2, or 3,
     Time Management infotypes have a separate, complex, time constraint logic. The Time
     Management infotype framework ensures that this is taken into account when creating
     and changing infotypes. Put simply, the complex time constraint logic is most
     comparable to time constraint 3. However, there are also situations in which an
     infotype's behavior is similar to time constraint 2.

      Defining assignment of form fields to InfoObjects


HR Administrative Services (PA-AS)           6956                                             158
SAP Online Help                                                                     22.04.2009


      If you want to execute the Create or Change operations on the InfoObjects, the data for
      the new data records to be created has to be made available. This is achieved by
      assigning form fields to InfoObjects. The InfoObjects are accessed via the Pnnnn
      infotype structures, where nnnn stands for the four-digit number of the infotype. The
      input help provides you with the available infotype structures.

      Using default values for form fields
      You can use the SAP_PT service to fill form fields with default values.



             You should restrict your use of this option. As Time Management infotypes
             usually have time constraint 3, more than one data record can exist
             simultaneously in the database for a key date or effective date. It is then unclear
             from which data record the default value is read. You should only use default
             values using the service SAP_PT if you are sure that only one data record exists
             for the point in time in question.
The default value type Current Value for the Effective Date means that the existing data
record for the effective date (EFFECTIVE_DATE) is read and the value it contains is entered
as a default value in the form field.

      Input help for form fields
      The SAP_PT service does not currently support input help. If you require input help,
      you either have to define it manually in the form scenario or make it available via a
      generic service.

      Mandatory fields
      The SAP_PT service has a range of mandatory fields:
       Field Name                  Name                             Personnel Number
       PERNR                       Personnel Number                 PERNR_D
       EFFECTIVE_DATE              Effective Date                   ASR_EFFECTIVE_DATE
       EFFECTIVE_BEGDA             Start Date                       ASR_EFFECTIVE_DATE
       EFFECTIVE_ENDDA             End Date                         ASR_EFFECTIVE_DATE


      These fields must exist in each form scenario used by the SAP_PT service with the
      name exactly as specified and with the data element exactly as specified.



             Do not delete these mandatory form fields.

Activities
      You set the default value determination.

      You decide whether you require input help, and define it manually or provide it via a
      generic service.

      You define the operations that are performed on InfoObjects.
      When entering the infotype, use the input help to display a list of the available
      infotypes. Only the infotypes that are supported by the time management infotype
      framework (BLP) can be used. It is not possible (and usually not necessary) to develop
      customer-specific infotypes in this framework.
      Also use the input help to enter the subtypes.



HR Administrative Services (PA-AS)              6956                                          159
SAP Online Help                                                                          22.04.2009


      If you only want to link a form field to an InfoObject to fill it with a default value, but do
      not want the value of the form field to be included in the operation, set the Exclude
      from Operation indicator (OpAusschl).



             If you want an operation to be executed only in particular circumstances, you
             assign a rule to it. You must have previously defined the rule in the form
             scenario. You must have assigned all form fields that you use in the rule to the
             SAP_PT service. The assigned operation is executed only if the rule - based on
             the values of the form fields used - has the value "true."

      You enter the record index. You usually enter the value 1. The following exceptions
      apply:

             If you have set the Create operation for the InfoObject and the InfoObject has
             time constraint 3, it is possible to create more than one new data record.

                     If you only want to create one new data record, use the value 1.

                     If you want to create two data records, use the value 1 for the fields to
                     be included in the first data record, and 2 for the fields that are to be
                     included in the second data record. You cannot start with the value 2 or
                     higher.

                     If you want to create additional data records, raise the value of the data
                     index by one for each new record.

             If you have set the Delete operation for the InfoObject, it is possible to delete
             more than one data record. Use the value * (asterisk) as the data index for this
             purpose. This value means that all data records in the relevant time interval are
             deleted.




     Settings for Back-End Service SAP_PD

You use this function to configure the SAP_PD back-end service for your form scenario. The
SAP_PD back-end service enables Organization Management infotypes to be created,
changed, and deleted in a form scenario. The SAP_PD back-end service is designed to deal
with only object types O (Org. Unit), S (Position), and C (Job). The standard back-end
services SAP_PA and SAP_PT enable the customer to create processes that update master
data related to an employee by updating PA (Personnel Administration) and PT (Personnel
Time Management) infotypes. A standard back-end service to update PD (Personnel
Development) infotypes is now available. The framework is enabled to support design and
execution of processes affecting PD objects.

Prerequisites
       The Design Time Tool allows the process designer to specify the object type for the
       process.

       The Design Time Tool allows the process designer to configure PD service for
       performing operations on multiple PD objects, Relationships, and PD infotypes.

Features
       Operations based on InfoObjects


HR Administrative Services (PA-AS)             6956                                              160
SAP Online Help                                                                      22.04.2009


       The SAP_PD service is based on InfoObjects. The infotypes can be restricted by
       specifying a subtype. An InfoObject can be represented as follows: [infty, subty].
       However, each InfoObject is tagged along with a 1000 Infotype OBJID Fieldname. As
       a result, an InfoObject can be called as a combination of OBJID_FIELDNAME, Infty,
       and Subty.

            Example

       The following table contains some examples of InfoObjects:

                                                  InfoObject

       [1000, space]

       [1001, A003]

       [1002, 0001]

       [1007, space]

       [1008, space]



       You can use InfoObjects to establish the relationship between form fields and
       infotype fields. Each InfoObject can be assigned an operation that is used on this
       InfoObject at the run time of the form scenario.

       The SAP_PD service supports the following operations:

           o   Create

           o   Change

           o   Change without delimiting

           o   Delete

       The effect of the operation depends on the time constraint of the InfoObject. The
       following three time constraints are used:

           o   Time constraint 1: Exactly one data record exists at each time.

           o   Time constraint 2: Exactly one or no data record exists at each time.

           o   Time constraint 3: Any number of data records exists at each time.

       For example, the Create operation always creates a new data record for an
       InfoObject with time constraint 3, without modifying the existing records. However, an
       existing data record is first delimited for an InfoObject with time constraint 1 or 2. You
       can only ever enter one operation for an InfoObject. It is not possible to execute
       multiple operations on the same InfoObject (for example, create and delete).

       Assigning form fields to InfoObjects, using P-Structures (PNNNN, PTNNNN)

       P-Structures enable access from form fields to the InfoObjects. At least one P-
       Structure exists for each infotype. Each P-Structure contains all infotype fields that
       are relevant for the user interface. These can be input fields or output fields (for
       example, for related texts or calculated fields).




HR Administrative Services (PA-AS)           6956                                            161
SAP Online Help                                                                     22.04.2009


       When assigning the form fields to InfoObjects, you have to choose one of the
       possible P-Structures of the infotype.

       There are no country-specific P-Structures in SAP_PD.

       As each InfoObject in a form scenario can be defined only once, you have to choose
       one P-Structure for each InfoObject. The input help displays the available P-
       Structures for you to select.

       Using default values for form fields

       You can fill form fields with default values from the SAP_PD service.

       The following default value types are available:

           o   Value for Effective Date

               Use this type if the form field is an input field and you want the value that
               “currently” exists on the database to be entered in the field as a default. The
               user can then retain the value or overwrite it. You have usually linked the
               form field to an InfoObject for which you have set the Change operation or
               Change Without Delimiting, and assume that data exists on the database that
               the user changes when editing the form. The mandatory field Effective Date
               (EFFECTIVE_DATA) determines the date on which the change in data
               becomes effective. The existing value for this date is determined as a default
               value. If there is no data record on the database for the effective date, no
               default value is determined for the form field.

           o   Value for Day Before Effective Date

               Use this type if the form field is a display-only field that displays the
               previously existing value on the database. You will usually have defined
               another form field as an input field for users to enter the newly changed
               value. for example, in a process to change an organizational unit's name,
               there may be a display field that displays the old organization unit name and
               an additional input field for entering the new name. The change is to take
               place as of the effective date. In this case, you would choose the Value for
               Day Before Effective Date type for the display field. For the field in which the
               new position is input, you would choose the Value for Effective Date type.
               This means that the existing organizational unit's name as at the effective
               date is specified in the field as the default value for the new name. In the
               case of both types, if there is no data record on the database on the day
               previous to the effective date (=EFFECTIVE_DATE – 1), no default value is
               determined for the form field.

           o   Default Value of Business Logic

               Use this type if the form field is assigned to an InfoObject for which you have
               set the Change operation. In this case, there is usually no data record on the
               database that could be used as a default value. If you use the Default Value
               of Business Logic type, the initial computation logic of the infotype is called
               and determines default values for the creation of a new data record. If the
               logic cannot determine a default value, no default value is entered in the form
               field.

       Activating input help for form fields

       The SAP_PD service provides input help for certain form fields.

       Mandatory form fields

       The SAP_PD service has a range of mandatory fields:


HR Administrative Services (PA-AS)             6956                                         162
SAP Online Help                                                                     22.04.2009



                   Field Name                       Name                      Data Element

        LEAD_OBJECT_ID                   Lead Object ID            ASR_FIELDNAME

        LEAD_OBJECT_TYPE                 Lead Object Type          OTYPE

        EFFECTIVE_DATE                   Effective Date            ASR_EFFECTIVE _DATE

        EFFECTIVE_BEGDA                  Effective Begda           ASR_EFFECTIVE _DATE

        EFFECTIVE_ENDDA                  Effective Endda           ASR_EFFECTIVE _DATE

        These fields must exist in each form scenario used by the SAP_PD service with the
        name exactly as specified and with the data elements exactly as specified.

            Note

        Do no delete these mandatory fields.


Special Fields

The SAP_PD attaches special meaning to some form scenario fields. These fields are dealt
with a specific logic inside the PD mapper.

        Lead Object ID: The form scenario field LEAD_OBJECT_ID contains the Object ID of
        the Object that the process is based on. For processes with Start Object, the value of
        the LEAD_OBEJCT_ID is supplied by the Start Application. For processes without
        start object, this object ID is generated inside the PD mapper. This should not
        normally be empty; the only exception is when the operation on the
        LEAD_OBJECT_ID is 'CREATE'. In that case, the mapper's initialize method
        generates the object ID.

        Lead Object Type: The form scenario field LEAD_OBJECT_TYPE contains the type
        of the 'Lead Object'. This information is always passed from the Start Application and
        must not be empty.

        Effective Date: The form scenario field EFFECTIVE_DATE is treated as the effective
        date of the process. This field is never empty. The data element for this field is
        ASR_EFFECTIVE_DATE.

        Effective Begin Date: The form scenario field EFFECTIVE_BEGDA is an optional field
        for SAP_PD service. When a value is provided to this field, it is used as the begin
        date for reading data or performing operations. This provides the flexibility for
        reading/updating data on a date range. The data element for this field is
        ASR_EFFECTIVE_DATE.

        Effective End Date: The form scenario field EFFECTIVE_ENDDA is an optional field
        for SAP_PD service. When a value is provided to this field, it is used as the end date
        for reading data or performing operations. This provides the flexibility for
        reading/updating data on a date range. The data element for this field is
        ASR_EFFECTIVE_DATE.

As part of the enhancements to the Design Time Tool (DTT) to support SAP_PD back-end
service, there are two tools available additional to the SAP_PA back-end service tools:

        Objects Tool




HR Administrative Services (PA-AS)           6956                                          163
SAP Online Help                                                                     22.04.2009


           o   This tool is part of the SAP_PD back-end service.

           o   It deals with all aspects related to PD infotype 1000. It is used to capture the
               Object ID, Object Abbreviation (SHORT), Object Name (STEXT), the
               operation to be performed on the object.

           o   The possible operations are derived through a search help: CREATE,READ,
               DELETE, UPDATE, MODIFY.

           o   If the operation is empty or contains a value other than CREATE, it means
               the object and related fields are read.

       Behavior of the tool:

           o   LEAD_OBJID is the OBJID field name of the Leading PD Object of any
               SAP_PD service.

           o   Hence, the DTT by default, on inclusion of a SAP_PD back-end service into a
               form scenario, creates tools for that particular object.

           o   Objects tool has a default entry in the table control for LEAD_OBJID. Also,
               the user can specify the OTYPE of the leading PD object and other related
               attributes.

           o   For that LEAD_OBJID, there is a tool available to define any relationships
               that are created as part of the process, by also specifying RELATED_OBJID
               field name.

           o   There is another tool to specify any other infotype's fields the form scenario
               deals with as related to LEAD_OBJID object of the form.

           o   The tool can be used to specify all the PD Objects' field names on the form
               related to Infotype 1000 that are involved in the process.

           o   As and when new entries are added into the tool, an event is raised to update
               the Object Browser Hierarchy dynamically to show tools to define
               Relationships, Fields, Infotypes, and Operations for the corresponding new
               PD Object with its OBJID_FLDNAME as the name.

       Relationships Tool

           o   This tool is part of the SAP_PD back-end service.

           o   It deals with all aspects related to PD infotype 1001, which can be used to
               specify relationship fields on the form and define relationships across objects
               defined in the above Object tool.

       Fields Tool

       This is an existing tool reused whose functions continue to be the same as in
       SAP_PA and SAP_PT. The user can use this tool to map fields from any PD infotype,
       even those from infotypes 1000 and 1001, which is not possible using the Objects
       and Relationships Tool.

       Infotype and Operations Tool

       This is an existing tool reused whose functions continue to be the same as in
       SAP_PA and SAP_PT. The user can use this tool to specify explicitly the infotypes
       and operation whose fields he or she wants to map in the Fields tool.




HR Administrative Services (PA-AS)          6956                                            164
SAP Online Help                                                                       22.04.2009


       Additionally, the Process Start Configuration Main Tool is enhanced with a field to
       specify the object type of leading object ID. In the case of a process without a start
       object, specifying an object type the process deals with is mandatory.

Activities
Under Form Scenario Version Back-End Services               in the object hierarchy area of
Design Time, make the following settings:

       Definition of operations based on InfoObjects

       Specify the operations that you want to use and determine the sequence in which
       they are performed.

       If you only want to use an InfoObject to supply a form field with an input help or
       default value, do not enter an operation for the InfoObject. This is the case, for
       example, if you use the Objects infotype (1000) to output the object's name on the
       form. you always enter an operation if you want to modify the InfoObject on the
       database (as a rule).

       Determining the time constraint of an infotype

       When defining the InfoObjects, always be aware of their time constraints as these
       affect the operations used. InfoObjects with time constraint 1 and 2 are usually no
       problem. However, there are restrictions for InfoObjects with time constraint 3.

       The time constraint of an infotype and subtype is also dependant on the object type.

       The time constraint is maintained in the maintenance view V_T777ZIT.

       If you do not want the value of the form field to be included in the operation, set the
       Exclude from Operation indicator (OpAusschl).


            Note

       If you want an operation to be executed only in particular circumstances, you assign a
       rule to it. You must have previously defined the rule in the form scenario. you must
       have assigned all form fields that you use in the rule to the SAP_PD service. The
       assigned operation is executed only if the rule — based on the values of the from
       fields used — has the value “true”.


       You enter the record index. You usually enter the value 1. The following exceptions
       apply:

           o   If you have set the Create operation for the InfoObject and the InfoObject has
               time constraint 3, it is possible to create more than one new data record.

                        If you only want to create one new data record, use the value 1.

                        If you want to create two data records, use the vale 1 for the fields to
                        be included in the first data record, and 2 for the fields that are to be
                        included in the second data record. You cannot start with the value 2
                        or higher.

                        If you want to create additional data records, raise the value of the
                        data index by one for each new data record.

           o   If you have set the Delete operation for the InfoObject and the InfoObject has
               time constraint 3, it is possible to delete more than one data record. Use the



HR Administrative Services (PA-AS)           6956                                             165
SAP Online Help                                                                        22.04.2009


                 value 8 (asterisk) as the data index for this purpose. The asterisk means that
                 all data records in the relevant time interval are deleted.



      Settings for Generic Services
Use
You use this function to configure the generic services for your form scenario.
If you use a generic service, you can link the form fields to the parameters or fields of the
operations of this generic service. You can use an operation more than once in a form
scenario. This enables you to link the form fields to field groups that link to operations, rather
than linking them directly to operations. More than one field group can reference the same
operation.

Prerequisites
       You have defined and implemented the generic service. Perform the IMG activities in
       Customizing for HR Administrative Services by choosing Configuration of
       Forms/Processes     Form Configuration    Define Generic Services.

       You have assigned form fields to the generic service that you want this service to
       process.

       If you want to use default values, the generic service must be implemented in such a
       way that it also provides default values.

       If you want to use input help and default values, the generic service must be
       implemented in such a way that it provides them. For more information, see
       Customizing for HR Administrative Services and choose Configuration of
       Forms/Processes       Form Configuration     Define Generic Services.

Features
       Field groups and operations
      You can use generic services to perform operations or to provide default values and
      input help. You can define field groups that you want to use for operations or default
      values and input help. A field group may have any name. However, if you use the field
      group for an operation we recommend that you choose a name that refers to the
      operation used.

       Default values and input help
      You can provide default values and input help for fields without defining an operation
      for them. The prerequisite is that the field is assigned to a field group. If the default
      value or input help for the field is dependent on other fields of the generic service,
      these fields must be assigned to the same field group as the field for which you want to
      provide the default value or input help.

       Mandatory fields
      A generic service can also have mandatory fields, as do the standard services,
      SAP_PA and SAP_PT. The mandatory fields must exist in each form scenario used by
      the generic service with the name exactly as specified and with the data element
      exactly as specified.

Activities
       You create field groups.

       You assign fields to the field groups.


HR Administrative Services (PA-AS)              6956                                           166
SAP Online Help                                                                       22.04.2009


      You select operations that you want to use.

      You assign field groups to the operations.

      You enter the name of the form field that you want to assign.

      You define the properties of the form field.

      You can fill the form field with a default value or input help that provides the generic
      service.

      If the generic service supports operations and you want to use them, enter the name of
      the operation.
      You can use the input help to display a list of all of the operations of the generic
      service.

      If you do not want the value of the form field to be included in the operation, set the
      Exclude from Operation indicator (OpAusschl).

      You enter the field group to which you want to assign the form field. If the generic
      service supports operations, the name of the field group corresponds to the operation
      of the generic service.




      Definition of Attachment Types
Use
You can use this function to provide additional information or supplementary documents on
the form. A differentiation is made between any information that cannot be specifically
classified, and documents that are required for the business execution of a process.
Depending on the attachment type, for example, the “Maternity Leave” process requires the
employee to submit a certificate of pregnancy.

Features
      You can create your own attachment types.
      The attachment type provided in the standard system, General Attachments
      (SFREEATTM), enables you to add attachments that cannot be classified more
      precisely. All other attachment types (provided in the standard system or created by
      you) uniquely classify the attachment. They provide information about which document
      is provided when the process is executed.



             The system cannot check whether the object provided is actually the required
             document.

      You define the attachment types that you want to use in a process or form scenario
      [External].
      All attachment types that are provided and that you create are potentially available for
      all form scenarios or processes.

      For each scenario step [External], you define the properties of the attachment types
      used. For example, the Creation Is Mandatory property means that the attachment
      template must exist.




HR Administrative Services (PA-AS)            6956                                               167
SAP Online Help                                                                       22.04.2009



      Creation of Links for Additional Information
Use
You use this function to create links that are to be available in your processes or form
scenarios on the form.
Links are any URLs for documents or information that support the processor with performing
the process.

Prerequisites
The required documents for which you want to create a link (URL) must be stored in your
intranet.

Activities
       You create the required links for additional information.

       You assign the link to the appropriate scenario step of the form scenario.
      For more information, see Definition of Scenario Steps [Page 150].

Example
You want to provide the employee in the “Maternity Leave” process with a document that
contains the legal and organizational guidelines for maternity leave.
You create the document in your intranet and use this function to define a link (URL) to this
document.
You then assign the link to the appropriate scenario step of the form scenario that you use in
the “Maternity Leave” process.
The document is now available to the employee in the “Maternity Leave” process via the link
in the form.




      Definition of Rules
Use
You use this function to create rules that you can use to control whether a back-end service is
called or whether a specific operation of this service is called.

Features
Rules are based on form fields and return “true” or “false” as a result at runtime, depending on
the input values. The back-end service or operation is called only if the result of the rule is
"true" at runtime.
A formula editor is available for defining a rule. The following parameters can be used in a
rule:

       All fields of a form scenario, except for fields that contain more than one value at
       runtime (for example, repeat fields that are supported by the SAP_PA service).

       System fields

       Constants

       Standard features


HR Administrative Services (PA-AS)            6956                                             168
SAP Online Help                                                                       22.04.2009


       Logical operations (AND, OR, and so on)



             If you assign the rule to an operation of a back-end service, all form fields that
             you use in the rule must also be assigned to the back-end service.
             You can only use rules that were defined as Boolean rules, meaning that the
             result of a rule must be either “true” or “false” in each case. Other rules are not
             supported.

Activities
You enter a Rule and a Description. When you have confirmed your entries, you can use the
icons in the Formula column to define or edit the rule in the formula editor.

Example
The “Entitled to Company Car” rule could be defined as follows:
(“Annual sales of employee” > 50000) OR (“Hiring date” <= 01/01/2000)




      Definition of User Events
Use
You use this function to create operations for subsets of form fields.
You can define more than one area for a form; each area corresponds to a field group with
more than one field. For each area you can provide a pushbutton that triggers an operation.
The operation checks, for example, the field contents of the area and simultaneously
initializes the fields of the subsequent area.
During the initialization, based on the field contents of the previous area(s), the system
provides information for the subsequent area, such as default values and input help.

Prerequisites
In Adobe LiveCycle Designer, you have created a pushbutton for the form and, in the script
editor of Adobe LiveCycle Designer, you have defined a name for the event that triggers this
pushbutton. For more information, see Creating Pushbuttons [Page 55]

Activities
       You create field groups.

       You assign form fields to the field groups.

       You create operations.



             The name of the operation must correspond to the name of the event that you
             have specified for the pushbutton in Adobe LiveCycle Designer.

       You assign the field groups to the operations.
      Also define whether the operation checks or initializes the field group and whether, in
      the case of an error, relevant error messages are displayed.




HR Administrative Services (PA-AS)            6956                                            169
SAP Online Help                                                                      22.04.2009


Example
You want to create a form with three areas. Each area should cover more than one field. The
first two areas should each contain a Derive Default Values pushbutton; the third area a
Check pushbutton.
In Adobe LiveCycle Designer, first create the relevant pushbuttons for the form. Name the
events triggered by the pushbuttons USER_EVENT_OP1 and USER_EVENT_OP2.
Then, you create the field groups FG1, FG2, and FG3. You assign the following fields to the
field groups:


Field Group                                         Fields
FG1                                                 FF1A, FF1B, FF1C, FF1D
FG2                                                 FF2A, FF2B, FF2C
FG3                                                 FF3A, FF3B, FF3C, FF3D, FF3E


You then create the operations USER_EVENT_OP1 and USER_EVENT_OP2 and assign
them the field groups as follows:


Operation                Field Group                Processing Type          Ignore Errors
USER_EVENT_OP1           FG1                        Check                    X
USER_EVENT_OP1           FG2                        Initialize               X
USER_EVENT_OP2           FG1                        Check
USER_EVENT_OP2           FG2                        Check
USER_EVENT_OP2           FG3                        Initialize


In this case, the user first fills out the first area of the form and chooses the Derive Default
Values pushbutton that triggers the operation USER_EVENT_OP1. The operation checks the
field contents in FG1 and provides default values and input help for the second area of the
form, that is, for the fields of field group FG2.
The user now fills out the second area of the form and again chooses the Derive Default
Values pushbutton. In this case, the pushbutton triggers the operation USER_EVENT_O2.
The operation checks the field contents in FG1 and FG2 and provides default values and
input help for the third area of the form, that is, for the fields of field group FG3.




      Settings for Message Mapping
Use
You can use this function to define message mapping based on form scenarios [External].
You can map error messages, warnings, information, success, termination, and exit
messages that are not relevant with suitable messages that are relevant for the form
scenario. You can also set the Hide indicator. In this case, the message text is not displayed.
You can also restrict the message mapping to a certain Processor Role.
If no alternate message is found for a form scenario, the system reads the settings for generic
message mapping. For more information, see the Implementation Guide for HR
Administrative Services and choose Tools      Message Mapping.


HR Administrative Services (PA-AS)           6956                                            170
SAP Online Help                                                                    22.04.2009


Features
      Mapping individual messages
      You can determine the replacement of system messages with specific messages
      depending on the message type, message ID, and message number. Determine the
      alternate message type, and if required, the alternate message ID and the alternate
      message number, for the message to be replaced.

      Mapping all messages of an error category
      You can determine the replacement of messages depending on their error category
      and message type. There are messages that are only classified by a message type,
      and messages that are also classified by an error category. You can use this function
      to only map messages with an error category. For example, you can replace all
      warnings from the No Authorization error category with an alternate message. To do
      this, you must enter an alternate message type, an alternate message ID, and an
      alternate message number.

Activities
      You determine how system messages are mapped depending on message type,
      message number, and message ID:

              You enter the message type to be mapped.
             You do not have to enter the message ID and the message number. Message
             mapping is then applied to all message IDs and message numbers of this
             message type.

              If you enter the message ID, you must also enter the message number, and
              vice versa.

              If you only enter the message type and the alternate message type, and leave
              all other fields empty, only the message type is replaced. Only the message
              type of a message is replaced, and not the message ID and message number.

      You determine how system messages are mapped depending on error category and
      message type.

      In the standard system, message mapping is switched on. You can use the parameter
      OFF_MSG_MAP to switch off message mapping for a user under System              User
      Profile   Own Data     Parameters, if this is necessary, for example, for test purposes.

Example
After a form is saved, the processing logic of the Basic Pay infotype (0008) generates the
error message PA 4711: Wage Type M610 Not Permitted for Employee Grouping XYZ.
However, the wage type is not available on the form and is not relevant for Employee Self-
Service or Manager Self-Service users. In the Customizing tables, the error message PA
4711 is replaced by the message XY 4713: Customizing Error, Send to Administrator. This
message is also displayed for the end user.




     Mass Processes and Fast Data Entry

It is now possible to start a process for multiple employees at the same time.

Processes for multiple employees are divided into the following categories:


HR Administrative Services (PA-AS)           6956                                            171
SAP Online Help                                                                                                              22.04.2009


                Fast Data Entry

                This type of process is a one-step process; no workflow is present.

                The first (and only) agent in the process updates the data and saves the data; this
                data is saved and updated in the backend.

                Mass Processes

                This type of process is a multi-step process; a workflow is present.

                When you update data and send it to the next agent in the process, the system
                generates separate process instances for each of the employees whose data you
                have edited. The next agent in the process (it is possible to have different agents for
                different process instances) receives a work item in his or her worklist. He or she
                proceeds to edit or review the data entered by the previous agent as in a standard
                process.

When you start either of the above processes in the Portal, the start application looks the
same; you enter or edit the data in a table format. Data appears in a form format only in Mass
Processes (when the next agent in the workflow opens his or her worklist item for one of the
employees involved in the process).

The following figure shows the difference between a fast data entry process and a mass
process:

                              Step 1                                       Step 2                            Step 3


   Fast Data Entry
  Pers.No.         Name               Manager      Job
  00220004         Ralf Rein          Doerr Rein   Developer
  00220005         Anno Rein          Doerr Rein   Developer
                                                               SAVE
  00220006         Danno Rein         Doerr Rein   Developer



     Select multiple employees in table
                                                                Data saved to back-end
                                                                Process is completed



                                                                             Form                           Form
   Mass Process
                                                                                    Form                           Form
  Pers.No.         Name               Manager      Job
  00220004         Ralf Rein          Doerr Rein   Developer
  00220005         Anno Rein          Doerr Rein   Developer
                                                               SAVE                        Form
                                                                                                  SEND                    Form
  00220006         Danno Rein         Doerr Rein   Developer




   Select multiple employees in table                           Process instance generated for each       Forms sent to next
                                                               employee                                  agent…
                                                                Form for each employee sent to next       …Data saved to back-
                                                               agent in workflow                         end
 © SAP AG 2009. All rights reserved. / Page 1




A Comparison of Fast Data Entry and Mass Process

You configure a process for fast data entry or mass process in Design Time for Processes
and Forms. For more information, see Configuring a Process for Fast Data Entry, Configuring
a Process as a Mass Process.




HR Administrative Services (PA-AS)                                         6956                                                    172
SAP Online Help                                                                        22.04.2009


You start a fast data process or mass process in the Portal using Start Process for Multiple
Employees. For more information, see Starting a Fast Data Entry Process, Starting a Mass
Process.



     Configuring a Process for Fast Data Entry

Configure a process for fast data entry when you want the process to affect more than one
employee at a time and there is only one agent (the initiator) in the process flow.

This type of process contains no workflow.

Configuring a process for fast data entry allows you to perform the following activities:

        You specify which roles access the process.

        Manager and HR Administrator roles each use a different employee selection screen.

        You choose which fields in the table are read-only or editable.

        You specify the order in which the fields are displayed in the table from left to right.

Prerequisites
        You have created the ISR scenario and form scenario.

        You have created the process.

Procedure
    1. In Design Time for Processes and Forms, choose the process you wish to configure.

    2. Configure the process start.

            1. Choose the Validity Period view.

            2. Enter the dates that you want the process to be valid for in Valid From and
               Valid To.

            3. In Settings for Start Step, choose Enable Mass Start of Process in the
               dropdown list for Process Type.

            4. Choose Save.

            5. Under Validity Period Process Start Role Assignment , add the
               relevant roles, for example, HR Administrator, who can execute this process.

                This process appears as a possible process to be executed when the user
                chooses Start Process for Multiple Employees in the Portal.

            6. Choose Save.

    3. Define and configure the form scenario in the process.

            1. Choose       Validity Period   Form Scenarios      .

            2. Enter the Form Scenario, Version, and Scenario Step you have created for
               this process.




HR Administrative Services (PA-AS)            6956                                             173
SAP Online Help                                                                      22.04.2009


            3. Define the order in which the form fields appear in the start application in the
               Portal.

                Choose Form Scenarios Fields and, in the Field Sequence column,
                enter a sequential number in each row.

                It is recommended to display the Personnel Number as the first column and
                the Employee Name as the second column.


                     Note

                To specify the sequence, you must assign the position of all fields in the table
                for the application.


            4. Define how the system displays the fields in the start application in the Portal.

                Use the Field Attribute column to decide which fields are read-only (Output
                Only) and which fields are not.

                In the Portal, the Details button displays whether fields are editable or read-
                only.

            5. Choose Save.

        For more information, see Creating a Form Scenario.

    4. Choose      Validity Period   Workflow    .

        It is mandatory to enter a workflow ID (even for this single-step process, without a
        workflow). Enter the workflow ID as NO_WORKFLOW.

    5. Choose Save.

    6. Optional setting: Permit parallel runs of process in    Validity Period   Process Start
        Frequency Restriction .

        Choose Without Restrictions radio button.

        Choose Save.


            Recommendation

        We recommend that you make this setting at least for the test and implementation
        phase. Otherwise you cannot start the required process for the same employee more
        than once when testing. During live system operations, you can undo this setting for
        individual processes.



Result
You have configured your process for fast data entry and have made all required settings.
You can start this process in the Portal using Start Process for Multiple Employees.



     Starting a Fast Data Entry Process



HR Administrative Services (PA-AS)           6956                                              174
SAP Online Help                                                                     22.04.2009


Fast data entry processes allow you to change data for multiple employees at the same time.

No workflow template is specified in the process; it is a single-step process.

Prerequisites
You have configured the process for fast data entry in Design Time for Processes and Forms
and have enabled it for start by the HR Administrator.

For more information, see Configuring a Process for Fast Data Entry.

Procedure
To start processes for multiple employees and enter data for all those employees at the same
time, use the Start Process for Multiple Employees service in the Portal. This is a single-step
process where no workflow is generated.


    Note

The same entry screen and table format are used for both mass processes and fast data
entry processes.


To start a fast data entry process, complete the following steps:

    1. In the Portal, choose Start Process for Multiple Employees.

        The Start Process for Multiple Employees window appears.

    2. Step 1 displays a list of processes which have been enabled for mass process start.

        To see the fields that are displayed in the next screen for a process, choose Details.
        You can see which fields are read-only and which are editable.

        Choose the process that you want to execute and choose Next.

    3. Step 2 allows you to select employees.

        Search for the employees whose data you want to edit.

        Select employees from the table displaying the search results and choose Add
        Employees.

        The employees that you want to edit data for are displayed in the table Selected
        Employees.

        Choose Next.

    4. Step 3 allows you to update the employees' data.

        Enter the date that you want the changes to be effective from and choose Initialize.

        Select the employees whose data you want to update and choose Set Values for
        Selected Employees.

        Enter the data in the dialog box that appears and choose OK to automatically update
        all the selected employees in one step.

        Choose Next.


             Note


HR Administrative Services (PA-AS)            6956                                          175
SAP Online Help                                                                      22.04.2009


        The following buttons are also available at the Enter Data step:

              Button                                    Button Description

                            Validates the data you enter for an employee. Displays the following
                            colored error messages that might occur for the selected employees:

        Check Selected          o           Red — a critical message. You must solve the problem
        Employees                   before proceeding to the next step.

                                o           Yellow — a warning message only. You can proceed to
                                    the next step without first solving the problem.

        Delete Selected
                            Deletes employees you do not wish to change data for.
        Employees

                            Deletes employees for which there is an error message.

        Delete                   Note
        Employees with
        Error               You cannot proceed to the next step in the process if the system displays
                            red error messages.



                            Removes data you have entered for the selected employees. The system
        Reset Selected
                            initializes the data and displays the entry as provided by the current
        Employees
                            infotype.



    5. Step 4 allows you to review the data you have entered.


             Note

        The system automatically performs an error check before proceeding to Step 4. You
        cannot proceed to this step if the system displays red error messages.


    6. Choose Save.

        When you save, the master data is updated.

        Verify the data is updated by using transaction PA30 in the backend system. Enter
        the personnel number to display a specific employee's details.

For a sample process, see Address Change (Single-Step Process).



     Configuring a Process as a Mass Process

Configure a process as a Mass Process when you want the process to affect more than one
employee at a time and there is more than one agent in the process flow.

This type of process always contains a workflow.

Configuring a process with mass start capability allows you to perform the following activities:


HR Administrative Services (PA-AS)            6956                                           176
SAP Online Help                                                                       22.04.2009


       You specify which roles access the process.

       Manager and HR Administrator roles each use a different employee selection screen.

       You choose which fields in the table are read-only or editable.

       You specify the order in which the fields are displayed in the table from left to right.

Prerequisites
       You have created the ISR scenario and form scenario.

       You have created the form.

       You have created the workflow template.

       You have created the process.

Procedure
   1. In Design Time for Processes and Forms, choose the process you wish to configure.

   2. Configure the process start.

           1. Choose the Validity Period view.

           2. Enter the dates that you want the process to be valid for in Valid From and
              Valid To.

           3. In Settings for Start Step, choose Enable Mass Start of Process in the
              dropdown list for Process Type.

           4. Choose Save.

           5. Under Validity Period Process Start Role Assignment , add the
              relevant roles, for example, HR Administrator, who can execute this process.

               This process appears as a possible process to be executed when the user
               chooses Start Process for Multiple Employees in the Portal.

           6. Choose Save.

   3. Define and configure the form scenario in the process.

           1. Choose       Validity Period   Form Scenarios      .

           2. Enter the Form Scenario, Version, and Scenario Step you have created for
              this process.

           3. Define the order in which the form fields appear in the start application in the
              Portal.

               Choose Form Scenarios Fields and, in the Field Sequence column,
               enter a sequential number in each row.

               It is recommended to display the Personnel Number as the first column and
               the Employee Name as the second column.


                    Note

               To specify the sequence, you must assign the position of all fields in the table
               for the application.


HR Administrative Services (PA-AS)           6956                                             177
SAP Online Help                                                                       22.04.2009




            4. Define how the system displays the fields in the start application in the Portal.

                 Use the Field Attribute column to decide which fields are read-only (Output
                 Only) and which fields are not.

                 In the Portal, the Details button displays whether fields are editable or read-
                 only.

            5. Choose Save.

        For more information, see Creating a Form Scenario.

    4. Choose      Validity Period   Workflow     .

        Enter the workflow template you have previously created for this process.

        For more information, see Creating a Workflow Template

    5. Choose Save.

    6. Optional setting: Permit parallel runs of process in     Validity Period   Process Start
        Frequency Restriction .

        Choose Without Restrictions radio button.

        Choose Save.


             Recommendation

        We recommend that you make this setting at least for the test and implementation
        phase. Otherwise you cannot start the required process for the same employee more
        than once when testing. During live system operations, you can undo this setting for
        individual processes.



Result
You have configured your process as a mass process and have made all required settings.
You can start this process in the Portal using Start Process for Multiple Employees.



     Starting a Mass Process

Mass processes allow you to change data for multiple employees at the same time.

A workflow template is specified in the process; it is a multi-step process.

Prerequisites
You have configured the process as a mass process in Design Time for Processes and
Forms and have enabled it for start by HR Adminstrator.

For more information, see Configuring a Process as a Mass Process.




HR Administrative Services (PA-AS)            6956                                            178
SAP Online Help                                                                      22.04.2009


Procedure
To start processes for multiple employees and enter data for all those employees at the same
time, use the Start Process for Multiple Employees service in the Portal. This is for multi-step
processes where a workflow is generated.


    Note

The same entry screen and table format are used for both mass processes and fast data
entry processes.


To start a mass process, complete the following steps:

    1. In the Portal, choose Start Process for Multiple Employees.

        The Start Process for Multiple Employees window appears.

    2. Step 1 displays a list of processes which have been enabled for mass process start.

        To see the fields that are displayed in the next screen for a process, choose Details.
        You can see which fields are read-only and which are editable.

        Choose the process that you want to execute and choose Next.

    3. Step 2 allows you to select employees.

        Search for the employees whose data you want to edit.

        Select employees from the table displaying the search results and choose Add
        Employees.

        The employees that you want to edit data for are displayed in the table Selected
        Employees.

        Choose Next.

    4. Step 3 allows you to update the employees' data.

        Enter the date that you want the changes to be effective from and choose Initialize.

        Select the employees whose data you want to update and choose Set Values for
        Selected Employees.

        Enter the data in the dialog box that appears and choose OK to automatically update
        all the selected employees in one step.

        Choose Next.


             Note

        The following buttons are also available at the Enter Data step:

             Button                                      Button Description

                            Validates the data you enter for an employee. Displays the following
        Check Selected      colored error messages that might occur for the selected employees:
        Employees
                                o           Red — a critical message. You must solve the problem
                                    before proceeding to the next step.



HR Administrative Services (PA-AS)           6956                                           179
SAP Online Help                                                                    22.04.2009



             Button                                   Button Description

                              o           Yellow — a warning message only. You can proceed to
                                  the next step without first solving the problem.

       Delete Selected
                          Deletes employees you do not wish to change data for.
       Employees

                          Deletes employees for which there is an error message.

       Delete                  Note
       Employees with
       Error              You cannot proceed to the next step in the process if the system displays
                          red error messages.



                          Removes data you have entered for the selected employees. The system
       Reset Selected
                          initializes the data and displays the entry as provided by the current
       Employees
                          infotype.



   5. Step 4 allows you to review the data you have entered.


            Note

       The system automatically performs an error check before proceeding to Step 4. You
       cannot proceed to this step if the system displays red error messages.


   6. Choose Save.

       When you save the data, the system generates different process instances for each
       employee. The process group reference number (which appears on the Confirmation
       screen) can be used to find these processes in the process browser.

       The next agent in the process (there can be different agents for different process
       instances) receives the work item in his or her worklist. He or she can also receive an
       e-mail in Microsoft Outlook with a link to the work item to be processed, if e-mail
       notification is set up. This agent can review and edit the data, which appears in a
       form, for the employee. If further processing is required, the form is sent to the next
       agent in the process. If no further processing is required, this agent saves the data,
       which is updated in the master data for that employee.

       Verify the data is updated by using transaction PA20 in the backend system. Enter
       the personnel number to display a specific employee's details.

For a sample process, see Special Payment for Mass Start (Multi-Step Process).



     Organizational Management Processes

Organizational Management (OM) processes are processes that are started for organizational
object types (with application type Personnel Development (PD)), like organizational units,
positions, and jobs. With a standard (Personnel Administration (PA)) process, you use the



HR Administrative Services (PA-AS)          6956                                          180
SAP Online Help                                                                    22.04.2009


object type employee to start a process. In an organizational management process, you use
the object types job, position, or organizational unit to start a process.

With the previous releases of HCM Processes and Forms, it was possible to build HR
processes that focused on updating an employee’s master data. This was achieved by
delivering an employee search-based start application and two standard back-end services —
SAP_PA, SAP_PT. There is now an enhanced start application and new back-end service
(SAP_PD). This process enables HCM Processes and Forms to design and execute
processes that affect objects other than employee objects (specifically PD objects). The goal
of this development is to start and execute an organizational process for Manager and HR
Administrator roles. There are also enhancements to the process browser to display
organizational management processes.

The process flow for organizational management processes is similar to the start process for
employee process flow. In the employee version, the start application first launches the
employee search and then the selection of the process, dependent on the employee. In the
PD start application, the selection of processes is dependent on the selection of the leading
object type (job, position, or organizational unit), which is the main change in the process
flow. After that, the behavior is the same as the existing (PA) processes.

Process




                            1                      2              3


                         Start
                       Process
                      with HCM                  Edit Data       Edit Data
                      Processes
                      and Forms




                 First agent starts        Second agent     Third agent edits
                 process, but instead of   edits data and   data and saves
                 selecting an employee,    sends form       form
                 the agent selects an
                 object type



                        Job

      Position                       Org Unit


Execution of an Organizational Management Process



   Creation and Configuration of Organizational
Processes




HR Administrative Services (PA-AS)               6956                                     181
SAP Online Help                                                                     22.04.2009


You can use Design Time for processes and forms to create organizational processes and to
make the necessary settings.

For more information on Organizational Processes, see Organizational Processes.

Integration
Create a process in the standard way as described in Creation and Configuration of
Processes along with the specific steps to make it an organizational process as outlined in the
Activities section of this document.

Features
Creating an Organizational Process
        You can create an organizational process in the Design Time Tool (DTT)

        When creating a form scenario, add the SAP_PD back-end service to make an
        organizational process.

Activities
Creating an Organizational Process
    1. Go to the Design Time Tool (DTT), in the navigation pane for a specific form
       scenario, choose Back-End Services.

    2. In the right-hand pane, add the SAP_PD (Infotypes for Organization Management)
       back-end service, which is available as a selection when you choose F4 help.

        The Relations, Fields, Infotypes and Operations tools are automatically available
        under this back-end service.

        It is also possible to select the back-end service when you are creating the form
        scenario.

    3. In the navigation pane, go toValidity Period.

        Enter Start Object Type as S = Job, enter Application Type as PD.

    4. Choose Save.

Configuring the Organizational Process
    1. In the navigation pane for the form scenario, go to    Back-End Services     SAP_PD
         PD Objects .

    2. In the right-hand pane, create an entry for the LEAD_OBJECT_ID, which is the object
       type that the process is to be started for — choosing from job, position, or
       organizational unit, depending on the process requirements.


             Example

        For process Change Job Name, the LEAD_OBJECT_ID is job.


To create a relationship between the lead object and a related object:

    1. In the navigation pane for the form scenario, go to    Back-End Services     SAP_PD
         PD Objects .



HR Administrative Services (PA-AS)           6956                                           182
SAP Online Help                                                                         22.04.2009


    2. The technical details for the leading object type are displayed in the first row of the
       table. Enter the details for the related object type in the next row of the table. Enter
       the object ID Fieldname, Object Type, Object Abbr. Fieldname, Object Text
       Fieldname, and the relevant operation.

        Choose Save. The system automatically creates new a new entry for the related
        object type in the hierarchy.

    3. In the navigation pane, go to Back-End Services           SAP_PD       PD Objects
         LEAD_OBJECT_ID Relations .

        Enter the technical details of the related object type in the first row of the table
        displayed on this screen.

        The Object ID Fieldname — for leading object type — is displayed as a reference
        object on the Relations, Fields, and Infotypes and Operations screens.


             Example

        You want to create and assign a position under the lead object Organizational Unit.


.

Execute an Organizational Process
To execute organizational processes for the object types job, position, or organizational unit:

    1. To start an organizational process, choose Start Organizational Process in the Portal
       services.

    2. Choose object type as Job, Position, or Organizational Unit.

    3. Search for specific object using search fields Object ID, Object abbreviation, and
       Object name. Select an object from the results displayed in the table. Choose Select
       Process.

    4. Choose a process from the list that appears in the table. Choose Edit.

    5. Enter the relevant data on the form. Insert a comment in the Comments field if
       necessary. At this point, you can choose to save the data you have entered so far if
       you want to leave the process and come back to it later by choosing Save Draft. For
       more information, see Workflow Template WS17900404: Draft for Process Start.

    6. To proceed with the process, choose Check and Send. Review the data you have
       entered and choose Send.

    7. If this is a single-step process, when you choose Send, the master data is updated,
       with no further processing involved. If this process requires workflow, the work item is
       sent to the next agent in the process for processing.

    8. The next agent in the process receives the work item in his or her worklist, or in an e-
       mail in Microsoft Outlook with a link to the work item to be processed, if e-mail
       notification is set up. This agent can review and edit the data, which appears in a
       form, for the object. If further processing is required, the form is sent to the next agent
       in the process. If no further processing is required, this agent saves the data, which is
       updated in the master data for that object. Verify the data is updated with transaction
       PP01 in the back-end system.

For a sample process, see Change Job Attributes.




HR Administrative Services (PA-AS)             6956                                            183
SAP Online Help                                                                     22.04.2009



     Creating an OM Process (Exercise 1)

In this lesson, you create a two-step Organizational Management (OM) process, which allows
to you to complete the following activities:

        Change the Abbreviation and Text fields of an organizational unit.

When you create the process, you test it at three different stages to make sure that each
component of the process is error free.

Procedure
This OM process is composed of the following steps:

    1. Create a form scenario using the Back-End service SAP_PD.

    2. Define the object type and operation of the leading object.

    3. Define the form scenario fields and operations.

    4. Create the process (with no workflow template and no form) using the form scenario
       you have created.

    5. Test the process to ensure the form scenario and form fields are error free.

    6. Create and define the form.

    7. Test the process (now including a form) in the Portal to ensure the form is error free.

    8. Create and define the workflow template (using tasks specific for OM processes).

    9. Test the process (now including a form and a workflow template) in the Portal to
       ensure that the workflow is error free.

Use the following figure as a template for the form you create.




HR Administrative Services (PA-AS)           6956                                           184
SAP Online Help                                                                22.04.2009




                  This form        you to change the              and Text
                  This form allows you to change the Abbreviation and Text
                  records a position.
                  records of an Organizational Unit.



                  Current Entry                  New Entry



                  Org. Unit ID

                  Org. Unit Abbrev.              Org. Unit Abbrev.


                  Org. Unit Text                 Org. Unit Text




                  Effective Date                      Refresh Data




Creating the Form Scenario using Back-End Service SAP_PD
You create a form scenario for an OM process in the same way you create one for a PA
process, with one exception: you use a different Back-End service, SAP_PD.

   1. Start Design Time for Processes and Forms (transaction HRASR_DT)

   2. In the object selection area, choose Form Scenario.

       In the ID field, enter ZH01 and choose Display.

   3. The Create Object dialog box appears.

       Choose Yes to create the object.

   4. The Create Form Scenario dialog box appears.

       Enter in the following information:

           o   Form Scenario: ZH01

           o   Name: Change Organizational Unit Name

           o   ISR: ZH01

           o   Form: ZH01

           o   Back-End Service: SAP_PD

   5. Save your entries. The Create Form dialog box appears.

       Choose Yes to create the form scenario and the ISR scenario.

       Design Time for Processes and Forms displays the hierarchy for your form scenario.


HR Administrative Services (PA-AS)                   6956                              185
SAP Online Help                                                                       22.04.2009


The form scenario of an OM process looks different to that of a PA process. Note that under
the Backend Services folder there is an extra view, PD Objects. Inside this view is a default
folder, LEAD_OBJECT_ID.

Defining Object Types and Operations
In an OM process, you must define the object type of the leading object.

In this process, the leading object is of Organizational Unit object type. Note that we choose
the Change operation for this object type, as we want to change the values in the
Abbreviation and Text fields of the organizational unit.

    1. In the object hierarchy area, choose      Back-End Services     SAP_PD      PD Objects
         .

        LEAD_OBJECT_ID appears in the first row as a default ID. This will represent the
        organizational unit object type.

        Enter the data in the following table (for columns marked with an asterisk, use the
        dropdown lists to enter the data; in the other columns, enter the data manually):

                                                                               Default
            Object ID                            Object Abbr.     Object Text            Operation
                              Object Type *                                   Value Type
            Fieldname                             Fieldname       Fieldname                  *
                                                                                   *

        LEAD_OBJECT_ID Organizational                                            Value for
                                      LO_O_ABBR                  LO_O_TXT        Effective     Change
                        Unit
        (default value)                                                          Date

    2. Save your entries.

        Messages inform you that your fields have been created and that these fields are
        mapped to the Back-End service SAP_PD.

        The PD Objects view now includes the following folder:

            o   LEAD_OBJECT_ID

        Note that the system uses the object ID field name that you entered in the table
        above for the folder names.

    3. Choose the Fields view.

        The field names for Object Abbreviation and Object Text that you provided in the
        table above (in PD_Objects) are now represented as fields in the rows of this table.
        This behavior is special to fields of infotype 1000. To add more fields in this folder,
        choose the Service Fields button.

        You define these fields later in this process.

Defining Form Scenario Fields and Operations
In this form scenario, we require two further form scenario fields in which to enter the new
values for Abbreviation and Text of the organizational unit (those fields you created previously
will display the current values for Abbreviation and Text).

For more information on adding fields to a form scenario, see the tutorial for creating a PA
process, 1.1 Configuring a Form Scenario and an ISR Scenario.


    Recommendation



HR Administrative Services (PA-AS)            6956                                             186
SAP Online Help                                                                        22.04.2009


PD Objects provides a Fields view for each of the objects in your form scenario. When you
add more fields to your form scenario in an OM process, it is recommended that you enter the
fields in these views. The other Fields view, in the object hierarchy area, shows the fields in
the PD Objects Fields views plus additional, mandatory fields, which the system
requires and adds automatically.


    1. In the object hierarchy, choose      PD Objects        LEAD_OBJECT_ID       Fields     .

    2. Choose Service Fields.

        The Transfer Service Fields dialog box appears. Enter the following data:

            o     Object ID Field Name: Lead_Object_ID

            o     Infotype: 1000

            o     Screen Structure: P1000

    3. Choose Enter.

    4. Choose Determine Fields to display the available list of fields for the chosen object
       type.

        Transfer the fields in the following table to your form scenario, making the following
        changes to Field Name and Default Value:

                Field Name         Service Field                Name                 Default Value

        LO_O_ABBR_NEW              SHORT                Object Abbreviation    Value for Effective Date

        LO_O_TXT_NEW               STEXT                Object Name            Value for Effective Date

    5. Save your entries.

    6. Ensure that the current (“old”) fields for the organizational unit (on your form) cannot
       be changed during runtime.

        To do this, remain in the Fields view of LEAD_OBJECT_ID and change the object
        settings as shown in the following table:

             Object            Field Attribute                 Default Value                Op. Exclusion

        LO_O_ABBR            Output Only           Day Before Effective Date           Select

        LO_O_TXT             Output Only           Day Before Effective Date           Select

    7. Set the Effective Date field to Required Entry.

        In the object hierarchy area, choose Fields. Effective Date is one of the mandatory
        fields which the system added automatically. Choose Required Entry as the Field
        Attribute for Effective Date.

    8. Choose       LEADING_OBJECT_ID            Infotypes and Operations      .

        Only one operation (Change) is shown here; it is the operation to be performed on the
        organizational unit.




HR Administrative Services (PA-AS)               6956                                             187
SAP Online Help                                                                     22.04.2009


Creating the Process
You create the process using the form scenario that you have created in the previous steps.

      In the object selection area, choose Process.
        Enter the name ZH01 and choose Display.

        The Create Object dialog box appears.

      Choose Yes to create the object.
        The Create Process dialog box appears.

      Enter the following information and choose Continue:

              Process Name: Change Organizational Unit Name

              Form Scenario: ZIH01

      Choose Continue.
        Design Time for Processes and Forms displays the data for your process.

      In the object hierarchy area, choose the Validity Period view and enter the following
      information:

              Send Variant: Write Data to Application Database

              Process Type: Process with Start Object

              Start Object Type: Organizational Unit

              Application Type: PD

      Choose Workflow.
        Enter the workflow ID as NO_WORKFLOW.

      In the object hierarchy area, double-click your process (the top level node in the
      hierarchy). Select Permit Parallel Runs.

             Recommendation

        Choose this setting at least for the test and implementation phase of your process. It
        allows you to start the required process, for the same object ID, more than once when
        testing. During live system operations, you can undo this setting for individual
        processes.



      Check the process consistency.
        To do this, in the object hierarchy area, choose the root node of the process. Choose
        Check on the toolbar. Edit your form scenario according to error messages displayed
        in the status bar.

      Save your entries.

Testing the Process
To test your process so far, complete the following steps:

    1. In the object hierarchy area, double-click the root node of your process.


HR Administrative Services (PA-AS)           6956                                             188
SAP Online Help                                                                     22.04.2009


        The Process menu option appears on the toolbar.

    2. Choose      Process    Test    .

        Enter the following information:

            o   Application: Personnel Development

            o   Process: ZHO1 (entered by default from Design Time for Processes and
                Forms)

            o   Object Type: O (Organizational Unit)

            o   Object Key: Enter the object ID of the organizational unit which you wish to
                change.

        The process is started and the data is displayed in tabular form. Enter the ID of the
        organizational unit you wish to change and step through the process until it is
        completed.

    3. Use Transaction PP01, in display mode, to check that the process has changed the
       data of your organizational unit.

Creating and Defining the Form
You create a form for an OM process in the same way that you create a form for a PA
process (for detailed information, see Creating a Form and Editing the Layout).

The following is an outline of the steps you complete:

    1. In the hierarchy, choose      Form Scenarios      <Form Scenario Name>     Form       .

    2. Create a new form.

    3. Add the ISR Form-Wide Scripts Control Element.

    4. Add the fields to your form, as detailed in the following table:

           Field Name (Data View tab)                    Label                ISR Control Element

        LO_O_ABBR_NEW                        Org. Unit Abbrev New         ISR Text Edit

        LO_O_TXT_NEW                         Org. Unit Text New           ISR Text Edit

        LO_O_ID                              Org. Unit ID                 ISR Text Display

        LO_O_ABBR                            Org. Unit Abbrev Old         ISR Text Display

        LO_O_TXT                             Org. Unit Text Old           ISR Text Display

        <BLANK>                              <BLANK>                      Hidden Bound Text Field

    5. Add an Effective Date field.

    6. Add a Refresh Data push-button. Edit the scripting behind it to
       USER_EVENT_INITIALIZE.

    7. Bind the form fields to the form scenario.

    8. Save and activate the form.



HR Administrative Services (PA-AS)            6956                                               189
SAP Online Help                                                                    22.04.2009


Testing the Process (with the Form)
You now test that the process with the form works correctly (for more information, see the
tutorial for creating a PA process, Testing a Process (Portal). To do this, complete the
following steps:

    1. Open the Portal and choose the HR Administrator role.

    2. Choose Start Organizational Process.

        A roadmap for Start Processes appears in a new window.

    3. Find the organizational unit whose Abbreviation and Text fields you wish to change.

        To do this, use the search fields Object Type, Object ID, Object Abbreviation and
        Object Name and choose Start.

    4. Select your located organizational unit in the table.

    5. Choose Select Process and select your process in the table.

    6. Choose Edit. The system displays your form.

        Check: Does the form display the values for the Abbreviation and Text fields for the
        organizational unit?

    7. Enter new data for Abbreviation and Text for the organizational unit.

    8. Choose Check and Send.

        Review the data you have entered, and make changes if necessary.

    9. Choose Send and close the process window.

    10. Check: Use transaction PP01, in display mode, to check that your process changes
        the values for the Abbreviation and Text fields for your chosen organizational unit.

Creating and Defining the Workflow Template
You define a workflow template for a OM process in a similar way that you define a workflow
template for a PA Process (for detailed information, see the tutorial for creating a process,
Creating a Workflow Template with the Process Form Workflow Step).

    Note

The interactive components that you insert into the workflow template for an OM process are
different to those interactive components that you insert into a PA process. In the Task
Groups folder (under My Workflow and Tasks menu bar) there are interactive components
specifically for OM processes.


The following is an outline of the steps you complete:

    1. In the object hierarchy area, choose Create Workflow Template. The Workflow
       Builder is started.

    2. Choose Basic Data and enter the required information.

    3. Retrieve the Tasks Groups for HCM Processes and Forms folder.

    4. Display the Workflow Container menu bar and create the Container Element for the
       Process Object.


HR Administrative Services (PA-AS)           6956                                            190
SAP Online Help                                                                     22.04.2009


    5. Define the trigger event for the workflow.

    6. Define the programming exit at the workflow template level.

    7. Activate the start-event.

    8. In the workflow template, define the workflow step using the task Process PD Form.

    9. Double-click the workflow step and define the properties of the step.

        Make the following settings:

            o   On the Control tab, choose Workflow Initiator as the agent type, so that you
                can test your process easily in the Portal. This is an OM process. You are not
                changing the attributes of an employee (as you do with a PA process).
                Therefore, you cannot later use rules like Find Manager. You must apply
                another logic to find your agents. For further information, see Agent
                Determination Rules for PD processes.

            o   Choose the Binding (Exists) push-button. In the Change Binding for Step
                dialog box, set the &SEND_VARIATION& row in the Data Flow window to A
                (Write Data to Application Database).

    10. Display the Workflow Container menu bar and double-click the container element
        Form. On the Initial Value tab, enter the form scenario details.

    11. Save and activate the workflow template.

    12. Provide your process with the workflow ID.

        Exit the Workflow Builder and return to your process. In the object hierarchy area,
        choose Workflow and enter the workflow ID.

Testing the Process (with Form and Workflow Template)
Execute your process in the Portal to see that there are no errors with the workflow template.
Use transaction PP01 as before, to see if your process has changed the Text and Attribute
values of your organizational unit.

Result
You have created a two-step process containing a form and a workflow template. You have
tested the process for possible errors.



     Creating an OM Process (Exercise 2)

In this lesson, you create a two-step Organizational Management (OM) process, which allows
to you to complete the following activities:

        Change the Abbreviation and Text fields of a position.

        Display the Abbreviation and Text fields of the organizational unit to which the
        position belongs.

When you create the process, you test it at three different stages to make sure that each
component of the process is error free.




HR Administrative Services (PA-AS)           6956                                             191
SAP Online Help                                                                     22.04.2009


Procedure
This OM process is composed of the following steps:

    1. Create a form scenario using the Back-End service SAP_PD.

    2. Define the object types and operations.

    3. Define the relationships between the object types.

    4. Define the form scenario fields and operations.

    5. Create the process (with no workflow template and no form) using the form scenario
       you have created.

    6. Test the process to ensure the form scenario and form fields are error free.

    7. Create and define the form.

    8. Test the process (now including a form) in the Portal to ensure the form is error free.

    9. Create and define the workflow template (using tasks specific for OM processes).

    10. Test the process (now including a form and a workflow template) in the Portal to
        ensure that the workflow is error free.

Use the following figure as a template for the form you create.



                  This form allows you to change the Text and Abbreviation of a
                  position, and to display the Text and Abbreviation of the
                  organizational unit to which the position belongs.



                  Org. Unit ID

                  Org. Unit Abbrev.


                  Org. Unit Text




                  Effective Date                             Refresh Data




                  Current Entry                        New Entry


                  Position ID

                  Position Abbrev.                     Position Abbrev.


                  Position Text                        Position Text




Form Template

Creating the Form Scenario using Back-End Service SAP_PD
You create a form scenario for an OM process in the same way you create one for a PA
process, with one exception: you use a different Back-End service, SAP_PD.


HR Administrative Services (PA-AS)                          6956                            192
SAP Online Help                                                                     22.04.2009


    1. Start Design Time for Processes and Forms (transaction HRASR_DT)

    2. In the object selection area, choose Form Scenario.

        In the ID field, enter ZI01 and choose Display.

    3. The Create Object dialog box appears.

        Choose Yes to create the object.

    4. The Create Form Scenario dialog box appears.

        Enter in the following information:

            o   Form Scenario: ZI01

            o   Name: Change Position Name

            o   ISR: ZI01

            o   Form: ZI01

            o   Back-End Service: SAP_PD

    5. Save your entries. The Create Form dialog box appears.

        Choose Yes to create the form scenario and the ISR scenario.

        Design Time for Processes and Forms displays the hierarchy for your form scenario.

The form scenario of an OM process looks different to that of a PA process. Note that under
the Backend Services folder there is an extra view, PD Objects, which contains a default
folder, LEAD_OBJECT_ID.

Defining Object Types and Operations
In an OM process, you must define the object type of the leading object.

In this process, the leading object is of Position object type. Note that we choose the Change
operation for this object type, as we want to change the values in the Abbreviation and Text
fields of the position.

The secondary object in this process is the Organizational Unit. No operation is performed on
it; the process simply displays the organizational unit's Attribute and Text fields.

    1. In the object hierarchy area, choose     Back-End Services     SAP_PD     PD Objects
         .

        LEAD_OBJECT_ID appears in the first row as a default ID. This will represent the
        position object type. You must also define the secondary object type (in our example,
        this is the organizational unit).

        Enter the data in the following table (for columns marked with an asterisk, use the
        dropdown lists to enter the data; in the other columns, enter the data manually):

                                                                             Default
            Object ID                          Object Abbr.     Object Text            Operation
                              Object Type *                                 Value Type
            Fieldname                           Fieldname       Fieldname                  *
                                                                                 *

        LEAD_OBJECT_ID Position               LO_S_ABBR        LO_S_TXT        Value for      Change
                                                                               Effective



HR Administrative Services (PA-AS)            6956                                            193
SAP Online Help                                                                      22.04.2009



                                                                                Default
            Object ID                            Object Abbr.      Object Text            Operation
                              Object Type *                                    Value Type
            Fieldname                             Fieldname        Fieldname                  *
                                                                                    *

                                                                                 Date
        (default value)

                                                                                 Value for
                              Organizational
        SEC_OBJECT_ID                        SO_O_ABBR             SO_O_TXT      Effective     <BLANK>
                              Unit
                                                                                 Date

    2. Save your entries.

        Messages inform you that your fields have been created and that these fields are
        mapped to the Back-End service SAP_PD.

        The PD Objects view now includes the following folders:

            o   LEAD_OBJECT_ID

            o   SEC_OBJECT_ID

        Note that the system uses the object ID field names that you entered in the table
        above for the folder names.

    3. For each of the above folders, choose the Fields view.

        The field names for Object Abbreviation and Object Text that you provided in the
        table above (in PD_Objects) are now represented as fields in the rows of these
        tables. This behavior is special to fields of infotype 1000. To add more fields in these
        folders, choose the Service Fields button.

        You define these fields later in this process.

Defining the Relationship between the Organizational Units
This process contains two object types. Therefore, you must define through which of the
possible relationships data will be retrieved.

    1. Choose LEAD_OBJECT_ID Relations and enter the data in the following table
       (for columns marked with an asterisk, use the dropdown lists to enter the data; in the
       other columns, enter the data manually):

        Related Object ID Fieldname* Relation* Relation Sign Default Value Type* Operation

        SEC_OBJECT_ID                     003          Bottom Up     Value for Effective Date <BLANK>

    2. Save your entries.

        Note that the Fields view of the leading object now contains extra fields from the
        secondary object.

Defining Form Scenario Fields and Operations
In this form scenario, we require two further form scenario fields in which to enter the new
values for Abbreviation and Text of the position (those fields you created previously will
display the current values for Abbreviation and Text).

For more information on adding fields to a form scenario, see the tutorial for creating a PA
process, 1.1 Configuring a Form Scenario and an ISR Scenario.




HR Administrative Services (PA-AS)              6956                                           194
SAP Online Help                                                                        22.04.2009



    Recommendation

PD Objects provides a Fields view for each of the objects in your form scenario. When you
add more fields to your form scenario in an OM process, it is recommended that you enter the
fields in these views. The other Fields view, in the object hierarchy area, shows the fields in
the PD Objects Fields views plus additional, mandatory fields, which the system
requires and adds automatically.


    1. In the object hierarchy, choose      PD Objects        LEAD_OBJECT_ID       Fields     .

    2. Choose Service Fields.

        The Transfer Service Fields dialog box appears. Enter the following data:

            o     Object ID Field Name: Lead_Object_ID

            o     Infotype: 1000

            o     Screen Structure: P1000

    3. Choose Enter.

    4. Choose Determine Fields to display the available list of fields for the chosen object
       type.

        Transfer the fields in the following table to your form scenario, making the following
        changes to Field Name and Default Value:

                Field Name         Service Field                Name                 Default Value

        LO_S_ABBR_NEW              SHORT                Object Abbreviation    Value for Effective Date

        LO_S_TXT_NEW               STEXT                Object Name            Value for Effective Date

    5. Save your entries.

    6. Ensure that the current (“old”) fields for the position (on your form) cannot be changed
       during runtime.

        To do this, remain in the Fields view of LEAD_OBJECT_ID and change the object
        settings as shown in the following table:

             Object            Field Attribute                 Default Value                Op. Exclusion

        LO_S_ABBR            Output Only           Day Before Effective Date           Select

        LO_S_TXT             Output Only           Day Before Effective Date           Select

    7. Set the Effective Date field to Required Entry.

        In the object hierarchy area, choose Fields. Effective Date is one of the mandatory
        fields which the system added automatically. Choose Required Entry as the Field
        Attribute for Effective Date.

    8. Choose       LEADING_OBJECT_ID            Infotypes and Operations      .

        Only one operation (Change) is shown here; it is the operation to be performed on the
        position.


HR Administrative Services (PA-AS)               6956                                             195
SAP Online Help                                                                    22.04.2009



            Note

        The view Infotypes and Operations is repeated in the folders of each object within PD
        Objects. The details in the view are identical in each folder, as it shows all the
        operations to be performed on the object types in the process.



Creating the Process
You create the process using the form scenario that you have created in the previous steps.

    1. In the object selection area, choose Process.

        Enter the name ZI01 and choose Display.

        The Create Object dialog box appears.

    2. Choose Yes to create the object.

        The Create Process dialog box appears.

    3. Enter the following information and choose Continue:

            o   Process Name: Change Position Name

            o   Form Scenario: ZI01

    4. Choose Continue.

        Design Time for Processes and Forms displays the data for your process.

    5. In the object hierarchy area, choose the Validity Period view and enter the following
       information:

            o   Send Variant: Write Data to Application Database

            o   Process Type: Process with Start Object

            o   Start Object Type: Position

            o   Application Type: PD

    6. Choose Workflow.

        Enter the workflow ID as NO_WORKFLOW.

    7. In the object hierarchy area, double-click your process (the top level node in the
       hierarchy). Select Permit Parallel Runs.


            Recommendation

        Choose this setting at least for the test and implementation phase of your process. It
        allows you to start the required process, for the same object ID, more than once when
        testing. During live system operations, you can undo this setting for individual
        processes.


    8. Check the process consistency.




HR Administrative Services (PA-AS)           6956                                           196
SAP Online Help                                                                      22.04.2009


        To do this, in the object hierarchy area, choose the root node of the process. Choose
        Check on the toolbar. Edit your form scenario according to error messages displayed
        in the status bar.

    9. Save your entries.

Testing the Process
To test your process so far, complete the following steps:

    1. In the object hierarchy area, double-click the root node of your process.

        The Process menu option appears on the toolbar.

    2. Choose      Process    Test    .

        Enter the following information:

            o   Application: Personnel Development

            o   Process: ZIO1 (entered by default from Design Time for Processes and
                Forms)

            o   Object Type: S (Position)

            o   Object Key: Enter the object ID of the position which you wish to change.

        The process is started and the data is displayed in tabular form. Enter the ID of the
        position you wish to change and step through the process until it is completed.

    3. Use Transaction PP01, in display mode, to check that the process has changed the
       data of your position and that the organizational unit to which it belongs is also
       displayed.

Creating and Defining the Form
You create a form for an OM process in the same way that you create a form for a PA
process (for detailed information, see Creating a Form and Editing the Layout).

The following is an outline of the steps you complete:

    1. In the hierarchy, choose      Form Scenarios      <Form Scenario Name>      Form      .

    2. Create a new form.

    3. Add the ISR Form-Wide Scripts Control Element.

    4. Add the fields to your form, as detailed in the following table:

           Field Name (Data View tab)                    Label                ISR Control Element

        LO_S_ABBR_NEW                         Position Abbrev New         ISR Text Edit

        LO_S_TXT_NEW                          Position Text New           ISR Text Edit

        LO_S_ID                               Position ID                 ISR Text Display

        LO_S_ABBR                             Position Abbrev Old         ISR Text Display

        LO_S_TXT                              Position Text Old           ISR Text Display




HR Administrative Services (PA-AS)            6956                                               197
SAP Online Help                                                                    22.04.2009



           Field Name (Data View tab)                 Label                  ISR Control Element

        SO_O_ABBR                            Org. Unit Abbrev            ISR Text Display

        SO_O_TXT                             Org. Unit Text              ISR Text Display

        SO_O_ID                              Org. Unit ID                ISR Text Display

        <BLANK>                              <BLANK>                     Hidden Bound Text Field

    5. Add an Effective Date field.

    6. Add a Refresh Data push-button. Edit the scripting behind it to
       USER_EVENT_INITIALIZE.

    7. Bind the form fields to the form scenario.

    8. Save and activate the form.

Testing the Process (with the Form)
You now test that the process with the form works correctly (for more information, see the
tutorial for creating a PA process, Testing a Process (Portal). To do this, complete the
following steps:

    1. Open the Portal and choose the HR Administrator role.

    2. Choose Start Organizational Process.

        A roadmap for Start Processes appears in a new window.

    3. Find the position whose Abbreviation and Text fields you wish to change.

        To do this, use the search fields Object Type, Object ID, Object Abbreviation and
        Object Name and choose Start.

    4. Select your located position in the table.

    5. Choose Select Process and select your process in the table.

    6. Choose Edit. The system displays your form.

        Check: Does the form display the values for the Abbreviation and Text fields for the
        organizational unit?

    7. Enter new data for Abbreviation and Text for the position.

    8. Choose Check and Send.

        Review the data you have entered, and make changes if necessary.

    9. Choose Send and close the process window.

    10. Check: Use transaction PP01, in display mode, to check that your process changes
        the values for the Abbreviation and Text fields for your chosen position.

Creating and Defining the Workflow Template
You define a workflow template for a OM process in a similar way that you define a workflow
template for a PA Process (for detailed information, see the tutorial for creating a process,
Creating a Workflow Template with the Process Form Workflow Step).


HR Administrative Services (PA-AS)           6956                                            198
SAP Online Help                                                                     22.04.2009



    Note

The interactive components that you insert into the workflow template for an OM process are
different to those interactive components that you insert into a PA process. In the Task
Groups folder (under My Workflow and Tasks menu bar) there are interactive components
specifically for OM processes.


The following is an outline of the steps you complete:

    1. In the object hierarchy area, choose Create Workflow Template. The Workflow
       Builder is started.

    2. Choose Basic Data and enter the required information.

    3. Retrieve the Tasks Groups for HCM Processes and Forms folder.

    4. Display the Workflow Container menu bar and create the Container Element for the
       Process Object.

    5. Define the trigger event for the workflow.

    6. Define the programming exit at the workflow template level.

    7. Activate the start-event.

    8. In the workflow template, define the workflow step using the task Process PD Form.

    9. Double-click the workflow step and define the properties of the step.

        Make the following settings:

            o   On the Control tab, choose Workflow Initiator as the agent type, so that you
                can test your process easily in the Portal. This is an OM process. You are not
                changing the attributes of an employee (as you do with a PA process).
                Therefore, you cannot later use rules like Find Manager. You must apply
                another logic to find your agents. For further information, see Agent
                Determination Rules for PD processes.

            o   Choose the Binding (Exists) push-button. In the Change Binding for Step
                dialog box, set the &SEND_VARIATION& row in the Data Flow window to A
                (Write Data to Application Database).

    10. Display the Workflow Container menu bar and double-click the container element
        Form. On the Initial Value tab, enter the form scenario details.

    11. Save and activate the workflow template.

    12. Provide your process with the workflow ID.

        Exit the Workflow Builder and return to your process. In the object hierarchy area,
        choose Workflow and enter the workflow ID.

Testing the Process (with Form and Workflow Template)
Execute your process in the Portal to see that there are no errors with the workflow template.
Use transaction PP01 as before, to see if your process has changed the Text and Attribute
values of your position.




HR Administrative Services (PA-AS)           6956                                             199
SAP Online Help                                                                     22.04.2009


Result
You have created a two-step process containing a form and a workflow template. You have
tested the process for possible errors.



     Creating an OM Process (Exercise 3)

In this lesson, you create a two-step Organizational Management (OM) process, which allows
to you to complete the following activities:

        Create a Position.

        Assign the position automatically to the Organizational Unit to which it belongs.

When you create the process, you test it at three different stages to make sure that each
component of the process is error free.

Procedure
This OM process is composed of the following steps:

    1. Create a form scenario using the Back-End service SAP_PD.

    2. Define the object types and operations.

    3. Define the relationships between the object types.

    4. Define the form scenario fields and operations.

    5. Create the process (with no workflow template and no form) using the form scenario
       you have created.

    6. Test the process to ensure the form scenario and form fields are error free.

    7. Create and define the form.

    8. Test the process (now including a form) in the Portal to ensure the form is error free.

    9. Create and define the workflow template (using tasks specific for OM processes).

    10. Test the process (now including a form and a workflow template) in the Portal to
        ensure that the workflow is error free.

Use the following figure as a template for the form you create.




HR Administrative Services (PA-AS)           6956                                           200
SAP Online Help                                                                           22.04.2009




                  This form allows you to create a position, and to display the records
                  for the organizational unit to which the position is assigned.



                   Org. Unit ID

                   Org. Unit Abbrev.


                   Org. Unit Text




                   Effective Date                              Refresh Data




                   Create New Position


                    Position Abbrev.


                    Position Text




Creating the Form Scenario using Back-End Service SAP_PD
You create a form scenario for an OM process in the same way you create one for a PA
process, with one exception: you use a different Back-End service, SAP_PD.

   1. Start Design Time for Processes and Forms (transaction HRASR_DT)

   2. In the object selection area, choose Form Scenario.

       In the ID field, enter ZJ01 and choose Display.

   3. The Create Object dialog box appears.

       Choose Yes to create the object.

   4. The Create Form Scenario dialog box appears.

       Enter in the following information:

           o   Form Scenario: ZJ01

           o   Name: Create Position, Assign to Org. Unit

           o   ISR: ZJ01

           o   Form: ZJ01

           o   Back-End Service: SAP_PD

   5. Save your entries. The Create Form dialog box appears.

       Choose Yes to create the form scenario and the ISR scenario.

       Design Time for Processes and Forms displays the hierarchy for your form scenario.


HR Administrative Services (PA-AS)                             6956                             201
SAP Online Help                                                                       22.04.2009


The form scenario of an OM process looks different to that of a PA process. Note that under
the Backend Services folder there is an extra view, PD Objects, which contains a default
folder, LEAD_OBJECT_ID.

Defining Object Types and Operations
In an OM process, you must define the object type of the leading object.

In this process, the leading object is of Organizational Unit object type. No operation is
performed on it; the process simply displays the organizational unit's Attribute and Text fields.
The organizational unit must be the leading object in this process; the position (the secondary
object), which the process creates, requires an existing organizational unit to which it can be
assigned.

    1. In the object hierarchy area, choose      Back-End Services     SAP_PD      PD Objects
         .

        LEAD_OBJECT_ID appears in the first row as a default ID. This will represent the
        organizational unit object type. You must also define the secondary object type.

        Enter the data in the following table (for columns marked with an asterisk, use the
        dropdown lists to enter the data; in the other columns, enter the data manually):

                                                                               Default
             Object ID                           Object Abbr.     Object Text            Operation
                              Object Type *                                   Value Type
             Fieldname                            Fieldname       Fieldname                  *
                                                                                   *

        LEAD_OBJECT_ID Organizational                                            Value for
                                      LO_O_ABBR                  LO_O_TXT        Effective    <BLANK>
                        Unit
        (default value)                                                          Date

                                                                                 Value for
        SEC_OBJECT_ID         Position         SO_S_ABBR         SO_S_TXT        Effective    Create
                                                                                 Date

    2. Save your entries.

        Messages inform you that your fields have been created and that these fields are
        mapped to the Back-End service SAP_PD.

        The PD Objects view now includes the following folders:

            o   LEAD_OBJECT_ID

            o   SEC_OBJECT_ID

        Note that the system uses the object ID field names that you entered in the table
        above for the folder names.

    3. For each of the above folders, choose the Fields view.

        The field names for Object Abbreviation and Object Text that you provided in the
        table above (in PD_Objects) are now represented as fields in the rows of these
        tables. This behavior is special to fields of infotype 1000. To add more fields in these
        folders, choose the Service Fields button.

        You define these fields later in this process.




HR Administrative Services (PA-AS)            6956                                            202
SAP Online Help                                                                     22.04.2009


Defining the Relationship between the Organizational Units
This process contains two object types. Therefore, you must define through which of the
possible relationships data will be retrieved.

    1. Choose SEC_OBJECT_ID Relations and enter the data in the following table
       (for columns marked with an asterisk, use the dropdown lists to enter the data; in the
       other columns, enter the data manually):

        Related Object ID Fieldname* Relation* Relation Sign Default Value Type* Operation

        LEAD_OBJECT_ID                    003          Bottom Up     Value for Effective Date Create

    2. Save your entries.

        Note that the Fields view of the leading object now contains extra fields from the
        secondary object.

Defining Form Scenario Fields and Operations
In this form scenario, we require no further form scenario fields.

For more information on adding fields to a form scenario, see the tutorial for creating a PA
process, 1.1 Configuring a Form Scenario and an ISR Scenario.

    Recommendation

PD Objects provides a Fields view for each of the objects in your form scenario. When you
add more fields to your form scenario in an OM process, it is recommended that you enter the
fields in these views. The other Fields view, in the object hierarchy area, shows the fields in
the PD Objects Fields views plus additional, mandatory fields, which the system
requires and adds automatically.



Creating the Process
You create the process using the form scenario that you have created in the previous steps.

    1. In the object selection area, choose Process.

        Enter the name ZJ01 and choose Display.

        The Create Object dialog box appears.

    2. Choose Yes to create the object.

        The Create Process dialog box appears.

    3. Enter the following information and choose Continue:

            o   Process Name: Create Position, Assign to Org. Unit

            o   Form Scenario: ZJ01

    4. Choose Continue.

        Design Time for Processes and Forms displays the data for your process.

    5. In the object hierarchy area, choose the Validity Period view and enter the following
       information:



HR Administrative Services (PA-AS)              6956                                           203
SAP Online Help                                                                     22.04.2009


            o   Send Variant: Write Data to Application Database

            o   Process Type: Process with Start Object

            o   Start Object Type: Organizational Unit

            o   Application Type: PD

    6. Choose Workflow.

        Enter the workflow ID as NO_WORKFLOW.

    7. In the object hierarchy area, double-click your process (the top level node in the
       hierarchy). Select Permit Parallel Runs.


             Recommendation

        Choose this setting at least for the test and implementation phase of your process. It
        allows you to start the required process, for the same object ID, more than once when
        testing. During live system operations, you can undo this setting for individual
        processes.


    8. Check the process consistency.

        To do this, in the object hierarchy area, choose the root node of the process. Choose
        Check on the toolbar. Edit your form scenario according to error messages displayed
        in the status bar.

    9. Save your entries.

Testing the Process
To test your process so far, complete the following steps:

    1. In the object hierarchy area, double-click the root node of your process.

        The Process menu option appears on the toolbar.

    2. Choose      Process    Test     .

        Enter the following information:

            o   Application: Personnel Development

            o   Process: ZJO1 (entered by default from Design Time for Processes and
                Forms)

            o   Object Type: O (Organizational Unit)

            o   Object Key: Enter the object ID of the organizational unit, for which you wish
                to create a new position.

        The process is started and the data is displayed in tabular form. Enter the ID of an
        organizational unit, for which you wish to create a new position, and step through the
        process until it is completed.

    3. Use Transaction PP01, in display mode, to check that the process has created the
       new position under your chosen organizational unit.




HR Administrative Services (PA-AS)           6956                                           204
SAP Online Help                                                                       22.04.2009


Creating and Defining the Form
You create a form for an OM process in the same way that you create a form for a PA
process (for detailed information, see Creating a Form and Editing the Layout).

The following is an outline of the steps you complete:

    1. In the hierarchy, choose     Form Scenarios       <Form Scenario Name>       Form     .

    2. Create a new form.

    3. Add the ISR Form-Wide Scripts Control Element.

    4. Add the fields to your form, as detailed in the following table:

            Field Name (Data View tab)                   Label                ISR Control Element

        LO_O_ID                                 Org. Unit ID              ISR Text Display

        LO_O_ABBR                               Org. Unit Abbrev          ISR Text Display

        LO_O_TXT                                Org. Unit Text            ISR Text Display

        SO_S_ABBR                               Position Abbrev           ISR Text Display

        SO_S_TXT                                Position Text             ISR Text Display

        SO_S_ID                                 Position ID               ISR Text Display

        <BLANK>                                 <BLANK>                   Hidden Bound Text Field

    5. Add an Effective Date field.

    6. Add a Refresh Data push-button. Edit the scripting behind it to
       USER_EVENT_INITIALIZE.

    7. Bind the form fields to the form scenario.

    8. Save and activate the form.

Testing the Process (with the Form)
You now test that the process with the form works correctly (for more information, see the
tutorial for creating a PA process, Testing a Process (Portal). To do this, complete the
following steps:

    1. Open the Portal and choose the HR Administrator role.

    2. Choose Start Organizational Process.

        A roadmap for Start Processes appears in a new window.

    3. Find the organizational unit, for which you wish to create a position.

        To do this, use the search fields Object Type, Object ID, Object Abbreviation and
        Object Name and choose Start.

    4. Select your located organizational unit in the table.

    5. Choose Select Process and select your process in the table.



HR Administrative Services (PA-AS)            6956                                               205
SAP Online Help                                                                    22.04.2009


    6. Choose Edit. The system displays your form.

        Check: Does the form display the values for the Abbreviation and Text fields for the
        organizational unit?

    7. Enter new data for Abbreviation and Text for the position.

    8. Choose Check and Send.

        Review the data you have entered, and make changes if necessary.

    9. Choose Send and close the process window.

    10. Check: Use transaction PP01, in display mode, to check that your process creates a
        new position for your chosen organizational unit.

Creating and Defining the Workflow Template
You define a workflow template for a OM process in a similar way that you define a workflow
template for a PA Process (for detailed information, see the tutorial for creating a process,
Creating a Workflow Template with the Process Form Workflow Step).


    Note

The interactive components that you insert into the workflow template for an OM process are
different to those interactive components that you insert into a PA process. In the Task
Groups folder (under My Workflow and Tasks menu bar) there are interactive components
specifically for OM processes.


The following is an outline of the steps you complete:

    1. In the object hierarchy area, choose Create Workflow Template. The Workflow
       Builder is started.

    2. Choose Basic Data and enter the required information.

    3. Retrieve the Tasks Groups for HCM Processes and Forms folder.

    4. Display the Workflow Container menu bar and create the Container Element for the
       Process Object.

    5. Define the trigger event for the workflow.

    6. Define the programming exit at the workflow template level.

    7. Activate the start-event.

    8. In the workflow template, define the workflow step using the task Process PD Form.

    9. Double-click the workflow step and define the properties of the step.

        Make the following settings:

            o   On the Control tab, choose Workflow Initiator as the agent type, so that you
                can test your process easily in the Portal. This is an OM process. You are not
                changing the attributes of an employee (as you do with a PA process).
                Therefore, you cannot later use rules like Find Manager. You must apply
                another logic to find your agents. For further information, see Agent
                Determination Rules for PD processes.




HR Administrative Services (PA-AS)           6956                                          206
SAP Online Help                                                                       22.04.2009


            o    Choose the Binding (Exists) push-button. In the Change Binding for Step
                 dialog box, set the &SEND_VARIATION& row in the Data Flow window to A
                 (Write Data to Application Database).

    10. Display the Workflow Container menu bar and double-click the container element
        Form. On the Initial Value tab, enter the form scenario details.

    11. Save and activate the workflow template.

    12. Provide your process with the workflow ID.

        Exit the Workflow Builder and return to your process. In the object hierarchy area,
        choose Workflow and enter the workflow ID.

Testing the Process (with Form and Workflow Template)
Execute your process in the Portal to see that there are no errors with the workflow template.
Use transaction PP01 as before, to see if your process has created a position for your chosen
organizational unit.

Result
You have created a two-step process containing a form and a workflow template. You have
tested the process for possible errors.



     Process Start without Employee Selection

It is possible to start a process without first selecting an employee; you proceed directly to the
process selection stage by choosing the Skip Employee Selection checkbox.

In this type of process, you have the following options when choosing to assign the employee:

        You choose to assign the employee at a later stage in the process (for example, the
        third agent in the process assigns the employee).

        You choose not to assign the employee at all.

        In this case, the data is not saved in the infotypes in the backend system but is saved
        in the process object in Case Management.

Use this type of process if, for example, you do not have the employee details readily
available, but want to get the process underway. You start the process, and a subsequent
agent involved in the process assigns the employee.

The following figure outlines this type of process:




HR Administrative Services (PA-AS)            6956                                            207
SAP Online Help                                                                         22.04.2009



                1                            2                          3


               Start
             Process
            with HCM
            Processes                      Edit Data                  Edit Data
               and
              Forms




        First agent starts
                                 Second agent edits data       Third agent edits data
        process, without
                                    and sends form                and saves form
     selecting an employee




                                                Assign employee
                                        (or leave employee unassigned)




With Enhancement Package 4, you receive the sample process Special Payment (XX)
(Process Start Without Personnel Number).

There is a new container element ASSIGN_OBJECT, which has been added to standard tasks
TS17900100 Edit Form and TS4000018 Process PD Form. This element allows you to assign
the object or employee at a later stage in the process. If this element is set to true (X) and the
employee is initial, the employee search component (HRASRA) is visible on the top of the
form. Alternatively, if the employee is already assigned, the search option (HRASRA) is made
invisible and the behavior of the task is similar to a standard task. Once the employee is
assigned, at process and step level, the attribute OBJECT_KEY is filled with the value of the
employee (personnel number).

When a work item appears in the UWL and the container element ASSIGN_OBJECT is set to
true, the work item text is modified to show that no employee is assigned in that step “No
employee assigned: PROCESS_NAME&:FORM_SCENARIO_STAGE&” (the process name
is the process being executed, scenario stage is status, for example, Approved). This appears
in the work item text. By selecting the work item, the employee search component is
launched, which allows the HR Administrator role, for example, to select the employee on top
of the form, where the employee is not yet assigned. The user starts the process and assigns
the employee in the next step; in the following step the employee details are displayed.

Activities
To enable a process to start without first selecting an employee, you must perform the
following activities:

        In Customizing, you specify which object types are available for specific application
        types, and define the roles that can access these object types.

        You also specify for which roles the Skip Object Selection / Skip Employee Selection
        flag is visible.




HR Administrative Services (PA-AS)               6956                                         208
SAP Online Help                                                                     22.04.2009


        In Design Time for Processes and Forms, you choose the Process without Start
        Object option for the process.

        In the Workflow Builder (transaction SWDD), you select the workflow step in which
        you want to assign the employee and make the necessary settings.

For more information, see Configuring and Starting Processes without Employee Selection.



  Configuring and Starting Processes without
Employee Selection

When you enable a process to start without first selecting an employee, you are presented
with a Skip Employee Selection checkbox in the start application; when you select the
checkbox, you go straight to the process selection stage and continue with the process from
there.

Prerequisites
In the Customizing activity HR Administrative Services Configuration of Forms/Processes
  Process Configuration Set Up Processes Validity for Process Start Define Properties
of Object Types , you have specified which object types are available for specific
application types, and the roles that can access these object types.

Procedure
To configure a process to start without first selecting an employee, you perform the following
steps:

    1. In Customizing, specify for which roles the Skip Object Selection or Skip Employee
       Selection flag is visible. To do this, complete the following steps:

            1. Start the Customizing activity HR Administrative Services Configuration
               of Forms/Processes Process Configuration Set Up Processes Validity
               for Process Start Define Properties of Object Types .

            2. Select an Object Type and choose Object Properties.

                Select an Agent Role and choose Is Skip Visible to display the Skip Object
                Selection or Skip Employee Selection flag in the start application.


                     Note

                Group of Organizational Views allows you to specify which organizational
                view group is used for object selection. A view group consists of a number of
                organizational views on the manager's area of responsibility. Organizational
                views and view groups are based on the Object and Data Provider.
                For more details on the Object and Data Provider (OADP), refer to the
                SAP Service Market Place: www.service.sap.com/erp End-User Service
                Delivery Manager Self-Service Media Library Other Information
                  Object and Data Provider & Employee Search .


    2. Open Design Time for Processes and Forms and make the following setting:

            1. Choose the process you wish to configure and choose the Validity Period
               view.


HR Administrative Services (PA-AS)           6956                                           209
SAP Online Help                                                                    22.04.2009


           2. Under Settings for Start Step, choose Process without Start Object for
              Process Type.

           3. Choose Save.

   3. Open the Workflow Builder and set the ASSIGN_OBJECT container element to True in
      the relevant standard task. This allows the employee to be assigned at that step in
      the process.

           1. Choose the workflow step, in which you want the employee to be assigned,
              and display the basic details of the step.

           2. Choose the Binding Exists push-button.

               The Display Binding For Step dialog box appears.

           3. Choose the dropdown list for the &ASSIGN_OBJECT& workflow container
              element and choose Enter Constant.

           4. Choose X = Pushbutton is Visible and Active.

   4. Start the process in the Portal. To do this, complete the following steps:

           1. Choose Start Process for Employee.

               The Start Processes window appears.

           2. At Step 1 (Select Employees), select the Skip Employee Selection checkbox.

               The employee selection options are grayed out and you move to the next
               screen.

           3. At Step 2, choose Select Process.

               A list of processes, enabled for start without employee selection, are
               displayed.

               Select a process and choose Edit.

           4. Step 3 displays the form for the process, with the fields for the employee
              details remaining empty.

               Fill out the data on the form. Enter an effective date, and a comment if
               necessary.

               Choose Check and Send

           5. Step 4 allows you to review the entered data.

               Choose Send to submit the form to the next agent in the workflow.

           6. The next agent receives the work item and reviews the form and approves or
              rejects the data. He or she chooses Send to submit the form to the final agent
              in the process.

           7. The final agent receives the work item and reviews the form. He or she
              assigns the personnel number of the employee using the Employee Search
              function at the top of the form. When the final agent chooses Send the
              system updates the master data in the backend system.


            Note




HR Administrative Services (PA-AS)          6956                                           210
SAP Online Help                                                                    22.04.2009


        In this example, the employee is not assigned by the initiator of the process, nor by
        the second agent in the workflow. The employee is finally assigned by the last agent
        in the workflow. The agent assigns the employee by using the search function which
        appears at the top of the form only at this step in the workflow.



More Information
For a sample process, see Special Payment (Process Start Without Employee Selection)



      Checks and Utilities for Processes and Forms
Use
The following checks and utilities are available in Design Time for processes and forms:

      Check the Configuration of a Process [Page 211]

      Test a Process [Page 212]

      Check Objects for Inconsistencies [Page 213]

      Compare and Reconcile Objects [Page 213]

      Export and Import of Objects As XML File [Page 215]




      Check the Configuration of a Process
Use
You can use this function to check whether the Customizing settings that you made for your
process are complete and correct.

Features
The system uses the report Check Consistency of Processes (RPASR_CHECK_PROCESS)
for the check. The system performs the following checks:

Process
      Is the start configuration of the process correct?

      Is the process assigned at least one initiator role?

      Are the settings for assigning reference numbers when running a process consistent?

      Are the settings for the Case Management case types consistent?

      Are the settings for handling errors consistent?

      Is the entire process for Design Time consistent?

Workflow Template
      Is the process assigned a workflow template?

      Is the assigned workflow template consistent?



HR Administrative Services (PA-AS)           6956                                          211
SAP Online Help                                                                     22.04.2009


      Is event type linkage generated for the assigned workflow template?

      Are rules set for determining processors?

      Which rules for determining processors are used in the workflow template?

      Are the settings for the workflow steps consistent?

      Which additional workflow template references the assigned workflow template?

      Are the background steps of the workflow template consistent?

      Is event type linkage generated for the standard workflow templates provided by SAP?

Form Scenario
      Which start form scenario does the process use?

      Which other form scenarios does the process use?

      Are the form scenarios consistent?
For more information, see the documentation for the report Check Consistency of Processes.

Activities
...




      To check all settings for a process, select the desired process, and in the menu
      choose Process      Check.

      To check the settings for a particular validity period of the process, double-click the
      validity period in the object hierarchy area to select it, and in the menu choose Process
         Check Validity Period.




      Test a Process
Use
You can use this function to test the execution of a process without needing the portal
environment and the form application.



             When testing the process, the user interface (portal, form application, and so on)
             is only simulated. However, the process itself is not simulated, it is really run.
             Therefore, use this test function in your test system only and not in the
             production system.

Features
To test, use the report Test Process (RPASR_TEST_PROCESS_EXECUTION). For more
information, see the documentation for this report.

Activities
Select the desired process, and in the menu, choose Process       Test.




HR Administrative Services (PA-AS)           6956                                          212
SAP Online Help                                                                       22.04.2009



      Check Objects for Inconsistencies
Use
You use this function to check processes and forms for database inconsistencies.



              A database inconsistency occurs, for example, if there is a field definition for
              form scenario version 1 in a form scenario, but this version is not defined in the
              form scenario.



              Such inconsistencies can occur when you edit a form scenario with the
              Customizing views in the Implementation Guide for HR Administrative Services
              under Configuration of Forms/Processes    Form Configuration. Design Time
              for processes and forms prevents such inconsistencies.

Features
       You can check the following objects for inconsistencies:

              Process

              Form scenario

       You can clean up the inconsistencies.
      The system deletes all unsuitable database entries.



              In the example above, the system would delete the database entries for the field
              definitions of form scenario version 1.
              Instead of deleting the database entries, in this example you could also create
              form scenario version 1 to remove the inconsistency.

Activities
Double-click the required object to select it, and then choose Utilities   Check
Inconsistencies or Remove Inconsistencies.



              You must open the object in change mode to remove inconsistencies.




      Compare and Reconcile Objects
Use
You can use this function to compare processes or form scenarios using systems or clients.
You can also copy the settings that you made in a different system or client for a process,
validity period of a process, a form scenario, or a form scenario version, into the current
system.




HR Administrative Services (PA-AS)            6956                                            213
SAP Online Help                                                                           22.04.2009




                 When reconciling, you overwrite the settings that you made in the current
                 system for the object to reconcile, with the settings for the object as they are in
                 the remote system.

Prerequisites
          You have set up an RFC connection between the current system and the remote
          system, which you want to use for the comparison and reconciliation.

          To reconcile, you must be in the change mode of the object that you want to reconcile.

Features
          You can reconcile the following objects with objects from a remote system:

                 Processes

                 Validity periods of processes

                 Form scenarios

                 Form scenario versions

          You can compare the following objects with objects from a remote system:

                 Processes

                 Form scenarios

          You can directly reconcile the object that you are currently processing with a different
          object in the remote system.
          The system overwrites all settings that you made for the current object with the settings
          for the object from the remote system.

          You can display a list of all processes or form scenarios existing in the remote system.

          You can compare all or selected processes or form scenarios from the displayed list.
          The system compares the objects from the remote system with the objects from the
          current system that have the same technical names.

          You can reconcile all or selected processes or form scenarios from the displayed list.
          The system overwrites all settings that you made for the selected object with the
          settings for the corresponding object from the remote system.

Activities
Reconcile Current Object
...




      1. Open the object you want to reconcile, in change mode.
      2. Choose Utilities    Reconcile.
      3. Specify an RFC connection and the object whose settings you want to copy to the
         current object, and choose Continue.
          The system informs you whether the reconciliation was successful.
      4. Save the settings copied from the remote system for the current object.

Display List of Objects in Remote System
...




HR Administrative Services (PA-AS)                6956                                            214
SAP Online Help                                                                        22.04.2009


      1. For processes choose Utilities Reconcile Processes, or for form scenarios choose
         Utilities Reconcile Form Scenarios.



                 Alternately, on the initial screen of Design Time for processes and forms, you
                 can choose Design Time          Reconcile Objects.
      2. Enter an RFC connection.
      3. Choose Display Processes from Remote System or Display Form Scenarios from
         Remote System.

Compare Objects with Objects in Remote System
...




      1. Select the desired objects in the list of objects from the remote system.
      2. Choose Compare with Remote System.
          The system displays the result of the comparison in a dialog box, and sets the
          appropriate status for the compared objects in the list (for example, Process in Current
          System and in Remote System Agree).

Reconcile Objects with Objects in Remote System
...




      1. Select the desired objects in the list of objects from the remote system.
      2. Choose Reconcile (Import from Remote System).
      3. Confirm the system’s query.



                 When you confirm the query, the system copies all settings from the remote
                 system for the affected objects, and saves them in the current system. If you
                 have made settings in the current system for these objects, they are overwritten
                 with the settings from the remote system and are deleted.
          The system informs you whether the reconciliation was successful.




          Export and Import of Objects As XML File
Use
You can use this function to export the settings that you made for a process or form scenario
from your ERP system, and save them as a local XML file on your hard drive. You can then
import the local file into a different system, for example.



                 When you import an XML file, you overwrite all the settings that you made for
                 the object into which you import the file with the settings from the XML file.

Prerequisites
To import an XML file, you must be in change mode in the object into which you want to
import the file.

Activities
Export
...




      1. Double-click the object that you want to export.


HR Administrative Services (PA-AS)               6956                                          215
SAP Online Help                                                                      22.04.2009


      2. Choose Utilities    Export to XML File.
      3. Save the file in the desired directory on your hard drive.

Import
...




      1. Open the object, whose settings you want to overwrite with the settings saved in the
         XML file, in change mode.
      2. Choose Utilities    Import from XML File and import the desired file.
          The system transfers the settings from the XML file into the object.
      3. Save the settings transferred from the XML file for the current object.




          Sample Processes in HCM Processes and Forms
Use
The sample processes delivered with HCM Processes and Forms are intended to show you
how you can configure your own business processes that you want to be handled using HCM
Processes and Forms.
Each of these processes contains the following technical objects that are required to
implement and execute the process:

          Process

                 Workflow template

          ISR Scenario

                 Interface

          Form Scenario

                 Form

                 Scenario step(s)

          Back-End Services

                 Generic services



                 You may not use the sample processes for productive implementation. Rather,
                 you must copy them as customer-specific processes.
                 The activities listed below only serve to make the sample processes delivered
                 executable.

Activities
To use the sample processes for test purposes, in Customizing for HR Administrative
Services you must have performed the IMG activities under Configuration of
Forms/Processes -> Sample Processes for HCM Processes and Forms.




HR Administrative Services (PA-AS)               6956                                           216
SAP Online Help                                                                     22.04.2009



      Hiring, Permanent (Germany)
Purpose
This process supports the hiring of an employee. The process can be started as follows:

       By the Recruiter in SAP E-Recruiting
      In this case, the Recruiter chooses the Transfer function. This automatically transfers
      an applicant’s data from the SAP E-Recruiting system into the HR system, using an XI
      interface. A workflow template is also started, which starts the hiring process in the HR
      system.

       By the HR Administrator in the HR system
      In this case, the HR Administrator manually completes the form that was filled
      automatically with data, using the XI interface, when started using SAP E-Recruiting.
The new employee is also involved in the process, in addition to the Recruiter or HR
Administrator. The new employee receives an e-mail requesting the employee to execute the
Life and Work Event [External] My First Days.
Using the Hiring process accelerates and optimizes the hiring procedure, since the system
integration of all roles guarantees that work items are forwarded as soon as possible, and that
all parties are informed at all times.

Prerequisites
To be able to use this sample process for test purposes, you must have performed the
Customizing activities for HR Administrative Services as described in Configuration of
Forms/Processes      Sample Processes for HCM Processes and Forms.
To be able to send the data, using the XI interface, you must have performed the Customizing
activities for HR Administrative Services as described in Configuration of Forms/Processes
XI Integration.

Technical Objects for Implementing and Executing the Process

Object Type            ID                              Name
Process                HIRE_01                         Hiring an Employee (DE)
Workflow Template      WS17900415                      Start Process for XI Data
                       WS17900011                      Hiring an Employee (DE)
                       WS17900260                      Save Form with Error Handling
                       WS17900015                      Follow-Up Activity after Process with XI
                                                       Scenario
ISR Scenario           SXHR                            Data of XI Message HireRequest
                       SHI1                            HR ASR Hire 01: HR Admin IT 0,1,2,3,6,8
                       SHI2                            HR ASR Hire 02: HR Admin, Form 2
Interface              ISR_IF_SXHR
                       ISR_IF_SHI1
                       ISR_IF_SHI2
Form Scenario          SXHR                            Data of XI Message HireRequest (New Hire)
                                                       Permanent Hire, Form 1
                       SHI1                            Permanent Hire, Form 2



HR Administrative Services (PA-AS)            6956                                          217
SAP Online Help                                                           22.04.2009


                     SHI2
Form                 ISR_HRASR_SXHR
                     ISR_HRASR_SHI1
                     ISR_HRASR_SHI2
Scenario Steps       SXHR:                   SXHR:
                     XI_DATA_HANDLING        Initial Processing of the XI Data of
                                             Recruitment Factory
                     SHI1:                   SHI1:
                     SCHRITT_01              Form 1 (Basic Data, Payment)
                     SHI2:                   SHI2:
                     SCHRITT_01              Form 2 (Taxes, Insurances)
Back-End Services
Standard Service     SAP_PA                  Personnel Administration infotypes
                     S_HIRE_ADD_FUNCTIONS    Additional Functions for Hire




HR Administrative Services (PA-AS)    6956                                          218
SAP Online Help                                                                                    22.04.2009


Process Flow

                              1a.                                       1b. HR Administrator
                           Recruiter                                   starts the Hiring process
                   starts the Hiring process                          Form: ISR_HRASR_SHI1
      WS17900415




                                2.
                        HR Administrator
                   receives work item with data
                    from SAP E-Recruiting and
                         selects process



                               3.
                      HR Administrator
                   receives work item, starts
                   process, and corrects and
                        completes data
                             Form:
                      ISR_HRASR_SHI1
                                       WS17900011




                                                               4.
                                                      HR Administrator
                                                        completes data
                                                           for Hiring
                                                             Form:
                                                      ISR_HRASR_SHI2


                                                                 5.
                                                         New employee
                                                         receives e-mail
                                                    requesting him or her to
                                                     start the Life and Work
                                                      Event “My First Days“


                                                              6.
                                                        End of process
                                       WS17900015




                                                               7.
                                                       HR system sends
                                                     confirmation message
                                                    back to the E- Recruiting
                                                             system


...




      1. Start of the Hiring process
                     a. Recruiter starts the Hiring process
                         The Recruiter transfers the data so that the system prefills the fields of the form
                         ISR_IF_SHI1 with the data from the XI interface.




HR Administrative Services (PA-AS)                                  6956                                 219
SAP Online Help                                                                    22.04.2009


         b. HR Administrator starts the Hiring process (form ISR_HRASR_SHI1)
             The HR Administrator chooses the Hiring (Germany) process and enters the
             applicant’s data manually.
  2. HR Administrator receives work item with data from SAP E-Recruiting and
     selects process
      In this step, the HR Administrator receives a work item with the information that
      applicant data has been received from SAP E-Recruiting. The processes Hiring
      (Germany) and Hiring (US) can be selected to process the data sent from SAP E-
      Recruiting. These processes are displayed in a list for the HR Administrator. He or she
      selects the process Hiring (Germany).



             This step is included as an optional step in the workflow template WS17900415.
             Depending on the data sent from SAP E-Recruiting, the XI integration
             Customizing settings determine whether the step is performed or skipped. In the
             sample process given, the step is performed because the Customizing settings
             determine that the processes Hiring (Germany) and Hiring (US) are possible for
             the applicant data sent.
             The HR Administrator can be the same person in step 2 and step 3. However,
             steps 2 and 3 can also be performed by different persons, depending on how
             you set up agent determination for these workflow steps.
  3. HR Administrator receives work item with data from SAP E-Recruiting and starts
     process
      The HR Administrator starts the Hiring process. The data from SAP E-Recruiting is
      transferred into the form ISR_HRASR_SHI1, but can be overwritten or supplemented
      by the HR Administrator.
  4. HR Administrator completes data for Hiring (form ISR_HRASR_SHI2)
      In this step, the HR Administrator completes the new employee’s data. The objective is
      to update the employee’s data so that the HR master data makes it possible to run a
      payroll for this employee.
  5. New employee receives e-mail
      The system sends an e-mail to the new employee requesting him or her to start the Life
      and Work Event [External] My First Days.
  6. End of process
  7. HR system sends confirmation message back to the E-Recruiting system

Result
The HR master record is created for the employee.




      Hiring (US)
Purpose
This process supports the hiring of an employee. The process can be started as follows:

      By the Recruiter in SAP E-Recruiting
      In this case, the Recruiter chooses the Transfer function. This automatically transfers
      an applicant’s data from the SAP E-Recruiting system into the HR system, using an XI




HR Administrative Services (PA-AS)           6956                                         220
SAP Online Help                                                                      22.04.2009


       interface. A workflow template is also started, which starts the hiring process in the HR
       system.

       By the HR Administrator in the HR system
       In this case, the HR Administrator manually completes the form that was filled
       automatically with data, using the XI interface, when started using SAP E-Recruiting.
The new employee is also involved in the process, in addition to the Recruiter or HR
Administrator. The new employee receives an e-mail requesting the employee to execute the
Life and Work Event [External] My First Days.
Using the Hiring process accelerates and optimizes the hiring procedure, since the system
integration of all roles guarantees that work items are forwarded as soon as possible, and that
all parties are informed at all times.

Prerequisites
To be able to use this sample process for test purposes, you must have performed the
Customizing activities for HR Administrative Services as described in Configuration of
Forms/Processes      Sample Processes for HCM Processes and Forms.
To be able to send the data, using the XI interface, you must have performed the Customizing
activities for HR Administrative Services as described in Configuration of Forms/Processes
XI Integration.

Technical Objects for Implementing and Executing the Process

Object Type            ID                                  Name
Process                HIRE_10                             Hiring an Employee (US)
Workflow Template      WS17900415                          Start Process for XI Data
                       WS18900008                          New Hire, Permanent (US)
                       WS17900260                          Save Form with Error Handling
                       WS17900015                          Follow-Up Activity after Process with XI
                                                           Scenario
ISR Scenario           SXHR                                Data of XI Message HireRequest
                       SHU1                                Hiring US – Form 1
                       SHU2                                Hiring US – Form 2
Interface              ISR_IF_SXHR
                       ISR_IF_SHU1
                       ISR_IF_SHU2
Form Scenario          SXHR                                Data of XI Message HireRequest (New Hire)
                                                           Hiring, Permanent US - Form 1
                       SHU1                                Hiring US – Form 2
                       SHU2
Form                   ISR_HRASR_SXHR
                       ISR_HRASR_SHU1
                       ISR_HRASR_SHU2
Scenario Steps         SXHR:                               SXHR:
                       XI_DATA_HANDLING                    Initial Processing of the XI Data of
                                                           Recruitment Factory



HR Administrative Services (PA-AS)            6956                                           221
SAP Online Help                                                        22.04.2009


                    SHU1:                     SHU1:
                    SCHRITT_01                Hiring, Permanent US, Form 1
                    SHU2:                     SHU2:
                    SCHRITT_01                Hiring, Permanent US, Form 2
Back-End
Services
Standard Service    SAP_PA                    Personnel Administration infotypes
                    S_HIRE_ADD_FUNCTIONS      Additional Functions for Hire
                    S_HIRE_ADD_US_FUNCTIONS   Additional functions for Hire US




HR Administrative Services (PA-AS)   6956                                        222
SAP Online Help                                                                                   22.04.2009


Process Flow

                              1a.                                      1b. HR Administrator
                           Recruiter                                  starts the Hiring process
                   starts the Hiring process                         Form: ISR_HRASR_SHU1
      WS17900415




                                2.
                        HR Administrator
                   receives work item with data
                    from SAP E-Recruiting and
                         selects process




                               3.
                       HR Administrator
                   receives work item, starts
                   process, and corrects and
                        completes data
                             Form:
                      ISR_HRASR_SHU1
                                       WS18900008




                                                               4.
                                                       HR Administrator
                                                        completes data
                                                           for Hiring
                                                             Form:
                                                      ISR_HRASR_SHU2


                                                                 5.
                                                         New employee
                                                         receives e-mail
                                                    requesting him or her to
                                                     start the Life and Work
                                                      Event “My First Days“


                                                              6.
                                                        End of process
                                       WS17900015




                                                               7.
                                                       HR system sends
                                                     confirmation message
                                                    back to the E-Recruiting
                                                             system


...




      1. Start of the Hiring process
                     a. Recruiter starts the Hiring process
                         The Recruiter transfers the data so that the system prefills the fields of the form
                         ISR_HRASR_SHU1 with the data from the XI interface.
                     b. HR Administrator starts the Hiring process (form ISR_HRASR_SHU1)


HR Administrative Services (PA-AS)                                 6956                                  223
SAP Online Help                                                                    22.04.2009


             The HR Administrator chooses the Hiring (US) process and enters the
             applicant’s data manually.
  2. HR Administrator receives work item with data from SAP E-Recruiting and
     selects process
      In this step, the HR Administrator receives a work item with the information that
      applicant data has been received from SAP E-Recruiting. The processes Hiring
      (Germany) and Hiring (US) can be selected to process the data sent from SAP E-
      Recruiting. These processes are displayed in a list for the HR Administrator. He or she
      selects the process Hiring (US).



             This step is included as an optional step in the workflow template WS17900415.
             Depending on the data sent from SAP E-Recruiting, the XI integration
             Customizing settings determine whether the step is performed or skipped. In the
             sample process given, the step is performed because the Customizing settings
             determine that the processes Hiring (Germany) and Hiring (US) are possible for
             the applicant data sent.
             The HR Administrator can be the same person in step 2 and step 3. However,
             steps 2 and 3 can also be performed by different persons, depending on how
             you set up agent determination for these workflow steps.
  3. HR Administrator receives work item with data from SAP E-Recruiting and starts
     process
      The HR Administrator starts the Hiring process. The data from SAP E-Recruiting is
      transferred into the form ISR_HRASR_SHU1, but can be overwritten or supplemented
      by the HR Administrator.
  4. HR Administrator completes data for Hiring (form ISR_HRASR_SHU2)
      In this step, the HR Administrator completes the new employee’s data. The objective is
      to update the employee’s data so that the HR master data makes it possible to run a
      payroll for this employee.
  5. New employee receives e-mail
      The system sends an e-mail to the new employee requesting him or her to start the Life
      and Work Event My First Days.
  6. End of process
  7. HR system sends confirmation message back to the E-Recruiting system

Result
The HR master record is created for the employee.




      Rehire (Germany)
Purpose
This process supports the rehiring of an employee that left the enterprise. The process can be
started as follows:

      By the Recruiter in SAP E-Recruiting
      In this case, the Recruiter triggers the data transfer. This transfers the following
      information (if available) about the employee to be rehired from the SAP E-Recruiting
      system to the HR system: personnel number, personal data, organizational
      assignment, address data, and employment contract. The data is transferred using the


HR Administrative Services (PA-AS)           6956                                         224
SAP Online Help                                                                   22.04.2009


      SAP NetWeaver Exchange Infrastructure (XI) interface. A workflow template is also
      started, which starts the hiring process in the HR system.

      By the HR Administrator in the HR system
      In this case, the HR Administrator manually completes the form that was filled
      automatically with data using the XI interface when started using SAP E-Recruiting.
Alongside the Recruiter or HR Administrator, the new employee is also involved in the
process. The new employee receives an e-mail requesting the employee to execute the Life
and Work Event [External] My First Days.
This process is intended for the country version for Germany.

Prerequisites
To be able to use this sample process for test purposes, you must have performed the
Customizing activities for HR Administrative Services as described in Configuration of
Forms/Processes      Sample Processes for HCM Processes and Forms.
To be able to send the data using the XI interface, you must have performed the Customizing
activities for HR Administrative Services as described in Configuration of Forms/Processes
XI Integration.

Technical Objects for Implementing and Executing the Process

Object Type                    ID                               Name
Process                        HR_PA_DE_REHIRE                  Rehire (DE)
Workflow Templates             WS61000081                       Rehire DE (HRASR Rehire,
                                                                SRD)
                               WS17900415                       Start Process for XI Data
ISR Scenarios                  SHR1                             Rehire DE 1: IT 0,1,2,3,6,7,8
                                                                (HRAdmin)
                               SHR2                             Rehire DE 2: IT
                                                                12,13,16,20,105
Interfaces                     ISR_IF_SHR1
                               ISR_IF_SHR2
Form Scenarios                 S_HRPA_DE_REHIRE_1               Rehire DE, permanent, form
                                                                1
                               S_HRPA_DE_REHIRE_2               Rehire DE, permanent, form
                                                                2
Forms                          ISR_HRASR_SHR1                   Rehire (DE): Form 1
                               ISR_HRASR_SHR2                   Rehire (DE): Form 2
Scenario Steps                 SCHRITT_01                       Form 1 (Basic Data,
                                                                Payment)
                               SCHRITT_01                       Form 2 (Taxes, Insurances)
Attachment Types               SHIRE_FREE                       Other Attachments for
                                                                ‘Hiring’ Process
                               SXIHIREATT                       Attachment of XI Message
                                                                ‘HireRequest’
                               SXIHIREDAT                       Form with Data of XI
                                                                Message ‘HireRequest’




HR Administrative Services (PA-AS)          6956                                            225
SAP Online Help                                                                                         22.04.2009


Process Flow

                                                                                    1b.
                                1a.                                      HR Administr ator starts the
                             Recruiter                                        Rehire proc ess
                    starts the Rehire proc ess                                    Form:
                                                                            ISR_HRASR_SHR1
      WS1 7900415




                                  2.
                         HR Administr ator
                    receives wor k item with data
                     from SAP E-Recruiting and
                           selects process




                                3.
                        HR Administr ator
                    receives wor k item, starts
                    process, and corrects and
                         completes data
                              Form:
                       ISR_HRASR_SHR1
                                  WS61000081




                                                              4.
                                                     HR Administr ator
                                               completes data and saves to the
                                                      bac k-end s ystem
                                                            Form:
                                                    ISR_HRASR_SHR2




                                                                 5.
                                                           Emplo yee
                                               receives e- mail requesti ng him or
                                                 her to start the Life and Wor k
                                                     Event “My First Days“



                                                               6.
                                                        End of process

...




      1. Start of Process
                      a. Recruiter starts the Rehire process
                          The Recruiter transfers the data so that the system prefills the fields of the form
                          ISR_HRASR_SHR1 with the data from SAP E-Recruiting.
                      b. HR Administrator starts the Rehire process
                          The HR Administrator selects the process and manually enters the employee’s
                          data into the form ISR_HRASR_SHR1. In the form, the data that was last stored
                          in the HR master data of the employee to be rehired is entered by default.



HR Administrative Services (PA-AS)                                     6956                                   226
SAP Online Help                                                                   22.04.2009


  2. HR Administrator receives work item with data from SAP E-Recruiting and
     selects process
     The HR Administrator receives a work item with the information that data has been
     received from SAP E-Recruiting. The processes Rehire (Germany) and Rehire (US)
     can be selected to process the data sent from SAP E-Recruiting. These processes are
     displayed in a list for the HR Administrator. He or she selects the process Rehire
     (Germany).



            This step is included as an optional step in the workflow template WS17900415.
            Depending on the data sent from SAP E-Recruiting, the XI integration
            Customizing settings determine whether the step is performed or skipped. In the
            sample process given, the step is performed because the Customizing settings
            determine that the processes Rehire (Germany) and Rehire (US) are possible
            for the rehire data sent.
            The HR Administrator can be the same person in step 2 and step 3. However,
            steps 2 and 3 can also be performed by different persons, depending on how
            you set up agent determination for these workflow steps.
  3. HR Administrator receives work item with data from SAP E-Recruiting and starts
     process
     The HR Administrator starts the process. The data from SAP E-Recruiting is
     transferred to the form ISR_HRASR_SHR1. Additionally, in the form, the system enters
     the data that was last stored in the HR master data of the employee to be rehired, as
     default entries.
     The HR Administrator completes and corrects this data. In this step, the administrator
     processes the following data:

            Personal data

            Address

            Information about company structure

            Working time

            Basic pay
  4. HR Administrator completes data for Rehire and saves to the back-end system
     On the chosen hiring date, the HR Administrator receives a work item with the
     information that he or she needs to complete the following data for the rehired
     employee in the form ISR_HRASR_SHR2:

            Fiscal data

            Social insurance data

            Contract data

            System user name and e-mail address

            DEUEV data
     The objective is to update the employee’s data so that the HR master data makes it
     possible to run a payroll for this employee.
  5. Employee receives e-mail
     The system sends an e-mail to the rehired employee requesting him or her to start the
     Life and Work Event My First Days [External].
  6. End of process


HR Administrative Services (PA-AS)         6956                                           227
SAP Online Help                                                                    22.04.2009




      Rehire (US)
Purpose
This process supports the rehiring of an employee that left the enterprise. The process can be
started as follows:

      By the Recruiter in SAP E-Recruiting
      In this case, the Recruiter triggers the data transfer. This transfers the following
      information (if available) about the employee to be rehired from the SAP E-Recruiting
      system to the HR system: personnel number, personal data, organizational
      assignment, address data, and employment contract. The data is transferred using the
      SAP NetWeaver Exchange Infrastructure (XI) interface. A workflow template is also
      started, which starts the hiring process in the HR system.

      By the HR Administrator in the HR system
      In this case, the HR Administrator manually completes the form that was filled
      automatically with data using the XI interface when started using SAP E-Recruiting.
Alongside the Recruiter or HR Administrator, the new employee is also involved in the
process. The new employee receives an e-mail requesting the employee to execute the Life
and Work Event [External] My First Days.
This process is intended for the country version for the US.

Prerequisites
To be able to use this sample process for test purposes, you must have performed the
Customizing activities for HR Administrative Services as described in Configuration of
Forms/Processes      Sample Processes for HCM Processes and Forms.
To be able to send the data, using the XI interface, you must have performed the Customizing
activities for HR Administrative Services as described in Configuration of Forms/Processes
XI Integration.

Technical Objects for Implementing and Executing the Process

Object Type                   ID                                  Name
Process                       HR_PA_US_REHIRE                     Rehiring an Employee (US)
Workflow Templates            WS61000091                          Rehire US Forms and
                                                                  Processes
                              WS17900415                          Start Process for XI Data
ISR Scenarios                 SHR5                                Rehire US – Form 1
                              SHR6                                Rehire US – Form 2
Interfaces                    ISR_IF_SHR5
                              ISR_IF_SHR7
Form Scenarios                S_HRPA_US_REHIRE_1                  Rehire (US), Basic Data
                              S_HRPA_US_REHIRE_2                  Rehire (US), Enhancement
Forms                         ISR_HRASR_SHR5                      Rehire (US), Basic Data
                              ISR_HRASR_SHR6                      Rehire (US), Enhancement
Scenario Steps                SCHRITT_01                          Form 1 (Basic Data)


HR Administrative Services (PA-AS)           6956                                           228
SAP Online Help                                                        22.04.2009


                            SCHRITT_01                Form 2 (Tax Data)
Attachment Types            SHIRE_FREE                Other Attachments for
                                                      ‘Hiring’ Process
                            SXIHIREATT                Attachment of XI Message
                                                      ‘HireRequest’
                            SXIHIREDAT                Form with Data of XI
                                                      Message ‘HireRequest’
Generic Services            S_HIRE_ADD_US_FUNCTIONS   Additional functions for Hire
                                                      US




HR Administrative Services (PA-AS)       6956                                  229
SAP Online Help                                                                                      22.04.2009


Process Flow

                                                                                  1b.
                               1a.                                     HR Administrator starts the
                            Recruiter                                       Rehire process
                   starts the Rehire process                                    Form:
                                                                          ISR_HRASR_SHR5
      WS17900415




                                2.
                        HR Administrator
                   receives work item with data
                    from SAP E-Recruiting and
                         selects process



                               3.
                       HR Administrator
                   receives work item, starts
                   process, and corrects and
                        completes data
                             Form:
                      ISR_HRASR_SHR5
                                 WS61000091




                                                            4.
                                                    HR Administrator
                                              completes data and saves to the
                                                     back-end system
                                                          Form:
                                                   ISR_HRASR_SHR6



                                                                5.
                                                          Employee
                                              receives e-mail requesting him or
                                                her to start the Life and Work
                                                    Event “My First Days“



                                                             6.
                                                      End of process

...




      1. Start of Process
                     a. Recruiter starts the Rehire process
                         The Recruiter transfers the data so that the system prefills the fields of the form
                         ISR_HRASR_SHR5 with the data from SAP E-Recruiting.
                     b. HR Administrator starts the Rehire process
                         The HR Administrator selects the process and manually enters the employee’s
                         data into the form ISR_HRASR_SHR5. In the form, the data that was last stored
                         in the HR master data of the employee to be rehired is entered by default.




HR Administrative Services (PA-AS)                                  6956                                   230
SAP Online Help                                                                   22.04.2009


  2. HR Administrator receives work item with data from SAP E-Recruiting and
     selects process
     The HR Administrator receives a work item with the information that data has been
     received from SAP E-Recruiting. The processes Rehire (Germany) and Rehire (US)
     can be selected to process the data sent from SAP E-Recruiting. These processes are
     displayed in a list for the HR Administrator. He or she selects the process Rehire (US).



            This step is included as an optional step in the workflow template WS17900415.
            Depending on the data sent from SAP E-Recruiting, the XI integration
            Customizing settings determine whether the step is performed or skipped. In the
            sample process given, the step is performed because the Customizing settings
            determine that the processes Rehire (Germany) and Rehire (US) are possible
            for the rehire data sent.
            The HR Administrator can be the same person in step 2 and step 3. However,
            steps 2 and 3 can also be performed by different persons, depending on how
            you set up agent determination for these workflow steps.
  3. HR Administrator receives work item with data from SAP E-Recruiting and starts
     process
     The HR Administrator starts the process. The data from SAP E-Recruiting is
     transferred to the form ISR_HRASR_SHR5. Additionally, in the form, the system enters
     the data that was last stored in the HR master data of the employee to be rehired, as
     default entries.
     The HR Administrator completes and corrects this data. In this step, the administrator
     processes the following data:

            Personal data

            Address

            Information about the company structure

            Working time

            Basic pay
  4. HR Administrator completes data for Rehire and saves to the back-end system
     On the chosen hiring date, the HR Administrator receives a work item with the
     information that he or she needs to complete the following data for the rehired
     employee in the form ISR_HRASR_SHR6:

            Fiscal data

            Social insurance data

            Contract data

            System user name and e-mail address
     The objective is to update the employee’s data so that the HR master data makes it
     possible to run a payroll for this employee.
  5. Employee receives e-mail
     The system sends an e-mail to the rehired employee requesting him or her to start the
     Life and Work Event My First Days [External].
  6. End of process




HR Administrative Services (PA-AS)         6956                                           231
SAP Online Help                                                                   22.04.2009



       Transfer (International)
Purpose
The Transfer process supports an employee's organizational reassignment to a new position
outside of the current manager's area of responsibility. After the process is run, the
employee's master data is up to date. The business roles of Sending Manager, Receiving
Manager, Supervisor of Sending Manager, and HR Administrator are actively involved in
performing the process. The affected employee is kept informed about the process by e-mail.
Using the Transfer process accelerates and optimizes the transfer procedure, since the
system integration of all roles guarantees that work items are forwarded as soon as possible,
and that all parties are informed at all times.

Prerequisites
To be able to use this sample process for test purposes, you must have performed the
Customizing activities for HR Administrative Services as described in Configuration of
Forms/Processes      Sample Processes for HCM Processes and Forms.

Technical Objects for Implementing and Executing the Process

Object Type              ID                          Name
Process                  ORG_CHANGE                  Transfer
Workflow Template        WS17900427                  Transfer
ISR Scenario             SOC1                        Transfer
Interface                ISR_IF_SOC1                 Transfer
Form Scenario            SOC1                        Transfer
Form                     ISR_HRASR_SOC1              Transfer
Scenario Steps           SENDING_MANAGER             Request
                         RECEIVING_MANAGER           Accept/process
                         APPROVE                     Approve
                         HR_ADMIN                    Complete processing
Attachment Types         SFREEATTM                   General attachments
Back-End Services
Standard Service         SAP_PA                      Personnel Administration infotypes
Generic Services         S_MGRS_POSITIONS            Positions reporting to manager
                         S_USER_NAME                 Functions for system user names




HR Administrative Services (PA-AS)          6956                                          232
SAP Online Help                                                                        22.04.2009


Process Flow

                                 1. Sending
                              manager initiates
                             transfer / edits the
                                   request
           Request
           revision

                                2. Receiving
                             manager accepts
                               the request or
      Request               requests for it to be
      revision                     revised



                             3. Supervisor of
                             sending manager
                            - Requests revision
                                - Approves
                                 - Rejects




                           4. HR Administrator        Rejection
                           completes data (and
                              system updates
                               master data)



                             5. End of process




...




      1. Sending manager initiates transfer
          The manager, from whose area the employee is to be transferred, initiates the Transfer
          process by selecting the relevant employee and the Transfer process. The manager
          then completes the appropriate form. In the form, the manager enters the date of the
          transfer, the receiving manager's system user name, and the reason for the transfer.
          After entering and checking the data, the manager sends the request.
      2. Receiving manager accepts the request or requests for it to be revised
          The transfer request appears in the universal worklist [Page 45] (UWL) of the receiving
          manager. On accessing the work item, the manager receives the form filled out by the
          sending manager in step 1. If all data is correct, the receiving manager enters the new
          position in the form and sends it on. If the receiving manager wants the sending
          manager to revise or change the form, he or she chooses Back to Author. The author
          (the sending manager) returns the form to the receiving manager after revising it.
      3. Supervisor of sending manager processes the request
          The request for transfer appears in the universal worklist of the receiving manager's
          supervisor. The supervisor can select the following:
             a. Request Revision - In this case, the form is sent back to the requester.
             b. Approve Transfer - In this case, the form is sent on to the HR Administrator
                (see step 4).




HR Administrative Services (PA-AS)                  6956                                          233
SAP Online Help                                                                     22.04.2009


         c. Reject Transfer - In this case, the process is complete, therefore step 4 is not
            executed.
  4. HR Administrator completes data
      The transfer request appears in the HR Administrator's universal worklist. The
      administrator adds data about the employee's organizational assignment.
  5. End of process
      After the HR Administrator has sent the form, the system transfers the data from the
      form to the master data. If you are using the Digital Personnel File (DPF) and have
      made the relevant Customizing settings, the system stores the form in the employee's
      DPF.

Result
The process has the following results:

      Transfer Carried Out: The employee's master data has been updated according to the
      entries on the form.

      Transfer Rejected: No changes have been made to the employee's master data.




    Transfer including Previous Position Update
(International)

The Transfer process supports an employee's organizational reassignment to a new position
outside of the current manager's area of responsibility. After the process is run, the
employee's master data is up to date. The business roles of Sending Manager, Receiving
Manager, Supervisor of Sending Manager, and HR Administrator are actively involved in
performing the process. The affected employee is kept informed about the process by e-mail.
Using the Transfer process accelerates and optimizes the transfer procedure, since the
system integration of all roles guarantees that work items are forwarded as soon as possible,
and that all parties are informed at all times.

This is an enhanced template of the Transfer (International) process. It includes the update of
the position vacated by the employee. The process behaves in the same way as the existing
Transfer (International) process (Form Scenario SOC1) but includes additional fields allowing
the previous manager of the transferred employee to decide what happens with the vacated
position.

The manager can select from the following options:

        Leave Position unoccupied

        Delimit Position

        Set Position vacant

Prerequisites
To be able to use this sample process for test purposes, you must have performed the
Customizing activities for HR Administrative Services as described in Configuration of
Forms/Processes Sample Processes for HCM Processes and Forms .




HR Administrative Services (PA-AS)           6956                                           234
SAP Online Help                                                                     22.04.2009


                  Technical Objects for Implementing and Executing the Process

Object Type            ID                             Name

Process                HR_PA_XX_TRANSFER_3            Transfer with Org. Management

Workflow Template WS04000051                          Transfer with Org. Management

ISR Scenario           SH12                           Transfer with Org. Management

Interface              ISR_IF_SH12                    Transfer with Org. Management

Form Scenario          S_HR_PA_XX_TRANSFER_3 Transfer with Org. Management

Form                   ISR_HRASR_SH12                 Transfer with Org. Management

                       SENDING_MANAGER                Request

                       RECEIVING MANAGER              Accept/process
Scenario Steps
                       APPROVE                        Approve

                       HR_ADMIN                       Complete processing

Attachment Types       SFREEATTM                      General attachments

Back-End Services

Standard Service       SAP_PA                         Personnel Administration infotypes

                       SAP_PD                         Infotypes for Organization Management

Generic Services       S_MGRS_POSITIONS               Positions reporting to manager

                       S_USER_NAME                    Functions for system user names

Process
    1. Sending manager initiates transfer

        The manager, from whose area the employee is to be transferred, initiates the
        process by selecting the relevant employee and the Transfer process. The manager
        then completes the appropriate form, entering the date of the transfer, the receiving
        manager's system user name, and the reason for the transfer. Additionally, the
        manager who started the process can decide what should happen to the vacant
        position by selecting on the form one of the following options:

              o   Leave Position Unoccupied — position is left unoccupied and technically
                  nothing is done on the PD infotype related to the position.

              o   Remove (Delimit) Position — Position and all its associated infotypes are
                  delimited.

              o   Set Position Vacant with Vacancy Effective Date — only the infotype 1007 of
                  the position will be updated ( VACAN set to X and Status set to OPEN)
                  starting from the specified Vacancy Effective Date.




HR Administrative Services (PA-AS)            6956                                            235
SAP Online Help                                                                      22.04.2009


        After entering and checking the data, the manager sends the request.

    2. Receiving manager accepts the request or requests for it to be revised

        The transfer request appears in the universal worklist (UWL) of the receiving
        manager. On accessing the work item, the manager receives the form filled out by the
        sending manager in step 1. If all data is correct, the receiving manager enters the
        new position in the form and sends it on. If the receiving manager wants the sending
        manager to revise or change the form, he or she chooses Back to Author. The author
        (the sending manager) returns the form to the receiving manager after revising it.

    3. Supervisor of sending manager processes the request

        The request for transfer appears in the universal worklist of the receiving manager's
        supervisor. The supervisor can select on of the following:

            o   Request Revision - In this case, the form is sent back to the requester.

            o   Approve Transfer - In this case, the form is sent on to the HR Administrator
                (see step 4).

            o   Reject Transfer - In this case, the process is complete, therefore step 4 is not
                executed.

    4. HR Administrator completes data

        The transfer request appears in the HR Administrator's universal worklist. The
        administrator adds data about the employee's organizational assignment.

    5. End of process

        After the HR Administrator has sent the form, the system transfers the data from the
        form to the master data. If you are using the Digital Personnel File (DPF) and have
        made the relevant Customizing settings, the system stores the form in the employee's
        DPF.

Result
The process has the following results:

        Transfer Carried Out: The employee's master data has been updated according to
        the entries on the form. Also the former position’s master data occupied by the
        employee is updated according to the entries on the form

        Transfer Rejected: No changes have been made to the employee's master data.



      Transfer, Initiated by E-Recruiting (International)
Purpose
This process supports an employee's organizational reassignment to a new position that is
outside the current manager's area of responsibility. The transfer occurs because the affected
employee applied for a position in the SAP E-Recruiting system. The recruiter then triggers
the data transfer in the E-Recruiting system. The transfer request is transferred from the E-
Recruiting system to the HR system, using the SAP NetWeaver Exchange Infrastructure (XI)
interface.
The employee’s new position and organizational unit, and the effective date, are automatically
sent from the E-Recruiting system and transferred to the form as default values. The back-
end services of the form scenario used provide additional default values in the form. The HR



HR Administrative Services (PA-AS)           6956                                           236
SAP Online Help                                                                     22.04.2009


Administrator checks the data, and corrects and completes the data as required. The data is
saved to the back-end system, in the Organizational Assignment infotype (0001).
The employee, his or her previous manager, and the new manager are informed about the
transfer by e-mail.
The process is international and can be used in all country versions, without requiring any
specific settings.

Prerequisites
To be able to use this sample process for test purposes, you must have performed the
Customizing activities for HR Administrative Services as described in Configuration of
Forms/Processes      Sample Processes for HCM Processes and Forms.
To be able to send the data using the XI interface, you must have performed the Customizing
activities for HR Administrative Services as described in Configuration of Forms/Processes
XI Integration.

Technical Objects for Implementing and Executing the Process

Object Type                     ID                               Name
Process                         HR_PA_XX_TRANSFER_2              Transfer 2
Workflow Templates              WS61000088                       Transfer 2
                                WS17900415                       Start Process for XI Data
ISR Scenario                    SH10                             Transfer 2
Interface                       ISR_IF_SH10
Form Scenario                   S_HR_PA_XX_TRANSFER_2            Transfer 2 (XX)
Form                            ISR_HRASR_SH10                   Transfer 2
Scenario Steps                  HR_ADMIN                         Maintain
Attachment Types                SFREEATTM                        General attachments
                                SXHIREATT                        Attachments of XI Message
                                                                 ‘HireRequest’
                                SXHIREDAT                        Form with Data of XI
                                                                 Message ‘HireRequest’




HR Administrative Services (PA-AS)           6956                                             237
SAP Online Help                                                                                    22.04.2009


Process Flow

                                  1.
                             Recruiter
                    starts the Transfer process
      WS17900415




                                 2.
                         HR Administrator
                    receives work item with data
                     from SAP E-Recruiting and
                          selects process



                                 3.
                         HR Administrator
                     receives work item, starts
                       process, corrects and
                   completes data, and saves to
                       the back-end system
                              Form:
                        ISR_HRASR_SH10
      WS61000088




                                  4.
                           E-mails sent to:
                             - Employee
                        - Previous manager
                           - New manager



                                 5.
                          End of process

...




      1. Recruiter starts the Transfer process
                   The Recruiter transfers the data so that the system prefills the fields of the form
                   ISR_HRASR_SH10 with the data from SAP E-Recruiting.
      2. HR Administrator receives work item with data from SAP E-Recruiting and
         selects process
                   If there is more than one process for processing the data sent from SAP E-Recruiting,
                   in this step, the HR Administrator receives a work item with information that data has
                   been received from SAP E-Recruiting. The HR Administrator performs the step and
                   selects the appropriate process from the list of processes displayed.



                          This step is included as an optional step in the workflow template WS17900415.
                          Depending on the data sent from SAP E-Recruiting, the XI integration
                          Customizing settings determine whether the step is performed or skipped. In the
                          sample process given, the step is skipped because the Customizing settings
                          determine that only the Transfer, Initiated by E-Recruiting (International) process
                          is possible for the sent transfer data.




HR Administrative Services (PA-AS)                         6956                                          238
SAP Online Help                                                                   22.04.2009


              The HR Administrator can be the same person in step 2 and step 3. However,
              steps 2 and 3 can also be performed by different persons, depending on how
              you set up agent determination for these workflow steps.
  3. HR Administrator receives work item with data from SAP E-Recruiting and starts
     process
       The data from SAP E-Recruiting is transferred to the form ISR_HRASR_SH10. The HR
       Administrator completes and corrects this data, and saves it to the back-end system.
  4. E-mails sent
       The employee, his or her previous manager, and the new manager are informed by e-
       mail about the employee’s transfer.
  5. End of process




       Maternity Leave (Germany)
Purpose
The Maternity Leave process supports an employee’s request for maternity leave that is
initiated by the employee herself. Once the process has been performed successfully, the
master data of the affected employee is updated. Meaning, the employee's leaving was
performed at the master data level. As well as the employee, the HR Administrator portal role
is also active in performing the process. The administrator receives an e-mail from the
employee who submits the Certificate of Pregnancy and the 7 Weeks Certificate as
attachments, using the Maternity Leave service in the Employee Self-Service application in
the Life and Work Events area.

Prerequisites
To be able to use this sample process for test purposes, you must have performed the
Customizing activities for HR Administrative Services as described in Configuration of
Forms/Processes      Sample Processes for HCM Processes and Forms.

Technical Objects for Implementing and Executing the Process

Object Type           ID                           Name
Process               MATERNITY_LEAVE_01           Maternity Leave (DE)
Workflow Template     WS17900366                   Maternity Leave
ISR Scenario          SML1                         Maternity Leave
Interface             ISR_IF_SML1                  Maternity Leave
Form Scenario         SML1                         Maternity Leave
Form                  ISR_HRASR_SML1               Maternity Leave
Scenario Steps        SML1:                        SML1:
                      STAGE_01                     Step 01
Attachment Types      SML1:                        SML1:
                      SPRGNYCRTF                   Certificate of Pregnancy
                      S7WEEKCRTF                   7 Weeks Certificate
Back-End
Services
Standard Services     SAP_PA                       Personnel Administration infotypes


HR Administrative Services (PA-AS)          6956                                          239
SAP Online Help                                                                                   22.04.2009


                          S_MATLEAVE                         Maternity Leave (Determine absence types)
                          SAP_PT                             Time Management Infotypes

      Process Flow

                                            1. Employee starts the Maternity Leave
                                            process, and attaches the Certificate of
                                         Pregnancy, or informs the HR Administrator by
                                                           telephone
                                                  Form: ISR_HRASR_SML1

            Request submission of “Certificate
            of Pregnancy“ (by telephone or
            mail)

                                          2. HR Administrator checks the submitted
                                         Certificate of Pregnancy, or requests that this
                                                          be submitted
                                                   Form: ISR_HRASR_SML1


                                                        Process waits until 7
                                                         weeks before the
                                                          expected date of
                                                              delivery



                                                 3. HR Administrator requests the
                                                        7 Weeks Certificate                      Update database
                                                                                       Infotype 0080:
                                                     Form: ISR_HRASR_SML1                  - Expected Date of Delivery
                                                                                       Infotype 2001:
                                                                                       (Data is determined automatically)
                                                                                           - Absence Type
                                                                                           - Absence Start
                                                                                           - Absence End
                                                         4. End of process




...




      1. Employee starts the Maternity Leave process
         The employee selects the Maternity Leave process and enters the expected date of
         delivery. The absence dates resulting from the expected date of delivery are displayed
         for the employee, for information purposes. The employee can also insert the
         certificates as attachments. (Alternatively, the employee can inform the HR
         Administrator by telephone, and the HR Administrator then enters the information for
         the employee.)
      2. HR Administrator checks the submitted Certificate of Pregnancy
         The HR Administrator checks the entered data for completeness, in particular, whether
         the Certificate of Pregnancy was submitted. If a certificate does not yet exist in the
         system, the administrator requests this from the employee (by mail or telephone).
      3. HR Administrator requests the 7 Weeks Certificate
         The HR Administrator requests the 7 Weeks Certificate (by mail or telephone).
      4. End of process




HR Administrative Services (PA-AS)                    6956                                                   240
SAP Online Help                                                                     22.04.2009


Result
       A new data record for maternity protection (Maternity Protection/Parental Leave
       infotype (0080)) is created in the employee's master data, and a new absence record
       is created in the time management data (Absences infotype (2001)). The system
       automatically determines the absence data, depending on the (estimated) date of
       delivery.




       Birth of a Child (Germany)
Purpose
The Birth of a Child process supports the notification relating to the birth of a child that an
employee can initiate. When the process has been performed successfully, the master data of
the affected employee is updated. Meaning, at the master data level, a new data record was
created for the child (Family/Related Person infotype and subtype 2 Child (0021)). In addition,
the number of children is increased by one in the Personal Data infotype (0002). As well as
the employee, the HR Administrator portal role is also active in performing the process. The
administrator receives an e-mail from the employee who submits the birth certificate as an
attachment using the Birth/Adoption (Germany) service in the Employee Self-Service
application, in the Life and Work Events area.

Prerequisites
To be able to use this sample process for test purposes, you must have performed the
Customizing activities for HR Administrative Services as described in Configuration of
Forms/Processes      Sample Processes for HCM Processes and Forms.

Technical Objects for Implementing and Executing the Process

Object Type           ID                            Name
Process               BIRTH_OF_CHILD_01             Birth of a Child (DE)
WS Template           WS17900367                    Birth of a Child
ISR Scenario          SBC1                          Birth of a Child
Interface             ISR_IF_SBC1                   Birth of a Child
Form Scenario         SBC1                          Birth of a Child
Form                  ISR_HRASR_SBC1                Birth of a Child
Scenario Steps        SBC1:                         SBC1:
                      STAGE_01                      Step 01
Attachment Types      SBC1:                         SBC1:
                      SBIRTHCRTF                    Birth Certificate
Back-End
Services
Standard Services     SAP_PA                        Personnel Administration infotypes
                      S_BIRTH_OF_CHILD              Birth of a Child (IT0002 Increase Number of
                                                    Children)




HR Administrative Services (PA-AS)           6956                                          241
SAP Online Help                                                                                22.04.2009


Process Flow



                                               1. Employee starts the Birth of a Child
                                                   process and attaches the birth
                                                    certificate, or informs the HR
                                                     Administrator by telephone
                                                     Form: ISR_HRASR_SBC1


                         Request submission of
                         “Birth Certificate“ (by
                         telephone or mail)


                                                2. HR Administrator checks the
                                              submitted birth certificate, or requests
                                                      that this be submitted
                                                   Form: ISR_HRASR_SBC1

                                                                                      Update database
                                                                              Infotype 0021 (Subtype 2
                                                                              “Child““):
                                                                                       - Date of Birth
                                                                                       - First Name
                                                                                       - Last Name
                                                                                       - Gender
                                                                                       - Place of Birth
                                                                                       - Country of Birth
                                                                              Infotype 0002:
                                                          3. End of process            - Number of Children
                                                                                       (automatic Increase by
                                                                                       1)




  5. Employee starts the Birth of a Child process
      The employee chooses the Birth of a Child process and enters the required data (date
      of birth, first name and last name of the child, gender, place of birth, country of birth).
      The employee can add the birth certificate as an attachment. (Alternatively, the
      employee can inform the HR Administrator by telephone.)
  6. HR Administrator checks the submitted birth certificate
      The HR Administrator checks the entered data for completeness, in particular, whether
      the birth certificate was submitted. If a birth certificate does not yet exist in the system,
      the administrator requests this from the employee (by mail or telephone).
  7. End of process

Result
A new data record for the child (Family/Related Person infotype and subtype 2 Child (0021))
was created for the employee’s master data, and the number of children was increased by
one in the Personal Data infotype (0002).




HR Administrative Services (PA-AS)                 6956                                                  242
SAP Online Help                                                                     22.04.2009



       Birth of Child (US)
Purpose
The Birth of a Child process supports the notification relating to the birth of a child that an
employee can initiate. When the process has been performed successfully, the master data of
the affected employee is updated. Meaning, at the master data level, a new data record was
created for the child (Family/Related Person infotype and subtype 2 Child (0021)). In addition,
the number of children is increased by one in the Personal Data infotype (0002). As well as
the employee, the HR Administrator portal role is also active in performing the process. The
administrator receives an e-mail from the employee who submits the birth certificate as an
attachment using the Birth/Adoption (US) service in the Employee Self-Service application, in
the Life and Work Events area.

Prerequisites
To be able to use this sample process for test purposes, you must have performed the
Customizing activities for HR Administrative Services as described in Configuration of
Forms/Processes      Sample Processes for HCM Processes and Forms.

Technical Objects for Implementing and Executing the Process

Object Type           ID                            Name
Process               BIRTH_OF_CHILD_10             Birth of Child (US)
WS Template           WS17900013                    Birth of Child (US)
ISR Scenario          SBU1                          Birth of Child (US)
Interface             ISR_IF_SBU1                   Birth of Child (US)
Form Scenario         SBU1                          Birth of Child (US)
Form                  ISR_HRASR_SBU1                Birth of Child (US)
Scenario Steps        SBU1:                         SBU1:
                      STAGE_01                      Step 01
Attachment Types      SBU1:                         SBU1:
                      SBIRTHCRTF                    Birth Certificate
                      S7WEEKCRTF                    7 Weeks Certificate
Back-End
Services
Standard Services     SAP_PA                        Personnel Administration infotypes
                      S_BIRTH_OF_CHILD              Birth of a Child (IT0002 Increase Number of
                                                    Children)




HR Administrative Services (PA-AS)           6956                                          243
SAP Online Help                                                                               22.04.2009


Process Flow



                                             1. Employee starts the Birth of a Child
                                                 process and attaches the birth
                                                  certificate, or informs the HR
                                                   Administrator by telephone
                                                   Form: ISR_HRASR_SBU1


                         Request submission of
                         “Birth Certificate“ (by
                         telephone or mail)


                                               2. HR Administrator checks the
                                             submitted birth certificate, or requests
                                                     that this be submitted
                                                  Form: ISR_HRASR_SBU1
                                                                                    Update database
                                                                            Infotype 0021 (Subtype 2
                                                                            “Child“):
                                                                                      - Date of Birth
                                                                                      - First Name
                                                                                      - Last Name
                                                                                      - Gender

                                                                            Infotype 0002:
                                                                                    - Number of children
                                                                                    (automatic Increase by
                                                                                    1)
                                                      3. End of process




  8. Employee starts the Birth of a Child process
     The employee chooses the Birth of a Child process and enters the required data (date
     of birth, first name and last name of the child, gender, place of birth, country of birth).
     The employee can add the birth certificate as an attachment. (Alternatively, the
     employee can inform the HR Administrator by telephone.)
  9. HR Administrator checks the submitted birth certificate
     The HR Administrator checks the entered data for completeness, in particular, whether
     the birth certificate was submitted. If a birth certificate does not yet exist in the system,
     the administrator requests this from the employee (by mail or telephone).
10. End of process




HR Administrative Services (PA-AS)             6956                                                     244
SAP Online Help                                                                    22.04.2009


Result
A new data record for the child (Family/Related Person infotype and subtype 2 Child (0021))
was created for the employee’s master data, and the number of children was increased by
one in the Personal Data infotype (0002).




        Salary Change Using Annual Salary (International)
Purpose
This process supports the changing of an employee's salary. The salary change is achieved
by changing the annual salary.
The manager requests a salary change by entering a date in the form from which the change
is valid. When a pushbutton is clicked to refresh the display, the employee's current salary
data will be displayed. The manager can then enter the new annual salary amount.
The superior manager receives the salary increase request for checking and can decide to
approve or reject it.
The HR administrator then checks the data, adjusts the basic pay in accordance with the
changed annual salary, and sends the data to the back-end system.
Both superior managers and HR administrators can send the form back to the requester with
a request for revision.
The requesting manager and the affected employee are informed by e-mail once an approval
or rejection has been decided.
This process is international. If you want to use the process for a specific country version
(country grouping not equal to 99), you must have maintained the appropriate settings for this
country grouping such as pay scale wage group and pay scale wage level in Customizing for
Payroll.

Prerequisites
To be able to use these sample processes for test purposes, you must have performed the
Customizing activities for HR Administrative Services as described in Configuration of
Forms/Processes      Sample Processes for HCM Processes and Forms.

Technical Objects for Implementing and Executing the Process

Object Type                 ID                                             Name
Process                     HR_PA_XX_CHANGE_SALARY_1                       Salary Change Using
                                                                           Annual Salary
                                                                           (International)
Workflow Template           WS61000080                                     Change Salary 1
ISR Scenarios               SH03                                           Salary Change Using
                                                                           Annual Salary Manager
                                                                           (XX)
                            SH04                                           Salary Change Using
                                                                           Annual Salary HR
                                                                           Administrator (XX)
Interfaces                  ISR_IF_SH03
                            ISR_IF_SH04
Forms                       ISR_HRASR_SH03



HR Administrative Services (PA-AS)          6956                                           245
SAP Online Help                                                            22.04.2009


                          ISR_HRASR_SH04
Form Scenarios            S_HRPA_XX_CHANGE_SAL1_MANAGER             Salary Change Using
                                                                    Annual Salary Manager
                                                                    (XX)
                          S_HRPA_XX_CHANGE_SAL1_HRADMIN             Salary Change Using
                                                                    Annual Salary HR
                                                                    Administrator (XX)
Scenario Steps            S_HRPA_XX_CHANGE_SAL1_MANAGER
                          APPROVEREQUEST
                          CHANGEREQUEST
                          S_HRPA_XX_CHANGE_SAL1_HRADMIN
                          COMPLETEREQUEST
Attachment Types
Back-End Services         SAP_PA                                    Personnel Administration
                                                                    infotypes

Process Flow

                         1. Manager starts salary
                                change
                                 Form:
                           ISR_HRASR_SH03

      Revision
      request
                          2. Superior manager
                          approves, rejects, or
                            requests revision       Rejection
                                 Form:
                           ISR-HRASR_SH03


                                                            System
                          3. HR administrator
                                                         sends e-mail
                         checks, completes, and
                                                          regarding
                         sends data to back-end
                                                           rejection
                                 system
                                  Form:
                          ISR_HRASR_SH04


                                 System
                              sends e-mail
                               regarding
                                approval



                            4. End of process



...




HR Administrative Services (PA-AS)       6956                                     246
SAP Online Help                                                                   22.04.2009


  1. Manager starts salary change: Form: ISR_HRASR_SH03
      The manager starts the Change Salary Using Annual Salary (XX) process and enters
      the following data:

             Validity date

             New annual salary
  2. Superior manager approves, rejects, or requests revision: Form:
     ISR_HRASR_SH03
      The salary change request appears in the superior manager's universal worklist. The
      superior manager has the following options:

             Request revision
             In this case, the form is sent back to the requester.

             Approve request
             In this case, the form (ISR_HRASR_SH04) is sent on to the HR administrator
             (see step 3).

             Reject request
             In this case, the process is ended and the additional steps are not executed.
             The requesting manager and the employee receive an e-mail informing them
             about the rejection.
  3. HR administrator checks, completes, and sends data to the back-end system:
     Form ISR_HRASR_SH04)
      The form appears in the HR administrator's universal worklist. The HR administrator
      checks the data, changes it if necessary, and determines the basic pay.
      The following options are available:

             The HR administrator adjusts the amount to the wage type.

             The HR administrator enters a new wage type and a new amount if necessary.
      The HR administrator sends the form to the back-end system, where the data from
      forms is saved automatically.
      The requesting manager and the employee receive an e-mail informing them about the
      salary change.
  4. End of process




   Salary Change Using Pay Scale Wage Group and
Level (International)
Purpose
This process supports the changing of an employee's salary. The salary change is achieved
by changing the pay scale wage group and the pay scale wage level.
The manager requests a salary change by entering a date in the form from which the change
is valid. When a pushbutton is clicked to refresh the display, the employee's current salary
data will be displayed. The manager can enter the new pay scale wage group and the pay
scale wage level.
The superior manager receives the salary increase request for checking and can decide to
approve or reject it.


HR Administrative Services (PA-AS)           6956                                            247
SAP Online Help                                                                  22.04.2009


The HR administrator then checks the data, changes the validity date if necessary, and sends
the data to the back-end system.
Both superior managers and HR administrators can send the form back to the requester with
a request for revision.
The requesting manager and the affected employee are informed by e-mail once an approval
or rejection has been decided.

Prerequisites
To be able to use these sample processes for test purposes, you must have performed the
Customizing activities for HR Administrative Services as described in Configuration of
Forms/Processes      Sample Processes for HCM Processes and Forms.

Technical Objects for Implementing and Executing the Process

Object Type                    ID                                            Name
Process                        HR_PA_XX_CHANGE_SALARY_2                      Salary Change Using Pay
                                                                             Scale Wage Group/Level
                                                                             (XX)
Workflow Template              WS61000079                                    Change Salary 2
ISR Scenarios                  SH05                                          Salary Change Pay Scale
                                                                             Wage Group Manager (XX)
                               SH06                                          Salary Change Pay Scale
                                                                             Wage Group HR
                                                                             Administrator (XX)
Interfaces                     ISR_IF_SH05
                               ISR_IF_SH06
Forms                          ISR_HRASR_SH05
                               ISR_HRASR_SH06
Form Scenarios                 S_HRPA_XX_CHANGE_SAL2_MANAGER                 Salary Change Pay Scale
                                                                             Wage Group Manager (XX)
                               S_HRPA_XX_CHANGE_SAL2_HRADMIN                 Salary Change Pay Scale
                                                                             Wage Group HR
                                                                             Administrator (XX)
Scenario Steps                 S_HRPA_XX_CHANGE_SAL2_MANAGER
                               APPROVEREQUEST
                               CHANGEREQUEST
                               S_HRPA_XX_CHANGE_SAL2_HRADMIN:
                               COMPLETEREQUEST
Attachment Types
Back-End Services              SAP_PA                                        Personnel Administration
                                                                             infotypes




HR Administrative Services (PA-AS)         6956                                         248
SAP Online Help                                                                     22.04.2009


Process Flow

                                 1. Manager starts salary
                                        change
                                         Form:
                                   ISR_HRASR_SH05

           Revision
           request
                                   2. Superior manager
                                   approves, rejects, or
                                     requests revision              Rejection
                                          Form:
                                    ISR-HRASR_SH05


                                                                            System
                                  3. HR administrator                    sends e-mail
                                 checks, completes, and                   regarding
                                 sends data to back-end                    rejection
                                         system
                                          Form:
                                   ISR_HRASR_SH06


                                       System sends
                                          e-mail
                                        regarding
                                         approval



                                     4. End of process



...




      1. Manager starts salary change: Form: ISR_HRASR_SH05
         The manager starts the Change Salary Using Annual Salary (XX) process and enters
         the following data:

                Validity date

                New pay scale wage group

                New pay scale wage level
      2. Superior manager approves, rejects, or requests revision: Form:
         ISR_HRASR_SH05
         The salary change request appears in the superior manager's universal worklist. The
         superior manager has the following options:

                Request revision
                In this case, the form is sent back to the requester.



HR Administrative Services (PA-AS)              6956                                       249
SAP Online Help                                                                      22.04.2009


              Approve request
             In this case, the form (ISR_HRASR_SH06) is sent on to the HR administrator
             (see step 3).

              Reject request
             In this case, the process is ended and the additional steps are not executed.
             The requesting manager and the employee receive an e-mail informing them
             about the rejection.
  3. HR administrator checks, completes, and sends data to the back-end system:
     Form ISR_HRASR_SH06)
      The form appears in the HR administrator's worklist. The HR administrator checks the
      data and changes the validity data if necessary.
      The following options are available:

              If all data is correct, the HR administrator sends it to the back-end system,
              where it is automatically saved.
             The requesting manager and the employee receive an e-mail informing them
             about the salary change.

              If the data is not correct, the HR administrator sends the form back to the
              requester.
  4. End of process




      Special Payment (International)
Purpose
This process supports the payment of a discretionary bonus to an employee. After the
process is run, the employee's master data is up to date. In addition to the employee, the
Manager, Superior Manager and HR Administrator business roles are actively involved in
performing the process. The process is initiated by the manager. The Superior Manager
business role is also assigned to the Manager portal role.
The requesting manager enters a validity date, a reason, and an amount for the special
payment.
The superior manager receives the special payment request for checking and can decide to
approve or reject it.
The HR administrator then checks the data, changes or completes it, and sends the data to
the back-end system.
Both superior managers and HR administrators can send the form back to the requester with
a request for revision.
The requesting manager and the affected employee are informed by e-mail once an approval
or rejection has been decided.
This process is international. If you want to use the process for a specific country version
(country grouping not equal to 99), you must have maintained the permitted wage types for
this country grouping in the Payment Reason field in the form scenario.

Prerequisites
To be able to use these sample processes for test purposes, you must have performed the
Customizing activities for HR Administrative Services as described in Configuration of
Forms/Processes      Sample Processes for HCM Processes and Forms.


HR Administrative Services (PA-AS)           6956                                             250
SAP Online Help                                                             22.04.2009


Prerequisites
Technical Objects for Implementing and Executing the Process

Object Type              ID                                    Name
Process                  HR_PA_XX_SPECIAL_PAYMENT              Special Payment
                                                               (International)
Workflow Template        WS61000073                            Special Payment 1 (XX)
ISR Scenario             SHSP                                  Special Payment 1 (XX)
Interface                ISR_IF_SHSP
Form                     ISR_HRASR_SHSP
Form Scenario            S_HR_PA_XX_SPAYMENT_1                 Special Payment 1 (XX)
Scenario Steps           REQUEST                               Request
                         APPROVE                               Approve
                         PROCESS                               Process
Attachment Types         SFREEATTM                             General attachments
Back-End Services        SAP_PA                                Personnel Administration
                                                               infotypes




HR Administrative Services (PA-AS)     6956                                          251
SAP Online Help                                                                          22.04.2009


Process Flow

                                   1. Manager starts
                                   special payment
                                        Form:
                                 ISR_HRASR_SHSP

         Revision
         request
                                 2. Superior manager
                                 approves, rejects, or
                                   requests revision        Rejection
                                        Form:
                                 ISR-HRASR_SHSP


                                                                     System
                                 3. HR administrator              sends e-mail
                               checks and sends data to            regarding
                                 the back-end system                rejection
                                        Form:
                                 ISR_HRASR_SHSP



                                    System sends
                                        e-mail
                                      regarding
                                       approval



                                  4. End of process



..




     1. Manager starts special payment: Form: ISR_HRASR_SHSP
        The manager starts the Special Payment (International) process and enters the
        following data:

               Validity date

               Payment reason

               Amount
     2. Superior manager approves, rejects, or requests revision: Form:
        ISR_HRASR_SHSP
        The special payment request appears in the higher-level manager's universal worklist.
        The superior manager has the following options:

               Request revision
               In this case, the form is sent back to the requester.

               Approve request
               In this case, the form is sent on to the HR Administrator (see step 3).



HR Administrative Services (PA-AS)              6956                                           252
SAP Online Help                                                                       22.04.2009


              Reject request
             In this case, the process is ended and the additional steps are not executed.
             The requesting manager and the employee receive an e-mail informing them
             about the rejection.
  3. HR administrator checks, completes, and sends data to the back-end system:
     Form ISR_HRASR_SHSP)
      The form appears in the HR administrator's worklist. The HR administrator checks the
      data and changes it if necessary.
      The following options are available:

              If all data is correct, the HR administrator sends it to the back-end system,
              where it is automatically saved.
             The requesting manager and the employee receive an e-mail informing them
             about the salary change.

              If the data is not correct, the HR administrator sends the form back to the
              requester.
  4. End of process




    Special Payment Without Personnel Department
(International)
Purpose
This process supports the payment of a discretionary bonus to an employee. After the
process is run, the employee's master data is up to date. In addition to the employee, the
Manager, and Superior Manager business roles are actively involved in performing the
process. The HR administrator is only involved in the process if errors occur. The process is
initiated by the manager.
The requesting manager enters a validity date, a reason, and an amount for the special
payment.
The superior manager receives the special payment request for checking and can decide to
approve or reject it.
The system automatically performs various checks:

      If no error occurs, no further interactive step is required and no further processor is
      involved in the process. The data is sent directly to the back-end system and the
      employee's master data is updated.

      If an error occurs, the approving manager receives a message with the request to
      forward the work item to an HR administrator.
      The HR administrator checks and corrects the data and sends it to the back-end
      system.
This process is international. If you want to use the process for a specific country version
(country grouping not equal to 99), you must have maintained the appropriate wage types for
this country grouping in the Payment Reason field in the form scenario.

Prerequisites
To be able to use these sample processes for test purposes, you must have performed the
Customizing activities for HR Administrative Services as described in Configuration of
Forms/Processes      Sample Processes for HCM Processes and Forms.


HR Administrative Services (PA-AS)           6956                                               253
SAP Online Help                                                          22.04.2009


Technical Objects for Implementing and Executing the Process
Object Type                   ID                               Name
Process                       HR_PA_XX_SPECIAL_PAYMENT_2       Special Payment Without
                                                               Personnel Department
                                                               (International)
Workflow Template             WS61000078                       Special Payment 2 (XX)
ISR Scenario                  SH08                             Special Payment 2 (XX)
Interface                     ISR_IF_SH08
Form                          ISR_HRASR_SH08
Form Scenario                 S_HR_PA_XX_SPAYMENT_2            Special Payment 2 (XX)
Scenario Steps                REQUEST                          Request
                              APPROVE                          Approve
                              PROCESS                          Process
Attachment Types              SFREEATTM                        General attachments
Back-End Services             SAP_PA                           Personnel Administration
                                                               infotypes




HR Administrative Services (PA-AS)      6956                                    254
SAP Online Help                                                                      22.04.2009


Process Flow


                              1. Manager starts
                               special payment
                                    Form:
                             ISR_HRASR_SH08

        Revision
        request              2. Superior manager
                             approves, rejects, or
                               requests revision            Rejection
                                    Form:
                              ISR-HRASR_SH08


                                                         Error while
                                                        checking data


                                No error while
                                checking data        3. HR administrator
                                                    checks, changes, and
                                                   sends data to the back-
                                                         end system
                                                            Form:
                                                     ISR_HRASR_SH08


                                System sends
                                 confirmation                             System
                                  message                                sends e-
                                                                           mail
                                                                        regarding
                                                                         rejection
                               4. End of process



...




      1. Manager starts special payment: Form: ISR_HRASR_SH08
         The manager starts the Special Payment (International) process and enters the
         following data:

                   Validity date

                   Payment reason

                   Amount
      2. Superior manager approves, rejects, or requests revision: Form:
         ISR_HRASR_SH08
         The special payment request appears in the superior manager's universal worklist. The
         superior manager has the following options:

                   Request revision
                   In this case, the form is sent back to the requester.

                   Approve request
                   In this case, automatic checks are performed:


HR Administrative Services (PA-AS)                   6956                                  255
SAP Online Help                                                                       22.04.2009


             If no error occurs, the process is complete. The data is sent directly to the back-
             end system and the employee's master data is updated.
             If an error occurs, the work item appears in the HR administrator's worklist (see
             step 3).

              Reject request
             In this case, the process is ended and the additional steps are not executed.
             The requesting manager and the employee receive an e-mail informing them
             about the rejection.
  3. HR administrator checks, changes, and sends data to the back-end system: Form
     ISR_HRASR_SH08)
      The form appears in the HR administrator's worklist, where the HR administrator
      analyzes and corrects it.
      If all data is correct, the HR administrator sends it to the back-end system, where it is
      automatically saved.
      The requesting manager and the employee receive an e-mail informing them about the
      special payment.
  4. End of process




      Change to Working Time (International)
Purpose
This process supports the changing of an employee's working time. The employee requests
this change in working time himself or herself. The manager and the employee both
participate in this process. The manager checks the request and approves or rejects it. The
HR administrator checks the data and ends the process. When the process is successfully
completed, the employee master data is updated (Planned Working Time (0007) infotype and
Basic Pay (0008) infotype).
In more detail, the master data affected is:

       Infotype Planned Working Time:

              Employment percentage

       Infotype Basic Pay:

              Employment fraction

              Working hours per payroll period
The employee can request the following changes to working time:

       From 100% to 80%

       From 100% to 60%

       From 80% to 100%

       From 80% to 60%

       From 60% to 80%

       From 60% to 100%
This process is international. No special Customizing settings are required.



HR Administrative Services (PA-AS)             6956                                           256
SAP Online Help                                                                22.04.2009


Prerequisites
To be able to use these sample processes for test purposes, you must have performed the
Customizing activities for HR Administrative Services as described in Configuration of
Forms/Processes      Sample Processes for HCM Processes and Forms.

Technical Objects for Implementing and Executing the Process

Object Type            ID                                          Name
Process                HR_PA_XX_CHANGE_WORKINGTIME_1               Change to Working
                                                                   Time (International)
Workflow Template      WS61000074                                  Change to Working
                                                                   Time (XX)
ISR Scenario           SH09                                        Change to Working
                                                                   Time (XX)
Interface              ISR_IF_SH09
Form                   ISR_HRASR_SH09
Form Scenario          S_HR_PA_XX_CHWT_1                           Change to Working
                                                                   Time (XX)
Scenario Steps         REQUEST                                     Request
                       APPROVE                                     Approve
                       PROCESS                                     Process
Attachment Types       SFREEATTM                                   General attachments
Back-End Services      SAP_PA                                      Personnel
                                                                   Administration
                                                                   infotypes
                       S_CHECK_ABSENCE                             Check an Employee’s
                                                                   Absences

Process Flow




HR Administrative Services (PA-AS)        6956                                            257
SAP Online Help                                                                        22.04.2009




                                   1. Employee starts
                                 Change to Working Time
                                         Form:
                                   ISR_HRASR_SH09

         Request for
          revision
                                  2. Manager approves,
                                    rejects, or requests
                                          revision                  Rejection
                                           Form:
                                    ISR-HRASR_SH09


                                                                             System
                                  3. HR Administrator                     sends e-mail
                                checks and sends data to                      about
                                     back-end system                        rejection
                                          Form:
                                   ISR_HRASR_SH09



                                          System
                                       sends e-mail
                                          about
                                         approval


                                     4. End of process




...
...




      1. Employee starts change to working time (Form ISR_HRASR_SH09)
         The employee starts the Change to Working Time (International) process and enters
         the new working time data.
      2. Manager approves, rejects, or requests revision (Form ISR_HRASR_SH09)
         In this step, the manager receives a work item with the information that a decision is
         required on the employee's request for a change to working time. The manager checks
         the request and returns it for revision, approves it, or rejects it.
         If the request is rejected, the system sends an e-mail to that effect to the manager and
         the employee.
      3. HR administrator checks and sends data to the back-end system (form
         ISR_HRASR_SH09)




HR Administrative Services (PA-AS)              6956                                          258
SAP Online Help                                                                       22.04.2009


       The form appears in the HR administrator's universal worklist. The HR administrator
       checks the data and sends the form to the back-end system, where the data from the
       form is saved automatically.
  4. End of process
       The master data of the employee is updated (infotype Planned Working Time (0007)
       and infotype Basic Pay (0008)).




       Change of Address (US)
Purpose
This process supports the changing of address data. If an employee changes residence to a
different state, the areas on the form for inputting tax data also become ready for input. It can
be optional or mandatory to enter this changed tax data. Employees can access the
necessary information regarding this using a corresponding link.
This process is intended for the country version for the US. No special Customizing settings
are required.

Prerequisites
To use this sample process for test purposes, you must have performed the Customizing
activities for HR Administrative Services as described in Configuration of Forms/Processes
Sample Processes for HCM Processes and Forms.

Technical Objects for Implementing and Executing the Process

Object Type                 ID                                                 Name
Process                     HR_PA_US_CHG_PERMANENT_ADDRESS                     Change of Address (US)
Workflow Template           WS61000075                                         Change to Permanent
                                                                               Residence (US)
ISR Scenario                SHAD                                               Change of Address (US)
Interface                   ISR_IF_SHAD
Form                        ISR_HRASR_SHAD
Form Scenario               S_HR_PA_US_CHG_PERM_ADDR                           Change of Address (US)
Scenario Steps              REQUEST                                            Request
                            PROCESS                                            Process
Attachment Types
Back-End Services           SAP_PA                                             Personnel Administration
                                                                               infotypes
                            S_CHECK_W4IND                                      Check W4 indicator for
                                                                               US state




HR Administrative Services (PA-AS)            6956                                            259
SAP Online Help                                                                      22.04.2009


Process Flow



                                             1. Employee starts
                                             change of address
                                                   Form:
                                            ISR_HRASR_SHAD


            Revision
            request

                                           2. HR Administrator
                                          checks, completes, and
                                          sends data to back-end
                                                  system
                                                   Form:
                                           ISR_HRASR_SHAD




                                              System sends e-
                                               mail regarding
                                              address change




                                              4. End of process


...




      1. Employee starts change of address (form ISR_HRASR_SHAD)
         In the form, the employee enters a date from which the new address is valid, the
         address data, and, if required, the new tax data.
      2. HR Administrator checks, completes, and sends data to the back-end system
         (form ISR_HRASR_SHAD)
         The HR Administrator checks the address data entered by the employee and
         completes the adjusted tax data. The HR Administrator then sends the data to the
         back-end system.
         The system sends an e-mail containing the changed address data and any changed
         tax data to the employee.
         If HR Administrators have a query, they can send the form back to the employee with a
         request for revision.



HR Administrative Services (PA-AS)             6956                                         260
SAP Online Help                                                                     22.04.2009


  3. End of process

Result
A new data record (infotype Address (0006)) was added to the employee's master data.
Depending on whether the new residence is in another state and whether the tax data was
adjusted accordingly, new data records were also created for the following infotypes:

       Residence Tax Area (0207)

       Work Tax Area (0208)

       Unemployment State (0209)

       Withholding Info W4/W5 US (0210)




       Company Loan (International)
Purpose
This process supports the processing of a request for a company loan.
In the form, the employee enters the date on which payment of the loan should begin.
The superior manager receives the request for a company loan for checking and can decide
to approve or reject it.
The HR administrator then checks the data and sends the form to the back-end system.
Both managers and HR administrators can send the form back to the requester with a request
for revision.
The manager and the employee are informed by e-mail once an approval or rejection has
been decided.
This process is international. No special Customizing settings are required.

Prerequisites
To be able to use these sample processes for test purposes, you must have performed the
Customizing activities for HR Administrative Services as described in Configuration of
Forms/Processes      Sample Processes for HCM Processes and Forms.

Technical Objects for Implementing and Executing the Process

Object Type                      ID                                   Name
Process                          HR_PA_XX_COMPANY_LOANS               Company Loan (International)
Workflow Template                WS61000077                           Company Loan (XX)
ISR Scenario                     SHCL                                 Company Loan (XX)
Interface                        ISR_IF_SHCL
Form                             ISR_HRASR_SHCL
Form Scenario                    S_HR_PA_XX_CL                        Company Loan (XX)
Scenario Steps                   REQUEST                              Request
                                 APPROVE                              Approve
                                 PROCESS                              Process
Attachment Types                 SCL_ST                               Certificates for Request for


HR Administrative Services (PA-AS)           6956                                          261
SAP Online Help                                                                    22.04.2009


                                                                      Company Loan
Back-End Services                  SAP_PA                             Personnel Administration
                                                                      infotypes

Process Flow

                               1. Employee starts
                                 Company Loan
                                    Form:
                              ISR_HRASR_SHCL

         Request for
          revision

                              2. Manager approves,
                               rejects, or requests
                                     revision            Rejection
                                      Form:
                               ISR-HRASR_S HCL



                                                              System sends
                              3. HR Administrator              e-mail about
                            checks and sends data to             rejection
                                back-end system
                                     Form:
                              ISR_HRASR_SHCL



                                 System sends
                                  e-mail about
                                    approval




                                4. End of process



...




      1. Employee starts company loan: form ISR_HRASR_SHCL
         The employee enters the data necessary for requesting a company loan.
      2. Manager approves, rejects, or requests revision: Form: ISR_HRASR_SHCL
      3. HR Administrator checks data, completes process: Form: ISR_HRASR_SHCL
         The HR administrator checks the completeness of the data entered by the employee.
         Once the check is complete, he or she sends the form to the back-end system.
      4. End of process
         New data records were created in the master data of the employee with the following
         infotypes:

                 Loans (Infotype 0045)

                 Loan Payments Infotype (0078)




HR Administrative Services (PA-AS)            6956                                         262
SAP Online Help                                                                   22.04.2009



       Membership Fees Sports Club (International)
Purpose
This process supports deducting membership fees for sports clubs from the employee's
salary. The employee requests this deduction using a form where he or she enters the date
on which deduction of the membership fees should begin. The employee provides the
necessary data about the membership fee by using an attachment or by entering a comment
in the appropriate field.
This process is international. If you want to use the process for a particular country version
(country grouping other than 99), then you have to enter a wage type and a payee key for the
country grouping. For more information, see the "Prerequisites" section.

Prerequisites
To be able to use these sample processes for test purposes, you must have performed the
Customizing activities for HR Administrative Services as described in Configuration of
Forms/Processes      Sample Processes for HCM Processes and Forms.

Technical Objects for Implementing and Executing the Process

Object Type                 ID                                    Name
Process                     HR_PA_XX_MEMBERSHIP_FEES              Membership Fees Sports
                                                                  Club (International)
Workflow Template           WS61000076                            Membership Fees (XX)
ISR Scenario                SHMF                                  Membership Fees Sports
                                                                  Club (XX)
Interface                   ISR_IF_SHMF
Form                        ISR_HRASR_SHMF
Form Scenario               S_HR_PA_XX_MF                         Membership Fees Sports
                                                                  Club (XX)
Scenario Steps              REQUEST                               Request
                            PROCESS                               Process
Attachment Types            SMF_RCT                               Certificate for Membership
                                                                  Fees Sports Club
Back-End Services           SAP_PA                                Personnel Administration
                                                                  infotypes


If you want to use this process for a country grouping other than 99, you also have to make
the following settings:

       In Customizing for Payroll, choose Payroll: International Basic Settings
       Environment of Wage Type Maintenance          Check Wage Type Characteristics. Select
       an appropriate wage type for deducting membership fees for sports clubs.

       In the Payee Authorization for Infotypes (V_T512C) view, enter a suitable Payee Key
       for Transfers for the Memberships (0057) infotype for subtype 3, Sports Club.




HR Administrative Services (PA-AS)          6956                                          263
SAP Online Help                                                                   22.04.2009


Process Flow


                                            1. Employee starts
                                          Membership Fees Sports
                                                  Club
                                                 Form:
                                           ISR_HRASR_SHMF


         Request for
          revision

                                           2. HR Administrator
                                          checks, completes, and
                                          sends data to back-end
                                                  system
                                                  Form:
                                           ISR_HRASR_SHMF




                                                     System
                                                     sends
                                                   confirmation
                                                    message




                                               3. End of process


....
   5. Employee starts Membership Fees Sports Club: Form ISR_HRASR_SHMF
       The employee enters the date from which the membership fees for the sports club
       should be deducted from his or her salary. Since the details for paying membership
       fees (such as, the amount and frequency of the payments) are fixed, the employee is
       only required to enter the start date.
       The employee can choose to enter the purpose.
       The employee can enter additional data in the form of Notes or as an attachment.
   6. HR administrator checks, completes, and sends data to the back-end system:
      Form ISR_HRASR_SHMF)


HR Administrative Services (PA-AS)          6956                                          264
SAP Online Help                                                                   22.04.2009


      The HR administrator checks the data entered by the employee and then enters the
      appropriate wage type and payee key. The HR administrator then sends the data to the
      back-end system.
      The employee is informed about the deduction of membership fees by e-mail.
      If HR administrators have a query, they send the form back to the employee with a
      request for revision.
  7. End of process




      Termination (Germany)
Purpose
The Termination process supports the termination of an employee that is initiated by the
employee. Once the process has been performed successfully, the master data of the
affected employee is updated. Meaning, a leaving was performed at the master data level. In
addition to the employee, the Personnel Officer, Manager, and HR Administrator business
roles are actively involved in performing the process.
Using the Termination process accelerates and optimizes the termination procedure, since
the system integration of all roles guarantees that work items are forwarded as quickly as
possible, and that all parties are informed at all times.



              For the Manager and HR Administrator business roles, SAP delivers the
              corresponding Manager [External] and HR Administrator [Page 370] portal roles
              in the standard system. The Personnel Officer business role is provided to help
              you better understand the process flow of the termination, and enables you to
              include customer requirements more quickly and more efficiently in the process
              flow of the termination. The Personnel Officer role is also assigned to the HR
              Administrator portal role.

Prerequisites
To be able to use this sample process for test purposes, you must have performed the
Customizing activities for HR Administrative Services as described in Configuration of
Forms/Processes      Sample Processes for HCM Processes and Forms.

Technical Objects for Implementing and Executing the Process

Object Type            ID                          Name
Process                TERMINATION                 Termination
WS Template            WS17900391                  Termination (DE)
ISR Scenario           STN1                        Termination Scenario 1
                       STN2                        Termination Scenario 2
                       STN3                        Termination Scenario 3
                       STN4                        Termination Scenario 4
Interface              ISR_IF_STN1                 Termination I
                       ISR_IF_STN2                 Termination II
                       ISR_IF_STN3                 Termination III



HR Administrative Services (PA-AS)          6956                                          265
SAP Online Help                                                             22.04.2009


                     ISR_IF_STN4             Termination IV
Form Scenario        STN1                    Termination Form Scenario 1
                     STN2                    Termination Form Scenario 2
                     STN3                    Termination Form Scenario 3
                     STN4                    Termination Form Scenario 4
Form                 ISR_HRASR_STN1          Termination I
                     ISR_HRASR_STN2          Termination II
                     ISR_HRASR_STN3          Termination III
                     ISR_HRASR_STN4          Termination IV
Scenario Steps       STN1:                   STN1:
                     EMPL_REQUEST            Request
                     HRG_IN                  Approve


                     STN2:                   STN2:
                     HRG_FR                  Create Final Version of Reference
                     MGR_AR                  Approve Final Version of Reference
                     MGR_RR                  Create Raw Version of Reference


                     STN3:                   STN3:
                     HRA_DATA                Maintain Data


                     STN4:                   STN4:
                     HRG_FINAL               Final Check and Writing of Data to Database
Attachment Types     STN1:                   STN1:
                     STN_TL                  Notice Letter of Employee


                     STN2:                   STN2:
                     STN_RL                  Reference
                     STN_TL                  Notice Letter of Employee


                     STN3:                   STN3:
                     STN_TL                  Notice Letter of Employee


                     STN4:                   STN4:
                     STN_RL                  Reference
                     STN_TL                  Notice Letter of Employee
Back-End
Services
Standard Services    SAP_PA                  Personnel Administration infotypes




HR Administrative Services (PA-AS)    6956                                         266
SAP Online Help                                                                        22.04.2009


Process Flow
                                                                 1. Employee starts the
                                                                  Termination process
                                                                        Form:
                                                                  ISR_HRASR_STN1
                                             Request
                                             revision             2. Personnel Officer
                                                                 approves termination or
                                                                    returns the form for
                                                                          revision
                                                                           Form:
                                                                   ISR_HRASR_ST N1


                         3a. Manager enters raw                                                     3c. HR
                           version of reference                                                          mis
                                  Form:                         3b. Employee performs                   Ter
                           ISR_HRASR_ST N2
                                                                 Life and Work Event
                                                                     “Termination“                      ISR


                          4a. Personnel Officer
                          creates final version of
                                reference
                                  Form:
    Request                ISR_HRASR_ST N2
    revision
                          5a. Manager approves
                           reference or requests
                              that it be revised
                                    Form:
                            ISR_HRASR_ST N2
                                                                        AND

                                                                 6. Personnel Officer
                                                                   checks documents
                                                                        Form:
                                                                  ISR_HRASR_ST N4

                                                                    7. M anager and
                                                                  Employee receive
                                                                  information e-mails

                                                                   8. End of process




1. Employee starts the Termination process
    The employee chooses the Termination process and enters the required termination
date.
2. Personnel Officer checks termination
      The Personnel Officer of the employee checks the termination request for correctness
      (for example, compliance with notice periods, company regulations). The personnel
      officer then has three options:

               Request Revision: In this case, the form is sent back to the requester.

               Approve Termination: In this case, the form is forwarded to the next agent.

               Reject Termination: In this case, the process is completed.
3. a) Manager enters raw version of reference



HR Administrative Services (PA-AS)             6956                                          267
SAP Online Help                                                                   22.04.2009


      The manager of the employee creates the raw version of a reference and adds this raw
      version as an attachment to the work item for processing the termination.
4. a) Personnel Officer creates final version of reference
      The Personnel Officer receives the raw version of the reference and completes the
      reference.
5. a) Manager approves the completed reference or requests that it be revised
      The manager receives the completed version of the reference and can choose from the
      following:

             Accept Reference

             Request Revision: In this case, the personnel officer receives the reference
             again for further revision. Step 4a is repeated.
3. b) Employee performs Life and Work Event Termination
      The employee performs the Life and Work Event Termination, for example, by clearing
      out his or her desk and leaving the company.
3. c) HR Administrator enters missing data for termination
      The HR Administrator enters the missing data for the termination that cannot be
      entered by the employee.
6. Personnel Officer checks documents and forms
      When this step has been performed, the system transfers the data from the forms to
      the database.
7. Information mails are sent to the employee and the manager
8. End of process



Result
The process has the following possible results:

      Termination Carried Out: The employee's master data has been updated according to
      the entries on the form.

      Termination Rejected: No changes have been made to the employee's master data.




      Termination (US)
Purpose
The Termination process supports the termination of an employee that is initiated by the
employee himself or herself. Once the process has been executed successfully, the master
data of the affected employee is updated. In other words, a leaving was performed at the
master data level. In addition to the employee, the Personnel Officer, Manager, and HR
Administrator business roles are actively involved in executing the process.
Using the Termination process accelerates and optimizes the termination procedure, since
the system integration of all roles guarantees that work items are forwarded as quickly as
possible and that all parties are informed at all times.




HR Administrative Services (PA-AS)          6956                                            268
SAP Online Help                                                                    22.04.2009




              For the Manager and HR Administrator business roles, SAP delivers the
              corresponding Manager Self-Service [External] and HR Administrator [Page
              370] portal roles in the standard system. The Personnel Officer business role is
              provided to help you better understand the process flow of the termination and
              enables you to include customer requirements more quickly and more efficiently
              in the process flow of the termination. The Personnel Officer role is also
              assigned to the HR Administrator portal role.

Prerequisites
To be able to use these sample processes for test purposes, you must have performed the
Customizing activities for HR Administrative Services as described in Configuration of
Forms/Processes      Sample Processes for HCM Processes and Forms.

Technical Objects for Implementing and Executing the Process

Object Type           ID                         Name
Process               TERMINATION                Termination
Workflow Template     WS18900010                 Termination (US)
ISR Scenario          STU1                       Termination Scenario 1
                      STU2                       Termination Scenario 2
                      STU3                       Termination Scenario 3
                      STU4                       Termination Scenario 4
Interface             ISR_IF_STU1                Termination I
                      ISR_IF_STU2                Termination II
                      ISR_IF_STU3                Termination III
                      ISR_IF_STU4                Termination IV
Form Scenario         STU1                       Termination Form Scenario 1
                      STU2                       Termination Form Scenario 2
                      STU3                       Termination Form Scenario 3
                      STU4                       Termination Form Scenario 4
Form                  ISR_HRASR_STU1             Termination I
                      ISR_HRASR_STU2             Termination II
                      ISR_HRASR_STU3             Termination III
                      ISR_HRASR_STU4             Termination IV
Scenario Steps        STU1:                      STU1:
                      EMPL_REQUEST               Request
                      HRG_IN                     Approve


                      STU2:                      STU2:
                      HRG_FR                     Create Final Version of Reference
                      MGR_AR                     Approve Final Version of Reference
                      MGR_RR                     Create Raw Version of Reference




HR Administrative Services (PA-AS)           6956                                          269
SAP Online Help                                                          22.04.2009


                    STU3:               STU3:
                    HRA_DATA            Maintain Data


                    STU4:               STU4:
                    HRG_FINAL           Final Check and Writing of Data to Database
Attachment Types    STU1:               STU1:
                    STU_TL              Notice Letter of Employee


                    STU2:               STU2:
                    STU_RL              Reference
                    STU_TL              Notice Letter of Employee


                    STU3:               STU3:
                    STU_TL              Notice Letter of Employee


                    STU4:               STU4:
                    STU_RL              Reference
                    STU_TL              Notice Letter of Employee
Backend Services
Standard Services   SAP_PA              Personnel Administration infotypes




HR Administrative Services (PA-AS)   6956                                      270
SAP Online Help                                                                        22.04.2009


Process Flow
                                                             1. Employee starts the
                                                              Termination process
                                                                    Form:
                                                              ISR_HRASR_STU1
                                           Request
                                           revision          2. Personnel Officer
                                                            approves ter mination or
                                                              returns the form for
                                                                    revision
                                                                     Form:
                                                              ISR_HRASR_STU1


                       3a. Manager enters raw               3b. Employee executes                   3c. HR Admin
                        version of reference                 Life and Work Event                    missing data f
                               Form:                             "Termination"                                For
                        ISR_HRASR_STU2                                                                  ISR_HRAS



                       4a. Personnel Officer
                       creates final version of
                             reference
                                Form:
                        ISR_HRASR_STU2
   Request
   revision
                       5a. Manager approves
                       reference or requests
                          that it be revised
                                 Form:
                        ISR_HRASR_STU2
                                                                    AND

                                                             6. Personnel Officer
                                                               checks documents
                                                                    Form:
                                                              ISR_HRASR_STU4

                                                                7. Manager and
                                                              employee receive
                                                              information e-mails
                                                              8. End of process




1. Employee starts the Termination process
     The employee selects the Termination process and enters the required termination
     date.
2. Personnel Officer checks termination
     The Personnel Officer of the employee checks the termination request for correctness
     (for example, compliance with notice periods, company regulations). The personnel
     officer then has three options:

              Request Revision: In this case, the form is sent back to the requester.

              Approve Termination: In this case, the form is forwarded to the next agent.

              Reject Termination: In this case, the process is completed.


HR Administrative Services (PA-AS)                6956                                       271
SAP Online Help                                                                   22.04.2009


3. a) Manager enters raw version of reference
      The manager of the employee creates the raw version of a reference and adds this raw
      version as an attachment to the work item for processing the termination.
4. a) Personnel Officer creates final version of reference
      The Personnel Officer receives the raw version of the reference and completes the
      reference.
5. a) Manager approves the completed reference or requests that it be revised
      The manager receives the completed version of the reference and can choose from the
      following:

             Accept Reference

             Request Revision: In this case, the personnel officer receives the reference
             again for further revision. Step 4a is repeated.
3. b) Employee executes Life and Work Event Termination
      The employee executes the Life and Work Event Termination, for example, by clearing
      out his or her desk and leaving the company.
3. c) HR Administrator enters missing data for termination
      The HR Administrator enters the missing data for the termination that cannot be
      entered by the employee himself or herself.
6. Personnel Officer checks documents and forms.
      When this step has been executed, the system transfers the data from the forms to the
      database.
7. Information mails are sent to the employee and the manager
8. End of process




   Special Payment for Mass Start (Multi-Step
Process)

This process supports a special payment to multiple employees. The process consists of the
following steps:

   1. The manager enters the data for the employees in the table - payment amount and
      payment type. After the Review and Save step, the data is automatically broken into
      separate process instances for each employee.

   2. The superior manager receives each of the process instances separately, and
      approves the payment requests.

   3. The HR Administrator saves the data to the backend. It is also possible for the HR
      Administrator to make changes in this step.

Prerequisites
To be able to use this sample process for test purposes, you must have performed the
Customizing activities for Personnel Management under HR Administrative Services
  Configuration of Forms/Processes Sample Processes for HCM Processes and Forms              .

Technical Objects for Implementing and Executing the Process


HR Administrative Services (PA-AS)          6956                                            272
SAP Online Help                                                                   22.04.2009



  Object Type                           ID                               Name

Process              HR_PA_XX_MSP_SPECIAL_PAYMENT Special Payment

Workflow
                     WS04000034
Template

ISR Scenario         SM01

Interface            ISR_IF_SM01

Form Scenario        S_HR_PA_XX_MSP_SPAYMENT                Special Payment

Form                 ISR_HRASR_SM01

Scenario Steps       Request, Approve, Process

Back-End                                                    Personnel Administration
                     SAP_PA
Services                                                    infotypes

Process


            Manager enters payment           Emp1
              details for selected
                                             Emp2                             Data is entered
             employees, payment
                                                                              in table format,
            amount, reason, checks           Emp3                             with a different
               and sends data                                                 employee in
                                             Emp4                             each row




            Superior manager reviews
              payment request and
               approves payment
                                                 Form
                                                    Form
                                                        Form                  Separate
                                                                              Process
                                                               Form           Instances (and
            HR Administrator reviews                                          forms) for each
              payment request and                                             employee
            saves data to the backend




                 End of Process




Special Payment For Mass Start

    1. After choosing Start Process for Multiple Employees in the Portal, the manager starts
       the Special Payment process.

    2. The manager searches for and selects employees to which the special payment is
       being given in the team view.



HR Administrative Services (PA-AS)           6956                                           273
SAP Online Help                                                                     22.04.2009


    3. The selected employee data is displayed in table format on the Enter Data screen.

        The manager selects the employees and chooses Set Values for Selected
        Employees.

    4. The manager enters payment amount and payment type in the dialog box that
       appears.

    5. He or she can choose Check Selected Employees to check for any errors in the data.

        If there are no errors, choose Next.

    6. The manager reviews the data entered and chooses Save. Separate process
       instances (and therefore work items) are automatically created for each employee.

    7. Each work item is sent to the next agent involved in the process — the superior
       manager — (there can be different agents for different work items). The superior
       manager reviews the payment data entered and approves the payment. The form is
       sent to the next agent in the process, the HR Administrator.

        Alternatively, the superior manager can send the form back to the requesting
        manager if there is an issue, for example, with the payment amount.

    8. The HR Administrator reviews the payment details and saves the data to the
       backend. It is also possible for the HR Administrator to make changes in this step.

    9. End of process.

Result
The payments have been approved for the selected employees.



     Address Change (Single-Step Process)

This process supports an address change for multiple employees at the same time. This is a
single-step process. It is started by the HR Administrator in the Portal. The HR Administrator
enters the new data for a number of employees and saves the changes, updating the master
data.

Prerequisites
To be able to use this sample process for test purposes, you must have performed the
Customizing activities for Personnel Management under HR Administrative Services
  Configuration of Forms/Processes Sample Processes for HCM Processes and Forms

Technical Objects for Implementing and Executing the Process

  Object Type                         ID                                   Name

Process             HR_PA_XX_MSP_ADDR_CHANGE                Address Change

Workflow
                    None
Template

ISR Scenario        SM02




HR Administrative Services (PA-AS)             6956                                          274
SAP Online Help                                                                    22.04.2009



   Object Type                        ID                                    Name

Interface           ISR_IF_SM02

Form Scenario       S_HR_PA_XX_MSP_ADDR_CHANGE Address Change

Form                ISR_HRASR_SM02

Scenario Steps      Default

Back-End                                                   Personnel Administration
                    SAP_PA
Services                                                   infotypes

Process




            HR Administrator enters
             new address data for
              selected employees,
            saves and sends data to
              the back-end system
                                                  Emp1


                                                  Emp2


                                                  Emp3


                                                  Emp4




                 End of Process

                                                          Data is entered in
                                                          table format, with a
                                                          different employee
                                                          in each row




Address Change

    1. The HR Administrator starts the Address Change process.

    2. The HR Administrator searches for and selects employees whose address he or she
       wants to change.

    3. The selected employee data is displayed in table format on the Enter Data screen.

        The HR Administrator selects the employees and chooses Set Values for Selected
        Employees.

    4. Enter the address data in the dialog box that appears.

    5. Choose Check Selected Employees to check for any errors in the data.



HR Administrative Services (PA-AS)         6956                                          275
SAP Online Help                                                                     22.04.2009


        If there are no errors, choose Next.

    6. Review the data you have entered and choose Save.

    7. End of process.

Result
The address data is changed for the selected employees, so that the new address now
appears. The master data is directly updated.



       Create Position

This process supports the creating of a new position along with the business attributes for that
position. The process consists of the following steps:

    1. The Requesting Manager enters the Name, Description and vacancy details for the
       new position and sends the request to the HR Administrator.

    2. The HR Administrator reviews the data entered by manager and enters the business
       attributes for the position.

Each role can enter comments using the field New Comments at the bottom of the form. All
comments can be read by the subsequent processors in the field Previous Comments.

Prerequisites
To be able to use this sample process for test purposes, you must have performed the
Customizing activities for Personnel Management under HR Administrative Services
  Configuration of Forms/Processes Sample Processes for HCM Processes and Forms               .

Technical Objects for Implementing and Executing the Process

   Object Type                        ID                                  Name

Process               HR_PD_CREATE_POSITION               Create Position

Workflow Template WS04000032                              Create Position

ISR Scenario          SO03

Interface             ISR_IF_SO03

Form Scenario         S_HR_PD_CREATE_POSITION             Create Position

Form                  ISR_HRASR_SO03

Scenario Steps        STAGE_01, STAGE_02

Back-End Services     SAP_PD                              Personnel Development Infotypes




HR Administrative Services (PA-AS)             6956                                         276
SAP Online Help                                                                   22.04.2009


Process




              Requesting Manager
              enters the name and
             details of new position



                                                        Create new
                                                      position request

           HR Administrator receives
            work item, reviews data
            and enters the business
           attributes for the position




                  End of Process




Create Position

   1. The Requesting Manager starts the Create Position process.

   2. The Requesting Manager selects the organizational unit to which this position is to be
      assigned, and goes to the Fill Out Form step. Here the Org. ID and abbreviation are
      displayed at the top of the form.

   3. The Requesting Manager enters the creation date of the new position.

   4. The Requesting Manager enters the new position name, position abbreviation, status
      of position, whether the position is vacant, and a description under New.

   5. If required, he or she can enter a comment in the New Comments field, for example,
      explaining the reason for the creation of the new position.

   6. The form is sent to the next role involved in the process, the HR Administrator.

   7. The HR Administrator reviews the data entered by the Requesting Manager and
      enters the position’s Account Assignment, Work Schedule, and Employee Group/Sub
      group.

   8. The HR Administrator enters a comment in the New Comments field, if necessary.
      The HR Administrator checks and sends the form and the changes are saved to the
      master data.

   9. End of process.

Result
The new position has been created.



HR Administrative Services (PA-AS)         6956                                          277
SAP Online Help                                                                  22.04.2009



       Change Position Name

This process supports the changing of a position name. This is a single-step process. It is
started by the HR Administrator in the HR system. The HR Administrator manually completes
the form, filling in the new position name and a description for the new name.

Prerequisites
To be able to use this sample process for test purposes, you must have performed the
Customizing activities for Personnel Management under HR Administrative Services
  Configuration of Forms/Processes Sample Processes for HCM Processes and Forms           .

Technical Objects for Implementing and Executing the Process

  Object Type                         ID                                 Name

Process            HR_PD_CHANGE_POSITION_NAME               Change Position Attributes

Workflow
                   None
Template

ISR Scenario       SO01

Interface          ISR_IF_SO01

Form Scenario      S_HR_PD_CHANGE_POSITION_NAME Change Position Name

Form               ISR_HRASR_SO01

Scenario Steps     STAGE_01

Back-End                                                    Personnel Development
                   SAP_PD
Services                                                    Infotypes




HR Administrative Services (PA-AS)         6956                                          278
SAP Online Help                                                                 22.04.2009


Process




          HR Administrator enters
            new position name,
         completes and sends data
          to the back-end system




              End of Process




Change Position Name

   1. The HR Administrator starts the Change Position Name process.

   2. The HR Administrator selects a position and goes to the Fill Out Form step. Here the
      Position ID and abbreviation are displayed at the top of the form.

   3. The HR Administrator enters the date that the name change is to be effective from.

   4. Under Old, the existing position name and description is displayed. The HR
      Administrator enters the new position name and a description under New. The new
      position name replaces the old one in the system, so that when the process is called
      up, the new name is displayed.

   5. If required, enter a comment in the comment field, for example, explaining the reason
      for the name change.

   6. End of process.

Result
The position name has been changed, so that the new position name now appears. The
master data is directly updated.



     Change Position Attributes




HR Administrative Services (PA-AS)        6956                                          279
SAP Online Help                                                                   22.04.2009


This process supports the changing of the business attributes of a position. The process
consists of the following steps:

    1. The Requesting Manager enters a new Name and Description for the position and
       sends the request to HR Administrator.

    2. The HR Administrator reviews the data entered by the manager and enters the new
       technical attributes for the position.

Each role can enter comments using the field New Comments at the bottom of the form. All
comments can be read by the subsequent processors in the field Previous Comments.

Prerequisites
To be able to use this sample process for test purposes, you must have performed the
Customizing activities for Personnel Management under HR Administrative Services
  Configuration of Forms/Processes Sample Processes for HCM Processes and Forms              .

Technical Objects for Implementing and Executing the Process

  Object Type                         ID                                  Name

Process           HR_PD_CHANGE_POS_ATTRIBUTES                Change Position Attributes

Workflow
                  WS04000038                                 Change Position Attributes
Template

ISR Scenario      SO08

Interface         ISR_IF_SO08

                                                             Change Business attributes of
Form Scenario     S_HR_PD_CHANGE_POS_ATTRIBUTES
                                                             Position

Form              ISR_HRASR_SO08

Scenario Steps    STAGE_01, STAGE_02

Back-End                                                     Personnel Development
                  SAP_PD
Services                                                     Infotypes




HR Administrative Services (PA-AS)          6956                                           280
SAP Online Help                                                                    22.04.2009


Process




             Requesting Manager
           starts the process, enters
             a new position name



                                                     Change attributes
                                                         request

           HR Administrator receives
            work item, reviews data
            and enters the technical
           attributes for the position




                  End of Process




Change Position Attributes

   1. The Requesting Manager starts the Change Position Attributes process.

   2. He or she selects a position and goes to the Fill Out Form step. The Position ID and
      abbreviation are displayed at the top of the form.

   3. He or she enters the date from which the changed attributes are effective.

   4. Under Old, the existing position name and description is displayed. The Requesting
      Manager enters the new position name and a description under New. The new
      position name replaces the old one in the system.

   5. If required, enter a comment in the New Comments field, for example, explaining the
      reason for the name change.

   6. The form is sent to the next role involved in the process, the HR Administrator. The
      Process Reference Number is displayed at the top of the form.

   7. The HR Administrator reviews the data entered by the Requesting Manager and
      enters the new technical attributes for the position.

   8. The HR Administrator enters a comment in the New Comments field, if necessary.
      The HR Administrator checks and sends the form and the changes are saved to the
      master data.

   9. End of process.

Result
The position attributes have been changed.



HR Administrative Services (PA-AS)           6956                                        281
SAP Online Help                                                                    22.04.2009



       Move Position

This process supports the moving of a position. The process consists of the following steps:

    1. The Requesting Manager enters the new organizational (org.) unit's details and
       sends the move request to the HR Administrator.

    2. The HR Administrator reviews the data entered by manager and sends the data
       (Update of master data).

Each role can enter comments using the field New Comments at the bottom of the form. All
comments can be read by the subsequent processors in the field Previous Comments.

Prerequisites
To be able to use this sample process for test purposes, you must have performed the
Customizing activities for Personnel Management under HR Administrative Services
  Configuration of Forms/Processes Sample Processes for HCM Processes and Forms                .

Technical Objects for Implementing and Executing the Process

    Object Type                      ID                                 Name

Process               HR_PD_MOVE_POSITION               Move Position

Workflow Template     WS04000035                        Move Position

ISR Scenario          SO09

Interface             ISR_IF_SO09

Form Scenario         S_HR_PD_MOVE_POSITION             Move Position

Form                  ISR_HRASR_SO09

Scenario Steps        STAGE_01, STAGE_02

Back-End Services     SAP_PD                            Personnel Development Infotypes




HR Administrative Services (PA-AS)          6956                                          282
SAP Online Help                                                                   22.04.2009


Process




             Requesting Manager
           starts the process, enters
                the new org. unit



                                                       Move position
                                                         request

           HR Administrator receives
            work item, reviews data
             and sends the data




                  End of Process




Move Position

   1. The Requesting Manager starts the Move Position process.

   2. The Requesting Manager selects the position and goes to the Fill Out Form step. The
      Position ID and abbreviation are displayed at the top of the form.

   3. The Requesting Manager enters the date that the position move is to be effective
      from.

   4. The Requesting Manager enters the target Org. ID that the position is to be moved to.
      If required, he or she can enter a comment in the New Comments field, for example,
      explaining the reason for the name change.

   5. The form is sent to the next role involved in the process, the HR Administrator.

   6. The HR Administrator reviews the data entered by the Requesting Manager and
      sends the data.

   7. The HR Administrator enters a comment in the New Comments field, if necessary.
      The changes are saved to the master data

   8. End of process.

Result
The position has been moved to the new organizational unit.




HR Administrative Services (PA-AS)         6956                                          283
SAP Online Help                                                                      22.04.2009



       Delete Position

This process supports the deleting of a position along with its business attributes. The
process consists of the following steps:

    1. The Requesting Manager reviews the Name, Description and vacancy details of the
       position to be deleted and sends the request to the HR Administrator.

    2. The HR Administrator checks and sends the data. (Updates master data.)

Each role can enter comments using the field New Comments at the bottom of the form. All
comments can be read by the subsequent processors in the field Previous Comments.

Prerequisites
To be able to use this sample process for test purposes, you must have performed the
Customizing activities for Personnel Management under HR Administrative Services
  Configuration of Forms/Processes Sample Processes for HCM Processes and Forms              .

Technical Objects for Implementing and Executing the Process

    Object Type                        ID                                 Name

Process               HR_PD_DELETE_POSITION                Delete Position

Workflow Template     WS04000039                           Delete Position

ISR Scenario          SO11

Interface             ISR_IF_SO11

Form Scenario         S_HR_PD_DELETE_POSITION              Delete Position

Form                  ISR_HRASR_SO11

Scenario Steps        STAGE_01, STAGE_02

Back-End Services     SAP_PD                               Personnel Development Infotypes




HR Administrative Services (PA-AS)           6956                                          284
SAP Online Help                                                                    22.04.2009


Process




            Requesting Manager starts
             the process, reviews the
            position to be deleted and
                forwards to the HR
                   Administrator

                                                        Delete Position
                                                           Request

            HR Administrator receives
             work item, reviews data
              and sends the data to
               delete the position




                  End of Process




Delete Position

    1. The Requesting Manager starts the Delete Position process.

    2. The Requesting Manager selects the position to be deleted, and goes to the Fill Out
       Form step. The Position ID and abbreviation are displayed at the top of the form.

    3. The deletion date is automatically entered as the current date.

    4. The Requesting Manager reviews the position details and forwards to the HR
       Administrator. If required, he or she can enter a comment in the New Comments field,
       for example, explaining the reason for the deletion of the position.

    5. The form is sent to the next role involved in the process, the HR Administrator.

    6. The HR Administrator enters a comment in the New Comments field, if necessary.
       The HR Administrator checks and sends the form and the change is saved to the
       master data.

    7. End of process.

Result
The position, along with its business attributes, has been deleted.



     Delimit Position Assignment



HR Administrative Services (PA-AS)           6956                                         285
SAP Online Help                                                                      22.04.2009


This process supports the delimiting of a position assignment to an organizational (org.) unit.
The process consists of the following steps:

    1. The Requesting Manager chooses the position, reviews the current assignment data,
       and sends the request to the HR Administrator.

    2. The HR Administrator checks and sends the data. (Update of master data). If you do
       not want to delimit the assignment, you can choose to withdraw the process by
       selecting Withdraw at the bottom of the form.

Each role can enter comments using the field New Comments at the bottom of the form. All
comments can be read by the subsequent processors in the field Previous Comments.

Prerequisites
To be able to use this sample process for test purposes, you must have performed the
Customizing activities for Personnel Management under HR Administrative Services
  Configuration of Forms/Processes Sample Processes for HCM Processes and Forms               .

Technical Objects for Implementing and Executing the Process

  Object Type                           ID                                   Name

Process            HR_PD_DELIMIT_POS_ASSIGNMENT                 Delimit Position Assignment

Workflow
                   WS04000036                                   Delimit Position Assignment
Template

ISR Scenario       SO10

Interface          ISR_IF_SO10

Form Scenario      S_HR_PD_DELIMIT_POS_ASSIGNMENT Delimit Position Assignment

Form               ISR_HRASR_SO10

Scenario Steps     STAGE_01, STAGE_02

Back-End                                                        Personnel Development
                   SAP_PD
Services                                                        Infotypes




HR Administrative Services (PA-AS)           6956                                           286
SAP Online Help                                                                    22.04.2009


Process




            Requesting Manager starts
             the process, chooses the
              position and reviews the
           current assignment data and
            sends to HR Administrator

                                                       Delimit Position
                                                        Assignment

           HR Administrator receives
            work item, reviews data
             and sends the data




                  End of Process




Delimit Position Assignment

    1. The Requesting Manager starts the Delimit Position Assignment process.

    2. The Requesting Manager selects the position and goes to the Fill Out Form step. The
       Position ID and abbreviation are displayed at the top of the form.

    3. The Requesting Manager enters the date from which the position should be delimited.

    4. The Requesting Manager enters the target Org. ID that the position is to be moved to.
       If required, he or she can enter a comment in the New Comments field, for example,
       explaining the reason for the move.

    5. The form is sent to the next role involved in the process, the HR Administrator.

    6. The HR Administrator reviews the data entered by the Requesting Manager and
       sends the data.

    7. The HR Administrator enters a comment in the New Comments field, if necessary.
       The changes are saved to the master data.

    8. End of process.

Result
The position has been delimited to the new organizational unit.



     Create Organizational Unit


HR Administrative Services (PA-AS)          6956                                          287
SAP Online Help                                                                     22.04.2009


This process supports the creation of an organizational unit. The process consists of the
following steps:

    1. The Requesting Manager enters the Name and Description for the new organizational
       (org.) unit and sends the request to HR Administrator.

    2. The HR Administrator reviews data entered by manager and enters the business
       attributes for the organizational (org.) unit.

Each role can enter comments using the field New Comments at the bottom of the form. All
comments can be read by the subsequent processors in the field Previous Comments.

Prerequisites
To be able to use this sample process for test purposes, you must have performed the
Customizing activities for Personnel Management under HR Administrative Services
  Configuration of Forms/Processes Sample Processes for HCM Processes and Forms               .

Technical Objects for Implementing and Executing the Process

  Object Type                           ID                                   Name

Process           HR_PD_CREATE_ORGANIZATION_UNIT                 Create Organizational Unit

Workflow
                  WS04000033                                     Create Organizational Unit
Template

ISR Scenario      SO05

Interface         ISR_IF_SO05

Form Scenario     S_HR_PD_CREATE_ORGANIZATION_UNIT Create Org. Unit

Form              ISR_HRASR_SO05

Scenario Steps    STAGE_01, STAGE_02

Back-End                                                         Personnel Development
                  SAP_PD
Services                                                         Infotypes




HR Administrative Services (PA-AS)           6956                                           288
SAP Online Help                                                                   22.04.2009


Process




              Requesting Manager
              enters the name and
             details of new org. unit



                                                      Create new org.
                                                        unit request
           HR Administrator receives
            work item, reviews data
            and enters the business
           attributes for the new org.
                       unit




                  End of Process




Create Organizational Unit

   1. The Requesting Manager starts the Create Organizational Unit process.

   2. The Requesting Manager goes to the Fill Out Form step. The root Org. ID and
      abbreviation are displayed at the top of the form.

   3. The Requesting Manager enters the creation date of the org. unit.

   4. The Requesting Manager enters the new org. unit name, position abbreviation, and a
      description.

   5. If required, he or she can enter a comment in the New Comments field, for example,
      explaining the reason for the creation of the new org. unit.

   6. The form is sent to the next role involved in the process, the HR Administrator.

   7. The HR Administrator reviews the data entered by the Requesting Manager and
      enters the org. unit’s Account Assignment and Work Schedule.

   8. The HR Administrator enters a comment in the New Comments field, if necessary.
      The HR Administrator checks and sends the form and the changes are saved to the
      master data.

   9. End of process.

Result
The new organizational unit has been created.




HR Administrative Services (PA-AS)         6956                                          289
SAP Online Help                                                                   22.04.2009



       Change Organizational Unit Name

This process supports the changing of an organizational unit name. This is a single-step
process. It is started by the HR Administrator in the HR system. The HR Administrator
manually completes the form, filling in the new organizational (org.) unit name and a
description for the new name.

Prerequisites
To be able to use this sample process for test purposes, you must have performed the
Customizing activities for Personnel Management under HR Administrative Services
  Configuration of Forms/Processes Sample Processes for HCM Processes and Forms             .

Technical Objects for Implementing and Executing the Process

  Object Type                          ID                                  Name

                                                              Change Organizational Unit
Process            HR_PD_CHANGE_ORG_UNIT_NAME
                                                              Name

Workflow
                   None
Template

ISR Scenario       SO04

Interface          ISR_IF_SO04

Form Scenario      S_HR_PD_CHANGE_ORG_UNIT_NAME Change Org. Unit Name

Form               ISR_HRASR_SO04

Scenario Steps     STAGE_01

Back-End                                                      Personnel Development
                   SAP_PD
Services                                                      Infotypes




HR Administrative Services (PA-AS)          6956                                           290
SAP Online Help                                                                    22.04.2009


Process




            HR Administrator enters
              new org. unit name,
           completes and sends data
            to the back-end system




                  End of Process




Change Organizational Unit Name

    1. The HR Administrator starts the Change Organizational Unit Name process.

    2. The HR Administrator selects an org. unit and goes to the Fill Out Form step. Here
       the Org. ID and abbreviation are displayed at the top of the form.

    3. The HR Administrator enters the date that the name change is to be effective from.

    4. Under Old, the existing org. unit name and description is displayed. The HR
       Administrator enters the new org. unit name and a description under New. The new
       org. unit name replaces the old one in the system.

    5. If required, enter a comment in the comment field, for example, explaining the reason
       for the name change.

    6. End of process.

Result
The organizational unit name has been changed, so that the new org. unit name now
appears. The master data is directly updated.



     Change Organizational Unit Attributes

This process supports the changing of the business attributes of an organizational unit. The
process consists of the following steps:



HR Administrative Services (PA-AS)          6956                                           291
SAP Online Help                                                                 22.04.2009


    1. The Requesting Manager enters a new Name and Description for the organizational
       (org.) unit and sends the request to HR Administrator.

    2. The HR Administrator reviews data entered by manager and enters the new technical
       attributes for the org. unit.

Each role can enter comments using the field New Comments at the bottom of the form. All
comments can be read by the subsequent processors in the field Previous Comments.

Prerequisites
To be able to use this sample process for test purposes, you must have performed the
Customizing activities for Personnel Management under as described in HR Administrative
Services Configuration of Forms/Processes Sample Processes for HCM Processes and
Forms .

Technical Objects for Implementing and Executing the Process

Object Type                          ID                                 Name

                                                            Change Organizational Unit
Process       HR_PD_CHANGE_ORG_UNIT_ATTRIBUTES
                                                            Attributes

Workflow                                                    Change Organizational Unit
              WS04000031
Template                                                    Attributes

ISR Scenario SO02

Interface     ISR_IF_SO02

Form                                                        Change Business attributes of
              S_HR_PD_CHANGE_ORG_ATTRIBUTES
Scenario                                                    Organizational Unit

Form          ISR_HRASR_SO02

Scenario
              STAGE_01, STAGE_02
Steps

Back-End                                                    Personnel Development
              SAP_PD
Services                                                    Infotypes




HR Administrative Services (PA-AS)         6956                                        292
SAP Online Help                                                                   22.04.2009


Process




             Requesting Manager
           starts the process, enters
             a new org. unit name



                                                     Change attributes
                                                         request

           HR Administrator receives
            work item, reviews data
            and enters the business
           attributes for the org. unit




                  End of Process




Change Organizational Unit Attributes

   1. The Requesting Manager starts the Change Organizational Unit Attributes process.

   2. The Requesting Manager selects an org. unit and goes to the Fill Out Form step.
      Here the Org. ID and abbreviation are displayed at the top of the form.

   3. The Requesting Manager enters the date that the name change is to be effective
      from.

   4. Under Old, the existing org. unit name and description is displayed. The Requesting
      Manager enters the new org. unit name and a description under New. The new org.
      unit name replaces the old one in the system, so that when the process is called up,
      the new name is displayed.

   5. If required, enter a comment in the New Comments field, for example, explaining the
      reason for the name change.

   6. The form is sent to the next role involved in the process, the HR Administrator.

   7. The HR Administrator reviews the data entered by the Requesting Manager and
      enters the new technical attributes for the org. unit.

   8. The HR Administrator enters a comment in the New Comments field, if necessary.
      The HR Administrator checks and sends the form and the changes are saved to the
      master data.

   9. End of process.




HR Administrative Services (PA-AS)         6956                                          293
SAP Online Help                                                                     22.04.2009


Result
The organizational unit attributes have been changed.



       Change Job Name

This process supports the changing of a job name. This is a single-step process. It is started
by the HR Administrator in the HR system. The HR Administrator manually completes the
form, filling in the new job name and a description for the new name.

Prerequisites
To be able to use this sample process for test purposes, you must have performed the
Customizing activities for Personnel Management under HR Administrative Services
  Configuration of Forms/Processes Sample Processes for HCM Processes and Forms                  .

Technical Objects for Implementing and Executing the Process

   Object Type                        ID                                  Name

Process              HR_PD_CHANGE_JOB_NAME                 Change Job Name

Workflow Template None                                     Change Job Name

ISR Scenario         SO06

Interface            ISR_IF_SO06

Form Scenario        S_HR_PD_CHANGE_JOB_NAME               Change Job Name

Form                 ISR_HRASR_SO06

Scenario Steps       STAGE_01

Back-End Services SAP_PD                                   Personnel Development Infotypes




HR Administrative Services (PA-AS)           6956                                           294
SAP Online Help                                                                   22.04.2009


Process




             HR Administrator enters
            new job name, completes
              and sends data to the
                back-end system




                  End of Process




Change Job Name

    1. The HR Administrator starts the Change Job Name process.

    2. The HR Administrator selects a job and goes to the Fill Out Form step. The Job ID
       and abbreviation are displayed at the top of the form.

    3. The HR Administrator enters the date that the name change is to be effective from.

    4. Under Old, the existing job name and description is displayed. The HR Administrator
       enters the new job name and a description under New. The new job name replaces
       the old one in the system.

    5. If required, enter a comment in the comment field, for example, explaining the reason
       for the name change.

    6. End of process.

Result
The job name has been changed, so that the new job name now appears. The master data is
directly updated.



     Change Job Attributes

This process supports the changing of the business attributes of a job. The process consists
of the following steps:



HR Administrative Services (PA-AS)          6956                                           295
SAP Online Help                                                                 22.04.2009


    1. The Requesting Manager enters a new Name and Description for the job and sends
       the request to HR Administrator.

    2. The HR Administrator reviews data entered by manager and enters the new technical
       attributes for the job.

Each role can enter comments using the field New Comments at the bottom of the form. All
comments can be read by the subsequent processors in the field Previous Comments.

Prerequisites
To be able to use this sample process for test purposes, you must have performed the
Customizing activities for Personnel Management under HR Administrative Services
  Configuration of Forms/Processes Sample Processes for HCM Processes and Forms            .

Technical Objects for Implementing and Executing the Process

  Object Type                        ID                                 Name

Process           HR_PD_CHANGE_JOB_ATTRIBUTES               Change Job Attributes

Workflow
                  WS04000037                                Change Job Attributes
Template

ISR Scenario      SO07

Interface         ISR_IF_SO07

                                                            Change Business attributes of
Form Scenario     S_HR_PD_CHANGE_JOB_ATTRIBUTES
                                                            Job

Form              ISR_HRASR_SO07

Scenario Steps    STAGE_01, STAGE_02

Back-End                                                    Personnel Development
                  SAP_PD
Services                                                    Infotypes




HR Administrative Services (PA-AS)         6956                                        296
SAP Online Help                                                                   22.04.2009


Process




             Requesting Manager
           starts the process, enters
                a new job name



                                                     Change attributes
                                                         request

           HR Administrator receives
            work item, reviews data
            and enters the technical
              attributes for the job




                  End of Process




Change Job Attributes

   1. The Requesting Manager starts the Change Job Attributes process.

   2. The Requesting Manager selects a job and goes to the Fill Out Form step. The Job
      ID and abbreviation are displayed at the top of the form.

   3. The Requesting Manager enters the date that the name change is to be effective
      from.

   4. Under Old, the existing job name and description is displayed. The Requesting
      Manager enters the new job name and a description under New. The new job name
      replaces the old one in the system.

   5. If required, enter a comment in the New Comments field, for example, explaining the
      reason for the name change.

   6. The form is sent to the next role involved in the process, the HR Administrator.

   7. The HR Administrator reviews the data entered by the Requesting Manager and
      enters the new technical attributes for the job.

   8. The HR Administrator enters a comment in the New Comments field, if necessary.
      The HR Administrator checks and sends the form and the change is saved to the
      master data.

   9. End of process.

Result
The job attributes have been changed.



HR Administrative Services (PA-AS)         6956                                          297
SAP Online Help                                                                  22.04.2009



   Special Payment (Process Start Without Employee
Selection)

This process supports starting a special payment process without selection of an employee.
The process consists of the following steps:

    1. The requesting manager enters the date of payment and any comments in the New
       Comments field.

    2. The superior manager approves, rejects, or sends back to requester.

    3. The HR Administrator selects and assigns the personnel number using Employee
       Search at the top of the form. He or she enters payment reason and amount, and
       checks and sends the special payment (data is updated in the HR master data).

Prerequisites
To be able to use this sample process for test purposes, you must have performed the
Customizing activities for Personnel Management as described in HR Administrative
Services Configuration of Forms/Processes Sample Processes for HCM Processes and
Forms .

Technical Objects for Implementing and Executing the Process

 Object Type                      ID                                  Name

                                                      Special Payment-3 (XX) (Process
Process           HR_PA_XX_SPECIAL_PAYMENT_3
                                                      Start w/o Pernr)

Workflow                                              Special Payment-3 (XX) (Process
                  WS04000004
Template                                              Start w/o Pernr)

ISR Scenario      SH11

Interface         ISR_IF_SH11

Form Scenario     S_HR_PA_XX_SPAYMENT_3               Special Payment

Form              ISR_HRASR_SH11

Scenario Steps Request, Approve, Process

Back-End
                  SAP_PA                              Personnel Administrator infotypes
Services




HR Administrative Services (PA-AS)         6956                                           298
SAP Online Help                                                                22.04.2009


Process

          Requesting Manager selects
            Skip Employee Selection
              checkbox, starts the
          process, enters the date and
             amount of the payment
                                                    Form can be sent
                                                   back to Requesting
                                                        Manager
              Superior Manager
             approves, rejects, or
           sends back to Requesting
                   Manager



          HR Administrator selects and
          assigns personnel number,
          enters payment reason and
          amount, checks and sends
          requested special payment



                  End of Process




Special Payment

   1. The manager chooses Start Process for Employee in the Portal.

       He or she selects the Skip Employee Selection checkbox. The employee selection
       options are greyed out. The manager chooses Select Process to proceed to the next
       step.

       The manager starts the Special Payment process.

   2. The employee data is not displayed on the screen.

       The requesting manager enters the date for the special payment to be issued, and
       the reason for the special payment in the New Comments field. He or she chooses
       Check and Send to review data, and then Send to submit the form to the superior
       manager.

   3. The superior manager reviews the data entered in the form, and enters a comment in
      the New Comments field if necessary. He or she approves, rejects, or sends the
      forms back to the requesting manager.

   4. If the payment is approved by the superior manger, the HR Administrator receives the
      work item in his or her worklist. The HR Administrator assigns the personnel number
      of the employee using the Employee Search function at the top of the form.

   5. The HR Administrator enters the payment reason and amount of the special payment.
      He or she chooses Send to issue the special payment. The data is updated in the HR
      master data.

   6. End of process.




HR Administrative Services (PA-AS)        6956                                        299
SAP Online Help                                                                        22.04.2009


Result
The payment is updated in the HR master data.



     Country-Specific Processes

In addition to the sample processes, you can also use further country-specific processes.



      Integration of EIC and HCM Processes and Forms
Use
The integration of Employee Interaction Center (EIC) and HCM Processes and Forms (as part
of the HR Administrative Services component), both web-based applications, makes it
possible to support EIC agents and personnel administrators when handling personnel
business processes.
EIC agents can launch and track processes from HCM Processes and Forms directly from the
EIC application. To do this, the EIC agents have access to the process browser [Page 45] .
The can also launch processes or receive and complete work items in their agent inbox as the
processor of process steps.
HR administrators can receive follow-up activities from the EIC and call up activities from the
EIC in their central worklist [Page 45]. They can also launch processes and create work items
in the agent inbox of EIC agents as part of these processes.

Prerequisites
You have switched on the ASR_INT constant in the EIC constant table
THREIC_CONSTANTS. You can adjust this setting in the IMG activity Employee Interaction
Center    Interaction Center Web Client Application Functions    Basic Settings Define
Application Constants.

Features
In activity processing, EIC agents see processes related to an activity in the Processes area.
In order for a user to see a list of all processes that can be launched for an employee in the
process launch application, you can add the no restrictions option to the selection of process
groups for launching a process. You do this in the activity profile. Alternatively, you can set
which processes the system offers for which category or subcategory. To do this, assign
process groups to EIC categories and EIC subcategories in Customizing for the EIC under
Interaction Center Web Client        Application Functions    Activity   Integration with HCM
Processes and Forms        Assign Process Groups to Categories/Subcategories. If you neither
choose the no restrictions option nor assign process groups to categories and subcategories,
then the user cannot launch any processes.
EIC agents and personnel administrators have the following options in the integration of EIC
and HCM Processes and Forms:

      If the owner of an activity cannot directly process the activity him- or herself, then it is
      possible for him/her to create a follow-up activity from the activity. If so, the process for
      follow-up activities [External] is triggered.

      EIC agents can launch and handle pre-defined personnel management processes (for
      example, birth of a child and maternity leave) directly from the EIC application through
      activity processing.



HR Administrative Services (PA-AS)            6956                                             300
SAP Online Help                                                                    22.04.2009


      EIC agents can track launched processes using the EIC application by monitoring
      follow-up activities, responsibilities, and appointments. You can access the process
      browser directly from the EIC application using the navigation bar. This way, you can
      receive information on the process flow.

      EIC agents can open and perform from the EIC inbox either workflow work items that
      they have received via their integration into the process flow or work items that were
      created while handling a process. Forms that need to be processed are displayed
      directly in the EIC application.

      Personnel administrators can call up an activity and launch a process for that activity
      using the follow-up activity in the central worklist. You can also directly change the
      activity (for example, create notes, add contacts, and so on) and change the status of
      the follow-up activity. You can process and forward forms directly on your computer
      screen using SAP Interactive Forms by Adobe [External].
...




   Integration of E-Recruiting and HCM Processes
and Forms
Use
You use this function to integrate the SAP E-Recruiting system with the HR system, using an
SAP NetWeaver Exchange Infrastructure (XI interface) interface.

Features
In SAP E-Recruiting candidates can apply for jobs. A selection process finds the suitable
candidate to hire. You can transfer candidate data on the employment contract from the SAP
E-Recruiting system into the HR system as a request, and process it further.
SAP E-Recruiting differentiates between the following types of applicants:

      Internal candidates: Applicants that are already active employees of the company

      External candidates: Applicants that are not employees, or are not active employees of
      the company
      The following cases are possible:

             The person was already employed in the company, but left the company.
             A personnel number with the employment status Left Company exists in the HR
             system.

             The person was an employee of the company and has retired.
             A personnel number with the employment status Pensioner exists in the HR
             system.

             The person is maintained in the company as “inactive”.
             A personnel number with the employment status Inactive exists in the HR
             system.

             The person was not yet an employee of the company.
             No personnel number exists in the HR system.
Depending on the type of the applicant and the transferred data, the HR Administrator
receives appropriate suggestions for the processing in the HR system.




HR Administrative Services (PA-AS)          6956                                           301
SAP Online Help                                                                      22.04.2009


The data is sent as an XI message to the HR system. The HR Administrator receives the data
as a workflow work item. The processing of the work item is divided into the following steps:

       In the first step, an HR Administrator selects a suitable request and the related
       process, as required.

              If the system does not find any inconsistencies when checking the transmitted
              data, the HR Administrator can directly select a process.

              If inconsistencies occur, the HR Administrator has an additional view. He or she
              can perform the following activities:

                     Select Type of Request
                    The HR Administrator can decide between the following requests:

                            New hire request

                            Rehire request

                            Transfer request

                     Find Employees
                    In the HR system, the HR Administrator can search for a person or
                    personnel number, and select a different personnel number for the
                    process to the personnel number suggested. The system checks whether
                    the combination of selected request type and personnel number is
                    permitted.

                     Reject Message
                    The HR Administrator can specify a reason to reject the request from
                    SAP E-Recruiting.
             When the HR Administrator has determined the required request type and
             personnel number, he or she then selects the appropriate process.

       In the second step, the same, or a different HR Administrator performs the selected
       process.

Activities
You use the XI content that is available for HCM Processes and Forms for the integration. For
more information, see XI Content for HCM Processes and Forms [Page 302].




      XI Content for HCM Processes and Forms
Use
You can use this XI content to integrate SAP E-Recruiting with HCM Processes and Forms.
The XI content is available on SAP Service Marketplace at
service.sap.com/netweaver                     SAP NetWeaver in Detail        Process
Integration. To use the XI content, you must import it into the Integration Repository. For more
information, see SAP Note 836200.
For more information about SAP NetWeaver Exchange Infrastructure, see SAP Help Portal at
help.sap.com           Documentation     SAP NetWeaver   SAP NetWeaver by Key
Capability    Process Integration by Key Capability SAP NetWeaver Exchange
Infrastructure.



HR Administrative Services (PA-AS)             6956                                          302
SAP Online Help                                                                     22.04.2009


Prerequisites
      You have used the SAP NetWeaver Exchange Infrastructure to link the E-Recruiting
      system with the HR system.
      For more information, see the Implementation Guide (IMG) for SAP E-Recruiting and
      choose Recruitment     Applicant Tracking   Activities Set Up Data Transfer for
      New Employees.

      In the ERP system, you have made the settings in Customizing for HR Administrative
      Services under Configuration of Forms/Processes    XI Integration.

Features
XI Content
The following XI content is available for HCM Processes and Forms:

      Integration scenario NewHire [Page 304]
Message interfaces

              HireRequestIn

              HireConfirmationOut

      Message types

              HireRequest

              HireConfirmation

      Interface mapping HireRequest

      Message mapping HireRequest

XI Scenarios
HCM Processes and Forms also use XI scenarios to differentiate further between the
business processes of the HireRequest XI message type.



             The XI scenarios are not part of the XI content in the Integration Repository.
             They are provided with the ERP system.
Depending on the data transmitted, the message type can initiate different processes, for
example, a new hire or rehire. The XI scenario assigns appropriate processes to the
respective business processes. When processing an inbound XI message, the HR
Administrator selects the appropriate one of these processes.
The following XI scenarios are available:

      NEWHIREREQUEST [Page 306]

      REHIREREQUEST [Page 306]

      TRANSFERREQUEST [Page 307]




HR Administrative Services (PA-AS)          6956                                              303
SAP Online Help                                                                         22.04.2009



         NewHire
Purpose
You can use this integration scenario to transfer data from SAP E-Recruiting to HCM
Processes and Forms and initiate processes such as hiring a new employee.

Prerequisites
The NewHire integration scenario is located in the Integration Repository in the software
component SAP HR in the namespace http://sap.com/xi/HR/Global.

Process Flow
The integration scenario consists of the following asynchronous communication steps
between the SAP E-Recruiting system and the HR system:


           Personnel                Recruitment
          Department             SAP E-RECRUITING
           SAP ECC



                                    Hire Request Out




         Hire Request In




        Hire Confirmation
               Out




                                   Hire Confirmation
                                          In



...




      1. Hire Request Out
         In the SAP E-Recruiting system, the recruiter triggers the data transfer for a candidate.
         The data is transferred with the periodic service for the data transfer using XI to the HR
         system.
      2. Hire Request In
            a. The HR system receives the HireRequest XI message and triggers inbound
               processing.
                The system determines the XI scenario involved and creates a process object in
                which the data and attachments received in the XI message are stored.




HR Administrative Services (PA-AS)              6956                                            304
SAP Online Help                                                                     22.04.2009


            The system starts workflow WS17900415 (Start Process for XI Data) that
            contains interactive steps for selecting and starting a process.
        b. With this workflow, an HR Administrator receives a work item with the following
           information in his or her universal worklist (UWL):

                    If inconsistent data is transmitted, a view, in which the HR Administrator
                    must first select the appropriate request type (for example, new hire
                    request or transfer) and if required, the appropriate personnel number

                    A list of possible processes to trigger

                    The attachments received through the XI message and field values of
                    the XI message
                   The HR Administrator receives this information in an Adobe form that is
                   generated by a form scenario specifically created for this purpose, the
                   “form scenario for the XI message type”.
            Based on this data, the HR Administrator selects a process from the list.



            “Inconsistent Data” means, for example:

                            An external candidate with a personnel number with employment
                            status 3 (active) was transferred from the E-Recruiting system.
                            However, a candidate with an active personnel number is an
                            internal candidate. Such a situation can occur, for example, if
                            there were problems with synchronizing the E-Recruiting system
                            with the HR system.

                            No personnel number was transferred from the E-Recruiting
                            system; however there is an employee with the same fist name
                            and date of birth in the HR system.
            If consistent data is transferred and only one process is available, step 2b is
            skipped, and step 2c is performed.
         c. In a second workflow step, either the same or a different HR Administrator
            receives a work item in his or her universal worklist (UWL) for starting the
            process that the HR Administrator selected in the previous step.
            The form fields can be filled with default field values from the XI message. The
            attachments from the XI message can also be available to the HR Administrator.
            This depends on how you configure the data transfer from the form scenario for
            the XI message type to the form scenario of the process to be triggered.
        d. The HR Administrator starts the process. Either the HR Administrator or others
           involved in the process enhance and correct the data transferred from the SAP
           E-Recruiting system as required.
  3. Hire Confirmation Out
     If the HR system creates a new personnel number, it sends confirmation with workflow
     WS17900015 (Follow-Up Activity After Process with XI Scenario) to the SAP E-
     Recruiting system once the process is complete.
  4. Hire Confirmation In
     The SAP E-Recruiting system receives the new personnel number that was created in
     the HR system and assigns it to the external candidate. With the personnel number, the
     external candidate can now be managed as an internal candidate in the E-Recruiting
     system. This prevents the new employee from being created as an internal candidate
     again (although he or she already exists as a candidate in the E-Recruiting system)
     during the next ALE distribution of HR master data from the HR system to the E-
     Recruiting system.


HR Administrative Services (PA-AS)           6956                                             305
SAP Online Help                                                                      22.04.2009




             Steps 3 and 4 are optional. They are only performed if the HR system creates a
             new personnel number.




   New Hire Request from E-Recruiting
(NEWHIREREQUEST)
Use
The system performs this XI scenario if the HireRequest XI message from the SAP E-
Recruiting system does not transfer a personnel number, or transfers an external candidate
with a personnel number with employment status 2 (Pensioner). Meaning that the applicant
does not exist in the HR system as an employee. In this case, the XI message triggers a
process for the new hiring of an employee.

Prerequisites
See XI Content for HCM Processes and Forms [Page 302].

Features
A list of possible processes to trigger is assigned to the XI scenario, using a process group.



             In the standard system, the process group HIRE is assigned to the XI scenario.
             This process group includes the following sample processes:

                            Hiring, Permanent (Germany) [Page 217]

                            Hiring (US) [Page 220]
When the HR Administrator receives the work item from the workflow triggered by the
HireRequest XI message, he or she can select the appropriate process from the processes of
the XI scenario process group. If there is no inconsistent data and the process group contains
only one process, the process selection step is skipped.




   Rehire Request from E-Recruiting
(REHIREREQUEST)
Use
The system performs this XI scenario if the HireRequest XI message from the SAP E-
Recruiting system transfers an external candidate with a personnel number with employment
status 0 (Left Company). Meaning that the applicant used to exist in the HR system as an
employee. In this case, the XI message triggers a process for rehiring the employee.

Prerequisites
See XI Content for HCM Processes and Forms [Page 302].

Features
A list of possible processes to trigger is assigned to the XI scenario, using a process group.



HR Administrative Services (PA-AS)            6956                                           306
SAP Online Help                                                                      22.04.2009




              In the standard system, the process group H001 is assigned to the XI scenario.
              This process group includes the following sample processes:

                             Rehire (Germany) [Page 224]

                             Rehire (US) [Page 228]
When the HR Administrator receives the work item from the workflow triggered by the
HireRequest XI message, he or she can select the appropriate process from the processes of
the XI scenario process group. If there is no inconsistent data and the process group contains
only one process, the process selection step is skipped.




   Transfer Request from E-Recruiting
(TRANSFERREQUEST)
Use
The system performs this XI scenario if the HireRequest XI message from the SAP E-
Recruiting system transfers an external candidate with a personnel number with employment
status 1 (Inactive) or transfers an internal candidate with a personnel number with
employment status 3 (Active). Meaning that the applicant already exists in the HR system as
an employee. In this case, the XI message triggers a process for transferring the employee.

Prerequisites
See XI Content for HCM Processes and Forms [Page 302].

Features
A list of possible processes to trigger is assigned to the XI scenario, using a process group.



              In the standard system, the process group H002 is assigned to the XI scenario.
              This process group comprises the sample process Transfer, Initiated by E-
              Recruiting (International) [Page 236].
When the HR Administrator receives the work item from the workflow triggered by the
HireRequest XI message, he or she can select the appropriate process from the processes of
the XI scenario process group. If there is no inconsistent data and the process group contains
only one process, the process selection step is skipped.




      Tutorial: Create a Process
Purpose
This tutorial describes how you create the Relocation process (see Sample Process for the
Tutorial [Page 310]), including all the related elements such as form scenario, form, workflow
template, and so on, in your test system.

Tutorial Objective
The objective of the tutorial is a process with the following steps:
Business Step        Process Step         Workflow Step        Form Scenario      Remarks


HR Administrative Services (PA-AS)             6956                                          307
SAP Online Help                                                                       22.04.2009


of Process            Processor                                Step
Relocation            Employee            None                 FSS_1 (Request)     Start of workflow;
notification                                                                       this step is
                                                                                   outside of the
                                                                                   actual workflow
Enter relocation      Direct superior     Edit Relocation      FSS_2 (Insert
benefit                                   Form (Superior)      Bonus Data)
Approve or reject     Next higher-level   Approve              FSS_3
relocation benefit    superior            Relocation Form      (Approve/Reject
                                                               Bonus)
Add data to the       Employee            Edit Relocation      FSS_1 (Request)     Optional step –
relocation form                           Form Again                               only if the next
                                          (Employee)                               higher-level
                                                                                   superior has
                                                                                   queries
Check data and        HR Administrator    Edit Relocation      FSS_4
save to back-end                          Form (HR             (Department
system                                    Administrator)       Check)
Send e-mail           System              E-Mail               None
                                          Confirmation to
                                          Employee

Technical Objects of Tutorial
In the course of the tutorial, you create the following objects:
Object Type                        Technical Name                     Name
Process                            ZTPR                               Relocation
Form Scenario                      ZTFS                               Relocation
ISR Scenario                       ZTFS                               Relocation
Form Scenario Steps                FSS_1                              Request
                                   FSS_2                              Insert Bonus Data
                                   FSS_3                              Approve/Reject Bonus
                                   FSS_4                              Department Check
Form                               Z_ISR_FORM_ZTFS
Workflow Template                  ZTWS                               Relocation

Prerequisites
       Units 1 to 3
       In these units you start the process in the HR Administrator portal role, and perform the
       further process steps, as the initiator of the workflow.
       Therefore, your user must be assigned the HR Administrator portal role for your test
       portal.

       Unit 4
       In this unit you consecutively insert the actual processor as the initiator and process
       step processor. Therefore, the following prerequisites must be fulfilled:

                The portal roles Employee Self-Service and Manager Self-Service of your test
                portal are also assigned to your user.


HR Administrative Services (PA-AS)             6956                                              308
SAP Online Help                                                                      22.04.2009


             In Customizing for your test system, your user is assigned to the administrator
             group that you use in the Organizational Assignment (0001) infotype.

Process Flow
Unit 1
...




      Lesson 1.1
      You create a form scenario. In the form scenario, you create the following types of
      fields:

             Mandatory fields that must be created for each form scenario

             Display fields that give the form user information about the employee whose
             data the form changes

             Fields for changing data
      As your process consists of two business steps, create the following form scenario
      steps in the form scenario:

             FSS_1 (Request) for the employee

             FSS_4 (Department Check) for the HR Administrator



             From a technical point of view, each process only needs at least one process
             step.
      In addition, create a form with display fields and the following fields from the Addresses
      (0006) infotype for changing data:

             Street and house number

             Postal code

             City

      Lesson 1.2
      You create a workflow template with a step in which an employee (or for test purposes,
      the workflow initiator) can edit the form.

      Lesson 1.3
      You create a process that is based on this workflow template, and make it (for test
      purposes) available for the HR Administrator in the start application.

      Lesson 1.4
      You check whether the process is consistent.

      Lesson 1.5
      You test the process in the back-end system.

      Lesson 1.6
      You test the process in the portal.

Unit 2
...




      Lesson 2.1




HR Administrative Services (PA-AS)           6956                                           309
SAP Online Help                                                                     22.04.2009


      You enhance the form scenario with the following fields from the Additional Payments
      (0015) infotype:

             Relocation Benefit (default value, not visible)

             Amount

             Currency (default value)
      You also enhance the form scenario with the following form scenario steps:

             FSS_2 (Insert Bonus Data) for the employee’s direct superior

             FSS_3 (Approve/Reject Bonus) for the next higher-level superior

      Lesson 2.2
      You also enhance the form with the fields from the Additional Payments (0015)
      infotype.

      Lesson 2.3
      You enhance the workflow template with an additional step in which the employee’s
      superior (or for test purposes, the workflow initiator) can also edit the form.
      In the workflow step container of this step, you determine that the FSS_2 (Insert Bonus
      Data) form scenario step is used.

      Lesson 2.4
      Using the form scenario steps, you provide the process step processors with various
      links to more extensive information. The processors are also able to insert attachments.

Unit 3
...




      Lessons 3.1 – 3.7
      You enhance the workflow template with an approval loop so that the next higher-level
      superior (or for test purposes, the workflow initiator) receives the form for approval.

Unit 4
...




      Lesson 4.1
      Using the Life & Work Events area of Employee Self-Service, you make the start
      application of the process available for the employee.

      Lesson 4.2
      You replace the workflow initiator, who until now, for test purposes, was the processor
      for all process steps, with the real processor.

      Lesson 4.3
      You set that a confirmation e-mail is sent to the employee after the process is
      completed.




      Sample Process for the Tutorial
Use
Based on the tutorial, you create a process with which an employee can notify the personnel
department of his or her new address after relocating, and simultaneously request a
relocation benefit.


HR Administrative Services (PA-AS)           6956                                          310
SAP Online Help                                                                22.04.2009


The following processors are involved in this process:

      the employee that enters his or her new address

      the employee’s direct superior who takes note of the new address and enters the
      relocation benefit for the employee

      the next higher-level superior who must approve the relocation benefit

      the HR Administrator who updates the changed data in the ERP system

Process Flow
The following image shows the process flow of the Relocation (ZTPR) process:




HR Administrative Services (PA-AS)           6956                                       311
SAP Online Help                                                                        22.04.2009




               Employee starts process and
                    changes address



             Optional

                 Employee receives form
                    again for editing




                 Superior enters relocation
                          benefit




                 Next higher-level superior
                 receives form for approval


             Query                    Rejection


                        Approval


               HR Administrator saves data
                  to back-end system




                  System sends e-mail to
                        employee




                         Process
                        completed
...




      1. In Employee Self-Service, an employee starts the Relocation process, enters his or her
         new address in the form (street and house number, postal code, and city), and chooses
         Send.
      2. The employee's superior sees a new work item in his or her Universal Worklist. He or
         she runs the work item and takes note of the information that the employee entered in
         the form. The superior also enters the relocation benefit for the employee in the form, in
         the Amount field. He or she then chooses Send.




HR Administrative Services (PA-AS)                6956                                         312
SAP Online Help                                                                        22.04.2009


      3. The next higher-level superior sees a new work item in his or her Universal Worklist. He
         or she runs the work item and takes note of the information in the form. The next
         higher-level superior has the following options:

                 He or she approves the relocation benefit.
                 In this case, the process continues with step 4.

                 He or she rejects the relocation benefit
                 In this case, the process is completed.

                 He or she sends a query to the employee.
                 In this case, the employee receives the form again for editing. After making
                 changes, he or she chooses Send. The process then continues with step 2.
      4. The HR Administrator sees a new work item in his or her Universal Worklist. He or she
         runs the work item and takes note of the information in the form. The HR Administrator
         then chooses Send and thereby automatically updates the data from the form in the
         back-end system.
      5. The system sends an e-mail to the employee informing him or her that the address has
         been changed in the system, and that he or she will receive a relocation benefit.
...




          Unit 1: Create Form, Workflow, and Process
Unit Objective
The objective of this unit is a process with the following steps:
Business Step          Process Step         Workflow Step       Form Scenario       Remarks
of Process             Processor                                Step
Relocation             Employee             None                FSS_1 (Request)     Start of workflow;
notification                                                                        this step is
                                                                                    outside of the
                                                                                    actual workflow
Check data and         HR Administrator     Edit Relocation     FSS_4
save to back-end                            Form (HR            (Department
system                                      Administrator)      Check)




  1.1 Configuring a Form Scenario and an ISR
Scenario

A form scenario, together with the related ISR scenario, provides the basis of a form-based
process and configures the interactive form.

In this lesson you will perform the following steps:

           Create the form scenario ZTFS and ISR Scenario ZTFS with the relevant personnel
           and address fields that enable the employee to use a form to inform the system of
           their change of address



HR Administrative Services (PA-AS)               6956                                           313
SAP Online Help                                                                      22.04.2009


        Define and configure fields from infotypes I0001 and I0006 (setting default values and
        input help) and define how the form data is processed in the back-end system

        Generate automatically the accompanying ISR scenario

        View the automatically generated form scenario step

        Check the form consistency

        Create the form for the form scenario.

Procedure
Create the Form Scenario and ISR Scenario with Design Time for
Processes and Forms
    1. Open Design Time for Processes and Forms.

    2. In the object selection area, choose Form Scenario from the dropdown list.

    3. Enter a name for the new form scenario – ZTFS – and choose Enter.

    4. A dialog box appears. Choose Yes to create a new object.

    5. In the Create Form Scenario dialog box, enter the following information:

            o   ISR Scenario: ZTFS

            o   Form: Z_ISR_FORM_ZTFS

            o   Backend Service: SAP_PA


             Note

        The Backend Service textbox should indicate which back-end service is being used in
        this form scenario. You may change the service by selecting from the dropdown list.
        You may also add further back-end services to the form scenario at a later stage.


    6. Choose Continue to confirm your entries.

    7. A dialog box appears asking to create both a form (scenario) and an interface (ISR
       scenario). Choose Yes to create them both.

    8. In the Object Entry Directory dialog box, choose Save to create a local object.

Define and Configure the Relevant Form Scenario Fields
Define the form fields for form scenario ZTFS version 0. This includes the following fields:

        Mandatory fields that you must always create (already provided by the system)

        Display fields that give the user of the form information about the employee whose
        data the form changes, for example data that is part of a form header row

        Specific form scenario fields for changing data

    1. In the object hierarchy area, double-click Fields.




HR Administrative Services (PA-AS)           6956                                              314
SAP Online Help                                                                        22.04.2009


       The object processing area displays the mandatory fields for your form scenario
       required by the back-end system. The fields displayed vary according to which back-
       end service you are using. Here we are using SAP-PA.

   2. Choose Service Fields to add more fields.

       The Transfer Service Fields window appears showing the back-end service in use
       and allowing you to select the infotype and infotype version. Choose the following
       settings. The system automatically displays the correct screen structure fields for the
       selected infotype:

           o      Infotype: 1

           o      Infotype Version: 99 (for International)

           o      Operation: Change

            Note

           o      Screen structure - This is used to display data on the user interface that is
                  derived from the relevant database, but not saved in the database. The data
                  can be input fields, output fields, or descriptive texts. You cannot make
                  assignments to more than one screen structure. Each screen structure
                  contains all infotype fields that are relevant for the user interface.

           o      Version - At least one screen structure exists for each infotype. If the infotype
                  is country-specific, more than one screen structure exists. Select the
                  appropriate version for the country.

           o      Operation - If you want to run the Create, Change, Delete, or Change without
                  Delimiting operations on the InfoObjects, you must provide the data for the
                  new data records to be created. You do this by assigning form fields to
                  InfoObjects. Access to the InfoObjects is enabled by screen structures.


   3. Choose Determine Fields to update the field list in the dialog box and select the fields
      from infotype I0001 in the following table. For each field:

           1. Scroll to the row with the appropriate Name or Service Fld.

           2. Select the corresponding Transfer column checkbox.

           3. Enter a Field Name using the values in the following table.

                  Name              Service Fld              Field Name                 Default Value

       Employee/app Name           ENAME          I0001_EMPLOYEE_NAME              SAP-PA service/Cur

       Personnel Area              WERKS          I0001_PERSA_TEXT                 SAP-PA service/Cur

       Position                    PLANS          I0001_POSITION                   SAP-PA service/Cur

   4. Choose Continue to transfer the selected fields to your form scenario.

       The display area now shows the added form fields.

   5. Add the default values for infotype I0001 fields in the above table. For each field,
      proceed as follows:

           0. Double-click the Default Value cell.


HR Administrative Services (PA-AS)             6956                                            315
SAP Online Help                                                                     22.04.2009


              1. From the Change Default Value Determination dialog box, select the Origin of
                 Default Value =SAP-PA radio button.

              2. In the Type of Default Value column, choose Cur(rent) from the dropdown
                 list.

              3. Save your entries.

   6. Select the fields from infotype I0006 (Addresses). These are form scenario specific
      fields allowing the employee to change data.

              0. Choose the Service Fields button.

              1. Choose the following settings:

                          Infotype: I0006

                          Version: 99

                          Subtype: 1 (for permanent addresses)

                          Operations: Change


                              Note

                          The Operations text box defines how the form data is processed in
                          the back-end system when the automatic save is executed. An
                          operation must be selected if you want to modify the infotype record
                          in the database. The SAP_PA back-end service enables data
                          records of Personnel Administration infotypes to be created,
                          changed, and deleted. The operation ‘change’ causes the back-end
                          service to copy the last infotype record and override any data with
                          the data from the form scenario


              2. Choose Determine Fields to display the infotype I0006 fields.

   7. Select the Infotype I0006 fields in the following table. For each field, proceed as
      follows:

              0. Scroll to the appropriate Name or Service Fld.

              1. Select the corresponding Transfer column checkbox.

              2. Enter a Field Name using the values in the following table.

                Name             Service Fld               Field Name                 Default Value

       Street                STRAS                I0006_STREET                   <blank>

       Postal Code           PSTLZ                I0006_POST_CODE                <blank>

       City                  ORT01                I0006_CITY                     <blank>

       Country Key           LAND1                I0006_COUNTRY                  DE

   8. Choose Continue to transfer the selected fields to your form scenario. The display
      area now shows the added form fields.

   9. Add the default value for Country.


HR Administrative Services (PA-AS)             6956                                         316
SAP Online Help                                                                     22.04.2009


            0. Double-click the Default Value cell of the Country row.

            1. From the Change Default Value Determination dialog box, select the Origin of
               Default Value =Manually radio button. Enter DE.

            2. Save your entries.

    10. Choose Save on the main toolbar to save the form scenario and automatically
        generate the ISR Scenario. The system reads the form fields of the linked form
        scenario and automatically creates all required form fields (characteristics) in the ISR
        scenario. The form scenario and ISR Scenario are now synchronized. If you enhance
        the form scenario at a later date and add new fields, you must then synchronize again
        by saving the form scenario in the described way.

View the Automatically Generated Form Scenario Step
    1. In the object hierarchy area, double-click Scenario Steps. A default scenario step is
       visible.

    2. Add the following scenario steps under the existing default scenario step:

                     Scenario Step                                        Name

        FSS_1                                          Request

        FSS_4                                          Department Check

    3. Save your entries. Notice that your new scenario steps have the same column
       settings as the default scenario step.

    4. Delete the default scenario step.

    5. Save your entries.


    Note

Scenario steps allow you to define specific Customizing for process steps. This Customizing
affects the use of certain fields, the processing of attachments, and the availability of
hyperlinks. For these settings to come into effect when the process is run, you must also
define which scenario step to use in the appropriate workflow step. When defining the
process, you define which scenario step is used to start the process under Creating a
Process. A form scenario must have at least one scenario step. Only one form in your form
scenario means that your form looks the same in all process steps. Note that all fields are
assigned to this step automatically.



Check the Form Scenario Consistency
Check the following settings for the form scenario:

        Definition of the form scenario

        Definition of the linked ISR scenario

        Definition of the back-end service used in the form scenario

    1. In the object hierarchy area, double-click your form scenario (the root of the
       hierarchy). The Check icon appears on the main toolbar.

    2. Choose Check.


HR Administrative Services (PA-AS)              6956                                        317
SAP Online Help                                                                      22.04.2009


    3. Process any error messages and warnings that are displayed in the Status Bar.


    Note

The results of these checks are displayed in the status bar, providing information, error
messages, or warnings. Incorrect settings should be corrected to enable the form scenario to
run properly.



Create the Form for your Form Scenario
    1. In the object hierarchy area, double-click Form. The form, the ISR Scenario, and the
       interface were created when you created the form scenario at the beginning of this
       tutorial. When you save the form scenario, the ISR Scenario and the Interface are
       updated.

    2. Choose Change Form. The Adobe LiveCycle Designer Form Builder opens, ready for
       you to create your form.

Result
You have now created the form scenario, the form scenario steps, the ISR Scenario, and the
interface as well as a form for entering the necessary data. You have checked that the form
scenario is consistent and you are now ready to use the form scenario in a workflow step.



      1.1.1 Creating a Form and Editing the Layout
Use
For the Relocation process, the employee needs a form in which their changed address
details can be entered. This interactive form is created using the Form Builder.
For basic information about working with Adobe LiveCycle Designer, see the Layout tab in the
menu, under Help       Adobe Designer Help.
For specific information about creating an interactive form, see Creating and Editing
Interactive Forms [Page 50].



Activities
You perform the following steps:
      You add the ISR-Form-Wide Scripts Control Element to the form. This element hides
      Adobe menu bars and ensures that the form fields cannot be edited once the form has
      been checked after processing.

      You check you are using the correct libraries. The ISR Native Control library should be
      available but it might be necessary to add a new library. Libraries are visible on the
      right-hand side of the screen. For more information, see Creating and Editing
      Interactive Forms.

      You add a header to the form.

      You add fields to the form that are bound to fields in the back-end service.

      You add fields to the form for displaying and processing agent notes (“Comments”.

      You add a date field.




HR Administrative Services (PA-AS)           6956                                          318
SAP Online Help                                                                    22.04.2009


          You add the Update Data pushbutton that updates the data in the form according to
          the selected date.

          You bind the form fields to the form scenario.

          You activate the form.

          You display a preview of the form.


Use the following template to create the form for this tutorial:



        Request Relocation Benefit
        With this form you may request a removal bonus. In addition,
        you may enter your new address details.

         Personnel Number

         Employee Name

         Position

         Personnel Area



         Effective Date                             Update Data

         Please enter your new address:

         Street

         Postal Code

         City

         Country            DE



         Previous Comments




         New Comments




Procedure

Creating a Form
When you save your form scenario, a form is automatically created.
...




      1. Open your form scenario in Design Time for Processes and Forms.
      2. In the object hierarchy area, double-click Form.
      3. Choose Change Form.


Adding the ISR Form-Wide Scripts Control Element
...




From the Utilities menu, choose Insert Web Dynpro Script. In the object hierarchy area, you
can now see a new element, Container Foundation_JS.


HR Administrative Services (PA-AS)                      6956                              319
SAP Online Help                                                                         22.04.2009




Adding Libraries (Optional Step)
To add a new library:
...




      1. In the object hierarchy area, choose Data View to return to the form layout.
      2. Right-click on an existing tab in the Library window.
      3. From the context menu, choose Add Group.
      4. Enter a name for the library to be included (this name appears on the tab).
      5. Browse to the folder in which the library is stored and choose OK to see the library
         elements appear in your new tab.
      6. For this tutorial, return to the ISR Native Library tab.


Adding Fields to the Form
...




      1. Add the Header to the Form:
             a. In the library, select the ISR Header field and drag and drop it on to the form.
             b. Enter the following text: Request Relocation Benefit.
             c. Save your entries.
      2. Add some general information about this form for the employee:
             a. Drag and drop an ISR Static Text field on to the form.
             b. Enter the following text: With this form, you may request a removal
                bonus. In addition, you may enter your new address details.
      3. The employee requires information telling them exactly what to do:
            a. Drag and drop an ISR Static Text field on to the form and enter the following:
               Please enter your new address.
      4. Now add the data fields in the following table. Some fields are display-only fields, other
         fields are used to collect information from the employee. For each of the form fields,
         complete the following steps:
             a. From the library tab, drag and drop the appropriate ISR Control Element on to
                the form.
             b. Label the control element according to the following table.

                     Duplicate a control element, once it is on the form, by selecting it and
                 pressing CTRL+D. Delete a control element from a form by selecting it and
                 pressing DEL.

                    Country requires an ISR Text Display control element because the
                 employee does not enter data here.

                     Even though you did not transfer the Comments fields to your form scenario,
                 they have been automatically added to the Data View tab. A Hidden Bound
                 Text Field is used to monitor an unbound form data node when it is modified
                 during scripting.


Form Fields and Related ISR Control Elements
Field Name (Data View tab)            Label                              ISR Control Element



HR Administrative Services (PA-AS)                6956                                             320
SAP Online Help                                                                           22.04.2009


I0001_PERNR                           Personnel Number                   ISR Text Display
I0001_EMPLOYEE_NAME                   Name                               ISR Text Display
I0001_POSITION                        Position                           ISR Text Display
I0001_PERSA_TEXT                      Personnel Area                     ISR Text Display
I0006_STREET                          Street and House Number            ISR Text Edit
I0006_POST_CODE                       Postal Code                        ISR Text Edit
I0006_CITY                            City                               ISR Text Edit
I0006_COUNTRY                         Country                            ISR Text Display
HRASR_CURRENT_NOTE                    Current Comments                   ISR Multiple Line (Edit)
HRASR_PREVIOUS_NOTE                   Previous Comments                  ISR Multiple Line (Edit)
<Blank>                               <Blank>                            Hidden Bound Text Field


Adding an Effective Date Field
The form requires a field for Effective Date.
...




      1. Drag and drop an ISR DateField control element on to the form.
      2. Label it Effective Date.

                      It is possible that the employee may add a future date in the Effective Date
                 field. Data and default values might then be no longer valid for this date. To
                 allow the user to update the displayed data, as it is stored in the Infotype at the
                 effective date, you can add a pushbutton. The pushbutton for initializing the
                 entire form resets the form to its initial status. The field Effective Date is not
                 reset. The script behind the pushbutton should be changed.


Creating a Pushbutton for Updating Data
A pushbutton is required for the Effective Date field.
...




      1. Drag and drop an ISR On-Form Event button on to the form.
      2. Label it Update Data.
      3. From the Pallets menu, choose Script Editor. The script relating to the pushbutton is
         now selected:
          $record.CONTROL_PARAM.ISR_EVENT = “CUSTOM_EVENT”
      4. Replace CUSTOM_EVENT with USER_EVENT_INITIALIZE
      5. Close the Script Editor.
      6. Save your entries.


Binding the Form Fields to the Form Scenario
The fields on the form must now be bound to the fields in the form scenario (and therefore
automatically to the ISR scenario):
...




      1. Choose the Data View tab to display the form scenario fields. Each field has a DATA
         element and a FIELD element.




HR Administrative Services (PA-AS)               6956                                               321
SAP Online Help                                                                        22.04.2009


      2. Drag and drop the FIELD element of each field on to the corresponding field on the
         form. In the Data View tab, an icon appears to the right of the FIELD element to show
         that it has been bound to a field on the form.
      3. Choose Don´t update any related properties in the Binding Properties dialog box.


Palettes – An Alternative Method of Binding Fields
Palettes offer an alternative method of binding form fields to the form scenario.
      4. Choose Palettes on the Layout menu bar and select Object. A new Object tab appears
         in the bottom right window.
      5. Choose the Binding tab. The Binding tab shows whether the field is bound to a form
         scenario field. To bind the field, click the arrow of the Default Binding text box and
         select the appropriate form scenario, field name and field element.
      6. Select a field on the form.
      7. Choose Don´t update any related properties in the Binding Properties dialog box.


Activating the Form
You must now activate the form. This creates or updates the form object and the interface
that is created for the form.
...




      1. Choose the Activate Form button on the Form Builder menu bar.
      2. In the Inactive Objects dialog box, select both objects (Form and ISR) for transfer.
      3. Choose Continue to activate the form and form scenario.


Displaying a Form Preview
Preview the form by clicking the PDF Preview tab. If you then need to amend your form,
return to the Body Pages tab.

Result
You have created the form with all the necessary fields for entering the change of address.
Once you have activated the form and the interface, the form can be processed further.



   1.2 Creating a Workflow Template with the
Process Form Workflow Step
Use
In this lesson, you first create a blank workflow template, ZTWS, for the form scenario ZTFS,
and make the necessary settings for this workflow template.
You then insert a workflow step with the Process Form standard task into the workflow
template, and make the necessary settings for this workflow step. With this workflow step, the
HR Administrator (or for test purposes, the workflow initiator) checks and saves the data that
the employee (or you, as the workflow initiator) enters in the form at the start of the process.

Procedure
This lesson is divided into the following sublessons:

Preparation
...




HR Administrative Services (PA-AS)               6956                                             322
SAP Online Help                                                                     22.04.2009


          Lesson 1.2.1: Retrieving Task Groups for HCM Processes and Forms

Creating a Workflow Template
          Lesson 1.2.2: Creating a Workflow Template

          Lesson 1.2.3: Creating a Container Element for the Process Object

          Lesson 1.2.4: Defining a Triggering Event for the Workflow

          Lesson 1.2.5: Defining the Programming Exit at the Workflow Template Level

          Lesson 1.2.6: Activating the Start Event and Setting Up Type Linkage for the Process

Inserting a Workflow Step
          Lesson 1.2.7: Adding the Process Form Workflow Step in the Workflow Template for
          the HR Administrator

          Lesson 1.2.8: Refining the Process Form Workflow Step in Detail for the HR
          Administrator

Reprocessing Workflow Templates
          Lesson 1.2.9: Determining the Form Scenario in the Workflow Container
See also:
Business Workflow for HCM Processes and Forms [Page 60]




   1.2.1 Retrieving Task Groups for HCM Processes
and Forms
Use
In this part lesson, you copy the task groups, workflow templates, and standard tasks that are
part of HCM Processes and Forms, into the Workflow Builder.

Procedure
...




      1. Access transaction SWDD, or choose Tools   Business Workflow         Development
         Definition Tools  Workflow Builder  Workflow Builder.
          The initial screen of the Workflow Builder appears.
      2. Choose the entry My Workflows and Tasks from the selection box on the bottom left.
      3. Click on the entry <New Search Range>.
      4. Choose the Task Group tab page.
      5. Enter the task group TG17900001 and choose Continue.




...
          1.2.2 Creating a Workflow Template
      1. Open the Workflow Builder.
      2. Choose Create New Workflow.



HR Administrative Services (PA-AS)              6956                                        323
SAP Online Help                                                                        22.04.2009


      3. Choose Basic Data and enter the following:

          Abbreviation: ZTWS

          Description: Relocation
          You can search your workflow template later using these entries.
      4. Save the workflow template as a local object.
          The system assigns a WS* technical identification number to the workflow template.
          You can see this number and the workflow template status in the Information Area.



Result
You have now created a workflow template.



   1.2.3 Creating a Container Element for the Process
Object
Use
In this part lesson, you specify the process object in the workflow container so that it can
exchange data with your workflow template while the process is running.



                 When an employee starts a process in the portal, the start application creates a
                 process object. The process object triggers the event TRIGGERED for class
                 CL_HRASR00_WF_PROCESS_OBJECT in the back-end system. This event
                 starts the workflow.

Procedure
...




      1. Open the workflow container for your workflow template. To do this, display the
         Workflow Container menu bar.
          The system displays the elements of the workflow container. The standard elements of
          the container are identified in gray.
      2. Create a new entry. To do this, double-click Double-Click to Create.
      3. Enter PROCESS_OBJECT in the Element field of the dialog box.



                 Enter the text exactly as written above, in the same uppercase format. This
                 format is required by the system for your process to run correctly.
      4. Enter the following Name and Short Description:

          Name: POBJ

          Short Description: Process object
      5. Specify the data type for the container element. To do this, choose the Data Type tab
         page and enter the following values for the Object Type indicator:

          ABAP Class

          CL_HRASR00_WF_PROCESS_OBJECT




HR Administrative Services (PA-AS)              6956                                           324
SAP Online Help                                                                          22.04.2009


      6. Specify the properties of the container element. To do this, choose the Properties tab
         page and select the Import indicator in the Parameter Settings area.
      7. Choose Apply and save your workflow template.



Result
The process object is specified in the workflow container for data exchange.



          1.2.4 Defining a Triggering Event for the Workflow
Use
In this lesson, you specify that the workflow template must be started by the event
TRIGGERED from class CL_HRASR00_WF_PROCESS_OBJECT.

Procedure
...




      1. Choose Basic Data for your workflow template, if it is not already displayed.
      2. Choose the Version-INdependent (Task) tab page.
      3. Choose the Start Events tab page.
      4. Enter the object type category CL.
      5. Enter the object type CL_HRASR00_WF_PROCESS_OBJECT.
      6. In the Event of the Object field, select the TRIGGERED entry.
      7. Specify the data flow. To do this, choose the pushbutton in the Binding column.
          The Change Binding for Workflow dialog box appears.
      8. Choose Exit Binding Editor.
          You return to the maintenance screen for basic data. The pushbutton in the Binding
          column now has the status Binding (Existing).
      9. Save your workflow template.

Result
You have defined the triggering event for the workflow and specified the data flow between
the event container and the workflow container. The start event symbol is now displayed in
the Graphical Model area.



                 You must set up the type linkage in the relevant production client so that the
                 workflow template can react to the event (see the lesson Activating the Start
                 Event and Setting up Type Linkage for the Process [Page 326]).




   1.2.5 Defining the Programming Exit at the
Workflow Template Level
Use
In this lesson, you define a programming exit for your workflow template so that the system
can ensure communication between the workflow and the process object.


HR Administrative Services (PA-AS)               6956                                             325
SAP Online Help                                                                                    22.04.2009


Procedure
...




      1. Choose Basic Data for your workflow template, if it is not already displayed.
      2. Choose the Version-Dependent (Current Workflow Version) tab page.
      3. Choose the Programm Exits tab page.
      4. Enter the class CL_HRASR00_POBJ_WF_EXIT in the Programm Exits (are called
         in the Displayed Order) area.
      5. Check the entry.
          To do this, choose Enter and check if the interface IF_SWF_IFS_WORKITEM_EXIT
          in the Implemented Interfaces area is displayed as implemented. Implemented
          interfaces are indicated by a green icon.
      6. Save your workflow template.

Result
The following graphic shows what the tab page looks like after inserting the programming exit:
        Version-INdependent (Task)        Version-Dependent (Current Workflow Version)


           Reviewer     Notifications         WebFlow       Events          Local Events     Programming Exits    Charac…




       Programming Exits (Accessed in the Displayed Sequence)
         Text Class
               CL_HRASR00_POBJ_WF_EXIT




       Implemented Interfaces
            Interface Name                      Description
             IF_SWF_IFS_WF_CONSTRUCTOR          Called When A Workflow Instance Is Created
            IF_SWF_IFS_WORKITEM_EXIT
            IF_SWF_IFS_WF_CONSTRUCTOR           Called When A Workflow Instance Is Created




   1.2.6 Activating the Start Event and Setting Up
Type Linkage for the Process
Use
If a user starts a process in the portal using the start application, he or she fills out a form and
sends it to the next processor. The start application creates a process object and saves the
data that the user entered to the process object. The process object triggers the event
TRIGGERED for class CL_HRASR00_WF_PROCESS_OBJECT.
This part lesson enables the workflow template ZTWS to react to this event in the system
client in which it is used.




HR Administrative Services (PA-AS)                        6956                                              326
SAP Online Help                                                                     22.04.2009



                 You must perform the type linkage in all clients in which you want to use
             your workflow template.

Prerequisites
      You have set up the standard settings and basic settings for the SAP Business
      Workflow. For more information, see the Implementation Guide for SAP NetWeaver, by
      choosing Application Server   Business Management         SAP Business Workflow.

      You have defined the triggering event for the workflow. For more information, see the
      Defining a Triggering Event for the Workflow [Page 325] lesson.

Procedure
Activating the start event
  7. Open your workflow template in the required client.
  8. Choose Basic Data if it is not already displayed.
  9. Choose the Version-INdependent (Task) tab page.
10. Choose the Start Events tab page.
11. Activate the type linkage.
      Do this by clicking on the symbol in the Active column in the line in which you specified
      class CL_HRASR00_WF_PROCESS_OBJECT.
      The symbol changes its shape to a square and its color to green.
12. Save your entries.
13. Choose Back and activate your workflow template.

Defining type linkage
14. Choose transaction SWETYPV (Define Event Type Linkage), or from the SAP Easy
    Access screen, choose Tools Business Workflow     Development       Definition
    Tools   Events Event Linkages    Type Linkages.
15. Select the following entry:
Object Category          Object Type                Event                   Receiver Type
ABAP class               CL_HRASR00_WF_P            TRIGGERED               <technical ID (WS*) of
                         ROCESS_OBJECT                                      your workflow
                                                                            template>
16. Choose Details.
17. Enter HR_ASR_CHECK_EVENT in the Check Function Module field.

                It is easier to enter the check function module HR_ASR_CHECK_EVENT
             manually, rather than select it from the dropdown list.
18. Leave the default settings in the other fields.
19. Save your entries.




HR Administrative Services (PA-AS)           6956                                            327
SAP Online Help                                                                        22.04.2009



    1.2.7 Adding Process Form W/F Step (HR Admin)
to W/F Template
Use
In this sublesson, you add a workflow step with the Process Form standard task to your
workflow template ZTWS.

Procedure
...




      1. Display the Graphical Model area in the Workflow Builder.
      2. Open the standard tasks for HCM Processes and Forms. To do this, display the My
         Workflows and Tasks menu bar.
      3. Choose Components for HCM Processes and Forms.
      4. Choose Task Groups.
      5. Choose TG17900002 (Interactive Components in HR ASR Dir.).
      6. Click and drag TS17900100 (Process Form) onto the Graphical Model area (the mouse
         pointer changes to a plus symbol (+) to show you where you can insert the step) just in
         front of the undefined step.
      7. Delete the Undefined template step by right-clicking the icon and selecting Delete.
      8. Save your workflow template.

Result
You have included a new step in your workflow template. Consequently the system has
placed new elements in the workflow container. The system automatically added these new
elements when you included the Process Form standard task in the workflow template. These
are the elements that are indicated as import or export elements in the standard task
container.
You can check the new elements in the Workflow Container by choosing the Workflow
Container menu bar.




   1.2.8: Defining Process Form W/F Step (HR
Administrator)
Use
In this lesson, you make the necessary settings for the new workflow step for processing the
relocation form in your workflow template ZTWS.

                     The procedure described below shows you an example of how to determine
                 the workflow initiator as the processor and how to determine constants.
                 Step 3 shows you how to determine the processor.
                 Step 5 shows how you access the input helps for constants. As an alternative to
                 this procedure, you can also directly enter the value for the constant instead of
                 using the input help.

Procedure
...




HR Administrative Services (PA-AS)              6956                                           328
SAP Online Help                                                                      22.04.2009


  1. Double-click the new Process Form icon in the Graphical Model area to display the
     Process Form workflow step details.
  2. Choose the Control tab. Overwrite the system-provided Step Name with the following
     text: Edit Relocation Form (Administrator)
  3. Define the agent determination for the step. Enter the workflow initiator as the
     processor so that you, as the processor that started the workflow, can also run the
     Process Form workflow step.
         a. In the Agents area, choose Workflow Initiator (Expression) as Agent type. For
            this processor type, the system automatically defines the entry
            &_WF_INITIATOR&.
  4. Choose Transfer and To Graphic.
  5. Choose Basic Data. In the Description field, re-enter Relocation. Save your entries.
  6. Determine the data flow between the workflow container and the workflow step
     container.To do this, choose the Binding(Exists) pushbutton. The Change Binding for
     Step dialog box appears. In the Binding ‘Relocation’ Workflow    Step’Process Form’
     area, in the ‘Relocation’ Workflow column, make the following settings:



             The Binding ‘Relocation’ Workflow    Step ’Process Form’ area of this dialog
             box shows the automatically generated definitions for data flow between the
             workflow container and the workflow step container (in both directions). The
             system automatically generated these definitions when you included the
             Process Form task in your workflow template.


         a. Ensure that the data in the infotypes is saved to the back-end system in this
            workflow step:
                i.    In the ‘Relocation’ Workflow column, click the drop-down list in the
                      &SEND_VARIATION& row. The Select Expression dialog box appears,
                      listing the container elements of the workflow template.
                ii.   Choose the Enter Constant pushbutton. The system extends the dialog
                      box to display fields for constants.
               iii.   From the dropdown list in the Constant field, select A (Write Data to
                      Application Database). Choose Continue. A (Write Data to Application
                      Database) now appears in the ‘Relocation’ Workflow column.
         b. Determine the form scenario to use.
                i.    In the ‘Relocation’ Workflow column, click the dropdown list in the
                      &FORM& row. The Select Expression dialog box appears.
                ii.   Choose the Enter Constant pushbutton on the dialog box toolbar. The
                      system extends the dialog box to display fields for the (Form) Scenario
                      and (Form Scenario) Version.
               iii.   Select the following values:

                             Form scenario: ZTFS

                             Version:     0000
               iv.    Choose Continue. The details for the form scenario now appear in the
                      ‘Relocation’ Workflow column.
         c. Determine the form scenario step to use.




HR Administrative Services (PA-AS)            6956                                            329
SAP Online Help                                                                             22.04.2009


                 i.    In the ‘Relocation’ Workflow column, click the drop-down list in the
                       &FORM_SCENARIO_STAGE& row. The Select Expression dialog box
                       appears.
                ii.    Choose the Enter Constant pushbutton. The system extends the dialog
                       box to display fields for the form scenario and its steps.
                iii.   Using the dropdown lists in these fields, select the form scenario ZTFS,
                       the version 0000 and form scenario step FSS_4.
                iv.    Choose Continue. The details for the form scenario step now appear in
                       the ‘Relocation’ Workflow column.
         d.
              The following graphic shows the Data Flow: ‘Relocation’ Workflow -> Step
              ‘Process Form’ area after the last step:


                  Data Flow: 'Relocation' Workflow -> Step 'Edit Form'
                  'Relocation' Workflow                                  Step 'Edit Form'



                  FSS_4




         e. Choose the Exit Binding Editor button.
  7. Determine the interaction between the workflow step and the process object.
         a. Navigate from the Control tab to the Programm Exits tab.
         b. Choose the Class menu bar and select the class
            CL_HRASR00_POBJ_WF_EXIT.
         c. Choose Transfer and to Graphic to return to the Graphic Model.
  8. Save your entries.
  9. Choose Generate and Activate Run-Time Version to activate your workflow template.
10.

Result
You have now completed all workflow step-specific settings Your workflow template now
resembles the following graphic:




HR Administrative Services (PA-AS)                      6956                                      330
SAP Online Help                                                                        22.04.2009




                                                 Workflow
                                                 started




                      Edit relocation form
                      (administrator)


          Step completed



                           Workflow
                           completed




                 The first process step in which the employee starts the process is outside of the
                 workflow and is therefore not represented in this graphic. The Edit Relocation
                 Form (Administrator) step that the graphic shows as the first step is the second
                 step of the process.
See also:
Standard Task TS17900100: Edit Form [Page 73]




   1.2.9 Determining the Form Scenario in the
Workflow Container
Use
In this lesson, you determine the form scenario that you want to use for the entire workflow
template. Use the workflow container element FORM.



                 We recommend that you always enter the form scenario in the workflow
                 container, as described in this lesson. The information is then available for the
                 entire workflow, through the form scenario, even if a form scenario is not defined
                 for one of the workflow steps.
                 In addition, you can enter the form scenario in the workflow step container, as
                 described in the previous lesson. If you do this, the workflow uses the step-
                 specific form scenario for this step, and not the form scenario from the workflow
                 container.

Procedure
...




      1. In the object hierarchy area, display the Workflow Container menu bar.
      2. Double-click the container element Form. The Change Container Element dialog box
         appears. The Data Type tab contains the ABAP Dictionary Data Type
         HRASR00_FORM_KEY_ELEMENT for this element.




HR Administrative Services (PA-AS)              6956                                           331
SAP Online Help                                                                           22.04.2009


      3. Determine the form scenario and its characteristics that you want to use by selecting
         the Initial Value tab. In the relevant fields, select the ZTFS form scenario and version
         ZTFS. The dropdown lists contain all form scenarios that you have defined in
         Customizing or that are part of the standard system.



                 The system does not display the entry 00000 - it displays an empty field.



                 Leave the Do Not Save field empty. Here you do not need the Do Not Save
                 field; you use the field if you implement more than one form scenario in a
                 workflow template.
      4. Choose Confirm and save your entries.
      5. Choose Transfer and Go To Graphic and activate your workflow template.




          1.3 Creating a Process
Use
In this lesson you create process ZTPR. This connects the workflow template and the form
scenario that you created in the previous lessons. You make the necessary settings for
process ZTPR in Customizing for HR Administrative Services, by choosing Configuration of
Forms/Processes        Design Time for Processes and Forms.



Prerequisites
          You have created the form scenario and ISR scenario ZTFS.

          The ISR interface and the form were automatically created.

          You have created the form layout.

          You have created workflow template ZTWS.

Procedure
...




Define the Process
      1. Open Design Time for Processes and Forms.
      2. In the object selection area, select Process.
      3. Enter ZTPR as the technical name for the process. In addition to the technical process
         name, you can enter a longer process description which is later displayed in the start
         application.
      4. Choose ENTER. Choose Yes to create the new process.
      5. In the Create Process dialog box, enter Relocation as the Process Description. The
         process name is later displayed in the start application and in the process browser.
      6. Specify the Validity Period (in which the process is actually visible in the start
         application).
      7. Select the form scenario ZTFS.
      8. Ensure that HR Administrator is selected as the Initiator Role.



HR Administrative Services (PA-AS)                6956                                          3