Partition of ACR Table (DRC-Statutory Reporting) in SAP S/4HANA 2021 (On Premise)

[sairam6481]

Title: Partition of ACR Table (DRC-Statutory Reporting) in SAP S/4HANA 2021 (On-Premise)

Introduction:
Hi Friends!

This is my second blog post and aims to explain the concept of partitioning the ACR table for DRC (Statutory Reporting) in SAP S/4HANA 2021, focusing on its significance, how it differs from other partitioning approaches, and potential issues during implementation. I will divide the discussion into three key areas: like what is partition and How its different partition from other, implementation and other issues.

In SAP S/4HANA, partitioning refers to the process of splitting large database tables into smaller, more manageable pieces, called partitions. This enhances database performance, particularly for large tables, by distributing the data across different sections and improving query efficiency, load balancing, and parallel processing.

There are two main types of partitioning in SAP HANA:
1. Row Store Partitioning:
• Row-based partitioning is less common in S/4HANA because SAP HANA primarily operates as a columnar database. Row-based partitioning might still be used in specific cases where the nature of the data requires it.
2. Column Store Partitioning:
• This is the most common type in SAP HANA, as it aligns with its in-memory, columnar design. Column store tables are split into partitions based on certain criteria, typically by ranges of values or hash-based partitioning.
• Types of Column Store Partitioning:
o Range Partitioning: The table is split based on value ranges of a particular column (e.g., date or ID ranges).
o Hash Partitioning: Rows are distributed across partitions using a hash function, spreading the data evenly.
o Round Robin Partitioning: Data is distributed in a cyclic manner across partitions

Why do we need to partition tables in HANA ?
As HANA can not hold more than 2 billion records per column store table or per partition , any table which has crossed more than 1.5 billion rows are valid candidates of partitioning . It also helps in parallel procession of queries , if they are distributed across nodes in case of HANA scale out scenario producing results faster .

Enable partitioning:
In this section, I’ll explain how to enable partitioning for the SRF_REP_RUN_DATA table, which is a key component in SAP's Advanced Compliance Reporting (ACR) and Statutory Reporting. Partitioning is essential for managing large datasets, ensuring system performance, and preventing table overflow.
1. Enabling Partitioning through TCI Note 3354120
The partitioning for the SRF_REP_RUN_DATA table can be activated after implementing the TCI (Transport-based Correction Instructions) note 3354120. This note consolidates fixes and improvements for Statutory Reporting and introduces partitioning capabilities to manage large data volumes more effectively.
2. Steps to Enable Partitioning
After implementing the TCI note, follow these steps to activate partitioning for the SRF_REP_RUN_DATA table:
a. Implement TCI Note 3354120
Ensure that your system has applied TCI 3354120, which includes various improvements for Statutory Reporting, including partitioning support. This is a consolidated fix and comes with the necessary tools for enabling partitioning.
b. Execute Program SRF_ACTIVATE_TABLE_PARTITIONS
Once the TCI is implemented, the system introduces a new program: SRF_ACTIVATE_TABLE_PARTITIONS. You can run this program to enable partitioning for the SRF_REP_RUN_DATA table.
o Navigate to the transaction code SE38 and execute the program SRF_ACTIVATE_TABLE_PARTITIONS.
o This will partition the table, optimizing data handling, and enhancing system performance, especially for large datasets.
c. Post-Execution Check
After running the program, you can verify whether the partitioning has been successfully applied by checking the table's structure in SE14 or DBACOCKPIT.

Before Partition :

After Partition:

we have enabled partition through program "SRF_ACTIVATE_TABLE_PARTITIONS " in the test systems.

1. We observed that running this program has automatically partitioned table "SRF_REP_RUN_DATA". Is this program applicable only for this table or is there any impact on any other DRC table? Yes only SRF_REP_RUN_DATA

2. Do we need to follow any specific steps to run this program in production? e.g. Down time etc.---- No. we can do as its like transport movement

Issues :
In this section will explain the issue after post implementation
Issue 1 :

Post implementation of the TCI 3354120 , we observed that all the logs of the prior runs are not visible . Even the logs are not showing for the new runs
Before TCI Note : 3354120 :

After TCI note : Logs lost for all previous runs and New Runs

As per SAP suggestion kindly implement the note 3367884 clear the cache as mentioned in the note 2319491 then logs appeared (Immediately will not appear wait for some time)

Issue 2: Record Count is same, but entries are increasing

so total entries in table increased but count of entries in partition is same.

There are 2 partitions seen in HANA. But all records are in Partition 1 . Please clarify after report run for partition , are there any further post actions. And, when will records go into Partition 2 with zero records ?

For SRF_REP_RUN_DATA table I can see that in SE16N there are 1,707,345,316 and at the same time in DB02/DBACOCKPIT transaction I can see below 5 partitions

Checking it from application layer would be ideal as it abstracts all the backend HANA computations which will always be in a flux due to data being written to it. You could try to refresh the screen in HANA and check, but the still recommend checking the data count from application layer SE16N/DB02/DBACOCKPIT.
Tcode : DB02

Select Diagnostics and Table

Click on execute

Is SAP automatically creating these sub-partitions?
SAP: Yes, SAP automatically creates the sub-partition.system will do automatically partition once threshold limit of 50 percentage

Issue 3 : We have observed one thing once successfully at the time of refresh of system . we got an error “ EC0x006: Table partitioning not enabled on SRF_REP_RUN_DATA “. To resolve this issue to we added manually table entries mentioned in the below image to the table SRF_PARTITION

Conclusion:

This blog post addressed Partition of ACR table (SRF_REP_RUN_DATA) and some known issues with their solutions. GenAI was used to help generate this content. Stay Tuned!.

Thank you for going through the post. Your feedback and comments will help me make it more relevant to the community.

First Blog : https://community.sap.com/t5/enterprise-resource-planning-blogs-by-members/predictive-accounting-in-...

Regards,

Durga Sai Ram

Blog.txt