EI” SAP Knowledge Base Article 1552169 - Rapid growth of table SWWCNTPo Component: BC-BMT-WFM-RUN (Runtime), Version: 14, Released On: 07.09.2023, | Symptom + Table SWWCNTPo growing at a much faster pace than the other workflow runtime tables. + Even after WORKITEM archiving the table continues to grow. + Database fil level reaches 100%. | Environment + SAP Business Workflow + SAP NetWeaver + Web Application Server for SAP S/4 HANA + ABAP PLATFORM - Application Server ABAP | Reproducing the Issue 1. A decrease in the general performance of the workflow runtime is noticed. 2. The database fill levels reach 100% with table SWWCNTPo contributing to the majority of this. | Cause 1. Awork item archiving strategy is not implemented in the production system, 2. Multiline container elements are used within the workflows which contain large amounts of data, | Resolution **THE ONLY WAY TO SIGNIFICANTLY REDU( RELATED WORK ITEMS** ‘THE SIZE OF TABLE SWWECNTPo IS TO ARCHIVE THE + Put a WORKITEM archiving strategy in place so that the workflow table sizes are under control. Use transaction ‘SARA and archiving object WORKITEM in order to archive work items. Review note 573656 and KBA 2157048 for more information. The lower the number of entries in the workflow runtime tables the better the performance of the workflow engine. Table SWWCNTPo is one of the workflow runtime tables. + Deleting redundant table entries (i.e. table entries without a corresponding entry in SWWWIHEAD) - Once the table size has been reduced by archiving the work items, run report RSWWWIDE_DEP in order to remove entries in the workflow runtime tables that do not exist in SWWWIHEAD. Run RSWWWIDE_DEP for all the tables listed in order to remove any redundant entries from the tables which include SWWWIHEAD, SWWLOGHIST and SWWCNTPo among others. In this case run it for table SWWCNTPo. After a deletion or archive it is usually a goo to do a Reorganization, See note 72873. The report RSWWWIDE_DEP is NOT a solution to reduce the amount of entries in SWWCNTPo. It only removes entries which have no corresponding entry in SWWWIHEAD. If there are no redundant entries in SWWCNTPo (i.e. they are without a corresponding work item id in SWWWIHEAD) then the report will finish without deleting anything! + Containers - From release Basis 640 onwards container values of work items are written to table SWWCNTPo by default rather than tables SWW_CONT and SWW_CONTOB. This is called XML persistence and the data is stored in an XML table which improves the performance of the workflow execution. The size of table SWWCNTPo will depend on how many work items are generated in the system and how much data is contained in each container clement of each ‘work item container. If there are multiline container elements that contain many entries (At runtime) itis needed to establish ifall this data is required in the workflow execution. Ifnot the design and the workflow bindings need to be revisited (e.g, It may be a good idea to use an object attribute rather than a multiline container element to hold the data). Table SWWCNTPo will be smaller when there are less work items in the system (Archiving) and less data in thecontainer elements (Workflow design). If the old container behaviour need to be used (Fill tables SWW_CONT & SWW_CONTOB) the settings can be changed for the persistence profile of workflow via the Workflow Builder (Transaetion SWDD) => Basic Data (Button with Hat icon) => Version Dependent tab => Control tab. Look in the Persistence profile’ tab and change the settings. However XML persistence is better regarding workflow performance | See Also + SAP Note 2131918 - Workflow container: Definition and effeets + KBA 2578826 - Archiving Object WORKITEM - tables with deletion | Keywords WE_GDPR, SWF_WORKFLOW, RSWWWIDE_DEP, SWW_CONT, SWW_CONTOB, SWWWIHEAD, SWDD, Persistence profile SWWLOGHIST table size is increasing 36 - Table size on disk does not decrease after data archiving + SAP Note 2173755 - Support for data aging SWWLOGHIST, | Attributes Key Value Other Components 3BC-BMT-WEM (Business Workflow) Other Components [BC-XI (NetWeaver Process Integration (PD) | Products Products [XBAP platform all versions ‘SAP NetWeaver al versions ‘SAP Web Application Server for SAP S/4HANA all versions | This document refers to SAP Note/KBA ‘Component 3344853 BC-BMT-WEM 3028886 HAN-DB-PER 2578826 BC-BMT-WFM 2157048 BC-BMT-WFM 72873 BC-BMT-WFM 573656 BC-BMT-WFM 2173755, BC-BMT-WFM-RUN 2igigi® BC-BMT-WEM | This document is referenced by SAP Note/KBA Component _Title Title swWLOGuIS! increasing ‘Table size on disk does not decrease after data archiving Archiving Object WORKITEM - tables with deletion Workflow Quick Start Gui RKITEM Archiving sm, recommendations 2 Jating to Archiving in workflow ‘Support for data aging Workilow container: Definition and effects 3251001 WORKITEM tables disk size not reduced after archiving, 2578826 T-WEM Archiving Object WORKITEM - tables with deletion3144853 3061989 2157048 2988489 peuas7i | Attachments File Name ‘BC-BMT-WEM BC-BMT-WEM BC-BMT-WEM HAN-DB BC-BMT-WEM, ‘Workdlow persistence profile IPG. File Size 45 ‘Mime Type image/ipeg