leave of absence (loa) administration sap best practices for public sector (canada)
TRANSCRIPT
Leave of Absence (LOA) Administration
SAP Best Practices for Public Sector(Canada)
© SAP 2008 / Page 2
Scenario Overview – 1
Purpose This scenario describes the typical process used when employees take leaves
of absence (LOA).
Benefits Employee records are kept in real time alignment, so payroll is timely and
accurate. Automated, efficient processing with complete history of employee’s
transactions.
Key process flows covered LOA Administration
Purpose and Benefits:
© SAP 2008 / Page 3
Scenario Overview – 2
Required SAP Enhancement Package 3 for SAP ERP 6.0
Enterprise roles involved in process flows Manager Employee HR Administrator
SAP Applications Required:
© SAP 2008 / Page 4
Scenario Overview – 3
LOA Processing
LOA – Active Status action is executed Employee is granted a paid LOA Event is added to employee’s master record
LOA – Inactive Status 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
Detailed Process Description:
© SAP 2008 / Page 5
Scenario Overview – 4
LOA Processing, cont’d
Return from LOA – Inactive Status is executed Employee returns from LOA Event is added to employee’s master record
Detailed Process Description:
© SAP 2008 / Page 6
Process Flow DiagramLeave of Absence (LOA) Administration
Legend – Please see next page
© SAP 2008 / Page 7
Legend
Symbol Description Usage Comments
Band: Identifies a user role, such as Accounts Payable Clerk or Sales Representative. This band can also identify an organization unit or group, rather than a specific role.
The other process flow symbols in this table go into these rows. You have as many rows as required to cover all of the roles in the scenario.
Role band contains tasks common to that role.
External Events: Contains events that start or end the scenario, or influence the course of events in the scenario.
Flow line (solid): Line indicates the normal sequence of steps and direction of flow in the scenario.Flow line (dashed): Line indicates flow to infrequently-used or conditional tasks in a scenario. Line can also lead to documents involved in the process flow.
Connects two tasks in a scenario process or a non-step event
Business Activity / Event: Identifies an action that either leads into or out of the scenario, or an outside Process that happens during the scenario
Does not correspond to a task step in the document
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
Process Reference: If the scenario references another scenario in total, put the scenario number and name here.
Corresponds to a task step in the document
Sub-Process Reference: If the scenario references another scenario in part, put the scenario number, name, and the step numbers from that scenario here
Corresponds to a task step in the document
Process Decision: Identifies a decision / branching point, signifying a choice to be made by the end user. Lines represent different choices emerging from different parts of the diamond.
Does not usually correspond to a task step in the document; Reflects a choice to be made after step execution
Symbol Description Usage Comments
To next / From last Diagram: Leads to the next / previous page of the Diagram
Flow chart continues on the next / previous page
Hardcopy / Document: Identifies a printed document, report, or form
Does not correspond to a task step in a document; instead, it is used to reflect a document generated by a task step; this shape does not have any outgoing flow lines
Financial Actuals: Indicates a financial posting document
Does not correspond to a task step in a document; instead, it is used to reflect a document generated by a task step; this shape does not have any outgoing flow lines
Budget Planning: Indicates a budget planning document
Does not correspond to a task step in a document; instead, it is used to reflect a document generated by a task step; this shape does not have any outgoing flow lines
Manual Process: Covers a task that is manually done
Does not generally correspond to a task step in a document; instead, it is used to reflect a task that is manually performed, such as unloading a truck in the warehouse, which affects the process flow.
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, this shape reflects data coming from an external source; this step does not have any incoming flow lines
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; instead it is used to reflect an automatic decision by the system that is made after a step has been executed.
<Fun
ctio
n>E
xter
nal t
o S
AP
Business Activity /
Event
Unit Process
Process Reference
Sub-Process
Reference
Process
Decision
Diagram Connection
Hardcopy / Document
Financial Actuals
Budget Planning
Manual Proces
s
Existing Version /
Data
System Pass/F
ail Decisio
n