Leave Of Absence (LOA) Processing (568

)
SAP Best Practices

efficient processing with complete history of employee’s transactions. Benefits  Employee records are kept in real time alignment.  Automated.Purpose. All rights reserved. so payroll is timely and accurate. and Key Process Steps Purpose  This scenario describes the typical process used when employees take leaves of absence (LOA). Key Process Steps  LOA Administration © 2011 SAP AG. 2 . Benefits.

3 .0 Enterprise roles involved in process flows  Manager  Employee  HR Administrator © 2011 SAP AG.Required SAP Applications and Company Roles Required SAP Applications  SAP enhancement package 5 for SAP ERP 6. All rights reserved.

All rights reserved. 4 .Detailed Process Description LOA Processing LOA –Paid action is executed – Employee is granted a paid LOA – Event is added to employee’s master record LOA – Unpaid action is executed – Employee is granted an unpaid LOA – Event is added to employee’s master record Return from LOA – Active Status is executed – Employee returns from LOA – Event is added to employee’s master record © 2011 SAP AG.

5 . All rights reserved.Process Flow Diagram LOA Processing Triggering Event SAP ERP Reporting for HCM (559) FMLA Processing (578) Benefits Administration (575) Payroll and Post Payroll Processing (566) Workforce Time Entry (564) Manager Manager Approval Employee Employe e Request for LOA Employee Notification of Return Date or Termination Is Employee Resigning ? No Yes Employee Terminations (569) Active Status during Leave? No LOA – Unpaid Action HR Administrator Yes New Hire / Rehire Administratio n (563) LOA –Paid Action Maintain Monitoring of Tasks Return from LOA © 2011 SAP AG.

Does not usually correspond to a task step in the document. or influence the course of events in the scenario. it is used to reflect a document generated by a task step. which affects the process flow. 6 . this shape does not have any outgoing flow lines Flow line (solid): Line indicates the normal sequence of steps and direction of flow in the scenario. it is used to reflect a document generated by a task step. instead. rather than a specific role. instead. Corresponds to a task step in the document Manual Process SubProcess Reference Sub-Process Reference: If the scenario references another scenario in part. All rights reserved. Flow line (dashed): Line indicates flow to infrequently-used or conditional tasks in a scenario. this step does not have any incoming flow lines Process Decision Process Decision: Identifies a decision / branching point. report. this shape does not have any outgoing flow lines Unit Process Unit Process: Identifies a task that is covered in a step-by-step manner in the scenario Corresponds to a task step in the document Manual Process: Covers a task that is manually done Does not generally correspond to a task step in a document. You have as many rows as required to cover all of the roles in the scenario. put the scenario number and name here. instead it is used to reflect an automatic decision by the system that is made after a step has been executed. put the scenario number. name. or an outside Process that happens during the scenario Connects two tasks in a scenario process or a non-step event Financial Actuals: Indicates a financial posting document Financial Actuals Does not correspond to a task step in a document. and the step numbers from that scenario here Corresponds to a task step in the document Existing Version / Data Existing Version / Data: This block covers data that feeds in from an external process Does not generally correspond to a task step in a document. instead. Symbol Description To next / From last Diagram: Leads to the next / previous page of the Diagram Usage Comments Flow chart continues on the next / previous page <Function> Diagram Connection Hardcopy / Document: Identifies a printed document. Reflects a choice to be made after step execution System Pass/Fail Decision System Pass / Fail Decision: This block covers an automatic decision made by the software Does not generally correspond to a task step in the document. Business Activity / Event: Identifies an action that either leads into or out of the scenario. instead. © 2011 SAP AG. The other process flow symbols in this table go into these rows. External Events: Contains events that start or end the scenario. This band can also identify an organization unit or group. Process Reference Process Reference: If the scenario references another scenario in total. Line can also lead to documents involved in the process flow. Usage Comments Role band contains tasks common to that role. this shape does not have any outgoing flow lines Business Activity / Event Does not correspond to a task step in the document Budget Planning: Indicates a budget planning document Budget Planning Does not correspond to a task step in a document. such as Accounts Payable Clerk or Sales Representative.Legend Symbol Description Band: Identifies a user role. this shape reflects data coming from an external source. Lines represent different choices emerging from different parts of the diamond. signifying a choice to be made by the end user. such as unloading a truck in the warehouse. it is used to reflect a document generated by a task step. or form External to SAP Hardcopy / Document Does not correspond to a task step in a document. it is used to reflect a task that is manually performed. instead.

Inc. The information in this document is proprietary to SAP. Please note that this document is subject to change and may be changed by SAP at any time without notice. OS/390. SAP does not warrant the accuracy or completeness of the information. z/VM. System z. R/3. Data contained in this document serves informational purposes only. This limitation shall not apply in cases of intent or gross negligence. Some software products marketed by SAP AG and its distributors contain proprietary software components of other software vendors. Massachusetts Institute of Technology. Xcelsius. i5/OS. links. No part of this document may be reproduced. PowerPC. This document contains only intended strategies. System z9. Linux is the registered trademark of Linus Torvalds in the U. iSeries. PostScript. Business Objects and the Business Objects logo. POWER5. Adobe. Redbooks. and MultiWin are trademarks or registered trademarks of Citrix Systems. Sybase 365. copied. and PowerPoint are registered trademarks of Microsoft Corporation. System p5. Excel. HACMP. ByDesign. IBM. System Storage. and/or development. Business Objects is an SAP company. 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.S. World Wide Web Consortium. This document is provided without a warranty of any kind. iAnywhere. Windows. Crystal Decisions. HTML. All rights reserved. SAP BusinessObjects Explorer. Citrix. and other Business Objects products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Business Objects Software Ltd. The statutory liability for personal injury and defective products is not affected. either express or implied. AS/400. Parallel Sysplex. Intelligent Miner. StreamWork. OSF/1. Duet. All other product and service names mentioned are the trademarks of their respective companies. Microsoft. ICA. BladeCenter. BusinessObjects. and other Sybase products and services mentioned herein as well as their respective logos are trademarks or registered trademarks of Sybase. and other countries. This document is a preliminary version and not subject to your license agreement or any other agreement with SAP. WebSphere. developments. POWER5+. Sybase and Adaptive Server. UNIX. xSeries. PowerVM. Outlook. System p. S/390. OpenPower. Netfinity. POWER6+. AIX. including but not limited to the implied warranties of merchantability. 7 . PartnerEdge. and Motif are registered trademarks of the Open Group. z9. POWER6. BatchPipes. System z10. eServer. Oracle and Java are registered trademarks of Oracle Corporation. z/OS. National product specifications may vary. SQL Anywhere. System i5. graphics. S/390 Parallel Enterprise Server. SAP shall have no liability for damages of any kind including without limitation direct. Inc. XML.© 2011 SAP AG. DB2. Tivoli and Informix are trademarks or registered trademarks of IBM Corporation. Web Intelligence. Program Neighborhood. X/Open. RACF. or other items contained within this material. or transmitted in any form or for any purpose without the express prior written permission of SAP AG. SAP assumes no responsibility for errors or omissions in this document. product strategy. zSeries. and Reader are either trademarks or registered trademarks of Adobe Systems Incorporated in the United States and/or other countries. The information contained herein may be changed without prior notice. SAP. Crystal Reports. the Adobe logo. special. and functionalities of the SAP® product and is not intended to be binding upon SAP to any particular course of business. pSeries. GPFS. RETAIN. VideoFrame. SAP NetWeaver. or non-infringement. Power Architecture. fitness for a particular purpose. System i. © 2011 SAP AG. XHTML and W3C are trademarks or registered trademarks of W3C®. SAP HANA. 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. Acrobat. OS/400. WinFrame. POWER. Sybase is an SAP company. text. MetaFrame. or consequential damages that may result from the use of these materials. OS/2. DB2 Universal Database. System x. DB2 Connect. z10. MVS/ESA. SAP has no control over the information that you may access through the use of hot links contained in these materials and does not endorse your use of third-party Web pages nor provide any warranty whatsoever relating to third-party Web pages. indirect.

Sign up to vote on this title
UsefulNot useful