Introduction - Many implementers working on SAP S/4HANA Cloud, Public Edition implementation projects have questions around deletion of data from SAP S/4HANA Cloud, Public Edition systems and this blog tries to cover some important aspects around the deletion scenarios across various situations which includes - deletion of org entities, deletion of custom configurations, deletion of master and transactional data from the system.
Target audience - First time Public Cloud implementers in SAP S/4HANA Cloud, Public Edition and SAP consultants who are curious to know what's possible w.r.t deletion in SAP S/4HANA Cloud, Public Edition.
This is a live blog series with continuous improvements, enhancements and additions/changes being done to meet the expectation of our viewers. I will be linking the actual blogs which should be able to provide a detailed guidance around deletion scenarios below. The intention of this blog is to create awareness and provide a one-stop shop for our viewers who have questions around deletions in SAP S/4HANA Cloud, Public Edition.
When it comes to SAP S/4HANA Cloud, Public Edition - one must be aware that deleting stuff in SAP S/4HANA Cloud, Public Edition is slightly different than that of legacy implementation experiences. SAP S/4HANA Cloud, Public Edition needs to be looked upon as a Software-as-a-Service where customers expect immediate time-to-value over their investments and optimized results. Hence the architecture is a bit different than legacy ERP solutions. Though SAP S/4HANA Cloud, Public Edition provides immense flexibility and control over certain aspects, there are some scenarios where the flexibility is not the same as compared to previous enterprise software solutions. Deletion is surely one of those aspects where flexibility is restricted in SAP S/4HANA Cloud, Public Edition.
Here comes the importance of SAP Activate Methodology as it provides step-by-step guidance towards implementation methodology in SAP S/4HANA Cloud, Public Edition. not just Activate is a pure implementation methodology but it also holds accelerators and artefacts totally integrated with the supporting tools (SAP Central Business Configuration, SAP Cloud ALM) which supports in intricate details around the ERP implementation. Coming back to the context of deletions, SAP Activate details around the fit-to-standard workshops and emphasizes deep enough on what are the detailed considerations within those workshops. For instance - If the project team is following the fit-to-standard workshops as per the provided guidance in the Starter Systems, questions around deletion scenarios have high possibility to be answered right during the Explore phase. This would ensure that once the project team starts with the Realize phase, they are well aware around the deletion scenarios in SAP S/4HANA Cloud, Public Edition.
However, we do also understand that often times even after following exact guidance by-the-book there can be mistakes (like creating wrong org entity, wrong custom entries in configurations, wrong master/transactional data etc.) which would need evaluation around the possibility of deletion. Hence the below simple table should be able to help you with some of the scenarios covered. I am also linking the detailed blog which attempts to cover in-depth if one wants to know more about it.
| Scenario | Situations | Deletion Possibility | Blog Link for more details |
| Organizational entity deletion | Wrong org. entity created, Typos, Org. entity not required anymore etc. | - If the org. entity is not yet confirmed in SAP Central Business Configuration - Yes, can be deleted
- If the org. entity is confirmed in the SAP Central Business Configuration, it cannot be deleted
| Deletion of Organizational entities in SAP S/4HANA Cloud, Public Edition |
| Custom Configurations deletions | wrong custom configuration entry created, Typos, not required anymore etc. | Check column Q - 'Delete Customer Record' in the SAP Activate Accelerator Configuration Activity.xlsm (SAP Customer) - If the column says 'Yes' - the custom configuration can be deleted via the transport management in SAP S/4HANA Cloud, Public Edition
- If the column says 'Deletion not supported' , you cannot delete the custom configuration
| Deletion of Custom Configurations (Customer Adaptation) in SAP S/4HANA Cloud, Public Edition |
| Master Data/Transactional Data deletions | wrong master data created, typos, redundant data, dummy data, resetting the transactional data, clear data, lifecycle, data archiving, data destructions etc. | Master and Transactional data cannot be directly deleted or archived from the system. The master data needs to be checked for any data associations, postings, open items, work in progress items etc. and should be undergoing the lifecycle behind the purpose of the data. This is governed by ILM framework in the SAP S/4HANA Cloud, Public Edition. Similarly transactional data generated or created in the system is required for compliance and regulatory purpose and depends on various factors. Hence deletion or archiving of this data needs to undergo policies and lifecycle governed by ILM framework. Being a very vast topic, different business functions need to look at this topic as per the business requirements. | Deletion of Master and Transactional Data in SAP S/4HANA Cloud, Public Edition - Link Collection |
Hope this helps our viewers as a summary and further in terms of finding more details if interested.
Happy reading.
Thanks,
Saumi
