Shell Copy is a new scenario introduced in SWPM 1.0 to support digital transformation with SAP Business Transformation Center. For more information, see [Everything about using SAP Business Transformation center for SDT S/4 HANA Conversion 2023 from ECC].
The shell copy scenario helps you prepare an SAP ERP shell system containing all Dictionary and Repository objects and all Customizing – while excluding application data. For more insights, please see the introductory blog: [Reducing the DataBase Size of SAP ERP Systems Using Shell Copy Scenario].
Below, you’ll find an example workflow that demonstrates a typical Shell Copy procedure using SWPM 1.0 for SAP ERP 6.0 EHP8 on Linux. The process consists of three main phases: system export, system provisioning, and post-copy steps.
IMPORTANT: Always consult the latest SAP product documentation and Shell Copy Guide specific to your operating system and database platform. Review and apply all relevant SAP Notes before starting the Shell Copy scenario on your landscape.
Step 1: System Export
1. Download the Latest SWPM:
Obtain the latest SWPM 1.0 for NW higher than 7.0x SAR file supporting Shell Copy from SAP Software Center. Review prerequisites: “Running Software Provisioning Manager“.
2. Start SWPM & Select Scenario
In the Product Catalog, select: SAP Business Suite 7i 2016 → EHP8 for SAP ERP 6.0 ABAP → <DB Type> → Shell Copy → Source System → Database Instance Shell Export
3. Set Source System Parameters
Confirm or enter the path to the SAP ECC profile folder
Enter <sid> adm password when prompted.
Provide the DDIC user’s password in client 000 (needed for online preparation).
4. Trigger Export with SUM 2.0
In the Shell Copy scenario, Software Update Manager (SUM) 2.0 replaces Migration Monitor for database migration.
Specify the export directory path where SWPM will extract and run SUM. Download and provide the latest SUM 2.0 archive from the SAP Software Center.
Confirm the “Parameter Summary” dialog to trigger exports.
5. Transfer Export Directory
When export is completed, copy the entire export directory to the target host (including SUM and data).
Step 2: System Provisioning (Import on Target Host)
1. Prepare Target Database
Set up the target database per the installation guide for SAP ERP 6.0. Under “Product Release”, make sure that you select “SAP NetWeaver 7XX-based”. Tip: Review and apply required SAP Notes required for Shell Copy
that resolve known issues.
2. Install ASCS Instance
Start SWPM 1.0 on the target and choose: SAP Business Suite 7i 2016 → EHP8 for SAP ERP 6.0 ABAP → <DB Type> → Shell Copy → Target System → ASCS Instance The SAP system ID (SAPSID) must remain the same between source and target (e.g., if source is SC1, target must also be SC1). In that example we provide a Master Password for all system users such, e.g. <sid>adm, SAPService<SAPSID>. If you did not create the operating system users manually before the installation, the Software Provisioning Manager creates them with the common Master Password. If users are not pre-created, SWPM will create them. For master password requirements, refer to he SAP System Parameters section of the installation guide.
3. Provide SAPEXE Kernel and SAP Host Agent Binaries
SWPM will prompt for SAPEXE Kernel archive and the SAP Host Agent binary files – have them ready.
4. Import Database Shell Instance
On the target DB host, launch SWPM and select:
SAP Business Suite 7i 2016 → EHP8 for SAP ERP 6.0 ABAP → <DB Type> → Shell Copy → Target System → Database Shell Instance For standard installation (all instances on one host), /sapmnt/ is local and SWPM will detect profile directory. Use the previously set master password and <sid>adm password Enter the same DBSID as used in the source system.
Provide the required SAP Kernel resourcesSpecify the SUM export directory path you copied earlier. Note: If changing CPU architecture (e.g., Windows to Linux), provide the appropriate SUM.SAR for the new OS on the target system
Address any DB-specific dialogs without making unsupported changes to the DB layer.
5. Install the Stub Primary Application Server (PAS)
Launch SWPM and choose: SAP Business Suite 7i 2016 → EHP8 for SAP ERP 6.0 ABAP → <DB Type> → Shell Copy → Target System → Stub Primary Application Server Instance Specify the instance profile folder. Use the previously set master password. Provide archives for SAPEXE, IGSEXE, and IGSHelper as requested. Address any DB-specific dialogs. Once the PAS instance installation has been completed, the Shell ABAP system should be up and running.
Step 3: Post-Copy Activities
The last step is to prepare the Shell ERP system as described in the Follow-Up Activities section of the Shell Copy Guide for your operating system and platform.
Tips & Recommendations
Prepare required SAP Notes in advance to avoid interruptions. Use the latest supported versions of SWPM and SUM. Avoid DB layer changes between source and target unless explicitly supported by SAP. Master passwords should comply with all OS-level security policies.
Useful Links
SAP Software Center Shell Copy Guide Post-Copy Activities SAP Notes required for Shell Copy “Reducing DB Size of SAP ERP systems via Shell Copy Scenario”
By following these steps, you can efficiently perform a shell copy of your SAP ERP landscape using SWPM 1.0 and SUM 2.0.
Shell Copy is a new scenario introduced in SWPM 1.0 to support digital transformation with SAP Business Transformation Center. For more information, see [Everything about using SAP Business Transformation center for SDT S/4 HANA Conversion 2023 from ECC]. The shell copy scenario helps you prepare an SAP ERP shell system containing all Dictionary and Repository objects and all Customizing – while excluding application data. For more insights, please see the introductory blog: [Reducing the DataBase Size of SAP ERP Systems Using Shell Copy Scenario]. Below, you’ll find an example workflow that demonstrates a typical Shell Copy procedure using SWPM 1.0 for SAP ERP 6.0 EHP8 on Linux. The process consists of three main phases: system export, system provisioning, and post-copy steps. IMPORTANT: Always consult the latest SAP product documentation and Shell Copy Guide specific to your operating system and database platform. Review and apply all relevant SAP Notes before starting the Shell Copy scenario on your landscape. Step 1: System Export1. Download the Latest SWPM: Obtain the latest SWPM 1.0 for NW higher than 7.0x SAR file supporting Shell Copy from SAP Software Center. Review prerequisites: “Running Software Provisioning Manager”. 2. Start SWPM & Select Scenario In the Product Catalog, select: SAP Business Suite 7i 2016 → EHP8 for SAP ERP 6.0 ABAP → <DB Type> → Shell Copy → Source System → Database Instance Shell Export 3. Set Source System Parameters Confirm or enter the path to the SAP ECC profile folder Enter <sid> adm password when prompted. Provide the DDIC user’s password in client 000 (needed for online preparation). 4. Trigger Export with SUM 2.0 In the Shell Copy scenario, Software Update Manager (SUM) 2.0 replaces Migration Monitor for database migration. Specify the export directory path where SWPM will extract and run SUM. Download and provide the latest SUM 2.0 archive from the SAP Software Center. Confirm the “Parameter Summary” dialog to trigger exports. 5. Transfer Export Directory When export is completed, copy the entire export directory to the target host (including SUM and data). Step 2: System Provisioning (Import on Target Host) 1. Prepare Target Database Set up the target database per the installation guide for SAP ERP 6.0. Under “Product Release”, make sure that you select “SAP NetWeaver 7XX-based”. Tip: Review and apply required SAP Notes required for Shell Copy that resolve known issues. 2. Install ASCS Instance Start SWPM 1.0 on the target and choose: SAP Business Suite 7i 2016 → EHP8 for SAP ERP 6.0 ABAP → <DB Type> → Shell Copy → Target System → ASCS Instance The SAP system ID (SAPSID) must remain the same between source and target (e.g., if source is SC1, target must also be SC1). In that example we provide a Master Password for all system users such, e.g. <sid>adm, SAPService<SAPSID>. If you did not create the operating system users manually before the installation, the Software Provisioning Manager creates them with the common Master Password. If users are not pre-created, SWPM will create them. For master password requirements, refer to he SAP System Parameters section of the installation guide. 3. Provide SAPEXE Kernel and SAP Host Agent Binaries SWPM will prompt for SAPEXE Kernel archive and the SAP Host Agent binary files – have them ready. 4. Import Database Shell Instance On the target DB host, launch SWPM and select: SAP Business Suite 7i 2016 → EHP8 for SAP ERP 6.0 ABAP → <DB Type> → Shell Copy → Target System → Database Shell Instance For standard installation (all instances on one host), /sapmnt/ is local and SWPM will detect profile directory. Use the previously set master password and <sid>adm password Enter the same DBSID as used in the source system.Provide the required SAP Kernel resourcesSpecify the SUM export directory path you copied earlier. Note: If changing CPU architecture (e.g., Windows to Linux), provide the appropriate SUM.SAR for the new OS on the target system Address any DB-specific dialogs without making unsupported changes to the DB layer. 5. Install the Stub Primary Application Server (PAS) Launch SWPM and choose: SAP Business Suite 7i 2016 → EHP8 for SAP ERP 6.0 ABAP → <DB Type> → Shell Copy → Target System → Stub Primary Application Server Instance Specify the instance profile folder. Use the previously set master password. Provide archives for SAPEXE, IGSEXE, and IGSHelper as requested. Address any DB-specific dialogs. Once the PAS instance installation has been completed, the Shell ABAP system should be up and running. Step 3: Post-Copy Activities The last step is to prepare the Shell ERP system as described in the Follow-Up Activities section of the Shell Copy Guide for your operating system and platform. Tips & Recommendations Prepare required SAP Notes in advance to avoid interruptions. Use the latest supported versions of SWPM and SUM. Avoid DB layer changes between source and target unless explicitly supported by SAP. Master passwords should comply with all OS-level security policies. Useful Links SAP Software Center Shell Copy Guide Post-Copy Activities SAP Notes required for Shell Copy “Reducing DB Size of SAP ERP systems via Shell Copy Scenario” By following these steps, you can efficiently perform a shell copy of your SAP ERP landscape using SWPM 1.0 and SUM 2.0. Read More Technology Blog Posts by SAP articles
#SAP
#SAPTechnologyblog
