Agenda

Disclaimer
Storing payroll results in a cluster
The information in this presentation is confidential and proprietary to SAP and may not be disclosed without the permission of SAP.
Except for your obligation to protect confidential information, this presentation is not subject to your license agreement or any other service or
Declustering
subscription:agreement
purpose, prerequisites
with and settings
SAP. SAP has no obligation to pursue any course of business outlined in this presentation or any related document, or to
Declustered payroll results
develop or release any functionality mentioned therein.
This presentation, or any related document and SAP's strategy and possible future developments, products and or platforms directions and functionality
as prerequisites
Generating forresults
and Storing declustered payroll
are all subject to change and may be changed by SAP at any time for any reason without notice. The information in this presentation is not a commitment,
promise or legal obligation to deliver any material, code or functionality. This presentation is provided without a warranty of any kind, either express or

implementation of SAP
implied, including but not limited to, the implied warranties of merchantability, fitness for a particular purpose, or non-infringement. This presentation is
for informational purposes and may not be incorporated into a contract. SAP assumes no responsibility for errors or omissions in this presentation, except
Test payroll results posting simulation (Cluster XT)
Payroll Control Center
if such damages were caused by SAP’s intentional or gross negligence.
All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ materially from expectations. Readers
are cautioned not to place undue reliance on these forward-looking statements, which speak only as of their dates, and they should not be relied upon in
Declustered Payroll Results Management Tools
making purchasing decisions.

Public

Public Public 3 2

1
Storing payroll results in a cluster

Public

2
 SAP HCM Payroll solution

Public 5

The traditional SAP Payroll solution, often referred to as SAP ERP HCM Payroll, is a
comprehensive and robust payroll management system designed to handle the complexities
of payroll processing for organizations of various sizes. Here are the key features of the
traditional SAP Payroll solution:
1. Global Payroll Capabilities:
•Localization for Multiple Countries: Supports payroll processing in over 50 countries,
including compliance with local tax laws, social security regulations, and reporting
requirements.
•Multi-Country Payroll Management: Allows organizations to manage payroll across different
countries with a unified solution, handling currency conversions, local regulations, and
reporting needs.
2. Accurate Payroll Processing:
•Automated Payroll Calculations: Automates the calculation of wages, taxes, deductions,
bonuses, and other payroll elements based on predefined rules.
•Support for Complex Payroll Scenarios: Handles complex payroll scenarios such as
retroactive payments, off-cycle payroll runs, and multiple payroll frequencies.
3. Integration with Financials: Connects with SAP Financials (FI/CO) for automatic posting of
payroll results to the general ledger, ensuring accurate financial reporting.
4. Data Management and Security:
•Payroll Data Clustering: Stores payroll results in clusters to optimize performance and
manage large volumes of data effectively.
•Secure Data Handling: Provides robust data security features to protect sensitive payroll
information and ensure compliance with data protection regulations.
5. Customization and Flexibility:
•Configurable Payroll Schemas: Allows customization of payroll schemas and rules to align
with specific organizational needs and policies.

3
 Storing payroll results in a cluster
Transaction se16n

Transaction pc_payresult

Public 6

•Custom Wage Types: Enables the creation of custom wage types to handle unique pay
elements such as specific allowances, deductions, or bonuses.
The main reason for using a cluster to store payroll results in SAP HCM Payroll is performance optimization and data
integrity.
Key reasons include:
• Efficient Data Management: Payroll data involves complex calculations and large volumes of information, such as
earnings, deductions, taxes, and benefits, often spread over multiple periods. Storing this data in a cluster format
helps manage it efficiently by organizing related data together.
• Performance Optimization: Clusters are designed to handle large datasets with high efficiency. By storing payroll
results in clusters, the system can quickly retrieve, process, and update payroll data, leading to faster payroll runs and
improved system performance.
• Data Integrity and Consistency: Payroll processing requires a high level of accuracy and consistency. Clusters ensure
that related payroll data is stored together in a consistent manner, reducing the risk of data corruption or
inconsistencies during payroll runs.
• Historical Data Storage: Payroll clusters are used to store historical payroll results, which are essential for audit
purposes, retroactive calculations, and legal compliance. This allows organizations to easily access and analyze past
payroll data.
• Support for Complex Payroll Scenarios: Clusters enable the system to manage complex payroll scenarios such as
retroactive payroll processing, where payroll results from previous periods need to be recalculated and adjusted.
• Security and Data Protection: Payroll data is sensitive and requires secure storage. Clusters in SAP HCM are designed
to protect payroll data, ensuring that only authorized personnel can access or modify payroll results. In summary,
clusters provide a robust, efficient, and secure way to manage payroll results in SAP HCM Payroll, ensuring that the
system can handle large volumes of data and complex payroll calculations while maintaining performance and data
integrity.
While storing payroll results in clusters in SAP Payroll offers many advantages, there are also some potential disadvantages:
Disadvantages of Storing Payroll Results in Clusters:
• Complexity in Data Access: Payroll data stored in clusters can be more complex to access and analyze compared to
data stored in standard database tables. Specialized knowledge is often required to extract and interpret the data,
which can be a challenge for users who are not familiar with SAP’s cluster structures.
• Limited Reporting Flexibility: Due to the complexity of the cluster structure, generating custom reports directly from
the cluster data can be difficult. Users often need to rely on predefined reports or use specific tools like SAP Query or
custom ABAP programs to access the data, which can limit flexibility.
• Difficulty in Data Recovery and Troubleshooting: Recovering data from clusters in case of errors or corruption can be
more difficult compared to standard database tables. Troubleshooting issues within clusters often requires deep
technical knowledge of SAP’s payroll engine and data structures.

4
• Dependency on SAP-Specific Tools: Accessing and managing payroll data in clusters often requires the use of SAP-
specific tools and expertise, which can be a limitation if the organization wants to use third-party tools or integrate
with non-SAP systems.
In summary, while clusters in SAP Payroll provide powerful and efficient data management for payroll processing, they also
introduce complexities in data access, reporting, and maintenance, requiring specialized knowledge and tools to manage
effectively.
System table T500l, where it’s possible to check cluster ID used for particular
country-specific versions.

Structure for payroll results: cluster directory

Transaction pc_payresult

Transaction se11

5
 Cluster ID for country specific payroll solution
Transaction sm30 Table T500L Transaction pecluster

……..

Note. The table T500L is for reference only. Don’t make any changes there.

This is a system table, which means that all records in it belong to SAP, and no
changes from the customer's side are implied in this table. Therefore, this table
was not included in Implementation Management Guide (IMG). To set up
declustering, it is important to know where to get information about the cluster
ID for a particular country.

6
Structure for payroll results: International

Transaction se11

Transaction pc_payresult

7
Declusteringpurpose, prerequisites and settings

Public

8
The traditional SAP Payroll solution is known for its robustness, flexibility, and ability to
handle complex payroll requirements, making it a popular choice for large, multinational
organizations. However, it is also recognized for its complexity and the need for experienced
SAP professionals to manage it effectively.
Payroll Control Center (PCC): Provides a centralized platform to monitor payroll
processing, manage validations, and address errors before payroll is finalized. It leads to
improved quality, reduced processing time, less stress, and will ultimately allow the
payroll to focus on strategic work in other areas such as new projects to cut out manual
activities
Payroll Control Center is the fully automated system. It represents the next
generation of payroll processing automation.
The Payroll Control Center has three components.
• A state-of-the-art user interface which simple to use, intuitive so that people
can do their job fats and efficient.
• The Payroll Control Center Core automate the complete end-to-end payroll
process, enables real time identification of all policy deviations and pushes
them actively to the right people.
• And finally, the “know how component” which holds the logic that
automatically finds the payroll issues.
Payroll Control Center automatically finds the policy violations in real time and
pushes them to the right people.
And last not least, with the help of Payroll Control Center, payroll is available at
any time and not just during the critical path.

9
 Prerequisites for
DeclusteredPayroll Results.

Prerequisites forDeclusteredPayroll Results.

Business functions that needs to be activated via transaction SWF5:
HCM_LOC_CI_50
OR
separate business function that needs to be activated for Concurrent Employment
Declustering
HCM_LOC_CI_75
AND
HCM_LOC_CI_63

Declustering Country-Specific Settings

Table V_T77DCT_OPTION
Table V_T77DCT_REG

Prerequisites for Payroll Control Center implementation is Payroll Results

Declustering
The slide lists the business functions that need to be activated for two
alternative SAP payroll solutions(single employment (SE) and concurrent
employment (CE)

10
Activating these Business Functions is a mandatory prerequisite for configuring
and using the declustered payroll results.
The Declustering functionality is not new – (available since EHP4); what is new
is the creation of pre-payroll declustered results, making PCC Validations
possible during monitoring step.
After activating the corresponding business functions, a new configuration steps will appear in the IMG. The
system needs to provide additional information for the declustering of payroll results. This is why the steps
shown on the slide were added in IMG.
There are two options for storing declustered payroll results :
• Ability to set DB connection. For example, declustered payroll results can be stored in a separate
database.
Then, it’s necessary to define how the declustered table will be filled (second setting):
• Immediately upon completion of the payroll processing, the payroll results will be exported to the
cluster and to declustered tables at the same time
• Or using a special report that runs as needed.
Then, defining what payroll result tables need to be declustered is necessary
Country Specific Declustering
There are several internal tables for storing different information connected with payroll results. In this step, it’s
necessary to define which tables must be stored in declustered format. It is important to understand that
storing declustered payroll results requires significant memory, and you should only use tables that are truly
needed for the validation rules and KPIs. Of course, the payroll results (RT) table is the most important. But for
various checks, you may need some additional tables.
Payroll Results Declustering: P2RX_EVAL_PERIOD

11
 Country-Independent Declustering Settings

Table V_T77DCT_OPTION Table V_T77DCT_REG

Generating and Storingdeclustered payroll results

Public

It is necessary to perform not only country-specific settings for declustering the

payroll results but also country-independent settings Make sure to declustered
tables P2RX_EVAL_PERIOD and P2RX_TPY_EVAL_P.
The meaning of the settings is the same as for country-specific settings, but in
this case, setting up declustering for a country-independent table
P2RX_EVAL_PERIOD must be done explicitly, otherwise, declustering cannot be
performed due to the technical features of storing payroll results

12
 Declustered Payroll Results
Transaction se16n Table PCL2

Transaction PC_PAYRESULT

Table P2RX_RT
Transaction se16

RCA: Payslip based on the productive payroll results

Public 20

Payroll Results Declustering: Myths & Misconceptions

● The Declustering functionality is not new – (available since EHP4), what is new is the creation of
pre-payroll declustered results, making PCC Validations possible during monitoring
● You do not need to decluster ALL Payroll tables
● You do not need to decluster PAST Payroll tables
● Declustering does NOT replace clustered payroll results
● Declustering will NOT affect existing payroll reports and results

13
 Payroll ResultsDeclustered Tables

Table HRDCT_TPY_RGDIR

Payroll Results Declustering: Table P2RX_RT

Difference between test and productive payroll results storing concept

Productive payroll results directory Test payroll results directory

Table HRPY_RGDIR Table HRDCT_TPY_RGDIR

SEQNR in productive range:

-99000
1 SEQNR in test range: 99001
-99999

Only the last payroll execution –(last

period)
in is stored in the test result directory. Every new execution
causes the table entries (for the selected employees) to be deleted and recreated. The entries that
correspond to the productive rows from HRPY_RGDIR are copied to the test payroll result directory so that
the chain of periods for each employee is completely contained in the test payroll result directory. This
allows the period evaluation to take place by analyzing the test directory as if it were the productive
directory, without the need for complicated comparisons between 2 different directories.

Clustered Results live on PCL2 and are created by RPCALC**

SAP translates these clustered results via a report such as PC_PAYRESULT.
Now with declustered results, it means that we can go and look at these results on a table and select
them directly
Tables HRDCT_TPY_RGDIR and HRPY_RGDIR are important to identify results,
payroll area, period and if it is for a retro - then it is important for your
developer to know as they build checks

14
Links tables such as P2RX_RT with the payroll area, period etc. via a single
sequence number. Entries created on P2RX_RT are for both test and regular
payroll.
Every time the test payroll results are created for an employee, the previous
existing test results are replaced. No history of test payroll results or versioning
is possible

15
RCA: Payslip based on the test payroll results

Public 21

16
 Relationship
between
payroll
results
directory
andotherdeclustered
tables
.
Test payroll results directory
Table HRDCT_TPY_RGDIR Table P2RX_RT

Validation rules should use a database joins between the test result directory
declustered
and other
tables.
For example, a validation rule should sum the total gross of an employee for the last actual period of 2024
(periods shown in green above) then the database join is built on the P2RX_RT and HRDCT_TPY_RGDIR by
joining fields PERNR and SEQNR. Table P2RX_RT contains both productive and test payroll results
SEQNRS, in any case, only the correct mixture of SEQNRS is considered by the database join due to result
directory selection criteria.

Test payroll results posting simulation (cluster XT)

Public

System selects wage types and amounts for an employee and a specific
payroll period in the table P2RX_RT using a sequential number from the
directory HRDCT_TPY_RGDIR.

17
Payroll Control Center: Storage of Test Payroll Results in Cluster Tables (BF
HCM_LOC_CI_110)
Transaction
SE16N

Previously, only part of the test payroll results

declustered
were and stored based on the configuration in
tablePayroll Result: Test Run in Payroll Control (V_T77DCT_REG).
Center Now,
in order tosupport
posting simulation, the complete test payroll results are stored in cluster
PCL2cluster
tablePayroll Result:
Test Run in Payroll Control Center( XT), in addition to the
declustered
test payroll results.

The report
Posting to Accounting: Create Posting(RPCIPE01/RPCIPE01CE
Run ) has been enhanced to
support simulating posting with test payroll results.

Payroll Control Center: Storage of Test Payroll Results in Cluster Tables | SAP
l Help Porta
Public 24

18
DeclusteredPayroll Results Management Tools

Public

Initial Load ofDeclustered Payroll Results: Output

19
 Initial Load forDeclustered payroll results report

Transaction HRDCT_LOAD_PY_RX

It’s necessary to define country-

specific cluster ID

Transaction HRDCT_LOAD_PY_RX is used to declustered past results stored in

database. You only need this if you want to build validation checks on past data.
Allows you to select only the tables you want, for example, RT table only

20
 Delete Declustered Payroll Results

Transaction HRDCT_DEL_DATA

Thank you.

© 2023 SAP SE or an SAP affiliate company. All rights reserved. See Legal Notice on www.sap.com/legal-notice for use terms, disclaimers, disclosures, or restrictions related to this material.

The HRDCT_DEL_DATA transaction is used to delete existing declustered results

stored in the database. It can delete both Test and Production results.

21