4 Scenario Overview – 3 Detailed Process Description: Payroll ProcessingRun PayrollAfter all employee master data changes are entered into the system for the relevant payroll period, the payroll is released in order to execute and run payroll for the pay period selected. If any errors occur, they must be corrected before you can exit the payroll. Prior to exiting payroll, a simulation of the third party remittance and finance posting is recommended.DME ActivitiesOnce payroll has been run without errors, the Pre- data medium exchange (DME) program is run for all employees in order to execute a bank transfer or check payment. The DME – Payment workbench is run for employees who have elected to be paid using direct bank transfer. For employees who are paid by check, the Check payment program will need to be executed.See template 577_Scenario_Oververview.zipTemplate Pool  SAP Best Practices Documentation Templates  577_Scenario_Overview.zipSample data are to be deleted and replaced (red entries)

5 Scenario Overview – 4 Detailed Process Description:Subsequent Payroll ActivitiesThird Party Remittance ProcessingThis business process allows you to complete three major tasks related to the final processing of a payroll run. They are:Posting financial data to the appropriate G/L and subledger accounts in FI and CO.Generating bank transfer and check payments to third parties, such as tax authorities and benefits providersReconciling payments made in FI with payables data stored in HR.

6 Scenario Overview – 5 Detailed Process Description:Subsequent ProcessingPosting to FI activitiesThe payroll results contain information that is relevant for Accounting. For this reason, they must be evaluated for posting to Accounting. The Posting to Accounting component performs this task. It is the interface between Payroll and Accounting. It helps to:Group together posting-relevant information from the payroll resultsCreate summarized documentsPerform the relevant postings in the Accounting componentsPayroll ReportingIn order to facilitate reconciliation of payroll payments various reports can be run such as the wage type reporter, payroll journal, garnishments report, and the payroll reconciliation report

7 Process Flow Diagram Off-Cycle ProcessingSee template 577_Scenario_Oververview.zipTemplate Pool  SAP Best Practices Documentation Templates  577_Scenario_Overview.zipThis slide is optional.Since the process flow diagram is later required in development process (scenario overview), it can reuse some effort in development, if the diagram ist created in blueprint/specification phase.The diagram visualizes the process flows and is a great tool to discuss the process with the stakeholders.Legend – Please see next page

8 Legend Symbol Description Usage Comments Symbol DescriptionBand: 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 eventBusiness Activity / Event: Identifies an action that either leads into or out of the scenario, or an outside Process that happens during the scenarioDoes not correspond to a task step in the documentUnit Process: Identifies a task that is covered in a step-by-step manner in the scenarioCorresponds to a task step in the documentProcess Reference: If the scenario references another scenario in total, put the scenario number and name here.Sub-Process Reference: If the scenario references another scenario in part, put the scenario number, name, and the step numbers from that scenario hereProcess 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 executionSymbolDescriptionUsage CommentsTo next / From last Diagram: Leads to the next / previous page of the DiagramFlow chart continues on the next / previous pageHardcopy / Document: Identifies a printed document, report, or formDoes 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 linesFinancial Actuals: Indicates a financial posting documentBudget Planning: Indicates a budget planning documentManual Process: Covers a task that is manually doneDoes 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 processDoes 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 linesSystem Pass / Fail Decision: This block covers an automatic decision made by the softwareDoes 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.Diagram Connection<Function>Hardcopy / DocumentExternal to SAPFinancial ActualsBusiness Activity / EventBudget PlanningUnit ProcessManual ProcessProcess ReferenceExisting Version / DataSub-Process ReferenceProcess DecisionSystem Pass/Fail Decision