1. DELETE CLIENT 066

mahesh_sardesai · ‎2019 Apr 06

The procedure below is for conversion of any source system to target system S/4HANA any release showing the steps to prepare the system to run SUM tool.

Here the details of the two tasks are provided (1) Delete Client 066 and (2) Dual Stack Split. In the prepare phase we run reports which do not change data or objects, but these 2 activities remove data and/or objects and therefore are more appropriate for the Realize phase.

Please find other blogs as follows at S/4HANA SQUARE ONE

SAP S/4HANA SQUARE ONE

UPGRADE	t1-RC	t2 - MP	t3 - SIC	t4 - CCM	t5 - SUM
S/4HANA 1809+	rcu iop	link	link	link	link

SYSTEM CONVERSION	t2 - RC	t3 - MP	t4 - SIC	t5 - CCM	t6 - SUM
S/4HANA 1909+	rc2 pd(bsr)	link	link	link	prepare EHP6/mss
S/4HANA 1809	rc2	link	link	link	EHP7/hdb EHP6/db6 EHP5/ora EHP6/mss

DISCLAIMER: The purpose of this blog is to provide guidance to fast track your SANDBOX conversion. Please provide latest documentation which may supersede the blog.

1. DELETE CLIENT 066

Client 066 is the Early Watch client which was set up during the installation of your system. It is not used in S/4HANA, you have to remove it before you start the conversion.

STEP1:

Check if client exists - by logging in from any client using tCode SCC4

STEP2:

Change Client 066 role to non SAP productive (e.g. demo). Client Copy and Comparison tool to level 0: No Restriction and uncheck Restrictions Protection against SAP upgrade

STEP3:

Logon to the client 066, the default password of user EARLYWATCH is support.

STEP4:

Using transaction SCC5, remove client 066. You can also define parallel processes to save time required for deletion of client 000. Activate the option to remove the entry in table T000.

TIP: In client 066 normally there is only one user EARLYWATCH and may allow login using standard user SAP*. This has limited authorization and as EARLYWATCH user you may not be allowed to provide the role needed for client deletion.

Also, even if you have the password for SAP* it may not have authorization and the only option is to make this SAP* user the super user by following below procedure to enable super user sapstar. At DB level to delete the record in table USR02:

- Set login/no_automatic_user_sapstar = 0 and restart SAP
- Run SQL command – delete erp.USR02 where BNAME='SAP*' and MANDT='066’

STEP5:

Using transaction SCC3 monitor the logs.

STEP6:

Using SCC4 confirm that Client is deleted

The standard installation also setup the Client 001. You can use the same procedure for deleting client 001 as well.

2. DUAL STACK SPLIT

Dual-stack systems are AS ABAP + AS Java combined in one system. They are not supported for conversion. You have to split it before doing the conversion.

To split you can use the (1) Keep DB option, (2) Move DB option or (3) Remove Java Stack only.

Dual Stack split may have already been done on your system as Business Suite 7i2011 (ECC6/EHP6) was the last Business Suite release with dual-stack support. No upgrade/update of dual-stack system to higher releases was allowed unless the dual stack was split.

The Dual Stack Split tool is provided with Software Provisioning Manager 1.0 from the archive, file SWPM*.SAR and is no longer available as standalone tool. To Remove Java Stack only from Dual Stack, please use option Move Java Database => Remove Java Stack from Dual Stack System.

In case you would like to split the dual stack using the Keep DB option or Move DB option, there is excellent video showing details of the steps: VIDEO: Split of Dual Stack System

Detailed Guide is available at https://support.sap.com/sltoolset System Provisioning (scroll down) => System Provisioning Scenarios => Split a System using Software Provisioning Manager 1.0 => Dual Stack Split Guides

Note 1655335 - Use Cases for Splitting Dual-Stack Systems
Note 1797362 - Dual-Stack Split for SAP Systems Based on SAP NetWeaver - Using SWPM 1.0

SAP Community Wiki - Dual-Stack Split

REFERENCES