Tell us what you think

We want to create the best possible experience for our learners. Your feedback helps us to improve the experience for everyone.

Running and Validating Continuous Payroll with PCC

Objective

After completing this lesson, you will be able to run and validate Continuous Payroll with PCC

A Continuous Payroll Process Run

Payroll Process Managers will have a process for pre-payroll activities that will run prior to running a live production payroll. In this lesson, you’ll learn the steps to complete these processes .

Pre-Payroll Activities

The image shows the four activities of a continuous payroll run. Step 1 - Create Test Payroll Data, Step 2 - Posting Simulation, Step 3 - Initiate Policy, Step 4 - Monitoring Process

A Continuous Payroll Process consists of various activities, which each have a specific function. These pre-payroll activities are run from the My Processes user interface. There are four steps to the pre-payroll process, summarized below:

Create Test Payroll Data
Posting Simulation
Initiate Policies
Monitoring

Next, let’s go into more depth to learn about how to complete each step.

Create Test Payroll Data: Step 1

During this step, test payroll results are created to be used for KPIs and payroll alerts.

General View

This is the first step of the process when the test payroll results will be created. If necessary, the Payroll Process Manager can select the See Details option.

The image shows the overview screen for step 1, create test payroll data.

Details Screen

This image shows that step 1 is complete. On this screen you're able to check the status, and when you select the job name, you can see the payroll log.

Payroll Log

This is the payroll log where you can see details of the payroll. An example of this would be how many employees were calculated successfully or rejected.

Step 2: Posting Simulation

During this step, test payroll results are posted to FI/CO in the simulation mode.

Posting Simulation Details Screen

From the details screen, you can access the posting run log which will show you details and statistics from the posting simulation.

The image shows the payroll log for posting simulation

Step 3: Initiate Policies

As you initiate policies, you will see your validation rules come to life as they are implemented in the process. During this step, predefined payroll alerts are checked against test payroll data. Also, KPI information is filled from test payroll data during this step.

Here is where you can see the status of the policy validation. Once you get the payroll results, you can run a validation of test results or test payroll posting run. After checking the validation rules assigned to the policies, then the system can start generating KPIs.

The image shows the overview screen for step 3, initiate policy

Initiate Policy Details Screen

This image shows the details where you can observe in real time how the system can run the rule validation. Each line shows the execution log for each validation rule or KPI.

The image shows the details screen for step 3, initiate policy

Initiate Policy - Team Alert Assignment Log

This is the log of the execution of the KPIs and validation rules. Here you can see the list. If you select each of these steps, you can see the execution log.

The image shows the payroll log of initiate policy.

Step 4: Monitoring

During this step, the Payroll Manager is given a user interface to view payroll alerts identified and KPI data.

What is the Monitoring Process?

The monitoring process is an important aspect of continuous payroll that allows users to check calculations and accuracy of payroll-relevant data and posting configuration as needed. Think of the monitoring process like a payroll "draft" or pre-payroll which means you can repeat all or parts of the process.

As such, the monitoring process is the final step. This process is essentially a visual representation of the results from the previous steps. In the Monitoring tab, you can see alerts, KPIs, and other details on the screen.

Alerts and Teams

The payroll process manager can assign alerts to the different processors or start the alert handling process for different teams. Notice that there are 12 different alerts. If you select the link "Team Assignment" you can jump to the next screen.

Note

Assigning a processor to the alert and handling the alert is possible only before the process is confirmed. Process status Confirmed means that all activities associated with this process are completed. Choose the Confirm button when the processing of alerts is fully completed.

Option Confirm makes impossible to assign alerts. The Payroll Process Manager can only confirm this step when all activities with this process are completed. All issues must be solved prior to confirming.

Team Assignments

The Payroll Process Manager can check which alerts were created for each of the teams. This is the alert criteria for the different teams (Team A and Team B). You can view more details that show the exact alerts assigned to each team.

The image shows two screens with assigning alerts to two teams

Start/Pause All

The team lead will be able to find and assign a team member to handle alerts only after the manager chooses the Start All button. If the manager decides that the handling of alerts should be paused, they must choose the Pause All button on that page.

The image shows the option to start or pause the monitoring process.

Business Example

This practice shows how to run the team monitoring process

ExerciseStart Exercise

Run the Team Monitoring Payroll Process

Business Example

As Payroll Process Manager, you need to start and complete the Team Monitoring process to detect issues with master data and simulation payroll data as early as possible. You will check alert assignments to teams and start alert processing. You can monitor the alert resolution process online via PCC My Processes application. You can also re-run the Team Monitoring payroll process at any time before productive payroll as many times as necessary to ensure all master data and payroll issues are resolved on time. Then a productive payroll will be run with the fewest issues or alerts.

Steps

Call PCC My Processes Application.
1. Open the Payroll Process Manager favorite folder.
2. Click on the PCC My Processes (Manager) application.
3. To log into the front end of the training system, provide the username HRH65-## and password Welcome1. (You already used the same username and password to log into the training system.)
Open the folder Upcoming processes, choose and start Z## HRH65 Team Monitoring Process.
1. Choose Upcoming Processes.
2. Start process Z## HRH65 Team Monitoring Process by choosing the Start Process button.
  This process disappears from the list of upcoming processes. It is now displayed on the Active Processes tab.
On Active Processes, note that you start the first out of 4 process steps, Create Test Payroll data, automatically when you select the Z## HRH65 Team Monitoring Process. Now, all 4 steps that are included in the process are displayed. When a step is performed, background jobs are created; when the step is completed, you can display the spool of the corresponding jobs. For the first step, Create Test Payroll data; you can now display the payroll log by choosing See details.
1. Choose Active Processes. The first step of the process is automatically started.
2. Choose the Z## HRH65 Team Monitoring Process.
  This opens a view with tabs for all four processes:
  - Create test payroll data.
  - Posting simulation.
  - Initiate policy (new).
  - Monitoring.
  Note
  When a step is performed, background jobs are created, and when the step is completed, you can display the spool of the corresponding jobs. For example, for the first step, you can see the payroll log by choosing See details.
3. For step Create test payroll data, choose the Refresh icon. Step Create Test Payroll Data has been finished successfully.
4. Choose See details.
5. As there are no entries on the Messages tab, choose Program details.
6. Choose 00001/Simulation Payroll Run. The log file for this simulation payroll run is displayed.
7. Choose the Back button to return to the Process Steps overview.
When the first step is finished successfully, the second step, Posting Simulation, is automatically started. For this step, a new job is created in the back-end system. You can display the log of each job created. After successfully finishing the second step, Posting Simulation, the third step, Initiate Policy (New), is automatically executed. Here, all validation rules included into the policy of this process are evaluated.
1. Choose the Refresh icon. Step Posting Simulation has been finished successfully.
2. Choose See details.
3. As there are no entries on the Messages tab, choose Program details.
4. Choose the Back button and the Simulate Posting log is displayed.
5. Choose Back and on the Posting Simulation screen, choose Display Posting Document.
6. The Display Posting Document log is displayed.
7. Choose the Back button twice to return to the Process Steps overview.
After the step Initiate Policy (New) is completed, you can ensure that all validation rules assigned to both policies are displayed, and they are finished. All KPIs assigned to Analytics were executed successfully. All generated alerts were assigned to the Team A.
1. Choose the Refresh icon. Step Initiate Policy (New) has been finished successfully.
2. Choose See details.
3. Choose Program details.
4. Choose 00001/EXECUTE CHECK INSTANCES job and ensure that all validation rules assigned to both policies are displayed, and they are finished.
5. Choose the Back button to come back to the Process Step Details screen.
6. Choose FILTER ALERTS RESULTS and ensure that this job was executed for all validation rules assigned to both policies successfully.
7. Choose the Back button to come back to the Process Step Details screen.
8. Choose 00001/EXECUTE KPI INSTANCES job and ensure that all KPIs assigned to Analytics were executed successfully.
9. Choose the Back button to come back to the Process Step Details screen.
10. Choose SYNC. TEAM ALERTS ASSIGNMENT and ensure that all generated alerts were assigned to the Team A.
11. Choose the Back button twice to return to the Process Steps overview.
After the step Initiate Policy (New) is completed, the last step Monitoring can be executed by choosing the Start button. Two alerts are generated, and they are assigned to Team A according to the criteria defined in Manage Team functionality.
1. You can see what kind of alerts are generated by clicking on the team:
  Z##_HRH65 - C026 - Employees with Gross pay over the threshold amount (5000 EUR)
  Z30_HRH65_C018 - Employee with missing cost center
2. Choose the Back button and return to the Z## HRH65 Team Monitoring Process screen.
3. On this page, besides the Alert section, other useful sections are displayed, for example the KPI sections such as the Employee Count Analysis, Payroll Analysis. All this information creates complete visibility for Payroll Process Manager around the payroll process. For example, you can find out how many new hires there are in a certain period.
  Note
  In case the system does not show progress at this stage of the exercise, you might need to refresh your browser window.
4. Choose Back to return to the Process Steps screen for Z## HRH65 Team Monitoring Process.
Choose Team Assignment link and start alerts processing.
1. Click on the link Team Assignment in the Alerts section.
2. Choose the Start All button in the lower right corner of the Manage Teams screen.
3. Choose the Back button and return to the Z## HRH65 Team Monitoring Process screen.
  Caution
  Don’t confirm Z## HRH65 Team Monitoring Process. The alerts are not yet solved! This will happen in another exercise.

PCC Process Run with a Full Configuration

Running PCC: Team Lead Responsibilities

Next, let’s talk about how activities and functions are assigned and performed by different members of the payroll team. Once the Payroll Process Manager selects the Start All button from the previous step, team leads will be able to see the alerts for their assigned team.

There are five primary tasks and action items the team lead will take via the Team Management app, including the following:

Manage teams and monitor the progress of alert processing
Assign alerts to team members
Activate or deactivate members
Forward alerts to another team

Let’s take a closer look at each of these tasks.

Team Management

First, the team lead will view the open alerts assigned to the team. To do this, a tile with alerts assigned to a team will appear on the team leader’s app after the Payroll Process Manager chooses the Start All button at the Monitoring step of the pre-payroll process.

The image shows how alert management is started for Team A.

Team Management: Check Alert Status

If the team lead wants to check the alert status generated by a particular validation rule, they will select the alerts that correspond to the validation rule title. Doing this allows the team lead to see more details as seen in the figure, Check Alert Status.

The image shows the option to check alerts status based on a dedicated validation rule.

The Results Bar

The red results bar appears to show the total amount of alerts per validation rule. You can select the bar to see a list of employees with that alert.

The image shows the red results bar which displays the total number of alerts per validation rule. Clicking on the bar allows you to view a list of employees who have that alert.

Let’s see this in action.

Assign a Processor

The main task of the team lead is to assign a processor to resolve alerts. The team lead will select the Not Assigned link to choose a Processor from the list that can be assigned to resolve that employee’s alert. When team leader selects the Not Assigned link, a pop-up window appears with all team members defined during team configuration step.

If the team leader wants to assign the processor to the alerts generated by a particular validation rule, they can select the results bar to the right of the validation rule name. After that, they can navigate to the page for assigning alerts to team members.

Root Cause Analysis Page

When the team lead selects the name of an employee to whom the system generated the alert, the team lead is directed to the root cause analysis (RCA) page. The RCA page allows the team lead to check employee information in accordance with the RCAs assigned to the validation rule. To do this, the team lead can select the line of the interested employee from the list.

The image shows the screen where the team lead chooses the employee to whom the system generated the alert, they will be directed to the root cause analysis (RCA) page. On the RCA page, the team lead can review employee information based on the RCAs assigned to the validation rule. This can be done by selecting the specific line of the employee from the list.

Here, we can see the employees who have an issue with a certain validation rule. By selecting the employee, the team lead can see the RCA screen to investigate what happened. The Team Lead can also see the processor who will be responsible for resolving the issue.

For more details about RCAs, refer back to Unit 4 for more information on this process.

Team Assignment Page

The Team Lead can activate and deactivate members of their team by choosing Team Assignment. Then, they can toggle a team member as active/inactive. Additionally, the team leader can move to the Team Assignments page, where they can check how many alerts have been assigned to team members. To do this, choose the Team Assignments button in the lower right corner of the overview page of the Team Management app. On the Team Assignments page, a team lead can also activate and deactivate their team members.

The image shows two screens where the team lead can see alerts assignments to team members.

Business Example

This practice shows how to handle alerts by logging in as a payroll administrator.

My Worklist

The My Worklist Without Alerts tab shows a history of the alerts that you previously resolved. This provides visibility about how issues were resolved in case any questions arise about the alert in the future. On the My Worklist Without Alerts tab, the payroll administrator can find all the alerts they previously processed.

Team Management Page

Team leads can see the alerts at a glance on this page. You can think of this page as a kind of dashboard for the team lead.

My Process App

You can see on the screen that the number of alerts is zero. Now that all corrections have been made and checks are done, the Payroll Process Manager can set the monitoring process as complete.

As alert processing progresses and issues are resolved, the number of open alerts on the Monitoring step in the My Process app are automatically updated. The Payroll Process Manager can monitor the issue resolution in real-time.

The Monitoring process can be restarted an unlimited number of times to start checking payroll relevant data and payroll results once after making any changes.

This image shows the My Processes app, with all alerts being resolved.

Business Example

This practice shows how the Team Lead will assign processors to the alerts using the My Team application.

ExerciseStart Exercise

Business Example

This practice shows how to handle alerts by logging in as a payroll administrator.

ExerciseStart Exercise

Confirm Team Monitoring Process

This practice shows how to confirm Team Monitoring Process.

ExerciseStart Exercise

Assign Alerts to a Payroll Administrator

Business Example

As Team Lead of Team A, user Z##_USER, wants to verify and assign the alerts which have been generated after the execution Z## HRH65 Team Monitoring Payroll Process.

Steps

Call PCC: Team Management Application.
1. Check if any front-end applications are open. And if some are open, close them all.
2. Open the Team favorite folder.
3. Click on the PCC: Team Management application.
4. To log into the front end of the training system, provide the username Z##_USER and password Welcome1. (You created this user in the exercise 23.)
To verify alerts, click on the tile with number open alerts for Team A.
Assign alert generated by a validation rule Z##_HRH65 - C026 - Employees with Gross pay over the threshold amount (5000 EUR) to Alert Processor.
1. Choose Not assigned link under Processor column in the Team Management page.
2. Select user HRH65-## from the drop-down list on the Assign Processor pop-up window.
  In this drop-down list, the system displays all members assigned to Team A during the Team configuration process.
3. Choose the Back button to return to the Team Management page.
Assign alert generated by a validation rule Z30_HRH65 - C018 Employee with missing cost center to Alert Processor.
1. To check which alerts are still unassigned сlick on the Not Assigned tab.
2. Click on the red bar to the right of the name validation rule HRH65.
3. Choose Not assigned link under Processor column in the Team Management page.
4. Select user HRH65-## from the drop-down list on the Assign Processor pop-up window.
5. Choose the Back button to return to the Team Management page.
6. Make sure the list of unassigned alerts is empty.
7. Choose the Back button to return to the Payroll Control Center - Team Management page.
8. Close Payroll Control Center - Team Management Application.

Resolve Alerts and Verify Results

Business Example

As PCC Payroll Administrator, you needs to resolve and verify the assigned alerts which have been generated by Z## HRH65 Team Monitoring Payroll Process using Payroll Control Center Alert Management application.

Steps

Call PCC My Alerts Application.
1. Check if any front-end applications are open. And if some are open, close them all.
2. Open the Payroll Administrator favorite folder.
3. Click on the PCC My Alerts (Administrator) application.
4. To log into the front end of the training system, provide the username HRH65-## and password Welcome1. (You already used the same username and password to log into the training system.)
Choose Z##_HRH65 - C026 - Employees with Gross pay over the threshold amount (5000 EUR) validation rule. Check Payslip on Test Payroll Results for the employee from the Alert Management application. Then navigate to the Root Cause Analysis and check RCA configured in the exercises 11-16.Then navigate to the Solutions where you can choose the required pre-configured solution for this alert. Correct issue and save your entry.
1. On the My Worklist With Alerts tab, 2 alerts are listed for the Z## HRH65 Team Monitoring Payroll Process.
2. Select the alert: Z##_HRH65 - C026 - Employees with Gross pay over the threshold amount (5000 EUR).
3. Click on the line with employee name.
4. On the details tab, scroll down to the details for Payslip on Test Payroll Results. In the payslip, you will find that the salary is EUR 5800.
5. Choose the Back button to return to the Alert page.
6. Navigate to the Solutions tab where you can display all the pre-configured solutions for this alert.
7. Take Review 0008 IT, as it seems that the error it is related to a wrong amount in Basic Pay infotype. Click on the solution link.
8. To login to the front end provide the username HRH65-## and password Welcome1.
9. Correct PS group from E03 to E01 and Level 01 in 0008 IT. Enter.
10. Make sure that the salary amount is now 3050 EUR.
11. Save your entry. Close Maintain HR Master Data application.
Validate alert.
1. Select check box to the left of the employee's name.
2. Choose Validate button in the lower right corner of the Alerts page.
  Since the alert has been resolved, the alert should disappear from the processor's worklist. If this does not happen, repeat the validation in a few minutes.
3. Choose the Back button to return to the Payroll Control Center Alert Management page.
Choose Z30_HRH C018 Employee with missing cost center validation alert. Check the Generic Overview RCA and make sure that the employee does not have a cost center. Navigate to the Solutions where you can choose the required pre-configured solution for this alert. Correct the issue and save your entry.
1. Now on the My Worklist With Alerts tab, 1 alerts are listed for the Z## HRH65 Team Monitoring Payroll Process.
2. Select the alert: Z30_HRH65 - C018 Employee with missing cost center.
3. Click on the line with employee name.
4. Generic Overview RCA and make sure that the employee does not have a cost center.
5. Choose the Back button to return to the Alert page.
6. Navigate to the Solutions tab where you can display all the pre-configured solutions for this alert. Take the first one, Review IT0001.
7. Click on that link.
8. To login to the front end provide the username HRH65-## and password Welcome1.
9. Choose Pen icon (Edit) in the Action column under Organizational Assignment.
10. Enter 4711 in the Cost Center field of the 0001 IT.
11. Save your entry. Close Maintain HR Master Data application.
Validate alert Z30_HRH65 - C018 Employee with missing cost center.
1. Select check box to the left of the employee's name.
2. Choose Validate button in the lower right corner of the Alerts page.
  Since the alert has been resolved, the alert should disappear from the processor's worklist. Choose the Back button to return to the Payroll Control Center Alert Management page.
3. As there aren’t any alerts in your worklist with alerts. Check your worklist without alerts. This list displays a Z## HRH65 Team Monitoring Payroll Process for which there are no unassigned or resolve alerts. If you click on the process name you can find 2 alerts on the Completed tab.

Validation of Payroll Results with PCC

Productive Payroll Process Type Category

In the last lesson, you learned about how to run a pre-payroll process using the monitoring category. Next, let’s look at how to prepare and run the productive payroll process.

The difference between the categories Productive Payroll and the Monitoring Process (MO and TM) are as follows:

The relevant payroll data must be closed from changes until the end of the current payroll.
The productive payroll results are saved both in declustered tables and in the cluster.
The productive payroll results will be posted to FI/CO and transferred to the bank.

Remember that a super admin or consultant will need to create a payroll process type with specific categories.

The image shows a screen where the Productive Payroll is listed as a category.

Start and End Payroll Overview

The main difference between the monitoring process and the productive payroll process are the start and end payroll steps. However, master of time data will be the same for payroll results.

The first step of the productive payroll process is to Start Payroll. The Start Payroll step sets the control record of the payroll area to the status released for payroll, which means that the payroll relevant data is locked from changes. At this stage, it’s not possible to change any of this information until the end of the current payroll period.

The image shows the status of the process after payroll has been started, this status is released f. payroll.

The last step End Payroll is when payroll relevant data will be open for changes. At this stage, the system validates all payroll relevant information by checking validation rules, generating KPIs, and resolving outstanding issue. Once all information is accurate, the team can close the payroll period. Any changes to payroll relevant data performed at this stage will lead to a recalculation in the future periods.

The image shows the status of the process after payroll has ended, this status is exit payroll.

User List for Master Data

PCC has specific settings for admin transactions. With PCC, the payroll admin has opportunities to make specific updates for singular users without disrupting the entire payroll process even when the payroll period is technically closed.

The image shows three screens with which you can see that the system allows first to display a user list for maintaining master data, then user names, and finally the table which lists entries that you use to maintain data.

Ideally, assigning an alert to update data is performed when the control record is locked.

Key notes about these transactions are the following:

Your user ID also must be assigned on the Maintain User List for Master Data option, which is given in the transaction PYC_ADM_TRANSACTION - PCC: Admin Transaction Conf.
PYC_D_EE_MDCA is the assignment between PERNR and PROCESSOR to update master data when the control record is in Released for Payroll status.

Use Case Example: A payroll admin needs to add a bonus for a certain employee, so they can open the data for that specific user rather than opening the payroll for ALL users. The PCC Administrator can use the Maintain User List for Master Data Maintenance option of transaction PYC_ADM_TRANSACTION to grant the possibility to change any payroll relevant data for the end users (alert processors) listed here even if the status of control records set to Release for payroll. So, the payroll admin can add information about the bonus for the one selected employee in the productive payroll phase. This is only one example, but there are other available transactions that an admin can perform.

Note

This is not a transaction for the end users. The PCC Administrator will set this up in the back end so that the payroll admin can modify data when the payroll area is released.

Productive Payroll: Step 1

This process begins in the steps tab of the Process Type screen. This is where you will Start Payroll.

The image shows the step start payroll as part of the whole payroll process. This process begins in the steps tab of the Process Type screen. This is where you will Start Payroll.

Productive Payroll: Step 2

To Run Payroll, you will use the parameter job size for parallel execution to specify how many people will be grouped into one job run for payroll. For example, if the job size is defined as 100, and there are 1000 employees you need to run payroll for, the system will trigger 10 jobs of the payroll run.

Make sure to assign the correct program name and program variant for this step. Some of these steps are country specific. You have to create a particular process type for each country and to assign a different driver for each country to the appropriate process type. Screen A in the image shows the variant with current payroll period for any existing payroll area and customer’s payroll schema.

The image shows the step run payroll as part of the whole payroll process. This process happens in the steps tab of the Process Type screen. You will have to select a country-specific payroll driver.

Productive Payroll: Step 3

During the posting simulation step, make sure you save a separate variant for your posting simulation than for your live posting run in the RPCIPE01 program. You will also execute the posting simulation variant in your production process.

The payroll program (RPCALC#0) will work correctly for the same variant for Monitoring (Simulation) and Production Payroll, but not for Posting.

The image shows the step posting simulation as part of the whole payroll process. This process begins in the steps tab of the Process Type screen. You will have to select a copy of an SAP Standard Posting Variant for your country grouping

Productive Payroll: Steps 4, 5, and 6

The last three steps of the productive payroll process include the following:

Initiate policy
Monitoring
End payroll

These steps are similar in that you don’t need to provide any specific program. All you have to do is assign the process for each of these steps.

The image shows three screens for the steps to end payroll. These steps are similar in that you don’t need to provide any specific program. All you have to do is assign the process for each of these steps.

Business Example

This practice shows how to configure productive Payroll Processes Type using Best Practices package.

ExerciseStart Exercise

Wrapping up the Process: Payroll Process Manager Tasks

When the Payroll Process Manager will create a new productive payroll process, they must complete the following tasks:

Assign the payroll process to the appropriate payroll process type.
Assign the payroll area, policies, analytics, processors, and payroll period.

Wrapping up the Process: Technical Consultant Tasks

When the consultant configures the payroll process type, the Payroll Process Manager creates a payroll process based on the process type based on who is being assigned payroll (what VRs, KPIs are going to be used in the process).

Productive Payroll Process Configuration: Predecessor

When processing alerts received during the monitoring process, some problems are identified and fixed; for alerts related to "false alarms," the processor set the status as resolved.

To avoid repeated processing for alerts with a resolved status while setting up a Productive Process, you can link it with a preceding Monitoring Process created for the same payroll area and the payroll period. For a Monitoring Process to be used as a predecessor to a Productive Process, both processes must be assigned at least one of the same policies.

The image outlines the following with two screens: During the monitoring process, alerts are addressed and resolved for identified problems. Alerts marked as false alarms are categorized as resolved. To prevent repeat processing of resolved alerts when setting up a Productive Process, it can be linked to a preceding Monitoring Process for the same payroll area and period. Both processes must share at least one policy to be used together.

Productive Payroll Process Run

The final stage of this process shows that all, or at least most, problems are identified, corrected, or resolved before the Productive Payroll run.

The image shows the final stage of the process, the productive payroll run. The final stage of this process shows that all, or at least most, problems are identified, corrected, or resolved before the Productive Payroll run.

Business Example

This practice shows how to configure Productive Payroll Process.

ExerciseStart Exercise

Business Example

This practice shows how to run the Productive Payroll Process.

ExerciseStart Exercise

Resolving Alerts

This practice showed how to resolve alerts.

ExerciseStart Exercise

Business Example

This practice shows how to confirm the productive payroll process.

ExerciseStart Exercise

Configure Productive Payroll Process Type in Configuration Workbench

Business Example

As a PCC consultant responsible for implementing the Payroll Control Center functionality, you need to configure the Productive Process Type so that the Payroll Process Manager can run productive payroll for their employees.

During the Productive Payroll Process, the payroll results are stored in both declustered tables and a cluster. Ultimately, the Initiate Policies steps fetch the data and create the alerts and KPIs handled in the monitoring step.

Steps

Access Configuration Workbench transaction (transaction code PYC_CONF_WB).
1. Open the Configuration tool favorite folder.
2. Execute Configuration Workbench transaction.
Create a new Process Type with ID Z##_HRH65_PROD_PROCESS_TYPE and name Z## HRH65 Productive Process Type relevant to Other Countries and category PP Productive Payroll.
1. Switch to the edit mode by choosing the Display/Change icon in the application toolbar.
2. By default, Process Type should be selected from the drop-down list on the left panel.
3. Choose the Create icon in the application toolbar to make a new process type.
4. Enter the following information on the Create Process Type pop-up window:
  - ID: Z##_HRH65_PROD_PROCESS_TYPE.
  - Name: Z## HRH65 Productive Process Type, where ## - your group number.
    Choose OK in the lower right corner of the pop-up window.
5. Set up the information in the Basic Information Tab:
  - Choose country: select 99 for Other countries.
  - Choose the category PP Productive Payroll.
  - Set the authorization prefix: PC##, where ## - your group number.
  - Selection Type: ABKRS payroll area(is populated automatically).
  - Recurrence type: PERIOD Payroll period (is populated automatically).
  - Period parameter: Set to 09 ECP Monthly.
  - Contacts group: Set to PC##.
  Check the box to select Use validation rules created from manage configuration. Please Pay attention that this checkbox is only accessible in creation mode.
Assign the required process steps to the new process type: Start Payroll, Run Payroll, Posting Simulation, Initiate Policy (New), Monitoring and End Payroll. Then, specify the ABAP program name and variant for each step where necessary.
1. Click on the Step tab and add the following new steps for the payroll process. The steps should appear in the following order. You can drag each step to rearrange the order.
  - Start Payroll (PYP_V2_OPEN_PAYROLL)
  - Run Payroll (PYP_V2_RUN_PAYROLL)
  - Posting Simulation (PYP_V2_SIMULATE_POSTING)
  - Initiate Policy (New) (PYP_TSK_INIT_POLICIES)
  - Monitoring (PYP_V2_MONITORING)
  - End Payroll (PYP_V2_CLOSE_PAYROLL)
2. To set the parameters step, double click on the step Create test payroll data.
  Configure the following parameters for the step:
  - ABAB Program: RPCALCX0
  - Job size for parallel execution: 20
  - ABAB program variant: choose GR##_HRH65 from the drop-down list.
    Make sure that this step will be automatically started and confirmed.
3. To set the parameters, double-click on the step Posting simulation. Configure the following parameters for the step:
  - ABAB Program: RPCIPE01.
  - ABAB program variant: choose GR##_PCC_EX_SP GR## Posting simulation from the drop-down list.
    Make sure that this step will be automatically started and confirmed.
4. To set the parameters step, double-click on the step Initiate Policy (New). Configure the following parameters for the step:
  - Job size for parallel execution: 20
    Make sure that this step will be automatically started and confirmed.
5. To check the parameters step, double click on the step Monitoring.
  Make sure that this step needs to be manually started and confirmed.
To assign Policy Types to the newly created Process Type click on the Policy Types tab
Choose and assign the following policy types: SBP Policies for personal information ( * )
SBP Policies for employment and job information ( * )
SBP Policies for time data processing ( * )
Z## HRH65 GROSS AND NET (you created it in the exercise 18)
Z30 HRH65 EE Personal Info.
Validate the newly created Process Type.
Save Process Type configuration.

Configure Productive Payroll Process

Business Example

As the Payroll Process Manager, you can start configuring the Productive Payroll Process.

The configuration of the Productive Payroll Process differs from that of the Team Monitoring process in that it requires direct assignment of team members to the process and designation of the Predecessor for the Productive Payroll Process. This ensures that the PCC can consider alerts resolved during the previous test payroll calculation stage.

Steps

Call PCC Manage Processes (Manager) application.
1. Open the Payroll Process Manager favorite folder.
2. Click on the PCC Manage Processes (Manager) application.
3. To log into the front end of the training system, provide the username HRH65-## and password Welcome1. (You already used the same username and password to log into the training system.)
Create a new payroll process based on the Z## HRH65_Productive Process Type (Z##_HRH65_TM_PROCESS_TYPE) created in the exercise 31. Call it Z## HRH65 Productive Payroll Process.
1. To create a new process, choose the + sign, Add Process in the lower right corner of the application screen.
2. Enter Z## in the search bar of the Select process type pop-up window.
3. Select Z## HRH65 Productive Process Type (Z##_HRH65_PROD_PROCESS_TYPE) from the drop-down list.
4. In the Process Name field, enter Z## HRH65 Productive Process.
Assign the payroll area to your process (X1-X9 for groups 01-09, Y0-Y9 for groups 10-19, Z0-Z9 for groups 20-29, and ZS for group 30).
1. To add the payroll area, choose the + sign, Add Selections to the right of the Selection section.
2. Enter your payroll area ID in the search bar of the Select payroll area pop-up window.
3. Select your payroll area.
Assign Policies Z##_HRH65 GROSS AND NET VALIDATION POLICY created by you in the exercise 24 and Z30 HRH65 Employee Personal Info was prepared for the course in the training system and the process.
1. To add the policy, choose the + sign, Add Policies to the right of the Policies section.
2. Select Z##_HRH65 GROSS AND NET VALIDATION POLICY and Z30 Employee Personal Info.
Assign HRH65-## and Z##_USER as team to the newly created process.
1. To add the Team Member, choose the + sign, Team Members to the right of the Team section.
2. Enter HRH65-## in the search bar of the Select Team Member pop-up window.
3. Select HRH65-##.
4. To add one more Team Member, choose the + sign, Team Members to the right of the Team section.
5. Enter Z## in the search bar of the Select Team Member pop-up window.
6. Select Z##_USER.
Assign Z## HRH65 Analytics for payroll Process (Z##_HRH65_Analytics).
Choose created Analytics in the exercise 25 from the drop-down list.
Assign 01 payroll period of the current year as recurrences for the payroll process.
1. To add the payroll period, choose the + sign, Add Recurrences to the right of the Recurrences section.
2. Enter current year in the search bar of the pop-up window Select payroll period, then ENTER.
3. Select 01 payroll of the current year from the drop-down list and choose OK.
Assign Z##_HRH65_Team Monitoring Payroll Process as a Predecessor of Z## HRH65 Productive Process Type.
1. To add the Predecessor, choose the + sign, Add Monitoring Processes to the right of the Predecessors section.
2. Select Z##_HRH65_Team Monitoring Payroll Process from the Select Predecessors pop-up window.
Validate the payroll process configuration.
1. Click on the Validate button in the lower right corner of the screen.
Save Z## HRH65 Productive Process.
Once the process validation is successful, click the Save button located at the bottom right corner of the screen.

Run Productive Payroll Process with alert.

Business Example.

As the Payroll Process Manager, you have prepared the Productive Payroll Process configuration and are ready to start the productive process.

Steps

As an HR specialist, it is necessary to create a record for the Absence (2001) infotype, subtype 0620 Unpaid Leave, lasting from the first to the last date of February for the current year, for personal number 722991##. Then, you need to create a record for the Additional Payments (0015) infotype with wage type CM03 Premium on the last date of February for the current year for your employee.
1. Execute transaction PA30. Maintain HR Master data.
2. Enter 722991## in the Personnel No field.
3. Enter 1001 (Absence) in the Infotype field and choose 0620 Unpaid Leave from the Subtype drop-down list.
4. Choose the first date to the last date of February of the current year in the field from and to in the Period section of the transaction screen.
5. Choose Create icon in the upper left corner of the transaction toolbar.
6. Save Unpaid Absence.
7. Enter 0015 Additional Payments in the Infotype field and choose CM03 Premium from the Subtype drop-down list.
8. Choose Create icon in the upper left corner of the transaction toolbar.
9. Enter 1000 EUR in the Amount field.
10. Choose the last date of February of the current year from the calendar as Date of origin.
11. Save your entry and return to the SAP Easy Access menu screen.
(Optional) Check transaction PA03 Payroll Control Record check the status of your payroll area, PCP0 Edit posting run and ensure that there aren’t any posting runs for your payroll area, PC_PAYRESULT Display results and ensure that there aren’t any payroll results for your employee.
1. Execute transaction PA03.In the Payroll Area field, enter your payroll area (X1-X9 for groups 01-09, Y0-Y9 for groups 10-19, Z0-Z9 for groups 20-29, and ZA for group 30). Then, choose the Glasses icon at the top left of the screen. Ensure that your payroll area status is set to New. Choose the Back button to return to the initial screen of the transaction.
2. Open a new GUI window (System → New GUI window). Execute transaction PC_PAYRESULT Display results. Enter 722991## in the field Personnel Number and ensure no payroll results for your employee.
3. Open a new GUI window (System → New GUI window). Execute transaction PCP0 Edit posting run, Ensure there are no posting runs for your payroll area in the list. Choose Back button to return to the SAP Easy Access menu
Open PCC My Processes Application
1. Open the Payroll Process Manager favorite folder
2. Click on the PCC My Processes (Manager) application.
3. To log into the front end of the training system, provide the username HRH65-## and password Welcome1. (You already used the same username and password to log into the training system
Confirm Z## Team Monitoring Payroll Process
1. Open the Active Processes folder, choose Z## Team Monitoring Payroll Process.
2. Choose the Z## Team Monitoring Payroll Process and choose Confirm
3. Enter a comment, such as Confirmed, and choose OK. Note: Because the Monitoring Process is completed successfully, the status has now changed to Completed
4. To check completion, choose Back. With this, you return to the My Processes screen
5. Choose the Completed Processes folder. Process Z## Team Monitoring Payroll Process is listed here.
To start the Productive Payroll process, switch to the Upcoming Processes from the My Processes tab. Here, you can see all processes for January of the current year. Start process Z## Productive Payroll Process
1. Choose Upcoming Processes
2. Start process Z## Productive Payroll Process by choosing the Start Process button. Now, this process disappears from the list of upcoming processes. Instead, it is displayed on the Active Processes tab.
On the Active Processes tab, note that you automatically start the first out of six process steps, Start Process, when you select the Z## Productive Payroll Process. All six steps included in the whole process are displayed. When a step is performed, background jobs are created; when the step is completed, you can display the spool of the corresponding jobs. You also complete steps Run Payroll and Posting Simulation
1. Return to the front end My Process App
2. Choose Active Processes and select Z## Productive Payroll Process. This starts the process automatically. In case of no errors, the Status changes to Start Payroll finished successfully. Note that the process is still displayed as In Process. Note: : In addition, you can see tabs for all six steps:
  - Start Payroll
  - Run Payroll
  - Posting simulation
  - Initiate policy
  - Monitoring
  - End Payroll
3. (Optional)Return to the back-end and execute transaction PA03. Then, choose the Glasses icon at the top left of the screen. Ensure that your payroll area status is set to Released for payroll. Choose the Back button to return to the transaction's initial screen. Note:When the Productive Payroll process starts, employee master data maintenance will be locked for all employees assigned to the process.
4. Choose the Run Payroll tab for the Z## Productive Payroll Process. The process runs automatically. In case of no errors, the Status changes to Run Payroll finished successfully. (Note that the process is still displayed as In Process. Choose the Refresh icon to set this step to Completed.)
5. (Optional) Return to the back end and execute transaction PC_PAYRESULT Display results. Choose the Update result icon on the transaction toolbar. Ensure that you can now find payroll results for your employees(Optional) Return to the back end and execute transaction PC_PAYRESULT Display results. Choose the Update result icon on the transaction toolbar. Ensure that you can now find payroll results for your employees. Return to the front end My Process App
6. Return to the front end My Processes App. Choose the Posting Simulation tab. In case of no errors, the Status changes to Posting Simulation finished successfully. Choose the Refresh icon to check if this step is Completed.
7. (Optional) Return to the back end and execute transactionPCP0 Edit posting run. Check that you can now find the posting run for your payroll area in the list. Note: With this step, you write the results in the payroll cluster to simulate posting document. Note the information: Policy violations are displayed and can be assigned to experts for further processing.
8. Choose the Refresh icon to check if this step is Completed.
Before you close the payroll period, initiate a policy to execute all checks included in the policy assigned to this process. You can check the results of the policy implementation In Monitoring step. Assign the alert Z##- HRH65 - C003 - Employees returning from long absence(maternity/sickness) to the user HRH65-## at this step.
1. From the Monitoring tab, choose Start to recognize policy violations, which would be listed as alerts. The process is displayed as In Process. You can view details, such as alerts or employee count analysis.
2. Click on the Not assigned link under the Alerts section.
3. Then click on the Z## GROS AN NET VALIDATION POLICY .
4. Assign the alert Z##- HRH65 - C003 - Employees returning from long absence(maternity/sickness) to the user HRH65-##.
Resolve alert as PCC Administrator using PCC My Alerts Application.
1. .Return to the back end and call PCC My Alerts(Administrator) Application from the Payroll Administrator favorite folder.
2. Choose Z##- HRH65 - C003 - Employees returning from long absence(maternity/sickness)generated for the Z## Productive Payroll Process.
3. Choose the solution Review Absence in payroll system the solution Review Absence in payroll system.
4. Enter user HRH65-## and password Welcome1to login to the backend system as Payroll administrator.
5. You understand that the Unpaid leave was mistakenly created for an employee. To delete the Absence record select the "Back" option from the toolbar at the top of the screen
6. Then, choose Overview option from the transaction toolbar at the top of the screen
7. Select the '0620 Unpaid Leave' record and click on the 'Delete' option from the transaction toolbar at the top of the screen.
8. Choose Delete option one more time from the toolbar at the top of the Delete Absences screen.
9. Close Maintain HR Master Data window.
10. Return to the My Alert Application and ensure that Validation option is inactive for theZ##- HRH65 - C003 - Employees returning from long absence(maternity/sickness) alert.
11. Close My Alert Application.
12. (Optional) Open PCC Administrator favorite folder and execute transaction PYC_ADM_TRANSACTION - PCC: Admin Transaction Conf.
13. Double-click on the Maintain User List for Master Data Maintenance option on the left panel of the transaction screen, scroll down the User Name list on the right side and ensure that user HRH65-## is included in the list. Therefore, you were able to change payroll-relevant data, even though the payroll area was released for payroll.
14. Close My Alert Application.
When all alerts are resolved, as PCC Payroll Process Manager, you need to restart the Z## Productive Payroll Process from the Run Payroll step, go through all process steps, and close the payroll period. .
1. Return to the front end My Processes App
2. Choose the Run Payroll process step. Choose the option Repeat and then Start
3. Choose option Erroneous at the bottom of the Start step popup window.
4. Go through all process steps.
5. At the Monitoring step, once all checks are confirmed as successful, you can Confirm the Monitoring step and make a note in the pop-up window.
6. Ensure that End Payroll step will be started and confirmed automatically.
Check if the Z## Productive Payroll Process is listed in Completed Processes.
1. Choose Back to return to the Active Processes tab. You can’t find Z## Productive Payroll Process here
2. Choose the Completed Processes tab. The Z## Productive Payroll Process is listed with a completion date and status OK. You have successfully run a Productive Payroll process.
3. Return to the back end. Check payroll area status is set to Exit payroll via the transaction PA03.

Continue to quiz