SAP Knowledge Base Article - Public

3795173 - Capacity of Checking of Eligible Archiving Tickets or Different BO's

Symptom

- Archiving tickets does not start after setting the retention periods and putting XX,XXX Number of tickets in the Right Status(Closed).

Environment

SAP Cloud for Customer

Reproducing the Issue

1. Activated archiving for tickets in the Business configuration fine-tuning activity Archiving Configuration.
2. Set the retention periods before archiving to 1 day.
3. Put 50,000 tickets in the right status(Closed).
4. Observed that archiving did not start.

Cause

  1. The "Collect and Verify" phase of the archiving batch job runs for a maximum of 1 hour.
  2. The system can verify between 80,000 and 120,000 instances during this hour.
  3. Archiving job runtime is 60(Standard BO) per minute

Resolution

Create an Incident with SAP to increase archiving job runtime increase from 60 (standard) to max 120 min so that it increase number of tickets picked for process archiving will increase

(Please note that this may effect performance of system)

See Also

Additional information:
KBA 3064083 - Archiving of Tickets FAQ

Keywords

Archiving, Different BO, Retention Period Before Archiving, Business Configuration, Fine Tuning activities, Standard, Increase, Job, Runtime, Collect and Verify, Batch, Closed, Eligible, Capacity , KBA , LOD-CRM-SRP , Service Request Processing , LOD-CRM-ARC , C4C Archiving , Problem

Product

SAP Cloud for Customer core applications 1.0