How-to Guide

How To Prepare your SAP ERP for Duets Leave Management Scenario
Version 1.00 June 2007 Applicable Release: Duet v1.0 SP3

1 of 33

Copyright Copyright 2007 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, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries, pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, Informix, i5/OS, POWER, POWER5, OpenPower and PowerPC are trademarks or registered trademarks of IBM Corporation. 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. MaxDB is a trademark of MySQL AB, Sweden. SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver, and other SAP products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned 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 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.

2 of 33

Contents Introduction ...................................................................................................................................................... 4 Prerequisites .................................................................................................................................................... 4 ESS Configuration for Leave Management ..................................................................................................... 5 Duet Setup ..................................................................................................................................................... 11 Leave Management ................................................................................................................................... 11 RFC Destination ..................................................................................................................................... 11 Logical Port............................................................................................................................................. 13 Role Management ...................................................................................................................................... 15 RFC Destination ..................................................................................................................................... 15 Logical Port............................................................................................................................................. 17 Releasing Service Definitions of Enterprise SOA ...................................................................................... 18 Duet Leave Management Reports ............................................................................................................. 20 Schedule Notification Report .................................................................................................................. 20 Database Clean-Up Report .................................................................................................................... 26

3 of 33

Introduction
The purpose of this guide is to provide information on the prerequisites, ESS configuration and setup in the ERP system for the Duet Leave Management scenario.

Prerequisites
In order to use the Duet Leave Management scenario, the HCM Time Management core configuration must have been completed. The configurations required include work schedules, absences and quotas. 1. To review the configuration for work schedules go to transaction SPRO and follow the IMG Path Time Management Work Schedules.

2. To review the configuration for absences, go to transaction SPRO and follow the IMG Path Time Management Time Data Recording and Administration Absences Absence Catalog.

4 of 33

3. To review the configuration for quotas go to transaction SPRO and follow the IMG Path Time Management Time Data Recording and Administration Managing Time Accounts Using Attendance/Absence Quotas.

ESS Configuration for Leave Management

In addition to the prerequisite configurations outlined above, configuration is also required for Employee Self-Service. 4. Go to transaction SPRO and follow the IMG Path Personnel Management Employee Self Services. 5. Alternatively, you can go to transaction PTARQ, select the Customizing button, and follow the IMG Path Employee SelfService Service-Specific Settings Working Time Leave Request.

NOTE: If the Employee Self-Service node is not available in the IMG, this may be due to the inactivation of the EA-HR Extension Set. To activate the Extension Set, follow the IMG Path SAP Customizing Implementation Guide Activation Switch for SAP R/3 Enterprise Extension Set. Activate the EA-HR extension set.

5 of 33

6. The first step in the customization is to create rule groups and assign the rules to the employees (using the WEBMO feature). 7. Select Create Rule Groups on the pop-up screen to continue.

8. In this step you create rule groups based on the requirements for different customizing settings for Leave Management. FOR EXAMPLE: Managers and executives are not eligible for some absence types that are available to the standard group. Executives do not require approval for absences 9. Save the rules and navigate back to the Choose Activity pop-up screen 10. Select Adjust WEBMO Feature on the popup screen to continue.

6 of 33

11. Using WEBMO feature you can assign employees to rule groups based on organizational or personnel criteria such as Employee Group/Subgroup 12. In the screenshot, a decision has been made on the employee group/subgroup allowing different rule groups to be assigned to managers and executives. This will allow configuration of absences to be handled differently based on the type of employee. 13. Save the feature and activate to continue.

14. The next step is Define Processing Processes for Each Rule Group. In this step you can define different processes for each of the groups defined.

7 of 33

15. The next step is Specify Processing Processes for Types of Leaves. In this step, the types of leaves to be considered are defined for each rule group. 16. Select the rule group/leave and double-click to see the detailed customizations.

17. For rule group 00000001 and absence type 0100 Vacation, the setting for the processing process is Use Workflow, Approval Required and the workflow task has been assigned. NOTE: Standard workflow WS12300111 can be used as delivered or as a basis for you own customer-specific workflow.

8 of 33

18. For rule group 00000003, the processing process setting is Without Workflow, Approval Not Required. 19. Since Executives have been assigned to rule group 00000003 (through WEBMO feature) they will not require approval when entering Vacation.

20. The next step is Specify Display of Absences and Default Values. This defines how you want to display absences in the Web application. 21. Customization in this step can differ for each rule group specified.

9 of 33

22. The next step is Specify Display of Absence Quotas. This defines which absence quotas are to be displayed, what sequence are they to be displayed in, and which entitlements are to be taken into consideration. 23. In addition to the rule group previously defined, customization in this area is also dependent on the ESG (Employee Subgroup Grouping) and PSGrp (Personnel Subarea Grouping) for Time Quotas. To review these groupings go to transaction SPRO and follow the IMG path Time Management Time Data Recording and Administration Managing Time Accounts Using Attendance/Absence Quotas Setting Groupings for Time Quotas. 24. Select the checkbox Display Un-transferred Quotas to allow both existing entitlements and as accrual entitlements to be displayed (accrual entitlements are entitlements that have not yet been transferred to the Absence Quota IT2006). 25. Select the checkbox Total Absence Quota Type to allow multiple quota records (IT2006) of the same type to be cumulated and display as a total value. 26. As with the previous customizing steps different rules can be applied for each rule group. FOR EXAMPLE: Executives do not accrue quotas for overtime or floating holiday, therefore rule group 00000003 does not require an entry for these quotas.

10 of 33

Duet Setup
Once you have completed the installation of the Leave Management business application, you must configure the ERP environment to allow the business application to send and retrieve the requested data.

Leave Management
RFC Destination
The Leave Management scenario requires an external service RFC destination which enables connectivity between the ERP system and the SAP Web Application Server Java system where you have deployed the SAP Duet Java Add-On 1. Go to transaction SM59 and click Create. 2. On the proposed RFC Destination screen, enter the RFC Destination (e.g. CONNECT_LEAVE) and Connection Type G (HTTP Connection to External Server). 3. Document the RFC by entering a short description in the Description area. 4. Press ENTER for additional fields.

11 of 33

5. Select the Technical Settings tab and enter the following: Target Host: Enter the IP address of the SAP Duet Java Add-On host. Service No.: Enter the port number of the SAP Duet Java Add-On host. Path Prefix: Enter
/WorkFlowIHWS/Config1?style=document

6. Select the Logon/Security tab and select the Logon Procedure No Logon and Send SAP Logon Ticket. 7. Save and test the RFC Destination.

12 of 33

Logical Port
The purpose of the Logical Port is to expose the workflow proxy classes in the ERP system to the SAP Duet Java Add-On components by leveraging the RFC destination that was previously created. 1. Go to transaction LPCONFIG 2. From the Proxy Class dropdown choose /OSP/CO_WORK_FLOW_IHWSVI_DOCUM 3. Enter a name for the Logical Port (e.g. DUET_LEAVE_LP). 4. Click Create.

5. Enter a description for the Logical Port and select the Default Port checkbox. 6. On the Call Parameters tab select the HTTP Connection radio button, and using the dropdown select the RFC Destination previously defined for Leave Management. 7. Save the Logical Port.

13 of 33

8. After saving the Logical Port the Activate icon appears. 9. Activate the Logical Port to complete the process.

14 of 33

Role Management
RFC Destination
The Leave Management scenario requires an RFC Destination and Logical Port to be set up for Role Management. Unlike Leave Management the RFC Destination for Role Management enables connectivity between the SAP ERP system and the SAP Web Application Server Java system in which you have deployed the SAP Duet Server components. 1. Go to transaction SM59 and click Create. 2. On the proposed RFC Destination screen enter the RFC Destination (e.g. CONNECT_ROLE_MANAGEMENT) and Connection Type G (HTTP Connection to External Server). 3. Document the RFC by entering a short description in the Description area. 4. Press ENTER to display additional fields.

15 of 33

5. Select the Technical Settings tab and enter the following: Target Host: Enter the IP address of the SAP Duet Server host. Service No.: Enter the port number of the SAP Duet Server host. Path Prefix: Enter /RMWrapper/Config1?style=document

6. Select the Logon/Security tab and select the Logon Procedure No Logon and Send SAP Logon Ticket. 7. Save and test the RFC Destination.

16 of 33

Logical Port
You must create a Logical Port for the RFC Destination. The purpose of the Logical Port is to expose the workflow proxy classes in the ERP system to the SAP Duet Java Server components by leveraging the RFC destination that was previously created. 1. Go to transaction LPCONFIG. 2. From the Proxy Class dropdown choose /OSP/CO_RMWRAPPER_VI_DOCUMENT. 3. Enter a name for the Logical Port (e.g. DUET_ROLEMGMT_LP. 4. Choose Create.

5. Enter a description for the Logical Port and select the Default Port checkbox. 6. On the Call Parameters tab select the HTTP Connection radio button, and using the dropdown select the RFC Destination previously defined for Role Management. 7. Save the Logical Port.

17 of 33

8. After saving the Logical Port the Activate icon appears. 9. Activate the Logical Port to complete the process.

Releasing Service Definitions of Enterprise SOA

You must release the service definitions of Enterprise Service-Oriented Architecture (Enterprise SOA) services in the ERP system for SOAP runtime. This allows you to activate the services in the system. The services that you release have default values that should not be modified. 1. Go to transaction WSCONFIG. 2. In the Web Service Definition field, enter the name of the service or choose the service from the dropdown list. (For ERP 2005, enter the same service definition in the Variant field.) 3. Select the Create icon.

18 of 33

4. Specify the virtual host, URL and the details of the internet communication framework if necessary. 5. Save the changes.

6. Once the Web Service has been saved, it will appear in the list of Web Services released for the SOAP runtime. 7. Go to the Duet for Microsoft Office and SAP; SAP Administration Guide for a complete list of all Web Services that are to be released. Repeat steps 2 through 5 for each of the Web Services listed.

19 of 33

Duet Leave Management Reports

Duet delivers two standard reports for the administration of the Leave Management scenario. These reports must be scheduled as periodic jobs in the ERP system. If the Leave Management business application was previously customized for Duet Preview 1.0, then the following reports must be un-scheduled. /OSP/WORKFLOW_SCHEDULER /OSP/WF_LEAVE_BKT_CLEANUP

Schedule Notification Report

The Leave Scheduler report is used to process leave request notifications and is recommended that it be scheduled to run every 15 minutes. 1. Go to transaction SM36 and select the Job Wizard icon.

20 of 33

2. The job wizard will guide you through the job setup. 3. Click Continue.

4. Enter a name for the scheduled job in the Job Name field. (e.g. Leave Scheduler). 5. Click Continue.

21 of 33

6. Ensure that the ABAP program step radio button is selected and click Continue.

7. Enter /OSP/NOTIF_LEAVE_SCHEDULE in the ABAP program name field. 8. For this job a variant is not required. 9. Click on Continue.

22 of 33

10. Click Continue.

11. The Leave Scheduler should be scheduled to run every 15 minutes. 12. To set the scheduled time, select the Date/Time radio button and click on Continue.

23 of 33

13. On this screen enter the date and time for the first run of this program. 14. Select the Period checkbox and click Continue.

15. Select the None of the above radio button and click on the Other Periods button.

24 of 33

16. On the Other Period Definition pop-up enter the job period (e.g. 15 minutes) and click Create. 17. On the Job Periodicity screen click Continue.

18. The Leave Scheduler has now been successfully defined. 19. Click Complete to end the process.

25 of 33

Database Clean-Up Report

Duet uses a book-keeping table that enables it to track mails and tasks already delivered to users. Over time, the table increases in volume and size. In order to maintain the volume and size of the table the database clean-up reports should periodically be run. 1. Go to transaction SE38, in the program name enter /OSP/MEND_LM_CLEANUP, and select the Execute icon.

2. In the table name field enter /OSP/T_IH_NOTIFS. 3. Enter the number of days that defines the age of records to be deleted (e.g. 90 days). 4. Click the Save icon to save the entries in a Variant. 5. Enter a Variant Name (e.g. T_IH_NOTIFS) and a short description, then click the Save icon to save the variant. 6. This Variant can now be used when scheduling the Database Cleanup Report.

26 of 33

7. Go to transaction SE38, enter /OSP/MEND_LM_CLEANUP in the program name, and select the Execute icon

8. Enter /OSP/T_MEND_LR in the name of table field. 9. Enter the number of days that defines the age of records to be deleted (e.g. 90 days). 10. Choose the Save icon to save the entries in a Variant. 11. Enter a Variant Name (e.g. T_MEND_LR) and a short description and then choose the Save icon to save the variant. 12. This Variant can now be used when scheduling the Database Cleanup Report.

27 of 33

13. Go to transaction SM36 and select the Job Wizard icon.

14. The Job Wizard will guide you through the job setup. 15. Select Continue.

28 of 33

16. In the Job Name field, enter a name for the scheduled job (e.g. /OSP/T_IH_NOTIFS). 17. Click Continue.

18. Ensure that the ABAP program step radio button is selected and click Continue.

29 of 33

19. Enter /OSP/MEND_LM_CLEANUP in the ABAP program name field. 20. In the Variant field use the dropdown list to select the correct variant for the job that is scheduled (e.g. Job /OSP/T_IH_NOTIFS with variant T_IH_NOTIFS). 21. Click Continue.

22. Click Continue.

30 of 33

23. The Data Base Cleanup should be scheduled to run periodically (e.g. every 90 days). 24. To set the scheduled time select the Date/Time radio button and click Continue.

25. On this screen enter the date and time for the first run of this program. 26. Select the Period checkbox and click Continue.

31 of 33

27. Select the None of the above radio button and click on the Other Periods button.

28. On the Other Period Definition pop-up, enter the job period (e.g. 90 days) and click Create. 29. Click on Continue on the Job Periodicity screen.

32 of 33

30. The Data Base Cleanup for variant T_IH_NOTIFS has now been successfully defined. 31. Click Complete to end the process 32. Repeat steps 13 through 31 for the variant T_MEND_LR with the following changes:
Job Name in step 16 to /OSP/T_MEND_LR Variant in step 20 to T_MEND_LR

33 of 33