Frequently Asked Questions
What SAP ABAP Systems can E2E System Refresh Automation support?
Post activities for S/4HANA (from release 1610) and all Netweaver ABAP instance types (BW, ERP, HR, CRM, SRM, SCM, GTS, WEM, Solman)
What config tables can be exported/imported using E2E System Refresh Automation?
Below is a list of technical data and configurations that may be exported/imported using end-to-end System Refresh.
Note that the selected options are saved on initial use and can be reused on subsequent execution of the refresh.
ALE Configuration
ALE Customizing
Archiving ADK Configuration
Archiving Customizing Configuration
Archiving Objects Configuration
Batch Jobs (SM37)
Report Variants
Batch Server Groups (SM61)
CCMS Configuration (RZ20, RZ21)
10. CCMS History
11. DBA Cockpit Configuration (DBACOCKPIT)
12. Additional DBA Cockpit Config. for Oracle
13. Operating System Commands (SM69)
14. Cross-Client File Names/Paths (FILE)
15. SAP License (SLICENSE)
16. Logon Groups (SMLG)
17. Operation Modes (RZ04)
18. Spool Configuration (SPAD)
19. System Profiles (RZ10)
20. RFC Connections (SM59)
21. RFC Inbound Queue Configuration (SMQ2)
22. RFC Outbound Queue Configuration (SM58, SMQ1)
23. Background RFC (SBGRFCMON)
24. SLD Data Supplier Configuration (RZ70)
25. SAPconnect Configuration (SCOT)
26. SAP Office Configuration (SBWP)
27. SAP Office Number Range for Attachments (SBWP)
28. HTTP Service Configuration (SICF)
29. SLD Access Data Configuration (SLDAPICUST)
30. Update Program Administration (SM14)
31. Security Audit Profile Configuration (SM19)
32. Trust Manager Configuration (STRUST)
33. SNC Access Control List (STRUSTSSO2)
34. TMS Configuration (STMS)
35. TMS Quality Assurance Configuration (STMS)
36. Version Management
37. Virus Scan Definitions (VSCAN)
38. Web Service Configuration (SOAMANAGER)
39. Users (SU01)
40. Test Workbench Configuration (CATT, eCATT, STWB)
41. Internet Transaction Server Config. (IACOR, ITS)
42. Project Customizing (SPRO)
43. Client Configuration (SCC4)
44. Integration Engine Configuration (SXMB_ADM)
45. SolMan Configuration in Managed System
46. ChaRM/CTS Configuration
47. Service Data Control Center Configuration (SDCCN)
48. Service Data Control Center Download Data (SDCCN)
49. Login Screen Information
50. Initial Screen Configuration (SMW0)
51. Lock/Unlock Users (EWZ5)
52. Batch-Input Data and Configuration (SM35)
53. SAP NetWeaver Workflow Configuration (SWU3)
54. SAP NetWeaver Workflow Runtime Data (SWU3)
55. SAP NetWeaver LDAP Configuration (LDAP)
56. Secure Store (SECSTORE)
57. Customer Defined Configuration Tables (CUSTOMER)
58. SAP Gateway Configuration
59. SAP Screen Personas Configuration
60. SAP Unified Connectivity (UCON)
61. SAP NetWeaver Enterprise Threat Detection (ETD)
62. SAP NetWeaver Switchable Authorize Checks (SACF)
63. SAP NetWeaver Maintain Whitelists (SLDW)
64. CRM Middleware Configuration
65. CRM Plug-In Configuration (CRM/ERP)
66. CRM Integration in ERP
67. CRM Component Configuration
CRM Analytic Component Configuration
CRM Interaction Center Component Configuration
CRM Marketing Component Configuration
CRM Miscellaneous Component Configuration
CRM Field Applications (Mobile) Component Configuration
CRM Sales Component Configuration
CRM Partner Channel Management Component Configuration
CRM Service Component Configuration
CRM Web Channel Enablement Component Configuration
68. CRM WebClient Configuration
Define transaction launcher and IC WebClient
Communication Management Software Connections
69. SRM Component Configuration
Technical Basic Settings
Settings for Supplier Synchronization
Activate Users
70. SCM Basis Integration Configuration
Activation of Incremental Data Transfer
Distribution Definition Maintenance
Generation of Distribution Definitions
Maintain Business System Group
Assignment of Logical System and Queue Type
Activation of CIF Error Handling
Assignment of RFC Destinations to Application Cases
User Parameters
71. SCM Server Integration Configuration
72. Remote Control and Communication Framework Configuration
73. SCM Configuration in ERP
Basic Settings for Setting Up the System Landscape
Basic Settings for the Data Transfer
Application-Specific Settings and Enhancements
74. GTS Component Configuration
SAP Compliance Management
SAP Customs Management
SAP Risk Management
75. EWM Server Configuration
Master Data Settings
Batch Management
Goods Issue Process (Work Center)
Printer Settings
Others Settings
76. EWM Interface Configuration RFID
Settings - mandatory
General Settings for ERP - mandatory
General Settings for ERP
Delivery Processing for ERP
Goods Movement
Transportation
General Settings for GTS - mandatory
General Settings for GTS
Non-SAP Systems
Availability Check
Migration from LE-WM
77. BW Configurations
Can some Basis configuration tables be cleaned up?
Below is a list of technical data and configurations that may be cleaned up using E2E System Refresh Automation. Note that the selected options are saved on initial use and can be reused on subsequent execution of the refresh.
Cleanup of CCMS Configuration (RZ20, RZ21)
Cleanup of CCMS History (CCMSHISTORY)
Cleanup of DBA Cockpit Configuration (DBACOCKPIT)
Cleanup of Additional DBA Cockpit Config. for Oracle
Cleanup of Spool Configuration (SPAD)
Cleanup of System Profiles (RZ10)
Cleanup of RFC Inbound Queue Configuration (SMQ2)
Cleanup of RFC Outbound Queue Configuration (SM58, SMQ1)
Cleanup of Background RFC (SBGRFCMON)
Cleanup of SAP Connect Data (SCOT)
Cleanup of SLD Access Data Configuration (SLDAPICUST)
Cleanup of TMS Configuration (STMS)
Cleanup of Web Service Configuration (SOAMANAGER)
Cleanup of Integration Engine Runtime Data (SXMB_ADM)
Cleanup of Batch-Input Data and Configuration (SM35)
Cleanup of Selected ABAP Basis Tables (OTHERS)
Cleanup of Operating System Monitoring Data (ST03N)
Can customer-specified config tables be added to the list for export/import?
Yes.
Precaution: Customer must be aware and accept full responsibility for cleaning table contents in the refreshed system.
Can E2E System Refresh Automation support my system applications deployed in the cloud?
Yes. Regardless of where your environment resides, you can use E2E System Refresh Automation to simplify your system refresh process if your systems are enrolled in IT-Conductor.
What are the most common factors affecting the application performance?
The automated process executed using E2E System Refresh Automation remains consistent without miss regardless of system complexity, provided instructions are followed properly. However, system complexity affects the runtime of the export/import/cleanup together with the degree of parallelism and the number of components you selected for the export/cleanup/import process.
How long does it take to perform the export/import/cleanup process using E2E System Refresh Automation?
The entire process may take from a few minutes up to several hours depending on the same factors mentioned in the previous question. On average, it would take 4 hours to complete the system refresh process end-to-end.
Last updated