Ansicht
Dokumentation

Declustering for Concurrent Employment Payroll Result ( RELNRELN_BF_HCM_LOC_75 )

RFUMSV00 - Advance Return for Tax on Sales/Purchases   PERFORM Short Reference  
This documentation is copyright by SAP AG.

Short text

Declustering for Concurrent Employment Payroll Result

Use

In Human Capital Management (HCM), the concurrent employee information is stored as a large object in a field within a database table. The database tables are referred to as cluster tables. The results for Payroll are stored in cluster tables, that is, the transparent tables are compressed to form a binary string. The cluster tables PCL1 and PCL2 store these binary strings (RAW format). This type of data storage does not allow the results of the payroll to be accessed directly from the database layer.

You use this business function to activate the declustering for concurrent employment payroll result. This declustering mechanism involves the creation of simple transparent database tables in addition to the standard non-transparent database tables and stores existing cluster data as well as synchronously updating the transparent tables. This allows you to process or retrieve data using complex SQL queries and perform aggregations on these concurrent employment payroll results right at the database layer.

Effects on Existing Data

When you activate the business function and perform the activities under Customizing, the system creates and synchronously updates transparent DDIC tables with the existing data contained in the registered HCM cluster result tables. If configured accordingly, the system will consistently update the corresponding transparent tables during the end-to-end payroll process.

Effects on Data Transfer

Effects on System Administration

You can execute the initial load report (RPCDCT_INITIAL_LOAD_CE) to fill in the new transparent DDIC tables with the existing payroll results.

You can control access to the new transparent tables (transaction SE16), using S_TABU_NAM. You can implement authorization checks at database level using suitable SQL privileges. In the report, you can check authorizations against the existing authorization objects for employee data, and against the cluster authorization object P_PCLX.

Effects on Customizing

You can switch on the declustering function and define the database connection per PCLx table and RELID, and you can configure which subset of the allowed cluster tables shall be declustered, using the Customizing activities iunder the Declustering Tools node of the relevant payroll structure.

Further Information

PERFORM Short Reference   General Material Data  
This documentation is copyright by SAP AG.

Length: 2668 Date: 20240520 Time: 203240     sap01-206 ( 79 ms )