PCC
PCC
Public
Warning
This document has been generated from SAP Help Portal and is an incomplete version of the official SAP product documentation.
The information included in custom documentation may not reflect the arrangement of topics in SAP Help Portal, and may be
missing important aspects and/or correlations to other topics. For this reason, it is not for production use.
This is custom documentation. For more information, please visit SAP Help Portal. 1
8/6/26, 2:23 PM
Use
The Payroll Control Center is an application that enables you to control the complete payroll process. It helps you to produce high
quality results quicker and more efficiently.
Plan your payroll processes and all involved payroll process steps
Monitor progress and status of all payroll processes and their steps
Execute checks at different times within the payroll process (for example, pre-payroll master data checks, post-payroll
checks) and distribute the identified issues and compliance violations to the responsible payroll administrator for
correction
Keep an up-to-date status of all identified issues and the progress in their resolution
Define authorizations for payroll processes and checks, so that users can only see the data that they need and are
authorized to see
Enable audit processes based on a log file which the system fills automatically and which the user can enhance by creating
new log entries
Implementation Considerations
It is possible to include the Payroll Control Center as a lane on the HR Renewal 2.0 Landing Page. For more information, see the
Installation and Upgrade Information section in the Administrator’s Guide at [Link] .
Integration
It is possible to use the capabilities of SAP HANA to speed up the execution of checks on payroll results. To do so, it is mandatory
to set up declustering tools. For more information, see the documentation for the HCM Declustering Tools (HCM_LOC_CI_50).
Customizing
To use the Payroll Control Center, you make the following Customizing settings:
1. You make your already existent PERNR authorizations (based on objects like P_ORGIN) available for the Payroll Control
Center in Customizing for Payroll International Authorization Framework .
Note
Authorizations on the level of checks, and payroll processes must be granted separately.
This is custom documentation. For more information, please visit SAP Help Portal. 2
8/6/26, 2:23 PM
2. You set up the payroll checks and assign the authorization types in Customizing for Payroll International Payroll Data
Source Framework .
3. You define your payroll processes for the Payroll Process Manager in Customizing for Payroll International Payroll
Control Center .
Related Information
Payroll Control Center (New Payroll Experience)
General
The Payroll Control Center supports the following two roles:
The payroll process manager, who is in charge of the successful execution of a complete payroll process (for example, a
payroll process manager in charge of the monthly payroll for June for a certain payroll area)
The payroll administrator, who is the subject matter expert in charge of resolving issues that have been identified during
the execution of a payroll process (for example, clarify if a payment to a non-active employee is justified)
For each of the user roles, the payroll control center offers a user interface, customized to their respective requirements.
Users can log on to the Payroll Control Center using Single Single-On (SSO) or using their user name and password, depending on
the set up of the SAP Gateway.
Within the Payroll Control Center a user session has an expiration time of 120 [Link] means, if the user does not perform
any activity during these 120 minutes, the session expires and the Payroll Control Center must be restarted again. You can change
the session expiration time using transaction SU01:
1. In transaction SU01, enter the user name for whom you want to change the session expiration time.
2. In the Parameters tab page, enter the parameter PYD_USER_SESSION_EXP and then specify in the Parameter Value field
the user session expiration time. The unit is minute.
For example, if you want the session expiration time to be an hour, then enter 60 in the Parameter Value field.
More Information
This is custom documentation. For more information, please visit SAP Help Portal. 3
8/6/26, 2:23 PM
1. First Level: Process View
Information Where?
Each payroll process Each of the lines below the Processes bar
Process instances of each process Each of the blocks in the calendar view on the right side of the
process name
Planned start and end date of each process instance In reference to the calendar bar. Current day is marked in blue
Execution status of a process instance (for example, In Process, Icon on the left of the header of each process instance
Completed, and so on)
Progress of each process instance Color of the progression bar of each process instance. This bar is
divided into blocks that represent the steps of each instance
Action How?
Reset the selection criteria to default ones Click the Reset icon on the selection bar.
Navigate to a different period of time Click the arrows on the left and right on the bar right above the
calendar bar.
2. Under the Calendar Size option, select the size you want.
2. Under the Start Day option, select the day you want.
Refresh the execution and error status of the processes Click the Refresh button in the right bottom corner of the screen.
This is custom documentation. For more information, please visit SAP Help Portal. 4
8/6/26, 2:23 PM
Action How?
Navigate to:
1. Click the header of a process instance block.
The process overview
2. Select the option you want.
The process overview starting with the process step group
currently in progress
If there are many process step groups in one process, all step groups are divided into several pages according to the screen
resolution. The arrows on the left and right side of the process step group boxes allow you to navigate to these pages.
This view provides the following information about each process step group and process step:
Information Where?
Planned start and end date of the process step group Progress bar on the process step group box.
Execution status Icon on the left side of the header of the process step group box
Number of days passed since the start date of the process step Progress bar on the process step group box.
group
Process steps:
Information Where?
Execution status Icon on the left side of the header of the process step box
Action How?
This is custom documentation. For more information, please visit SAP Help Portal. 5
8/6/26, 2:23 PM
Action How?
repeat the payroll for the employees whose master data has been
changed. To be able to run the payroll again, you must reset the
process step group.
You can see a split screen: On the left side, you can view activities possible in this step and on the right side the details of each of
these activities.
Activity Description
Execute If you click this activity, you see on the right side of the screen the
details involved in the execution of this step. After reviewing the
execution details, you can trigger the activities that are indicated by
the buttons on the right bottom corner of the screen. These
activities vary according to the type of step.
Status If you click this activity, you see the results of the execution of an
activity with additional information depending on the type of step.
Example
For the process step Open Payroll, you find information about
the background job status and the spool list, if there is any.
If the step has not been executed yet, you see the Not Specified
icon in blue.
When the status of a step is “green” (that means, it has been set to
OK), you must confirm the step in order to close it and move to the
next one.
Confirm Enables you to confirm a process step. When you confirm a process
step, the process step status changes to Closed. Only when a
process step is confirmed, can you start executing the next process
step.
This is custom documentation. For more information, please visit SAP Help Portal. 6
8/6/26, 2:23 PM
Activity Description
Action Log Shows all log entries created by the system and by the user.
The number of log entries is displayed on the left side of the screen,
beside the Action Log activity. On the top of the right screen you
can see a selection bar. If you click the options, you can change the
display of the log entries according to these criteria.
If you click one log entry on the right screen, you can see the details
of this log entry.
Example
The system detected that some salaried employees in the current period have a gross salary that is 10% above the gross salary
of previous periods. The payroll administrator needs to verify if this is right and eventually correct this.
Information Where?
Payroll process included in the tile Line above the title of the tile
Number of errors determined in the payroll process Number on the top right corner of the tile
Period of the related payroll process Line below the payroll process title
Action How?
Filter errors by a specific characteristic of the main entity Use the corresponding bar where all filter possibilities are listed
(Example: filter errors from payroll area US Salaried Employees
Monthly Payroll only)
This is custom documentation. For more information, please visit SAP Help Portal. 7
8/6/26, 2:23 PM
Action How?
Information Where?
Error count for each folder Top right bottom of the folder box
Error count for each check Number below the round icon of each check
Information Where?
Information Where?
Employee details In the Generic Overview tab page on the right hand side of the
screen
Check status Status icon beside the employee name on the left hand side of the
screen
Move your mouse to the icon to view the text explanation for the
icon.
Check details Click the check result detail tab, if any, next to the Generic
Overview tab.
This is custom documentation. For more information, please visit SAP Help Portal. 8
8/6/26, 2:23 PM
Action How?
Change the sort order and sort criteria of the employee list Use the sorting conditions in View Settings at the bottom of the left
hand side of the screen
Display details of one employee on the right side of the screen Click the employee
Set the error status of one employee to OK or Error Click the corresponding button in the bottom right side corner of
the screen
Example
After the first payroll run, the payroll process manager may want to verify the payroll results before continuing with the next
steps of the payroll process.
To make these checkpoints available, SAP delivers two process step templates as standard:
Prepare Verification
This process step template executes all defined checks that are relevant at a given time of the process.
Example
After the Run Payroll process step, the Prepare Payroll Data Verification process step is executed in order to update all
relevant payroll checks based on the latest results from the Run Payroll process step.
Verification
This process step template enables the payroll process manager to distribute the available check results to the individual
payroll administrators. This can be done using different criteria.
Example
In the process step Verify Payroll Data, the payroll process manager distributes the 50 errors resulting from the last
payroll run to 3 payroll administrators according to personnel area of the employees. As a result, payroll administrator 1
receives 10 errors; payroll administrator 2 receives another 10 errors, and payroll administrator 3 receives the remaining
30 errors. Once the 3 payroll administrators access the payroll control center for the payroll administrator, each of them
finds a new tile with the respective errors as distributed by the payroll process manager.
Distribute work packages (so-called worklists) of the found issues to payroll administrators so that they can work on
the resolution of these issues. The issues can be distributed to different payroll administrators according to different
criteria. Mostly the issues are related to employee data, and for these cases the standard solution allows the payroll
This is custom documentation. For more information, please visit SAP Help Portal. 9
8/6/26, 2:23 PM
manager to build work packages for payroll administrators according to, for example, the organizational assignment
of the employees.
Monitor the status of the resolution of the found issues which were allocated to the payroll administrators.
For the payroll administrator, a certain worklist of found issues has been assigned to him or her by the payroll process
manager. Details of the check’s errors and supporting evidences are provided for them to find the root cause. Then they can
either mark it as “OK” to indicate that it is a false alarm or correct the master data or configuration that causes the error.
Set to Manually OK
The payroll administrator sets this status if he or she believes that the error is reasonable and acceptable. When
setting the error status manually to OK, the payroll administrator has to specify a root cause reason.
Reset to Error
The payroll administrator sets this status if he or she has set an error to OK and now considers the error not
reasonable or acceptable.
The payroll administrator sets this status when he or she starts to correct the error. As a result, other payroll
administrators assigned to the same errors can skip this one. If the payroll process manager starts verification
again, the verification result of this status will still be treated as an error.
The payroll administrator sets this status when he or she finishes correcting the error.
The payroll process manager can re-execute the checks to see whether they are fixed and decide whether the payroll
process can be continued. When all the errors are set to Correction Finished or manually set to OK, the worklist status
turns to yellow in the Payroll Control Center for the payroll process manager. As a result, the payroll process manager
knows that the correction is complete and that he or she can perform the verification again. And if all issues have been
solved, the payroll process manager confirms the step in the Confirm process step activity.
Example
In the standard delivered template, you will find two kinds of data verification: master data verification and payroll data verification.
A validation process group for master data is composed of two steps: Prepare Data Verification and Verification.
The Prepare Data Verification step is where the payroll process manager triggers the execution of the checks at the backend.
The Data Verification step is where the payroll process manager will distribute the issues work-lists to payroll administrators and
monitor the resolution of the issues.
In the steps’ configuration, it is specified which group of checks needs to be executed and monitor. This allows organizing different
checks to different processes accordingly.
To execute this step, the payroll process manager is already at the third level of his or her user interface.
When the payroll process manager executes this step, he or she can only see the relevant checks that are executed and if there are
no errors or exceptions during the execution of these checks. Based on this, payroll process managers can set this step to status
OK. Setting the status to OK in this step means: The execution of the checks was successfully finished. Setting the status to OK
This is custom documentation. For more information, please visit SAP Help Portal. 10
8/6/26, 2:23 PM
does not depend on if there were issues found on employee’s master data or not. An example of “Not OK”status for this step is, for
example, when the check instances to be executed depend on a secondary database connection, and this connection was broken
during the checks execution.
Within the Status activity, in the Job Result tab page, the payroll process manager can review the execution status, and set the
status to OK.
In the Check errors tab page, the payroll process manager can review the number of issues found per payroll area. The error count
on a higher level allows payroll process managers to identify major execution errors, for example, if an uncommonly high number
of errors were found on the current run, or if no errors at all were found when some should already be expected. Before continuing
to the next step, the payroll process manager has to set this status to OK as well.
After the statuses are set to OK and this step is confirmed, the payroll process manager can jump to the next step of this step
group (Data Verification) and distribute the error findings to payroll administrators.
On the Execution activity of this step, the payroll process manager can choose a set of payroll administrators to assign the worklist
to. Default worklists will be automatically proposed taking into account the state from the previous process instance (e.g. from the
last payroll period).
Once the payroll process manager has assigned all worklists, he or she sends these worklists to the corresponding payroll
administrators (Submit worklist button in the bottom-right corner of the screen).
By submitting the worklist, the payroll process manager can see the error count distribution for each worklist in the Status
activity.
Now the payroll administrators can log into their own payroll administrator’s view to see the list of errors they need to resolve.
Meanwhile, the payroll process manager can monitor the status in the payroll process manager view.
By clicking a tile, the payroll administrator navigates into the folders view.
Further in the detail view, the payroll administrator can see the root cause of why, for example, the employees failed the check. In
this way, the payroll administrator can decide either to correct the master data based on the evidences and keep the status as
error, or to manually set the employee’s issue to OK (to indicate that this is a false alarm).
When all the errors are set to Correction Finished or manually set to OK, the worklist status turns to yellow in the Payroll Control
Center for the payroll process manager. As a result, the payroll process manager knows that the correction is complete and that he
or she can perform the verification again. And if all issues have been solved, the payroll process manager confirms the step in the
Confirm process step activity.
This is custom documentation. For more information, please visit SAP Help Portal. 11
8/6/26, 2:23 PM
The Payroll Control Center is an application based on two frameworks: the payroll data source framework and the process
framework on top. The process framework uses the payroll data source framework in some aspects. The payroll data source
framework contains process modeling, management of checks and the Applications Programming Interfaces (APIs) that are
necessary to handle the backend applications. Both frameworks can be extended and modified to adapt to customers, countries,
and business needs.
Furthermore, SAP provides process templates that include process groups and process steps. You can use these standard process
templates or create new ones by using ABAP object classes. The same applies to checks.
In the following sections these entities are described in a more technical and detailed way.
Data Sources
Data sources are used to model steps of a payroll process. The statement “I am responsible for checking instances A, B, C” can
then be translated into “I am authorized for data sources X, Y, Z”, where data source X covers the required functionality of check
instance A.
Example
Employees assigned to payroll area UM, having a claim in payroll period May 2013.
Data provided:
List of selection parameters (Payroll Area UM, Payroll Period May 2013)
For each employee, list of relevant wage types from the payroll result, like total gross, statutory and other deductions,
claim amount.
An operation could be performed on the data, for example, to set the status of an employee to “OK” in case that the claim correctly
occurs.
When you implement a data source type, a result object list is calculated. This calculation is made out of the following:
The input parameter values that provided by the input parameter types
The result list that is reflected by the result details type. This list contains additional information to the result
This is custom documentation. For more information, please visit SAP Help Portal. 12
8/6/26, 2:23 PM
Example
Data Source Type “Employees with Claim”
Payroll Area: the value for this parameter has to be fixed by the customer when configuring the payroll process
Payroll Period: the value of this parameter is flexible and depends, for example, on the status of the payroll area
control record in the production system.
Personnel Number
(Category: Data) List of amounts for total gross, statutory deductions, other deductions, claim
Use
In order to classify Data Source Types, Data Source Classes are used. Data Source Classes combine a certain list of Data Source
Types. It is also possible to classify a data source class in folders. That means, create a hierarchical structure where the data
source types are classified in folders and the folders are contained in one data source class.
Data Source Classes are delivered by SAP as well as by partners, and they can be extended and created in customer systems.
Example
A Data Source Class consists of Data Source Types that reflect checks on payroll results. The Data Source Types are
grouped in folders.
This is custom documentation. For more information, please visit SAP Help Portal. 13
8/6/26, 2:23 PM
A Data Source class that builds payroll process steps of a US regular payroll. One of the steps in the step group “Payroll” is
reflected by the “Checks on Payroll Results” Data Source Type. This one mainly allows to monitor the status of the finer-
granular work covered by Data Source Class “Checks on Payroll Results” shown in the first example. It also allows opening a
detailed user interface (Payroll Control Center) that displays the details of the connected Data Source Class.
This is custom documentation. For more information, please visit SAP Help Portal. 14
8/6/26, 2:23 PM
Use
By using Data Source Instances, you can decide to use a Data Source Type for a specific entity value, for example, using the Data
Source Type “Employees with claims in payroll area UM” for payroll area UM.
Authorization is an important aspect when talking about Data Source Instances. You can assign authorizations to access Data
Source Instances to specific users.
Example
Referring to the example in section Data Source Classification, this would allow formulating the following requirements:
Users A, B and C are responsible for performing the checks on payroll results for payroll area UM.
This is custom documentation. For more information, please visit SAP Help Portal. 15
8/6/26, 2:23 PM
Users A and B get authorization for Data Source Class “Checks on Payroll Results”.
User A gets authorization for Data Source Instance “Gross Deviation greater than expected for payroll area UM”.
User B gets authorization for Data Source Instances “Employees with Claim in payroll area UM” and “Errors in Regular
Payroll Run for payroll area UM”.
User C gets authorization for Data Source Class “Regular US Payroll Process”and for Data Source Instance “Checks on
Payroll Results for payroll area UM”.
If User C needs to access the details of the checks on payroll results, he or she also gets authorization for Data Source
Class “Checks on Payroll Results” and the corresponding Data Source Instances for payroll area UM.
This authorization concept allows modelling payroll processes using generic entities and to assign certain steps for specific
selection criteria to individual users (or user groups). This, in turn, enables generic (user interface) consumers to show users
exactly the objects they are authorized and responsible for. And the assignment of users to tasks and objects is done directly.
Use
A data source result is the result of a calculation of a data source type for the input parameter values configured in the
corresponding data source instance, plus values for further mandatory input parameters types that have not been specified by the
data source instance.
It is possible to mark certain input parameter types as key fields. Each combination of key fields can have an own data source
result. Changing non-key fields and keeping the values of all key fields does not create a new data source result.
Example
For a data source instance like “Employees with claim in payroll area UM”, you need to specify the input parameter “payroll area
UM”. But the list of employees that have claims differs between different periods. This is solved by using the additional (mandatory
but not necessarily fixed) input parameter “Period”.
If you want to express this in terms of data source framework concepts, you would have the following explanation:
The list of employees with claims for “payroll area UM”, period May 2013 is the list of result objects of parameter type “Personnel
Number” that are calculated by the data source type “Employees with claims” when using “Payroll Area UM” and “Period May
2013” as input parameter values.
All the mandatory input parameters values that are necessary to calculate or build the result.
Lists of result objects, represented by the result parameter types of the corresponding data source type. These lists are
returned as a result of calculating or building the data source type using the above mentioned list of mandatory input
parameter values.
Data source results and its subentities are the keys that allow assigning status, workflow, and so on to concrete data source types.
This is custom documentation. For more information, please visit SAP Help Portal. 16
8/6/26, 2:23 PM
Use
Usually, when talking about a payroll process, we need one main selection entity like a group of employees for which payroll is run
together (for example, “Payroll Area”, “Company”, “Legal Employer”, and so on.) Additionally, the data that the payroll process uses
refers to a certain period of time, like the payroll period (a month, a week, etc.), a quarter or other kind of period. This leads to the
introduction of the following two concepts:
This is the main selection entity type that is used for a certain payroll process type, for instance the Payroll Area is used for
performing the preparation and calculation of the regular payroll results.
The Instance Selection Parameter Type is assigned to a Data Source Class and tells a generic consumer how the individual data
source types and instances can be configured. In particular it can be assumed that the programs performing the individual process
steps understand values of that type as input data – or at least a mapping exists between Instance Selection Parameter values and
the input data such a program is able to deal with.
This is the entity type that describes the period of time relevant for a certain payroll process instance. For example, this can be a
payroll period for which a regular payroll calculation runs.
The Time Selection Parameter Type is also assigned to the Data Source Class and tells a generic consumer how data source
results are created. Again it can be assumed that the programs performing the individual process steps understand values of that
type as input data – or at least a mapping exists between Time Selection Parameter values and the input data such a program is
able to deal with.
Example
A Data Source Class has Instance Selection Parameter Type “Payroll Area”and Time Selection Parameter Type “Payroll Period”The
Data Source Types assigned to that Data Source Class have to have Payroll Area and Payroll Period as input parameter types.
A Data Source Instance representing the regular payroll run for a given payroll area AB would specify “Payroll Area = AB” in its
input parameter list.
The regular payroll run for payroll area AB and period 01.2014 would then be the Data Source Result for that Data Source Instance
which additionally specifies “Payroll Period = 01.2014” as input parameter value. If there is additionally configuration to derive the
program name and some other administrative information, it is possible then to generically start that program with the given
selection (Payroll Area = AB, Payroll Period = 01.2014) without the need to modify that program or to even write coding specifically
for executing that program.
Note
This configuration is explained in more detail in SAP Note 1995698.
1. Define Parameter Types and Result Details Types: These are required before a Data Source Type can be configured.
2. Create Data Source Type: The data source type view will indicate a runtime ABAPclass which will contain the business logic
(and also the logic for displaying the issues root-cause) for the check. The runtime classes linked to the Data Source Type
inherit predefined interfaces from a set of base classes. Methods “Execute” and “Result_details_get” of these interfaces are
the ones responsible for the check’s logic and displaying the root cause. They have to be implemented according to each
check’s use case.
4. Define Data Source Instances: In the data-source instance view, the data source type is linked to an instance. In this
instance the parameter values for the execution are specified.
Note
As of EA-HRRXX 608 SP25, you can use the Generate Process Context (PYC_GENERATE_PROCESS_CONTEXT) report
to automatically generate data source instances instead of having to manually define each check instance. For more
information, see Generating Process Context.
As of EA-HRRXX 608 SP25, you can use the Generate Process Context (PYC_GENERATE_PROCESS_CONTEXT) report to
automatically generate data source instances instead of having to manually define an instance selection parameter (typically
ABKRS Payroll Area) for each check instance.
Example
Previously if a payroll process XX has been assigned 4 check types. You must manually define the check instance for each
check type (data source type with category DF (Default Category Check Type). If each check type has 2 input parameters, you
must also manually define the value of each of the input parameters for the corresponding check instance. This means you
must define the input parameter values 8 (4x2=8) times for payroll process XX.
Now you can use this Customizing activity to generate process context, and hence the check instances, for the payroll process
XX at one click.
You can also use this report to check whether the Customizing in your system has been done correctly: if there is anything
incorrect configuration for the process in Customizing, this report does NOT generate any check instances and displays the
relevant error log.
For more information, see the system documentation for the Customizing activity Generate Process Context under Customizing
for Payroll Payroll: International Payroll Control Center Payroll Process Management .
This is custom documentation. For more information, please visit SAP Help Portal. 18
8/6/26, 2:23 PM
Step Template
The step template represents a business operation step. It can start a report in backend job or just remind that some operations
should be done “offline”. There are three types of step templates:
Asynchronous batch step which will start one or more reports as background job(s).
Synchronous step which will start one or more task and return results immediately.
The template behavior (business logic) depends on its run time class (ABAP class) implementation and the parameter types used
for input and result.
Use
Input parameter
Result parameter
UI Category attributes
Structure
Input parameter
Input parameters contain all necessary information needed to notify the step to run. For instance, the report name which needs to
be started in the step and the variant which should be used.
Result parameter
Result parameters record the step execution’s results. When a job is submitted by a background job, the step needs to answer the
following questions:
Example
This is custom documentation. For more information, please visit SAP Help Portal. 19
8/6/26, 2:23 PM
A background job generally has three result objects:
Result status
Result details types are always assigned to a given result object and give information about how to process the result object
(operation) or what kind of information should be shown (displaying data for that object).
UI Category Attribute
A UI Category defines either the UI technology for building the UI, for example, SAPUI5 or SAP GUI, or the data service for the UI
that gets data from the backend, for example, OData.
UI category attributes define the configurable elements of the UI. UI category attributes are used to replace the standard views by
specialized ones, for the Execution view as well as the sub status views and others.
Although most steps share the same default view (that is, the structure how data is presented), it can be useful to specify a
different view for a step. When the user clicks on the activities on the left within a step, the framework calls a Business Server Page
(BSP) component that is displayed on the right side. These components are configurable. That means, that you can configure your
own HTML views on the BSP pages and they can be displayed on the step.
While configuring this, you can specify the location of the BSP component of the step.
This is custom documentation. For more information, please visit SAP Help Portal. 20
8/6/26, 2:23 PM
Process Template
Step templates can be combined in certain groups and in a certain order to form a process. This is called a “process template”. It is,
for example, possible to create a “regular payroll process template” which is used throughout the year and a “year-end payroll
process template” which is used toward year’s end. The process template can be time-dependently assigned to a payroll process.
Finally it is necessary to have several instances of a process, one for each payroll period.
The following picture illustrates the idea of a process template assigned to processes:
This is custom documentation. For more information, please visit SAP Help Portal. 21
8/6/26, 2:23 PM
A payroll process does not only consists of the steps involved in running payroll itself, but also preliminary steps like master data
maintenance, where it might be necessary to run some data preparation programs like pay scale updates, for example, and also of
many subsequent steps like legal reporting.
Legal reporting steps are often not related to a payroll area in terms of employee reporting grouping but rather to legal entities like
Tax Company or Company Code. Therefore, such steps cannot be included in the same payroll process which runs by payroll area.
The following picture illustrates how a “payroll area process” and a “company code process” might interact from a calendar
perspective. Note that the employees from payroll areas A1 and A2 can be included in the process of company code US01.
Therefore, the processes have to be synchronized (based on the date configuration of their process instances) towards day 20 on
the calendar below, because the legal reporting of company code US01cannot start before the payroll areas A1 and A2, which have
different periodicities, are closed and finished for the periods that belong to July:
This is custom documentation. For more information, please visit SAP Help Portal. 22
8/6/26, 2:23 PM
Example of Payroll Area Process and Company Code Process in Calendar View
Note
View clusters start with prefix VC_*, while maintenance views start with prefix V_*.
This is custom documentation. For more information, please visit SAP Help Portal. 23
8/6/26, 2:23 PM
Each view cluster and maintenance view has a step in Customizing for Payroll Control Center under Payroll Payroll
International Payroll Control Center l . The following list shows the sequence of the Customizing steps that corresponds to the
view clusters and maintenance views mentioned in the previous graphic:
Reports
You can find the following reports in the area menu under Human Resources Payroll International Tools Payroll Data
Source Framework and Payroll Control Center.
The following list contains only general information about each report. For more information, refer to the online documentation for
each one of them:
This is custom documentation. For more information, please visit SAP Help Portal. 24
8/6/26, 2:23 PM
Execute Data Source Instances (PYD_EXECUTE_INSTANCES)
You use this report to execute all data source instances selected. Normally, this report will be triggered automatically by the payroll
control center steps. It can also be manually started depending on the use case.
You use this report to delete expired sessions, the corresponding user variants and details. User variants are created for each UI
session. The expiring period is defined by default 2 hours, or taking the value from user parameter PYD_USER_SESSION_EXP. It
is also possible to schedule a regular job with this report to clean the expired session’s data in their system.
You use this report to delete all data source instances selected and the log related to each data source instance.
You use this report to generate process steps for a process. You are required to do so before you can generate process instances
for the same process.
For example, in Customizing for Payroll under Payroll: International Payroll Control Center Payroll Process Management ,
you have defined a process “Regular Payroll for Payroll Area California” and a step template “Master Data Verification” in this
process. You then use this report to generate the steps for this process. In this case, the report generates a process step “Master
Data Verification” for “Payroll Area California”
This is custom documentation. For more information, please visit SAP Help Portal. 25
8/6/26, 2:23 PM
The report generates an authority ID, which is used by the authorization object P_PYD_INST (Payroll Data Source Instances) for
granting authorizations on a process. For more information about the authorization object, see Payroll Data Source Instance
(P_PYD_INST).
You use this report to generate payroll process instances. A process instance is a process for a given payroll period which is based
on a certain process ID which is assigned to a process template. With this report you can better specify the date intervals of each
step group. These dates will appear on the calendar screen on first level of the user interface for payroll process managers.
You use this report to customize the texts displayed on the front-end user interface of each process step of the Payroll Control
Center. The texts you define in this report will overwrite the texts delivered in the code.
The front-end SAPUI5 user interface of Payroll Control Center provides the action only in the step view of each process instance.
For the purpose of administration or auditing, however, a central place for viewing all the action logs is needed.
Payroll Process Manager or consultants can use this report to query the payroll process action log and download the query result
in an Excel file for further processing.
Authorizations
In order to use the Payroll Control Center, you have to check the following authorizations:
Furthermore, take into account that you also need to check the authorizations needed for the backend applications. For example,
users will need to have all required authorizations (for payroll results or personnel numbers, for example) to execute the
corresponding reports in the back end.
This is custom documentation. For more information, please visit SAP Help Portal. 26
8/6/26, 2:23 PM
Payroll Data Source Instance (P_PYD_INST)
Definition
Using this authorization object, you can control which processes are displayed in the Payroll Control Center of a user and which
actions the user can execute on processes, process step groups, and process steps.
For more detailed information about the authorization objects and their fields, see the system documentation that is accessed, for
example, by calling the Maintain Authorizations Object (su21) transaction.
Example
Values for a user who only has read access to a process and the action logs of the process:
P_PYD_INST: PYP_PI_PYP_X0_TEST
P_PYD_IAUT: R,H
P_PYD_RDT: <empty>
Values for a user who is allowed to perform all process activities but not able to confirm reset or lock anything. The user has
no read access to the action log:
P_PYD_INST: PYP_PI_PYP_X0_TEST
P_PYD_IAUT: R,E,D,L
P_PYD_INST: PYP_PI_PYP_X0_TEST
This is custom documentation. For more information, please visit SAP Help Portal. 27
8/6/26, 2:23 PM
P_PYD_IAUT: *
P_PYD_RDT: *
Note
Process authorization is granted based on the whole process, not for subentities like process steps. Therefore, a process gets a
unique data source instance assigned (in the example, PYP_PI_PYP_X0_TEXT) that is used to hold status information on
process instance and step group instance level and that is the anchor for the authorization checks.
More Information
Authorizations for Human Resources
Definition
This authorization object allows a user to maintain user variants for other users.
ACTVT The authorization object is used for the data verification steps. The
payroll manager needs to have value 01 for maintaining worklists.
For more detailed information about the authorization objects and their fields, see the system documentation that is accessed, for
example, by calling the Maintain Authorizations Object (su21) transaction.
More Information
Authorizations for Human Resources
Integration
The main concept of the Authorization Framework is the authorization type. The authorization type is a technical vehicle that
carries information about how the authorization checks on PERNRlevel are parameterized. The authorization type ensures that the
data from the standard HR authorization objects, such as P_ORGIN and the structural authorization profiles from the
Organizational Management component are properly inherited into the Payroll Control Center. This means that you must ensure
that these standard HR roles and authorization objects are set up properly for all payroll users.
Example
Depending on their standard HR roles and your settings for authorization types, the payroll users assigned to the same check in
the Payroll Control Center see different check results:
A payroll administrator is authorized for the Basic Pay (0008) infotype at the US organization level. This user sees
exceptions for 200 employees for the severance payments checks in the Payment Control Center.
The payroll administrator responsible only for employees in the Detroit location sees only 10 employees for the same
checks in the Payment Control Center.
Activities
To cover as many of your organization-specific requirements for the payroll process as possible, the Authorization Framework is
designed as a flexible tool that allows you to create and build the check-specific permissions specific to your own business
process. The following table summarizes the important settings that you should make to ensure that users have the relevant
authorizations to the checks they want to execute during the payroll process.
Settings that impact what users can Required setup checks Location for defining settings
access in the Payroll Control Center
Authorization level The use of authorization levels optimized Customizing for Payroll under Payroll
the performance of the Payroll Control International Authorization Framework
The authorization level allows you to define
Center. For example, a payroll manager Define Authorization Level
how the authorization interface behaves or
may be allowed to view the checks results
is used by the Payroll Control Center for a
for thousands of employees, while a payroll
given group of users.
administrator may only be allowed to view
50 employees. If the appropriate
authorization levels are assigned to each
(for example, by choosing a level that
permits database indexing of
authorizations for the manager), then the
authorization checks can be optimized.
Authorization type Ensure that the authorization types reflect Customizing for Payroll under Payroll
the required objects for which the International Authorization Framework
An authorization type is a collection of
authorizations must be checked against, Define Authorization Type
infotypes and other HR objects for which
for example, the infotype Basic Pay
an authorization check is performed. A
(0008). A combination of profiles and
Payroll Control Center check can use a
authorization levels must be assigned to
given authorizations type, that operates
the authorization type.
like a filter, to define the data to which
users are not allowed access. An
authorization type can be used by several
different applications.
Authorization set ID Ensure that you make the necessary Customizing for Payroll under Payroll
settings for your authorization objects and International Authorization Framework
This is custom documentation. For more information, please visit SAP Help Portal. 29
8/6/26, 2:23 PM
Settings that impact what users can Required setup checks Location for defining settings
access in the Payroll Control Center
BAdI: Authorization Controller Adapt authorization levels assigned t users Customizing for Payroll under Payroll
and authorization types to your needs. International Authorization Framework
BAdI: Authorization Controller.
To ensure that users can see the employees found by a check for which they are authorized in the Payroll Control Center, the
authorization type acts as a link between the Authorization Framework and the Payroll Data Source Framework. You must assign
the authorization types to the corresponding data source types. .
In addition to making these Customizing settings, you can also track your authorization configuration for specific checks and test
it with the following reports:
To access the HR Authorization Administration tab page, choose, on the SAP Easy Access screen, Payroll
International Tools Authorization Framework Start the HR Authorization Administration . Alternatively, you can
use the HR_TR_AUTH_V_ADM transaction.
To access the Person to User Authorization Assignment Extractor tab page, choose, on the SAP Easy Access screen,
Payroll International Tools Authorization Framework Person to User Authorization Assignment Extractor .
Alternatively, you can use the HR_TR_AUTH_EXTRACTOR transaction.
To access the Test Authorization Tool tab page, choose, on the SAP Easy Access screen, Payroll International Tools
Authorization Framework Test Authorization Tool . Alternatively, you can use the HR_TR_AUTH_TESTER transaction.
The concepts of authorization type and authorization level are directly or indirectly assigned to users, according to your settings.
The authorization object Check actions user is allowed on PCTR Authorization concept (P_PCTR_AUT) allows a fine-grained
control on the allowed authorization types and level for a user.
You can also determine if a user is allowed to read and update their own user information or that of another user, as listed below:
P_PCTR_USR (Action on own user/other user) You can select the following actions:
On own user
On other users
P_PCTR_TYP (Authorization Type) Same selection as the options for the authorization level
This is custom documentation. For more information, please visit SAP Help Portal. 30
8/6/26, 2:23 PM
Use
By using this authorization object, you can control which tiles are displayed in the worklist for a user on the user interface.
For more detailed information about the authorization objects and their fields, see the system documentation that is accessed, for
example, by calling the Maintain Authorizations Object (su21) transaction.
More Information
Authorizations for Human Resources
Use
If you use this authorization object, you can control the access to the check results that are displayed on the user interface (for
example, the results for a check if any employees have retroactive calculations) and allow the user to perform certain actions on
these check results, for example, changing the status.
This is custom documentation. For more information, please visit SAP Help Portal. 31
8/6/26, 2:23 PM
For more detailed information about the authorization objects and their fields, see the system documentation that is accessed, for
example, by calling the Maintain Authorizations Object (su21)transaction.
More Information
Authorizations for Human Resources
Glossary
Use
The following list provides definitions of terms that are used within the Payroll Control Center documentation:
Term Definition
Example
Show all salaried employees with an increase of %10 in their
gross payment.
Payroll process The sequence of all steps that are required to execute payroll and
all related activities (for example, legal reporting) in an
organization.
Example
Typical examples for steps included in a payroll process are:
master data validation, running payroll, issuing the
remuneration statement, transferring data to Accounting, and
creating DME files for bank transfer or check printing, and legal
reporting.
Payroll process instance Defines a payroll process for a sepcific entity and period.
Example
Payroll process instance for November of the current year and
payroll area AB.
Step group All steps that are required to execute one specific task within the
payroll process.
This is custom documentation. For more information, please visit SAP Help Portal. 32
8/6/26, 2:23 PM
Term Definition
Example
Create, release and post posting document are three steps
within the step group Postingto transfer payroll results
information to Accounting.
Tile A user interface element that contains the check results for a
specific checking step, a specific main entity, and a specific period
that the user has authorization for.
Example
A tile that contains the check results after the payroll run for
payroll area AB and payroll period 01 in the current year.
More Information
For more information about SAP terms and their definitions, refer to [Link] .
This is custom documentation. For more information, please visit SAP Help Portal. 33