Introduction: Welcome to another deletion series blog where our focus is going to be around deletion of master as well as transactional data in SAP S/4HANA Cloud, Public Edition. As you can guess from the title itself, I am touching on a highly sensitive topic. However, as more customers are getting started with their implementations in SAP S/4HANA Cloud, Public Edition projects for their ERPs - this topic cannot go unseen. With more customers going live with SAP S/4HANA Cloud, Public Edition data and deleting it remains a hot-topic.
Purpose: The purpose of this blog is NOT to detail each and every step in the process of deletion of master & transactional data but rather provide an comprehensive list of standard help documentation in one place which provides you a direction further on specific activities around the deletion process. As the scope and depth of this topic is highly wide as well as quite scattered as per different Lines of Business, localization, legalizations, business-industry specific needs etc., it would be challenging to cover every aspect of it. Hence it is highly recommended that for specific deletion queries around master and transactional data in your ERP system, you are leveraging your SAP experts
Target Audience: This blogpost is targeted towards first time SAP S/4HANA Cloud implementers and consultants, project managers, technical & functional consultants, ILM experts who are looking for a one place information for standard documentation around deletions, blocking, data archiving and data destruction of master and transactional data in SAP S/4HANA Cloud, Public Edition.
Disclaimer: This blog is being written today (9th Feb 2024) and is applicable as of SAP S/4HANA Cloud, Public Edition 2402 release version. Features & capabilities are subjected to change as per SAP's product development roadmap, hence always consider looking at the latest standard documentation. Also this blog attempts to cover as many aspects around master & transactional data deletion in SAP S/4HANA Cloud, Public Edition, but as the scope is quite wide I might miss some information. In such case, our viewers can bring such scenarios to my notice by commenting below and I shall include that accordingly.
------------------------------------------------------------------------------------------------------------------------------------------------
Let's begin.
Definitions:
- Master Data - Master data in SAP comprises the core, foundational data that remains relatively stable and provides essential information about entities, objects, or elements used in business processes. Master data serves as a reference point for transaction data. Data Objects like Customers, Suppliers, Products (Materials), Fixed assets etc. are examples of master data business objects type.
- Transactional Data - Transaction data, on the other hand, represents the actual business activities and events conducted within an organization. It captures the specific details of individual transactions or operations. Sales Orders, Purchase Orders, Balances, Accounts receivable and Accounts payable are some of the examples of transactional data business objects type.
You can get more idea on what types of data objects make master data and transactional data by checking in the Available Migration Objects in SAP S/4HANA Cloud, Public Edition which provides a comprehensive table of data objects available for Data Migration.
First things first - Creating, Importing and Migrating Data (mostly Master Data) into the SAP S/4HANA Cloud, Public Edition is one workstream and needs completely different skill sets. However, when it comes to data deletion; it requires different skill sets. This is not to say that a persona who is involved in creation of data cannot manage deletion, but just that's data migration and data deletion are totally two different workstreams and can differ highly depending on the type, business context and industry-country context of the data relevance.
Now further to this, we cannot move forward without introducing the scope item - Information Lifecycle Management (1KA). This scope item enables you to manage the lifecycle of live and archived data based on rules. SAP ILM uses ILM-specific, enhanced data archiving functions in the SAP S/4HANA Cloud, Public Edition. This scope item provides you with the app which will help you manage and schedule the data archiving and data destruction (deletion) from the system.
Also we must understand some terms which might be useful in your journey ahead while dealing with the data management intricacies.
- End of Purpose - End of purpose in data management has to do with retention of data, and it is a feature of the SAP Information Lifecycle Management (ILM) component. This concept is driven by the necessity to retain legal and business critical data for defined periods and to eliminate it once it no longer serves any purpose. For SAP S/4HANA Cloud, when the purpose of the data is fulfilled (or "end of purpose" is reached), the data can be retired and deleted in compliance with legal and business requirements. This is performed through archiving and deletion processes as set up in the ILM.
The term “end of purpose” is actually part of the General Data Protection Regulation (GDPR), which states that personal data should only be retained as long as the original purpose for which it was collected is valid. With ERP systems like SAP S/4HANA Cloud, administrators set up data retention rules according to their company's policies, as well as local and international regulations. These rules trigger the system to periodically move data past its useful lifespan from primary storage to an archive, and then eventually delete it once its legal and operational relevance has passed.
These processes help ensure compliance and reduce the data footprint of the system, which reduces storage costs and can improve system performance. - End of Business - In SAP S/4HANA Cloud, the term "end of business" often refers to end of a business process lifecycle, which means that a certain business scenario or process that has been in operation is no longer required or needs to be retired. In terms of data management, when a business process comes to an end, the associated transaction data and master data might reach a point where they are no longer needed for operational reporting or other ongoing business activities. This does not necessarily mean that the data can be immediately deleted - regulatory requirements may require you to retain certain types of data for a specific period. SAP S/4HANA Cloud offers features to mark and manage data for deletion, leading to space management. Please note that deletion of data should be done carefully, considering legal, audit, and compliance factors. If the term is used in context with Information Lifecycle Management (ILM), then "end of business" refers to the point in time when the data has completed its business purpose, after which it can be archived or eventually deleted when it has also fulfilled any legal retention period.
Please refer to the SAP guidelines and data retention regulations specific to your industry and geographic location to ensure compliance with all rules and regulations when deciding on the retirement of business processes and associated data. - Residence Period - The residence period is an important concept in data management within SAP S/4HANA Cloud. It refers to the duration of time that data needs to remain readily available before it can be transferred to the system's storage for long-term retention. During the residence period, transactional data is typically kept on the primary database where it can be quickly accessed to support ongoing business operations and reporting needs. The length of the residence period may be determined by a number of factors including internal business policies, operational needs for the data and legal requirements. The residence rule in SAP S/4HANA Cloud system essentially dictates, based on user configuration, what data is subject to retention, the duration for how long the data should be retained in the active database for fast access (residence period), and the period it should be held in the system before it’s completely deleted (retention period).
At the end of the residence period, the data should be archived, i.e., moved from the primary database to a more cost-effective long-term storage solution. How rapidly and frequently this archiving occurs will depend on the specific business processes, compliance obligations and the data volume management strategy of your organization. Keep in mind that management of the residence period should align with not only your business requirements but also the legal and regulatory data retention policies specific to your industry and country. It's recommended that you work closely with your legal, compliance and IT teams when setting data residence periods. - Blocking - Blocking in data management refers to the process where certain data records are flagged or tagged in SAP S/4HANA Cloud so they can not be available for further use in other operations or transactions. This is often used in situations where the data is obsolete, incorrect or no longer relevant.
A typical example is blocking a business partner (customer, supplier etc.) in SAP. The blocked business partner cannot be used in transactions until it's unblocked. Similarly, product/material numbers, employee records, costs centers, or other objects can also be blocked. This is a reversible step; records can later be unblocked if necessary. Blocking data does not delete it from the system, rather it prevents the data from being used in the system, offering a safe way to handle data that should no longer be used in business operations. Keeping track of these block status changes is also an important part of data management, as it helps preserve information on why and when data was deactivated. Please note that even though the data is blocked, it still has to be kept in the system for a certain period due to legal and audit purposes. - Personal Data - Personal data in the context of data management in SAP S/4HANA Cloud refers to any information that can directly or indirectly identify an individual/business partner. This includes details like names, addresses, email addresses, IP addresses, phone numbers, identification numbers, online user identifiers, location data, biometric data, or any other specific factors that could relate to the physical, physiological, genetic, mental, economic, cultural, or social identity of a person. It's important that such information is handled with care due to the General Data Protection Regulation (GDPR) and other similar data protection laws around the world. It must be processed, stored, and if necessary, even deleted or anonymized in a compliant manner. SAP offers specific features and tools to facilitate the compliant handling of personal data. For example, S/4HANA Cloud supports data blocking and deletion functionality to ensure data is not processed beyond its intended purpose or retained for longer than necessary, which is an integral part of GDPR compliance. It also offers data anonymization/masking features that can help obscure personal identifiers in data sets to protect individual privacy & sensitive data. SAP S/4HANA Cloud also includes functions for creating reports to prove to the authorities that personal data has been deleted in compliance with applicable regulations.
Remember, managing personal data is not just a technical task; it also requires a good understanding of the legal and regulatory requirements that your organization needs to comply with. Always ensure to consult with data protection experts or legal advisors when dealing with personal data. - Marking for Deletion - Marking for deletion is a status that can be applied to certain kinds of master data in SAP S/4HANA Cloud to indicate that this data is no longer necessary for operations and can be removed from the active database. This doesn't mean the data is immediately deleted. It's a two-step process where data is first flagged (or marked for deletion) and then it can be deleted from the system during data housekeeping tasks by the administrator. This approach offers an opportunity to review and confirm that the data in question can be safely removed without impacting business operations.
For instance, if a customer or supplier is not active anymore, their data can be marked for deletion. Similarly, materials/products that are no longer in use can also be marked for deletion.
Marking a record for deletion prevents it from being used in future transactions, but it doesn't remove transaction history, or records that are already in existence. Also, it's not possible to delete master data that still has dependent transactional data. Please note, while marking for deletion helps in data housekeeping, it must be done carefully and in compliance with data retention policies and other legal requirements.
Now that we have extensively looked upon some definitions, lets jump into the topic of ILM.
With that said, any data cannot be just selected and deleted from SAP S/4HANA Cloud, Public Edition system (or for that matter most of the ERP systems). Any data which is created (master/transactional) or generated (mostly transactional) is business purpose data and oriented towards a particular business executions. Usually no dummy is encouraged into the system as it create inconsistencies and complications, but this depends on the type of system you are dealing with. In Non-Prod environments (Starter, Dev and Test systems), dummy or test data creation is a common practice. Whereas due to obvious reasons, no dummy or test data should be created or generated in the Production environment.
How to delete master and transactional data in SAP S/4HANA Cloud, Public Edition System?
Some warnings before we look into the answer -
- Always backup data as required. In SAP S/4HANA Cloud, Public Edition there is no direct way to backup the data actively. A customer might require to acquire any extra solutions to backup the data required
- Use your Quality or Development system first - never test in Production.
- Make sure the master data records do not have any open items or dependencies, otherwise, it can disrupt your workflows and create inconsistencies in your reporting.
- Check your organization's data retention policy requirements and validate that the records can be legally marked for deletion.
Master Data - Deleting master data directly in SAP S/4HANA Cloud is typically not recommended or even impossible if the data is linked to transactions due to the integrated nature of the system. However, you can mark master data for deletion which prevents it from being used in future transactions. If we look into very generic steps, you can follow it as below:
Go to the app appropriate for the master data type you want to manage, e.g., "Manage Business Partner" app for business partner data, “Manage Product Master Data” for material data, etc.
Search and select the data you want to delete.
For most master data you'll find a Status or similar field where you can change the status to 'Marked for Deletion', or 'Blocked'. Save your changes.
Also remember that even after the master data is marked for deletion, the actual deletion process usually needs to involve a scheduled job set up by the system administrator to run the archiving and/or deletion activities which is again driven by the Information Lifecycle Management which is a multi-step activity. The archiving and data destruction jobs may need to be planned in such a way not to affect system performance, like scheduling during non-peak hours, as it may consume system resources.
Transactional Data - The deletion of transactional data directly is not supported due to reasons related to data integrity, security, compliance, and audit.
Rather than trying to delete transactional data, you can:
- Cancel or reverse transactions
- Archive old data
- Anonymize or redact personal data for GDPR compliance
Remember that manipulating transactional data in enterprise systems such as SAP S/4HANA Cloud could lead to serious issues related to data consistency and regulatory compliance.
But again, it's not that simple and straightforward for both master and transactional data deletion. Not because SAP complicates it, but due to several business and legal requirements such steps cannot be missed or there can be serious loss & consequences due to wrong data being manipulated. As an instance out of many the Personal Data is of utmost importance over here. There can be personal data associated with the master/transactional data which needs to be acted upon before working on the data. Hence the system provides a framework which looks after simplified blocking and deletion. A detailed guide is available over here - Simplified Blocking and Deletion. I am just referring some screenshots from this documentation which can definitely get you excited :
Learn about Information Lifecycle Management in SAP S/4HANA Cloud, Public Edition (Sessions) - One of the best learning sessions around ILM is available here - Are you ready to embrace Information Lifecycle Management in SAP S/4HANA Cloud, public edition? which will ascertain your understanding on the usage, flow, apps and different mechanisms available in the ILM framework in SAP S/4HANA Cloud, Public Edition. (Before you can access the links below, a one-time registration in the SAP Learning Hub, edition for SAP Enterprise Support, is required. A detailed step-by step guide to registration can be found here.)
Now let's jump into the Link Collection (which is the main intention of the blog). We hope the below extensive list of the links should provide a one-stop-shop for all standard guidance around the Blocking, Deletion and ILM activities in SAP S/4HANA Cloud, Public Edition for various data types as well as Lines of Business:
Information around Information Lifecycle Management (includes both data archiving and data destruction) :
- SAP Signavio Process Navigator scope item - Information Lifecycle Management (1KA) (This includes the Manual Test Script, Cloud ALM Test Script, Setup Instructions, Country-industry-solution relevance and generic information. This is important to be evaluated during the Prepare-Explore and Realize phase while setting up the system)
- Information Lifecycle Management - SAP Help (This consist of steps and detailed guidance on all the step during the information lifecycle management) :
Blocking and Deletion (usually involved wherever personal data is involved with master-transactional data)
- SAP Signavio Process Navigator scope item - Data Protection and Privacy (5LE)
- Simplified Blocking and Deletion - SAP Help (Explains the steps around blocking and deletion of personal data involved in the Information Lifecycle Management as explained above)
- Blocking and Deletion: Transactional Data - SAP Help (Explains about maintaining the appropriate ILM settings for residence and retention rules around transactional data)
- Blocking and Deletion: Master Data - SAP Help (Explains about blocking, unblocking and deletion of central master data)
- End of Purpose (EoP) Check
- Blocking, Unblocking and Deletion of Business Partner, Customer and Supplier Master Data
- Blocking and Deletion of Personal Data in Master Data Maintenance (objects - Business Partner -CA_BUPA, Suppliers - FI_ACCPAYB, Customers - FI_ACCRECV, product - MM_MATNR, )
- Blocking and Deleting Business Users
- Destroying Contacts Using FI_ACCKNVK (object - FI_ACCKNVK)
- Fiori apps
Data Management in different areas and lines of business (Steps or links which provide information around some of the data archiving objects and steps if applicable)
- HR, Workforce and timesheet -
- Data Management for HR Connectivity and Workforce Details
- workforce assignments - WFD_ASSIGNMENT
- business partner data - CA_BUPA
- Data Management in Timesheet
- timesheet data - CATS_DATA
- daily availability - /SHCM/AVLB
- Data Management for HR Connectivity and Workforce Details
- Finance -
- Data Management in General Ledger Accounting
- Financial Documents FI_DOCUMNT
- GL Transaction figures - FI_TF_GLF
- Temporary FI data FI_TEMP
- Cash Journal Documents - FI_TCJ_DOC
- protocols of flat-rate individual value adjustment - FI_BSBWVAL
- global hierarchies - FI_UH
- deferred taxes - FI_DEFTAX
- accruals - FI_ACEOBJS
- destruction object for GR/IR reconciliation processing history - FINS_DEST_GRIRPROCHIS
- Data Management in Management Accounting and Margin Analysis
- predictive accounting- FINS_PRED
- line items transaction data in profitability analysis - COPA2_A000
- profitability segment - COPAC_A000
- cost rates - CO_RATE
- cost center allocations - CO_ALLO_ST
- allocation run data - CO_ALLCRUN
- cost center transaction data - CO_TRANS
- Material ledger document information - FCML4H_DOC
- runtime for organizations changes -FI_OC_RT
- organizational changes - FI_ORGLCHG
- Data Management in Reporting and Analysis
- FI Journal Entry - FI_DOCUMENT
- credit loss allowances - FINS_LOSS_ALLOWANCE
- destruction object for advanced closing runs - FINS_CLS_RUN_DESTRCT)
- Data Management in Intercompany Matching and Reconciliation
- intercompany matching items - ICA_JOURNA
- destruction object - ICA_JOURNA_DES
- Data Management in Receivables Management
- correspondence request -FI_ARPCORR
- bank communication management - BNKCOM_ARC
- bank statements - FI_ELBANK
- dispute-case management: case - SCMG
- credit segment business partner - CA_BUPA
- credit management application log - BC_SBAL
- collection management - UDM_COLL
- credit management - FIN-FSCM-CR
- dispute case - UDM_DISP
- SEPA mandate - CA_SEPA
- customer open items - FI_AR_UPLCUSTOPENITEMS_ILM;
- destruction objects - balance confirmations - BLNC_CNFRM_DESTRUCTION,
- Dunning data - FI_DUNNING_DESTRUCTION
- lockbox file - FIN_FO_LB_FILE , FIN_FO_LOCKBOXFILE_DESTRUCTION
- bank statement reprocessing rules - FI_AR_RP_RULES_DESTRUCTION
- history global lock on SEPA mandate - CA_SEPA_LCH_DESTRUCTION
- customer open items - FI_AR_UPLCUSTOPITM_DATA_DESTRU
- Data Management in Invoice Management
- bank communication management- BNKCOM_ARC
- FI checks -FI_SCHECK
- payment requests - FI_PAYRQ
- payment release list items - FI_FPRL
- synchronization of customer master data - BP_FKREDEB_SYNC_DESTRUCTION
- balance confirmations - BLNC_CNFRM_DESTRUCTION
- direct debit pre-notifications - FI_DD_PRENOTIF_DESTRUCTION
- recurring supplier invoice template - FI_AP_MGRECSUPINVS_DATA_DESTRU
- payment plans - FI_PAYMENT_PLAN_DESTRUCTION)
- Data Management in Contract Accounting
- Contract Accounts: FI_FICA
- Documents: FI_MKKDOC
- Payment Lots: FI_MKKPAYL
- SEPA Mandates: CA_SEPA
- Direct Debit Mandate Changes: CA_DDMA1
- Banks: FI_BANKS
- Payment Data from Payment Runs: FI_MKKPAYH
- Returns Lots: FI_MKKRET
- Returns Histories: FI_MKKREHI
- Dunning Histories: FI_MKKDUNN
- Correspondence: FI_MKKCORR
- Headers and Histories of Installment Plans: FI_MKKIPH
- Payment Card Supplements: FI_MKKPCRD
- The Revenue Distribution Table: FI_MKKREVD
- Sample Documents: FI_MKKMDOC
- Checks: FI_MKKCREG
- Official Document Numbers: FI_MKKEXTD
- Information Container: FI_MKKINF
- Data from Submissions to Collection Agencies: FI_MKKCOLL
- Payment Orders: FI_MKKPYOR
- Installment Plan Data for Key Dates: FI_MKKIPL
- Provider Contracts: FI_MKKCAVT
- Security Deposits: FI_MKKSEC
- Information About the Foreign Currency Valuation: FI_MKKVAL
- Data for Doubtful Receivables: FI_MKKDRVA
- Business Partner Item Factoring Data: FI_MKKFAC
- Promises to Pay: FI_MKKPP
- Inbound Data from External Cash Desks: FI_MKKEXCJ
- External Payment Information: FI_MKKEXC
- Totals Records for External Payment Information: FI_MKKEXCS
- Clearing Histories: FI_MKKPCR
- Reconciliation Keys: FI_MKKSUM
- Business partner direct debit limit: FI_MKK0002_DESTRUCTION
- Note to payee: FI_MKK0006_DESTRUCTION
- Foreign Trade Declarations: FI_MKKAWM_DESTRUCTION
- Credit list: FI_MKKCRPO_DESTRUCTION
- Worklists from FIORI Apps: FI_MKKKWL_DESTRUCTION
- Dunning exceptions: FI_MKKMAEX_DESTRUCTION
- Open items in item list: FI_MKKOPREP_DESTRUCTION
- Clarification worklists from payment run: FI_MKKPRUN_DESTRUCTION
- Clarification proposals for incoming payment: FI_MKKTFK006_DESTRUCTION
- Champion/challenger log for dunning: FI_MKK_CC_PROT_DESTRUCTION
- Simulation data from factoring: FI_MKK_FACTSIMU_DESTRUCTION
- Business operations for contract partner: FI_MKK_EVENT_DB_DESTRUCTION
- EC Sales List: FI_MKKREPZM_DESTRUCTION
- Business partner extracts: FI_MKK_GP_EXTR_DESTRUCTION
- Document extracts: FI_MKK_DOC_EXTR_DESTRUCTION
- Tax report (time of clearing): FI_MKKREP07_DESTRUCTION
- Data Management in Convergent Invoicing
- rated consumption items - FKKBIXCIT4
- billed items - FKKBIXBIT4
- billing plans - FKKBIXBIP
- credit memos and debit memos -FKKBIXREQ
- billing documents - FKKINVBILL
- invoicing documents - FKKINVDOC
- clarification cases - FI_MKKFINV_DESTRUCTION
- invoicing document extracts - FKKINVDOC_EXTR_DESTRUCTION
- Data Management in International Trade
- authorizations - ITRLM
- trade compliance documents - SD_VBAK, RV_LIKP, ME_EKKO
- classifications destruction - ITR_CLS_CONTENT
- Data Management in Asset Accounting
- fixed asset - FAA_ASSET
- fixed asset - FAA_ASSET
- Data Management in Cash and Liquidity Management
- banks, SEPA mandates - FI_BANKS
- risk business partners & netting business partners for banks - FCLM_BANK_DESTRUCTION
- bank account contact person - BAM_AMD
- personal data in one exposure - FQM_FLOW
- data generated in bank statement monitor - FI_AR_BSM_DATA_DESTRU
- power of attorney for banking transactions - FCLM_POA_DESTRUCTION
- personal data in Manage Liquidity Item transfer - FCLM_LQT
- Data Management in Treasury and Risk Management
- Transactions - TRTM_FTR
- Positions - TRTM_TPM
- Correspondence Objects - TRTM_CO
- Raw Exposures - TRTM_REXP
- Exposure Positions - TRTM_EXPOS
- Limits and Limit Utilizations - TRTM_LM
- Security Class Data - TRTM_SEC
- Financial Objects - JB_FOBJ
- Single Records (RDB) - RDBRA_REC
- Data Management in Settlement Management
- Condition contracts - WCB_COCO
- Settlement documents - WZR
- Data Management in Production and Revenue Accounting (Oil & GAs, JVA)
- Manual Revenue Accounting Documents - PRA_MRAD_DOCUMENT
- Revenue Accounting Documents - PRA_RAD_DOCUMENT
- Valuation Documents - PRA_VAL_ILM_OBJ
- Destroying Vendor Audit Table Content - OIUDP_RPAUDIT_DELETE
- Generic Tax - PRA_GT01
- Texas UTX Royalty - PRA/UTX01
- PRA Interest Processing - /PRA/INTP
- Data Management in Enterprise Contract Management and Assembly
- Legal transactions - LCM_LT
- Legal documents - LCM_DOC
- Legal contexts - LCM_CTX
- Data Management in Real Estate Management
- Real Estate Contracts - REFX_CN
- Real Estate Contract Cash Flows - REFX_CNCF
- Real Estate Objects - REFX_IO
- Real Estate Documents - REFX_RADOC
- Generic Rental Objects - REFX_GO
- Architecture Objects - REFX_OB
- Data Management in General Ledger Accounting
- Professional Services -
- Data Management in Customer and Internal Project Management
- Customer & Internal Projects - CPD_SS
- Customer & Internal Projects - CPD_SS
- Data Management in Resource Management
- Customer & Internal Projects - CPD_SS
- Customer & Internal Projects - CPD_SS
- Data Management in Customer and Internal Project Management
- Sales -
- Data Management in Sales
- Customers - FI_ACCRECV
- Sales Documents - SD_VBAK
- Agreements - SD_AGREEM
- Solution Orders - CRMS4_SOLO
- Condition Records - SD_COND
- Condition Contracts - WCB_COCO
- Billing Process Documents - SD_VBRK
- Deliveries - RV_LIKP
- Settlement Documents - WZR
- Advanced Returns Management Documents - MSR_TRC
- Campaigns - SD_CAMPAIGN_DESTRUCTION
- Free Goods - SD_FREE_GOODS_DESTRUCTION
- Material Determination Records - SD_MAT_DETERM_DESTRUCTION
- Material Listings and Exclusions - SD_MAT_LIST_EXCL_DESTRUCTION
- Product Proposals - SD_PRODUCT_PROPOSAL_DES
- Sales Plans - SD_SALESPLAN_DESTRUCTION
- Sales Order Requests - SD_SOR_DESTRUCTION
- Data Management for Integration of Sales Billing with SAP Subscription Billing
- Provider contacts for Sales Billing - FI_MKKCAVT
- Provider contacts for Sales Billing - FI_MKKCAVT
- Data Management in Sales
- Manufacturing -
- Data Management in Quality Management
- Inspection Characteristics - QM_CHARACT
- Inspection methods - QM_METHOD
- Inspection Plans - QM_PLAN
- Inspection Lots - QM_CONTROL
- Quality info records for procurement - QM_QINF
- Quality Notifications - QM_QMEL
- Quality Certificates - QM_CERT
- Quality Tasks - QM_QTASK
- Non conformance management defects - QM_DEFECT
- Failure modes and effects analyses - QM_FMEA
- Data Management in Waste Management
- Waste transportation document - EHEWA_WTD
- Waste transfer request - EHEWA_WTR
- Waste partner data - EHEWA_EWP
- Waste stream data - EHEWA_EWS
- Disposal Channel Data - EHEWA_WDC
- Data Management in Environment Management
- Compliance requirement - EHFND_REQT
- Compliance Scenarios and tasks - EHENV_SCEN
- Data Management in Health and Safety Management
- Safety instructions - EHHSS_FSI
- Safety instructions - EHHSS_FSI
- Data Management in Production Planning and Control
- Bills of Material - CS_BOM
- Master Recipes - PI_PLAN
- Process Orders - PR_ORDER
- Production Orders - PP_ORDER
- Repetitive Manufacturing Data - PP_BKFLUSH
- Routings - PP_PLAN
- Summarized JIT Calls - PP_SUMJITC
- Work Centers - PP_WKC
- Messages for Service Interfaces in Production - AIF_MES
- Kanban Control Cycle - PP_KANBANCC_DESTRUCTION
- pMRP simulations - PP_PMRP_SIMULATION_DESTRUCTION
- pMRP constraints - PP_PMRP_CONSTRAINT_DESTRUCTION
- Data Management in Just-In-Time Supply to Customer
- Just-In-Time Call Data - NJIT_ICALL
- Just-In-Time Inbound Packaging Units Data - NJIT_IPKGU
- Data Management in Incident Management
- Incident summary reports - EHHSS_ISR
- Incidents - EHHSS_INC
- Data Management in Quality Management
- Supply Chain -
- Data Management in Supply Chain
- Material Documents - MM_MATBEL
- Inventory Documents - MM_INVBEL
- Batches and Special Stocks - MM_SPSTOCK
- Valuated Special Stocks - MM_STO_VAL
- Messages for Service Interfaces in Inventory - AIF_MES
- Value Chain App runtime - VCM_RT
- Deliveries (Inbound & Outbound) - RV_LIKP
- Batch Master records - LO_BATCH
- Batch where used records - LO_CHVW
- Serial number history - PM_OBJLIST
- Handling Units - LE_HU
- Service Interfaces in transportation management - /AIF/MES
- Freight Order Management Documents, Freight Unit Documents - SCMTMSTOR
- Freight Settlement Documents - SCMTMSSFIR
- Freight Agreements - SCMTMSFAG
- Business Partner Master - CA_BUPA
- Characteristics catalog data - AATP_CHARC_CTLG_DESTRUCTION
- Alternative controls - ATP_OVD_ALTVCTRL_DESTRUCTION
- Substitution Control - ATP_OVD_SUBSTNCTRL_DESTRUCTION
- Backorder Processing segment - ATP_BOP_SEGMENT
- Backorder Processing custom sort sequence - ATP_BOP_CUSTOM_SORT
- Availability check data - ATP_CHECK_LOG_DESTRUCTION
- Product Allocation data - AATP_PROD_ALLOC_DESTRUCTION
- Supply Protection data - ATP_SUP_DESTRUCTION
- Delivery management analysis data file - LE_SHP_ANALYSIS_DESTRUCTION
- Packing instruction determination records - LO_HU_PI_DESTRUCTION
- Data Management in Warehouse Management
- Inbound Deliveries - DLV_INB
- Outbound Deliveries - DLV_OUT
- Physical Inventory Documents - LIME_PI
- Handling Units - WME_HU
- Warehouse Tasks - WME_TO
- Warehouse Orders - WME_WO
- Data Management in Supply Chain
- Sourcing and Procurement -
- Data Management in Sourcing and Procurement
- Purchase Requisitions - MM_EBAN
- Purchasing Documents - MM_EKKO
- Purchasing Info Records - MM_EINA
- Invoice Documents - MM_REBEL
- Catalog Items - MMPUR_CAT
- Catalog Item Proposals - MMPUR_OCII
- Data Management in Sourcing and Procurement
- Service -
- Data Management in Service
- Service Contracts - CRM_SRCONT
- Service Orders - CRM_SERORD
- Service Confirmations - CRM_SRVCON
- In-House Repairs - CRMS4_REPA
- Data Management in Service
- Asset Management -
- Data Management in Maintenance Management
- Pieces of Equipment - PM_EQUI
- Functional Locations - PM_IFLOT
- Measurement Documents - PM_IMRG
- Maintenance Notifications - PM_QMEL
- Maintenance Orders - PM_ORDER
- Task Lists - PM_PLAN
- Maintenance Plans - PM_MPLAN
- Serial Number History - PM_OBJLIST
- Data Management in Maintenance Management
- R&D/Engineering -
- Data Management in Enterprise Portfolio and Project Management
- Enterprise projects - /S4PPM/PRO
- Enterprise projects - /S4PPM/PRO
- Data Management in Product Compliance
- Supplier Raw Materials - EHFND_CSM
- Compliance Requests - EHFND_CRQ
- Chemical Customer Materials - EHFND_CCM
- Preprocessed Material Documents - EHPMA_SVT
- Safety Data Sheet Shipment Requests - EHSDS_OR
- Safety Data Sheet Contact Data - EHSDS_CNTCT_ADR
- Compliance Disclosures - EHFND_CD
- Data Management in Product Development for Discrete Industries
- Change record - /PLMB/ECR
- Archive file destruction in change records - PLM_ECR
- Data Management in Enterprise Portfolio and Project Management
- Cross-LoB area -
- Data Management in Master Data Maintenance
- Archiving Products Using MM_MATNR
- Destroying Contacts Using FI_ACCKNVK
- Data Management in Identity and Access Management - IDENTITY
- Data Management in Management of Change - /IAM/ACT & /IAM/ISSUE
- Data Management in Responsibility Management
- Team Owner Data - RSM_TEAM_OWNER_DESTRUCTION
- Draft Team Owner Data - RSM_TEAM_OWNER_DRAFT_DESTRUCT
- Responsibility Definition Data - RSM_TEAM_RESPY_DEF_DESTRN_OBJ
- Team Member Data - RSM_TEAM_MEMBER_DESTRUCTION
- Draft Team Member Data - RSM_TEAM_MEMBER_DRAFT_DESTRUCT
- Data Management for Integration Scenarios
- Data Management in Google Workspace - Document Info Record (DIR) - CV_DVS
- Data Management in Consent Administration - Consent record - CON_CNSNT
- Data Management in Situation Handling - Situation instances - SIT_INST , situation instance activity - SIT_INST_ACTY
- Data Management in Attachment Service- Document Info Record (DIR) - CV_DVS
- Data Management for Retrieved Information - Retrieved information - DTINF_DESTRUCTION
- Data Management in Business Event Logging - BEL_TIMESTAMP_DESTRUCTION
- Data Management in Electronic Documents - Electronic document - EDOCUMENT, Electronic document consistency - EDCNSTENCY, Electronic document tax authority record - EDCTAXAUTH
Country specific listing for Data Management can be found directly in this page:
- Country/Region-Specific Functions >> Navigate to the country in interest and check for the data archiving scenario for a specific business function here (Ex: Data Management in Golden Tax Interface etc.)
How to delete transactional data generated from testing in the TEST system?
I would also like to cover one more aspect when it comes to Transactional data deletion in SAP S/4HANA Cloud, Public Edition. This aspect and function is not very widely known but brings in tremendous value.
Often customers-partners during the implementation of the project create test data (master data) in the test system and run business process testing. This naturally means that transactional data will be created into the system. But due to various reasons customer want to perform multiple rounds of testing with the same master data in the test system. But as posting and transactional data related to the previous testing rounds interfere, second and further testing cycles might be disrupted. For this issue, SAP S/4HANA Cloud, Public Edition provides a functionality ONLY IN THE TEST SYSTEM - to Reset certain transactional data under general ledger accounting. A detailed guide can be found here on the standard help documentation here - Reset Transaction Data.
Though this guide is a live documentation and will be ever-evolving, I hope the links which are brought together should at least save some time to get started with ILM as well as Data Management in SAP S/4HANA Cloud, Public Edition.
Happy learning and execution.
Thanks,
Saumi
- SAP Managed Tags:
3 Comments
