How to improve performance by reducing ticket data volumes in C4C.

[former_member814480]

Dear Team,

Please suggest a possible way to control the high volume of data that is currently present in the ticket (C4C).

There are nearly 1 crore tickets are present in the system. As a consequence of this, it can impact system load and performance.

As a solution, we have worked out ticket archiving functionality, but in this case, after a certain period of time, it's getting deleted from the system. We don't want to remove the data from the system after 5 to 7 years at all. (We want to keep the entire set of older data somewhere)

Kindly suggest any other way to reduce the high volume of tickets without losing the data.

Thank You.

[Juliuspereira]

Hi Sibishake,

If you are on the C4C public cloud, I believe the only way to reduce the volume of tickets is through archiving, as you already know. With archiving you can set the retention periods and deletion periods to a number of days of your choice. And you can also change those retention/ deletion periods as your needs change in the future.

For instance, you can even set it as high as 100,000 days or more, which is 273 years. So that way the data is almost never deleted. But you might want to confirm with SAP support on whether there is a max value and what that value is. I tried saving 100,000 days and it took it without any error.

Alternately, you could post a comment on this Archiving blog https://blogs.sap.com/2020/12/03/archiving-how-it-is-designed-how-does-it-work/

This is written by Schuade Horst and he is very prompt in replying to comments on his blog and I also believe he is the owner for the archiving piece from SAP.

If however you learn about limitations either by contacting Horst on the blog above or through SAP support, you could check with SAP thorough your C4C SCP (SAP client partner) or your SAP AE (Account executive) on whether the C4C private cloud has anything different to offer in terms of archiving, as compared to the public cloud. Then you could evaluate what makes sense for your business.

Julius

[former_member814480]

Hi Julius,

Thank you for your valuable responses!

Let me look into your valid point. If the system allows for 273 years, that appears to be a cool feature. also considering with the SAP support partner.

Thank you.

[Juliuspereira]

The 273 years was just an example. The system should allow you to go even more. But just confirm with SAP through a ticket or a comment on the blog whether it is really designed to work for that large number of years.

[AnkushPashine]

Hello Sibishake,

1.Yes - If their is huge data, it might lead to performance (but I can't comment the 'number of record' which will lead to performance) .

2. Since, you are archiving - it seems getting deleted, else c4c won't delete ticket data automatically (I can see in my internal system data for year 2012 too).

3.One of the proposal could be :- As we 'Export to Excel' functionality in Ticket View (OWL) , you can go to 'Advance Search' ->filter data based on 'Reported On / Created On' Year wise (i.e. can you Between ...operation to filter ticket reported between X date to Y date) ==>Then export those year wise data via Excel function ...

Hope this answer !

Best Regards,

Ankush.

[former_member814480]

Hi Ankush,

Thank you for your valuable responses!

In real time, we need to provide a path file to get the older data into the system so that whenever a company wants to refer to the older data, they can do so accordingly (storing the data internally and sharing it every time, not preferring the business).

Thank you.

[former_member814480]

Hi Ankush,

For the second point Could you please provide the archiving setup screenshot for the reference.

Thankyou,

Sibi

[AnkushPashine]

Hello Sibishake,

Archiving related blog was mention in the post from "Julius Pereira" - please check it .

BR,Ankush