Objective
VIDEO
Now that you’re ready to configure PCC, let’s look at the first step: configuring policy types. To configure a policy type, you will use the Configuration Workbench.
The policy types are used to logically group together the validation rules/alerts that could later be assigned to a payroll process, such as Monitoring, Productive Payroll, and so on.
This practice shows how to create new policy types.
As a PCC consultant, you need to create a new Policy type designed for a specific country and functional area.
Access Configuration Workbench transaction (transaction code PYC_CONF_WB).
Open the Configuration tool favorite folder.
Execute Configuration Workbench transaction.
Create a new Policy Type with ID Z##_HRH65_POLICY_TYPE and name Z## HRH65 GROSS AND NET. Set up the new policy type to be applicable for Other Countries and for Validation Rules created in Manage Configuration application.
Choose Policy Type from the drop-down list on the left panel.
Select the Display/Change pencil icon in the upper left corner of the application toolbar.
Choose the Create icon in the application toolbar.
Enter ID Z##_HRH65_POLICY_TYPE, where ## - your group number and name Z## HRH65 GROSS AND NET.
Define the policy type by country. You must decide to which country (or countries) the policy type will apply. For this exercise, use 99 Other countries.
Check the box to select Use validation rules created from manage configuration.
Validate the newly created Policy Type by clicking the Validate button.
Save your configuration.
If the validation passed without warnings or errors, save the configuration.
The process type is featured by many attributes. One of the most important is the category. There are various kind of categories: they can be classified in off-cycle and classical categories.
The Off-Cycle categories will be discussed in Unit 8 of this course.
The classical categories can be classified in 3 types:
The Monitoring and Team Monitoring process types are working with the pre-payroll concept (also known as "Test Payroll" or "Continuous Payroll"). The payroll result is "Test Payroll".
The Monitoring process type does not use the team concept. This means that only one team is created at the level of the process configuration with only team members and no team leader.
Unlike the Monitoring process type, the Team Monitoring process type does use the team concept. You can create dimensions to define the teams that will get the alerts automatically assigned to.
The Productive Payroll is dedicated to the execution of the Productive Payroll. The payroll result is "Productive Payroll".
There is no concept of team in the Productive Payroll; there is (like for Monitoring) only one team created at the level of the process configuration with only team members and no team leader.
This category is mainly used for post-payroll activities or any other non-payroll process type.
There is no concept of team at all in this category of process types.
The next step is to configure process types using Configuration Workbench. The process type defines a series of steps that are to be executed once the Payroll Manager creates a process based on the process type. The process type is the most important object because it uses the entities created before.
This practice shows how to configure Team Monitoring Process Type
The Process Type defines a series of steps to be executed once the Payroll Process Manager creates a process based on the Process Type.
As a PCC consultant responsible for implementing the Payroll Control Center functionality, you need to configure the Team Monitoring Process Type so that the Payroll Process Manager can run pre-payroll validations for their Payroll Area.
The Team Monitoring process creates test payroll results (the data is stored in the de-clustered tables and the cluster XT, not in the cluster for production payroll results). Ultimately, the Initiate Policies steps fetch the data and create the alerts and KPIs handled in the monitoring step.
Access Configuration Workbench transaction (transaction code PYC_CONF_WB).
Open the Configuration tool favorite folder.
Execute Configuration Workbench transaction.
Create a new Process Type with ID Z##_HRH65_TM_PROCESS_TYPE and name Z## HRH65 Team Monitoring Process Type relevant to Other Countries and category TM Team Monitoring.
Switch to the edit mode by choosing the Display/Change icon in the application toolbar.
By default, Process Type should be selected from the drop-down list on the left panel.
Choose the Create icon in the application toolbar to make a new process type.
Enter the following information on the Create Process Type pop-up window:
Choose OK in the lower right corner of the pop-up window.
Set up the information in the Basic Information Tab:
Choose country: Select 99 for Other countries.
Choose the category TM Team Monitoring. Once you select this option, a new tab called Team Dimensions will be automatically added to the object.
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 01 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: Create Test Payroll Data, Posting Simulation, Initiate Policy (New), and Monitoring. Then, specify the ABAP program name and variant for each step where necessary.
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.
Create Test Payroll Data (PYP_V2_RUN_PAYROLL_TEST)
Posting Simulation (PYP_V2_SIMULATE_POSTING)
Initiate Policy (New) (PYP_TSK_INIT_POLICIES)
Monitoring (PYP_V2_MONITORING)
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 GR30_HRH65 from the drop-down list.
Make sure that this step will be automatically started and confirmed.
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 GR30_PCC_EX_SP GR## Posting simulation from the drop-down list.
Make sure that this step will be automatically started and confirmed.
To set the parameters step, double click on the step Initiate Policy (New).
Configure the following parameter for the step:
Job size for parallel execution: 20Make sure that this step will be automatically started and confirmed.
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:
Activate Event Handler
To activate Event Handler click on the Event Handler Tab.
Check the box to select Event Handler Enabled.
Relevance Check Logic: CL_PYC_EHI_RELE_CHECK_DEF (is populated automatically).
Choose Payroll area and Policy ID as Team Dimensions.
Click on the Team Dimensions tab.
Choose Payroll area and Policy ID.
Validate the newly created Process Type.
Save Process Type configuration.