Wolverine RISE Migration Project- Cutover Plan for Production

Component Cutoff Leads- WWW Email Contact

Component Cutoff Owner- Pratip Email Contact

Component Cutoff Lead - Additional Email
Contact
 Activity list
Uptime/
Activity
Downtime

Ensure all the pre-requisite are Open and pre-requiste file is located on WWW teams folder.
Unicode Pre-Conversion Activities
SPUMG Scans
Dual Stack Split/Remove Java Stack from CQ2
SUM Preparation
Extraction Roadmap Step
Configuration Roadmap Step
Checks Roadmap Step
Preprocessing Roadmap Step
General Preparation Steps
Decision for Starting Downtime "Yes/No"

RampDown activities
Handover from Customer to SAP
Downtime Roadmap Step
SPUMG--> Consistency check
Perform the export and Import tasks in parallel.
Post steps
Perform Installation check SICK
Run SGEN,Adjust profile parameters for Installed languages and Default client
System Integrity Check(SM21,SM50 and ST22)
Adapt old SAP profile parameters
Merge Start profile for other Application servers
During the update, the start profile is merged automatically with the instance profile for all instances that are started on the target
system.
For those instances for which the profiles are not merged automatically during the update, perform manual steps to merge the
profiles. The procedure is described in SAP Note 1898687

Adapt and load system profiles in RZ10

Extract component information from table CVERS and check components version
Delete all entries from the following tables: ALCONSEG, ALSYSTEMS, DBSNP, MONI, OSMON, PAHI, SDBAD, SDBAP, SDBAR.
Delete entries in the table DDLOG for buffer synchronization.

Activate DB02
Refresh & Check DB02 for any missing table and indexes
Run Report SAP_UPDATE_DBDIFF
Check Tcodes ST22, sick, SM21, SM50
Migrate the ABAP secure store:
1. Call transaction SECSTORE to change the entries in the secure storage.
2. In case of entries with errors with message text System-dependent data for entry … changed, see SAP Note:816861

Check the logon groups and the assignment of the application servers to the logon groups as per Source System (transaction SMLG).

Adapt RFC server groups.

Call transaction RZ12 and change the instance name of the RFC server groups under Group assignment as per Source System
Delete obsolete spool requests and spool inconsistencies while executing the ABAP program RSPO0041 (transaction SE38).

Call transaction SP12 and run report RSPO1043 for a spool data consistency check
Delete canceled and finished batch jobs while executing the RSBTCDEL ABAP program, selecting Delete with forced mode
(transaction SE38).
Adapt the definition of the printers to meet the new system requirements (transaction SPAD)
Maintain spool server in SPAD: Select Configuration > Output Devices > Display > Edit (pencil icon) Select from menu Utilities > For
output devices Click Assign Server > Display list > Convert & Unlock

Open System: SCC4 & SE06 Client 000

Allow Changes as required for COM_PRODUCT_UPGRADE report
Change the RZ12 settings to utilize all work processes for SGEN
Execute SGEN
Manually execute report RASUVAR2 in client 000 in background
RASUVAR1 was executed manually during the PREPARE, so execute report RASUVAR2 in background mode
Client "000"
user:DDIC

Follow-up activities for language transport

Call TA smlt ; check sm37 for successful finished job RSTLAN_AFTER_UPGRADE
Adapt Glossary will be started automatically

Check the Kernel release

Check and release the delta SPDD transport request, if not released by Upgrade
Performing Follow-Up Activities for Application Link Enabling (ALE).The report must be run for each client in the system
If you are using Application Link Enabling Shared Master Data Management (SMD), you need to migrate the change pointers to the
new table BDCP2. Until you have migrated all change pointers, both the former and the new table are used. For performance
reasons, migrate the change pointers as soon as possible after the upgrade.

Procedure
1. To check which message types are affected and how many change pointers need to be migrated, run report
RBDCPMIG_ALL_WITHOUT_MIG_FLAG in test mode.
2. Decide if you want to run the report for all message types at once or separately.
Running the report for each message type separately splits up the total runtime into smaller sections.
3. Run report RBDCPMIG_ALL_WITHOUT_MIG_FLAG in production mode.

Capture the output

Select mandt, count(*)from sapsr3.bdcp group by mandt;
Select mandt, count(*)from sapsr3.bdcps group by mandt;
Select mandt, count(*)from sapsr3.bdcp2 group by mandt;
Select mandt, count(*)from sapsr3.bdcpv group by mandt;
select count(*) from sapsr3.TBDA2 group by BDCP2_ACT;

Delete QCM entries

Check LONGPOST.log and inform the ABAP team
Language Supplementation (000 & productive client)
Execute Report COM_PRODUCT_UPGRADE
Make sure that operation mode is defined on the central instance as per the Original settings
Execute RTCCTOOL from SE38 & fix Addon Impl , Addon/Upgrade steps
DBA: ICF Service-Activation for WebDynpro DBA Cockpit
SAP Note1245200
Copy old global directory to /sapmnt/<SID>/global
Give heads-up to SAP ABAP team for their availability
Delete old ST03N source system data (program SWNC_COLLECTOR_CLEAN_SWNCMONI)
Check correctness of tables (program RSDU_TABLE_CONSISTENCY). Run in background and set parameter to store issues. see SAP
Note1937062
Reset the parameters set as per SAP note 2351294 to reduce the downtime to default values

Unicode conversion specific post steps

Go to transaction SE38, and execute report UMG_ADD_POST_STEP.
Special handling of TLOCK* tables:Run the correction reports as described in SAP Note 795871
Special handling of table DBTABLOG:Follow the description in SAP Note 514967
Convert all non-Unicode files to Unicode (see SAP Note 539404, section [30] Question for details).
Adapt SAP system profile parameters.
Adapt R/3 parameter settings according to SAP Note 790099.
RFC Destinations To avoid problems with internal TCP/IP-connections after the Unicode conversion, you should maintain those
connections which refer to the Unicode system itself, before using the destinations (for example SAPFTPA, SAPHTTPA connections
with activation type Start on Application Server).
■ Go to transaction SM59, open tree TCP/IP connection, choose a connection and press pushbutton Change from the taskbar.
Select tab strip MDMP & Unicode. In dialog box Communication Type with Target System select radio button Unicode. Save the
settings.
■ Apply SAP Note 706528.
To avoid problems with outgoing R/3 connections after the Unicode Conversion, you should check the connections in transaction
SM59 as described above before using the destinations.
■ When the destination is a Unicode system you should set Communication Type with Target System) to Unicode.
■ When the destination is a non-Unicode system you should set Communication Type with Target System) to non-Unicode.
To avoid problems with incoming R/3 connections after the Unicode Conversion from non-Unicode client systems which are on
releases lower than SAP_BASIS 6.10 you should check whether Legacy RFC mode needs to be set up as described in SAP Note
722193.

TMS RFC connections after the Unicode Conversion:

Run report RSTMS_UNICODE_FIX as described in SAP Note 935239.
Transport problems with customizing data in the ALE/IDOC environment.
Go to transaction SE54 and regenerate the form routine responsible for the transport as described in SAP Note 566874.

Problems with Spool Requests after Unicode Conversion:

Forwarded spool requests look different to the requests in the print preview in transaction SP01 or the performance is very slow
when you process spool requests (forward or download). Read SAP Note 1299738 and implement the corrections attached to this
Note if necessary.

Handover from SAP Basis to PCE Team

ECS Post Steps
ADS Setup
Addon installation
Handover from Customer to SAP
CUNUC Post-Activities
Unicode Conversion (SAP Notes, Technical Steps)
Perform UCCHECK and code adjustments post Unicode conversion
Check System Unicode status
Adapt Instance profiles
Validate Installed languages

Quality Check
Finance and Controlling

Quality Check

ABAP Adjustments
Move SPDD/SPAU/Unicode Transport
Perform Delta SPAU adjustments
Perform Delta Unicode Enablement

Handover from SAP to Customer

Functional Validation
Unlock Functional and Key users as per the list
Testing & Reconciliation reports(Execution of Validation Reports)
Test Batch Input processing (SM35,SM35P)

Business User Validation

Unlock Business users for Validation (Key User)
Business User Validation

Ramp Up Activities

Maintain the security configuration.

1. Call transaction STRUST.
2. Replace all existing PSE files in the target system with new ones, which contain the new system's information.
For more information, see the SAP Library at: http://help.sap.com/nw703-Security Information Security Guide: English System
Security System Security for SAP NetWeaver AS ABAP Only Trust Manager Creating or Replacing a PSE.
NOTE:
--> Since replacing a PSE will remove all of the previously used certificates, also import all necessary trusted certificates into the new
PSE's certificate list. (Check the old PSE's certificate list.) Distribute the new PSE's public-key certificate to the systems where it will
be used.
--> Make sure the new PSE contains the new system ID.
--> Note the naming conventions to use for each PSE. The naming conventions are usually specified by the Certification Authority
(CA) where you obtain the certificate, however, the type of PSE also has some restrictions, for example, for the SSL server PSE, the
CN part of the Distinguished Name must be the host name used to access the server. For the system PSE, we recommend using the
SAP system ID as the CN part.
Therefore, make sure that the Distinguished Name used for the PSE conforms with the naming convention that applies.

Configure the Transport Management System (TMS) and TM tool

A) Reschedule the transport dispatcher (RDDIMPDP) in client 000:
1. Log on as user DDIC.
2. Call transaction SE38.
3. Run program RDDNEWPP and set the priority to high.
B) Adapt the transport parameters in the TMS as follows:
1. Call transaction STMS.
2. Choose System Overview and double-click your system.
3. On the Transport Tool tab page, adapt the parameters to your target system as required.
C) Adapt the transport routes in the TMS as follows:
1. Call transaction STMS.
2. Choose Transport Routes.
3. Adapt the transport routes as required.
D) Configure the domain controller in the TMS.
1. Call transaction STMS.
2. Choose System Overview and double-click your system.
3. On the Communication tab page, adapt the controller as required.

Add new IP's into saprouttab file and restart SAP Router services
Check and adapt the connection to SAP Net - R/3 Frontend (transaction OSS1)
For every client in your SAP system check the detail settings (client role, changes and transports for client-dependent objects,
changes for client-independent objects, protection level, restrictions) (transaction SCC4)
 Check self-defined external commands (transaction SM69)

External commands are predefined commands for end users. They are operating-system independent and are protected by
authorizations, so that normal end users can schedule only those commands that the system administrator permits them to.
With an external command, an ordinary end user—any user without background processing administrator authorization—may run
a host system command or program that has been pre-defined by the administrator in the SAP System. The user who schedules the
external command must have the authorization required for the external command.

External commands let you control what your users do outside the SAP System. End users can run only the commands and
arguments that you specify in external command definitions. And you can control access to external commands with SAP
authorizations

Check whether the External commands created before Upgrade & Unicode are working fine

Check & Adapt RFC destinations copied from the source system to the target system.
CAUTION
Before you delete RFC destinations, make sure that they are not needed in the target system.
1. To check and adapt qRFC destination, call transaction SMQR
2. To check and adapt tRFC destination, call transaction SM58
3. To delete obsolete RFC destinations, call transaction SM59

Unlock all system users including batch job & RFC (non-dialog)
Validate housekeeping jobs are running
Update SAProuter settings for connection to OSS
Change default background server name (SM61)
J Connected systems- Customer to update the steps

Releasing the system for End Users

 Upgrade +
Status Team Performed By DB Migration
+ UC

Open SAP Basis/WWW BASIS X

Open SAP BASIS X
Open SAP BASIS X
Open SAP BASIS
Open SAP BASIS X
Open SAP BASIS X
Open SAP BASIS X
Open SAP BASIS X
Open SAP BASIS X
Open SAP BASIS
Open Customer X
START of Business Downtime
Open Customer X
Open Customer
Open SAP BASIS X
Open SAP BASIS
Open SAP BASIS
Open SAP BASIS X
Open SAP BASIS X

Open SAP BASIS X

Open SAP BASIS X

Open SAP BASIS X

Open SAP BASIS X

Open SAP BASIS X

Open SAP BASIS X

Open SAP BASIS X

Open SAP BASIS X

Open SAP BASIS X

Open SAP BASIS X

Open SAP BASIS X

Open SAP BASIS X

Open SAP BASIS

Open SAP BASIS

Open SAP BASIS

Open SAP BASIS X

Open SAP BASIS X

Open SAP BASIS X

Open SAP BASIS X
Open SAP BASIS X

Open SAP BASIS X

Open SAP BASIS X

Open SAP BASIS X

Open SAP BASIS X

Open SAP BASIS X

Open SAP BASIS X
Open SAP BASIS X
Open SAP BASIS X
Open SAP BASIS X
Open SAP BASIS X

Open SAP BASIS X

Open SAP BASIS X

Open SAP BASIS X
Open SAP BASIS

Open SAP BASIS X

Open SAP BASIS

Open X
Open SAP Basis
Open SAP Basis X
Open SAP Basis X
Open SAP Basis X

Open SAP Basis X

Open SAP Basis X

Open SAP Basis X

Open SAP Basis X

Open SAP Basis X

X
Open SAP ECS X
Open ECS ECS X
Open ECS ECS X
Open ECS ECS X
Open Customer X

Open SAP Navneet

Open SAP Basis

SAP X
Open SAP Basis X
Open SAP ABAP X
Open SAP ABAP X

Open SAP X
Open David WWW Func X
Open David WWW Func X
Open David WWW Func X
Open David WWW Func X

Open WWW X
Open Carol/Carlos WWW Basis X
Open David WWW Func X

Open Customer X

Open Carol/Carlos WWW Basis X

Open Carol/Carlos WWW Basis X

Open Carol/Carlos WWW Basis X

Open Carol/Carlos WWW Basis X

Open Carol/Carlos WWW Basis X

Open Carol/Carlos WWW Basis X

Open Carol/Carlos WWW Basis X

Open Carol/Carlos WWW Basis X

Open Carol/Carlos WWW Basis X
Open Carol/Carlos WWW Basis X
Open Carol/Carlos WWW Basis X
Open X

Open Customer X
END of Business Downtime
Start Date & Time End Date & Time Duration
DD/MMM/YY DD/MMM/YY hh:mm:ss
Comments
 Activity list
Uptime/
Activity Status
Downtime

Ensure all the pre-requisite are completed & validated Open Wolverine
Source Access from WWW to SAP after Pre-requisite completion for validations. Open SAP
Technical members to inform functional team members to start validation. Open SAP
Request to ECS team to enable CIFS and Migration_BW correctly Open ECS
Ensure that you are able to logn to Jump hosts: ROCSAPMGT01, ROCSAPMGT02 and
ROCSAPMGT03 Open SAP

Check and Connect to BLOB from Azure Explorer using SAS URl in Source System ( ECS team Open SAP
and request new one from ECS if URL is expired.)
Delta clearance activities in ERP systems Open Wolverine/SAP
Run Platform Task Automation Tool Open SAP
Run export preparation using SWPM Open SAP
Identify big tables and Run table splitting preparation, if needed Open SAP
Run SMIGR_CREATE_DDL Open SAP
Generate migration key for OS/DB migration Open SAP
If target DB is HANA: Update latest version of cluster check using SAP Note: 1077403 as
applicable (Report SDBI_CLUSTER_CHECK) Open Wolverine

If target DB is HANA: Cluster Tables and Pool Tables check as per SAP Note 1784377 (Report
SDBI_POOL_CHECK and SDBI_CHECK_BCD_NUMBERS) Open Wolverine

All required passwords - SAP services user ID, DDIC in 000, User in business client, sidadm,
Open Wolverine
schema

SE38: Check Cluster Tables for corrupt or invalid cluster records or decimal numbers Open Wolverine

SM13: update or delete the corresponding update requests Open Wolverine

DB02 - Missing Table / Index check & fix if required Open Wolverine
Brtools: Update database statistics Open Wolverine
SE38: Check Cluster Tables for corrupt or invalid cluster records or decimal numbers Open SAP
Create required directory Structure for parallel export/import Open SAP
SWPM : Execute "Export Preparations" Open SAP
DB02: Extract Large tables > 3GB and verify with from POC/MOC Open SAP
Create Table Splitting plan Open SAP
Extend PSAPTEMP 20% of DBSIZE Open SAP
SWPM: Execute "Export Table Splitting" Open SAP
Backup Export Directory and make it empty Open SAP
SM02 : Message for system down for export Open Wolverine
Please change sapstart services to manual Open Wolverine
Brtools: Update database statistics (update/verify if ran in recent past) Open Wolverine
DB02 - Missing Table / Index check & fix if required Open Wolverine
SM13: update or delete the corresponding update requests Open Wolverine
SE14: Delete QCM tables Open Wolverine
Process all pending Batch Input jobs in transactions SM35 and SM35P. See SAP note 175596 Open Wolverine
for details. Delete obsolete entries (unprocessed or in error)[1st run]
Process all pending Queues and Clear the queues SMQ1 [1st run] Open Wolverine
Process all pending Queues and Clear the queues SMQ2 [1st run] Open Wolverine
Decision for Starting Downtime "Yes/No" Open Wolverine
RampDown activities Open Wolverine
A BASIS Activities(Parallel) Open Wolverine

Make sure that all production work in the SAP system is stopped and no users are logged on Open
to the SAP system and parallelly stop the R/3 application servers in sequence Wolverine

Lock all users (ewz5), except the technical upgrade users (DDIC, SAP* and SDC users) Open Wolverine
Unlock key users Open Wolverine
Restart SAP R/3 systems to kill all user sessions and start only R/3 application server Open Wolverine

Process pending Batch Input log consistency in transactions SM35 and SM35P. See SAP note
175596 for details [2nd RUN] Open Wolverine

Process all pending Queues and Clear the queues SMQ1 [2nd RUN] Open Wolverine

# Confidential
 Process the
Disable all pending Queues and
RFC destinations andClear the queues
connections SMQ2systems
to other [2nd RUN] Open Wolverine
Note:-
Process Toallchange
pending RFC destinations
Locks and pointing
Updates and to other
Clear SM13productive
failed systems, use transaction
Updates Open Wolverine
Before For
SM59. performing
example,anyou export, make sure
can change that name
the host no incremental
by addingconversion
a string likeis“.syscopy”
in progressor a
To testlike
prefix if an incremental
“#”. conversion
Then the host is in progress,
name points run transaction
to a nonexistent ICNV.
server and If there are any
communication is table
entries in table Wolverine
impossible
Check for usingTICNV,
unfinished
an incremental conversion is in progress. In this case, you have the
this table
destination.
conversion then delete QCM tables (SE14: Extras -> Invalid temp. Open
following options:
table,
1. Defermark all QCM tablesuntiland
theRS_SCRP_D020S_CLEAN
migration the delete them
incremental Open Wolverine
Run report to checkconversion
if there arehas finished.
invalid entries in tables D020S and
2. Try to finish the
DYNPSOURCE. incremental
If invalid entries conversion
are detected,by remove
performing
them the following
before steps:
running the export. See
● If the Wolverine
also SAPtables are in state For conversion or in state Done, delete the entries by choosing
Note 870601 Open
Control Delete Entry .
● If the tables are in any other state, you have to finish the incremental conversion. Choose Wolverine
Assistant and proceed according to the online documentation. Open
Delete Entries from TATGPC and TATGPCA Open Wolverine
BW : Run SAP_DROP_TEMPTABLES SAP Notes:1139396 Open Wolverine

Stop all the Jobs

1. Log on in client 000 as user DDIC Open Wolverine
2. Execute report BTCTRNS1

Functional Validation Open Wolverine

Delta clearance activities in ERP systems(After users locked) Open Wolverine/SAP
Run Reconciliation reports for Functional Validation Open Wolverine
Send results of reports for functional validation Open Wolverine
OS Activities(Parallel) Open Wolverine
Make sure that no CRON job is scheduled that affects the SAP system, such as starting and
stopping the SAP system, saving the database or similar actions. (comment out FS /interface Open Wolverine
housekeep cronjob)

Comment out the SAP auto start/stop command in HA start/stop scripts (COMMENT: vi edit
Open Wolverine
HA start/stop script) & Stop the Monitoring agents and backup scheduler

DBA Activities(Parallel) Open Wolverine

Take Full DB backup Open Wolverine
Ensure the Log mode is not Enabled Open Wolverine
Final Ramp Down Steps Open Wolverine
Restart SAP R/3 systems to kill all user sessions and start only R/3 CI server Open Wolverine
Handover from Customer to SAP Open Wolverine
Export from Source System Open SAP
DownTime Activities Open SAP
Stop Source SAP Instances Open SAP
Ensure Source Database is up and running Open SAP
Create Export and Exchange directory Open SAP
Start SWPM for the parallel export Open SAP
Perform the Paraller export tasks Open SAP
Import into Target System Open SAP
Set Log_mode to overwrite Open SAP
Use the mass loader option of the installer, SAP note:1806935
To activate the option, set the environment variable HDB_MASSIMPORT=YES before starting Open SAP
the SWPM
Start SWPM for the import & Parameter Input Open SAP
Pre Load(Part of SWPM tool) Open SAP
Table migration Import process(Part of SWPM tool) Open SAP
Post Load(Part of SWPM tool) Open SAP
Validate the import logs Open SAP
Post steps Open SAP
Start additional App server Open SAP
Verify Schema name Open SAP
Validation of schema in ABAP and JAVA. Open SAP
Perform Installation check SICK Open SAP
Migration check -> SHDB_Migration_Check Open SAP
BW only: Start program RS_BW_POST_MIGRATION in the background Open SAP
"Refresh & Check DB02 for any missing table and indexes
Run Report SAP_UPDATE_DBDIFF " Open SAP

Execute SGEN Open SAP

Complete Excel spreadsheet for ECS Handover Open SAP
SMLT Language supplementation Open SAP
Slicense check Open SAP
KERNEL info and system info Open SAP
Target Component check Open SAP
System Integrity Check(SM21,SM50, SM51 and ST22) Open SAP

# Confidential
 Ensure that there are no open transport requests(SE01) Open SAP
check Tcode DB02, SM65, SM61, SE14, SPAM
Check the logon groups and the assignment of the application servers to the logon groups as
per Source System (transaction SMLG). Check RZ12 Open SAP

Update SE06 settings Open SAP

STMS (To be taken care by ECS), By SAP only Create Virtual Transport route Open SAP

Migrate the ABAP secure store:

1. Call transaction SECSTORE to change the entries in the secure storage.
2. In case of entries with errors with message text System-dependent data for entry … Open SAP
changed, see SAP Note:816861

Table Consistency check Open SAP

load system profiles in RZ10 Open SAP

Adapt old SAP profile parameters Open SAP

Restart CI and all app server Open SAP
Set Log_mode to normal Open SAP
BW Functional Post validation Open SAP
Handover from SAP SDC to HEC Open SAP
ECS Post Steps Open ECS
Handover from HEC to SAP SDC Open ECS
ABAP Adjustments Open SAP
Perform Transports as per list provided by SAP team Open SAP
Final Handover to Customer from SAP Open SAP
Functional Validation Open Wolverine
Unlock Functional and Key users as per the list N/A Wolverine
Testing & Reconciliation reports(Execution of Validation Reports) N/A Wolverine
Test Batch Input processing (SM35,SM35P) Open Wolverine
Business User Validation Open Wolverine
Unlock Business users for Validation (Key User) N/A Wolverine
Business User Validation N/A Wolverine
Ramp Up Activities Open Wolverine
Connected systems- Customer to update the steps Open Wolverine
Releasing the system for End Users Open Wolverine
SSL Certificatte import Open Wolverine
SSO Tasks Open SAP
Mount /usr/sap/trans Open Wolverine

# Confidential
 Duration hh.mm Duration hh.mm Duration hh.mm Duration hh.mm
Team Performed By
BSJ DEV QAS DR1

Surbhi
Surbhi
Carol/Carlos
Lokesh
Surbhi
Team

Func/Tech

Func/Tech

Lokesh
Surbhi
Surbhi
Surbhi
Surbhi
Surbhi

Carol/Carlos

Carol/Carlos

Carol/Carlos

Carol/Carlos

Carol/Carlos
Carol/Carlos
Carol/Carlos
Surbhi
Surbhi
Surbhi
Surbhi
Surbhi
Surbhi
Surbhi
Surbhi
Carol/Carlos
Carol/Carlos
Carol/Carlos
Carol/Carlos
Carol/Carlos
Carol/Carlos

Carol/Carlos

Carol/Carlos
Carol/Carlos

Carol/Carlos
Carol/Carlos

Carol/Carlos

Carol/Carlos

Carol/Carlos

Carol/Carlos

Carol/Carlos

Carol/Carlos

# Confidential
 Carol/Carlos
Carol/Carlos

Carol/Carlos

Carol/Carlos

Carol/Carlos

Carol/Carlos

Carol/Carlos
Carol/Carlos

Carol/Carlos

Functional
Lokesh
Carol/Carlos
Carol/Carlos
Carol/Carlos

Carol/Carlos

Carol/Carlos

Carol/Carlos
Carol/Carlos
Carol/Carlos
Carol/Carlos
Carol/Carlos
Carol/Carlos
Surbhi
Surbhi
BASIS 31-Dec-99 17-Feb-00 24-Jan-00
BASIS
BASIS
BASIS
BASIS
BASIS
BASIS

BASIS

BASIS 12.30 9.27 9.27

BASIS
BASIS
BASIS
BASIS
Surbhi
Surbhi
Surbhi
Surbhi
Surbhi
Surbhi
Surbhi

Surbhi

Surbhi
Surbhi
Surbhi
Surbhi
Surbhi
Surbhi
Surbhi

# Confidential
 Surbhi

Surbhi

Surbhi
Surbhi

Surbhi

Surbhi

Surbhi

Surbhi
Surbhi
Surbhi
Lokesh
Surbhi
ECS X
BASIS
ABAP
Surbhi

Func / Security
BASIS
BASIS
BASIS
BASIS
BASIS N/A
BASIS N/A
BASIS
BASIS N/A
BASIS N/A
BASIS
Kanika
BASIS

# Confidential
 Comments

<== Total Runtime

<== Total Downtime

# Confidential
# Confidential
# Confidential
# Confidential
 Activity list
Uptime/
Activity Status Team
Downtime

Ensure all the pre-requisite are completed & validated. Pre-requiste file is located on
Open Wolverine Carol/Carlos
WWW teams folder.
All required passwords - SAP services user ID, PCEADMPO, Administrator, sidadm,
schema, SLD users, Communication Users should be provided with the Pre-requesite Open Wolverine Carol/Carlos
sheet.

Check access and Validity of SAP HEC desktop access Open SAP Surbhi/Lokesh

Source Access from WWW to SAP after Pre-requisite completion Open Wolverine Surbhi/Lokesh
Request to ECS team to enable CIFS and Migration_BW correctly Open ECS Team
Ensure that you are able to logn to Jump hosts: ROCSAPMGT01, ROCSAPMGT02 and
ROCSAPMGT03 Open SAP Surbhi/Lokesh

Check and Connect to BLOB from Azure Explorer using SAS URl in Source System ( ECS
Open SAP Surbhi
team and request new one from ECS if URL is expired.)
General Preparation Steps Open SAP Surbhi
Run export preparation using SWPM Open SAP Surbhi
Generate migration key for OS/DB migration Open SAP Surbhi

All required passwords - SAP services user ID, Administrator, sidadm, schema Open Wolverine Surbhi

Create required directory Structure for export/import Open SAP Surbhi

SWPM : Execute "Export Preparations" Open SAP Surbhi
Please change sapstart services to manual Open SAP Surbhi
Decision for Starting Downtime "Yes/No" Open Wolverine Carol/Carlos
Functional Validation Open Wolverine Lokesh
Run Reconciliation reports for Functional Validation Open Wolverine Carol/Carlos
Send results of reports for functional validation Open Wolverine Carol/Carlos
OS Activities(Parallel) Open Wolverine Carol/Carlos
Make sure that no CRON job is scheduled that affects the SAP system, such as starting
and stopping the SAP system, saving the database or similar actions. (comment out FS Open Wolverine Carol/Carlos
/interface housekeep cronjob)

Comment out the SAP auto start/stop command in HA start/stop scripts (COMMENT: vi
Open Wolverine Carol/Carlos
edit HA start/stop script) & Stop the Monitoring agents and backup scheduler

DBA Activities(Parallel) Open Wolverine Carol/Carlos

Take Full DB backup Open Wolverine Carol/Carlos
Ensure the Log mode is not Enabled Open Wolverine Carol/Carlos
Handover from Customer to SAP Open Wolverine Carol/Carlos
Export from Source System Open SAP Surbhi
DownTime Activities Open SAP Surbhi
Stop Source SAP Instances Open SAP Surbhi
Ensure Source Database is up and running Open SAP Surbhi
Create Export directory Open SAP Surbhi
Start SWPM for the export Open SAP Surbhi
Import into Target System Open SAP Surbhi
Set Log_mode to overwrite Open SAP Surbhi
Use the mass loader option of the installer, SAP note:1806935
To activate the option, set the environment variable HDB_MASSIMPORT=YES before Open SAP Surbhi
starting the SWPM
Start SWPM for the import & Parameter Input Open SAP Surbhi
Pre Load(Part of SWPM tool) Open SAP Surbhi
Table migration Import process(Part of SWPM tool) Open SAP Surbhi
Post Load(Part of SWPM tool) Open SAP Surbhi
Validate the import logs Open SAP Surbhi
Post steps Open SAP Surbhi
Update JAVA-ID and Start SAP System Open SAP Surbhi
Update UME Destination from Configtool Open SAP Surbhi
Verify Schema name Open SAP Surbhi
Check system and Compoenet Info Open SAP Surbhi
Check Lincense Open SAP Surbhi

# Confidential
 Check JCO Destination Open SAP Surbhi
Check UME Destination Open SAP Surbhi
Handover from SAP to ECS Open SAP Surbhi
ECS Post Steps Open ECS ECS
Handover from ECS to SAP Open ECS BASIS
Final Handover to Customer from SAP Open SAP BASIS

Functional Validation Open Wolverine Func / Security

Unlock Functional and Key users as per the list Open Wolverine Carol/Carlos
Enable the JCO destinations and connections to other systems & interfaces Open Wolverine Carol/Carlos
Enable/Start Interfaces Open Wolverine Carol/Carlos
Business User Validation Open Wolverine Carol/Carlos
Unlock Business users for Validation (Key User) Open Wolverine Carol/Carlos
Business User Validation Open Wolverine Carol/Carlos
Ramp Up Activities Open Wolverine Carol/Carlos
Connected systems- Customer to update the steps Open Wolverine Carol/Carlos
Releasing the system for End Users Open Wolverine Carol/Carlos

Provide system sign-off Open Wolverine

# Confidential
 Duration Duration
Duration hh.mm Duration hh.mm
Performed By hh.mm hh.mm
BSJ DR1
DEV QAS

Surbhi
Surbhi

# Confidential
 X

N/A
N/A

N/A
N/A

N/A

# Confidential
 Comments

<== Total Runtime

<== Total Downtime

###
###
###
###

###

###

###
###
###
###
###
###
###
###
###
###
###
###

###

###
###
###
###
###
###

# Confidential
 ###

###
###

###
###
###
###
###
###
###
###
###
###

# Confidential
 Activity list
Uptime/
Downtime
A
C

F
 Decision for Starting Downtime "Yes/No"

A
D

F
 Activity list

Activity

Ensure all the pre-requisite are completed

Import Automation tool TR ACDK900568
Create a non-DDIC administrator named user in 000 and Production(working) clients.
Update kernel to the latest SP level (including R3trans,TP, Brtools and DB Library) available on market place.
Ensure SPS level is same across landscape (SBX, DEV, QAS, PRD)
To avoid termination may occur in the phase RUN_RSAIMMERGE_UPG or RUN_RSAIMMERGE_UPG_SHD due to a memory overflow, Check parameter value is set to
"em/initial_size_MB = 4096" in the instance profile.For more information see SAP note 1460004
Check installed languages via SMLT / RSCPINST report / TCPDB table entry
RSCPINST should shows consistent values between TCP0I and profile parameter

Check and apply License Key and Maintenance Certificate

Deleting Application Logs. For more information see SAP note 195157
Check for old SPAU/SPDD entries in the system
Update SPAM to latest patch
SAPLOCALHOSTFULL & SAPLOCALHOST parameters should be set in Instance profile
Check & Update the Profile parameters - DIR_TRANS, DIR_PUT & DIR_EPS_ROOT
DIR_PUT=/usr/sap/<SID>/SUM/abap

Check & Update the structural requirements. Refer the comments attached.
Check & Update STMS configuration
Check & Update hostname in SMLG,STRUSTSSO2,RZ10,SMLT,RZ04 ,SM50,SM51, SM65 ,RZ12,SCC4, System status
Check & Make sure there is at least one package in the customer namespace (Z*) before the start of the upgrade/migration

Run DB Consistency check and look for Missing tables and Indexes (via DB02 Transaction) and fix them
Check OP Modes & Increase the Background processes to minimum 15 for Upgrade
Delete invalid operation modes if any exists

Add the SAPSYSTEM parameter to the start profile of your system.The entry should look like as "SAPSYSTEM=<instance number>

Take a note of activated ICM services. Check from transaction SICF

SA38 --> RS_ICF_SERV_ADMIN_TASKS --> Export of Active Services into CSV file
Make sure to clean the profile directory before the start of upgrade. Remove any old, unused profiles and move any backup copies to other directory.

Ensure that there are no unconfirmed Support Packages in your SAP system
Make sure the server group SAP_DEFAULT_BTC must include the primary application server instance.Refer SAP note 786412.
Check for customer objects with TADIR-SRCSYSTEM = 'SAP'. Refer comments for details.
The output of command sapcontrol -nr <instance_number> -function GetProcessList should be green
Check TBATG table for any erroronous entries and clean.
For 3rd party add-ons installed please verify with the software vendor if they are compatible with target version ERP 6.0 EhP7 . Please plan for necessary actions
during and before Migration based on Vendor recommendations.
Setup or Verify SNOTE Digital Signed Notes as replacement of SAPOSS RFC
Verify and clear obsolete LUWs - queues SMQ1,SMQ2 and transactional rfcs SM58 (Clear old and error)
Clear obsolete update records - SM13
Clean Invalid Temporary Tables (QCM tables) from failed conversions.
SE14 --> DB Requests (Check for all 4 options listed)
Check for running or failed incremental table conversions (ICNV)
Release the open transports or repairs
Apply SAP notes (1077403, 1807959, 2378987) to get latest programs for Cluster, Pool & BCD Numbers Checks.
SDBI_CLUSTER_CHECK report version need to be "03.2017"
Check consistency of pool tables by running report SDBI_POOL_CHECK (SAP note 1784377)
Check consistency of table clusters by running report SDBI_CLUSTER_CHECK.
Run SDBI_CLUSTER_CHECK report in background by runing individual job for some table e.g. CDCLS, EDI40, RFBLG, DOKCLU. And other tables in one background job
Run the report SDBI_CHECK_BCD_NUMBERS and fix if any inconsistencies found

It is recommended to execute the parallel runs of the job at least 2-4 weeks in advance of the expected start of migration/UC activities in other systems

WWW to check if anything relevant to be checked as per their landscape

Set the log mode for your target database SAP HANA manually to Overwrite
Generate the migration key for migration to SAP HANA database
Database specific prerequsities
Make sure there is 100GB of free DB space in the database.
Operation System and Space requirements
Ensure that system user limits are set optimally as per SAP note 1704753
About 10 GB free space in DIR_EXE
Atleast 2000 GB free space required in filesystem /usr/sap/<SID> or separate mount point for data export, media, SUM directory
About 50 GB of free space on drive having /usr/sap/trans
Provide minimum 500 MB on filesystem having /usr/sap/hostctrl
Provide minimum 2 GB on filesystem having /usr/sap/<SID>/ASCS<Instance Nr>
Provide minimum 25 GB on filesystem having /usr/sap/<SID>/D<Ins Nr>
SWPM 1.0 latest version on Source
Update SAP HOSTAGENT to 7.21 latest patch level
Target Kernel: UC Kernel 753 - DB independent Linux (Kernel Part I (753) ; OS: Linux on x86_64 64bit ; DB: Database independet)
Target Kernel: UC Kernel 753 - HANA dependent Linux (Kernel Part II (753) ; OS: Linux on x86_64 64bit ; DB: SAP HANA database)
Source Kernel: DB independent < > Latest Patch Level
Source Kernel: DB dependent < > Latest Patch Level
SUM 2.0 latest verison on Target.
Provide S-User with download authorization.

GRC Functional Prereq

Close all open workflow instances and all open survey instances(Recommened not mandatory to avoid any issues):ACT
Resolve all potential issues identified before upgrade (Optional).
Make sure sync job for all connectors to be validated are working(Provide screenshot)
Create user GUPTAKA with authorizations same as that sandbox system
Provide necessary test cases for unit testing (Mandatory)
List of Connectors to be validated in GRC SBX: RD2300(Pointing to RS1 Client 010), AFS(DV2300)
Download or screenshots all necessary connector settings in SPRO (Mandatory).
Backup all master data related information from NWBC or SAP standard table (Mandatory).
WWW to check if anything relevant to be checked as per their landscape
Handover to SAP BASIS to execute downtime further

RampDown activities

BASIS Activities(Parallel)
Make sure that all production work in the SAP system is stopped and no users are logged on to the SAP system and parallelly stop the R/3 application servers in
sequence
Lock all users (ewz5), except the technical upgrade users (DDIC, SAP* and SDC users)

Unlock key users

Restart SAP R/3 systems to kill all user sessions and start only R/3 application server
Process pending Batch Input log consistency in transactions SM35 and SM35P. See SAP note 175596 for details [2nd RUN]

Process all pending Queues and Clear the queues SMQ1 [2nd RUN]
Process all pending Queues and Clear the queues SMQ2 [2nd RUN]
Process all pending Locks and Updates and Clear SM13 failed Updates
Disable the RFC destinations and connections to other systems

Note:- To change RFC destinations pointing to other productive systems, use transaction SM59. For example, you can change the host name by adding a string like
“.syscopy” or a prefix like “#”. Then the host name points to a nonexistent server and communication is impossible using this destination.
Check for unfinished table conversion then delete QCM tables (SE14: Extras -> Invalid temp. table, mark all QCM tables and delete them
Run report RS_SCRP_D020S_CLEAN to check if there are invalid entries in tables D020S and DYNPSOURCE. If invalid entries are detected, remove them before
running the export. See also SAP Note 870601
Before performing an export, make sure that no incremental conversion is in progress
To test if an incremental conversion is in progress, run transaction ICNV. If there are any table entries in table TICNV, an incremental conversion is in progress. In this
case, you have the following options:
1. Defer the migration until the incremental conversion has finished.
2. Try to finish the incremental conversion by performing the following steps:
● If the tables are in state For conversion or in state Done, delete the entries by choosing Control Delete Entry .

● If the tables are in any other state, you have to finish the incremental conversion. Choose Assistant and proceed according to the online documentation.
Delete Entries from TATGPC and TATGPCA
Additional Downtime Steps
Make sure that the system is in business downtime now, i.e. no users should be working in the system. Then go to SPUMG menu à Extras à Additional Downtime
Steps.

Stop all the Jobs

1. Log on in client 000 as user DDIC

2. Execute report BTCTRNS1
WWW to check if anything relevant to be checked as per their landscape

Functional Validation
Run Reconciliation reports for Functional Validation
Send results of reports for functional validation
OS Activities(Parallel)
Make sure that no CRON job is scheduled that affects the SAP system, such as starting and stopping the SAP system, saving the database or similar actions.
(comment out FS /interface housekeep cronjob)
Comment out the SAP auto start/stop command in HA start/stop scripts (COMMENT: vi edit HA start/stop script) & Stop the Monitoring agents and backup
scheduler
Take a backup of the Instance, Profile directory
DBA Activities(Parallel)
Take Full DB backup
Ensure the Log mode is not Enabled

Final Ramp Down Steps

Restart SAP R/3 systems to kill all user sessions and start only R/3 CI server

Handover from Customer to SAP

Export from Source System

Stop Source SAP Instances

Ensure Source Database is up and running
Start SWPM for the export
Perform the export tasks
Transfer the export files to the target system
Transfer all files and directories (recursively) that are located on the source host in the migration export directory <EXPDIR> from the source host to the target host.
Choose one of the following methods:
Copy the export dump directory using azure storage explorer to the target host.

Import into Target System

Start SWPM for the import
Start the Import process
Validate the import logs

Full Online Backup

Prepartion for SUM Upgrade
Import SUM Missing Notes TR ACDK900010
Move cofiles and data files of SPDD TR ACDK900012
SUM Preparation - on PCE.
Copy SUM to upgrade directory
Extract SUM archive
Register SUM with Host agent
Launch URL to access SUM
Provide "sidadm" password

Quality Check
Extraction Roadmap Step
Provide the Stack Configuration Text file
This step is only relevant if you perform a release upgrade from source release SAP R/3 4.6C
Provide the Stack Configuration File
Provide the Location of the Download Directory
Provide Keyword in case of upgrade from 4.6c
Enter the password for SAP user DDIC in client 000:
DDIC PASSWORD: ********
Enter the password for OS user "sidadm"
OS PASSWORD: ********

SAP Note Implementation (CHECK4NOTES_TOOL)or import transport created in development system

Import TR BIOK017944(Applicable Incase of CU&UC from 4.6C) for more information see SAP note 867193
Check the phase log
Quality Check
Configuration Roadmap Step
Selection for the Tool Configuration
> Choose the main configuration of the tool
Caution:- Select accordingly as for CUUC and DMO advance option has to be selected.
Select accordingly : "Keep archiving on during the Whole procedure
Select "Ask some expert options"
Select the option if advance mode has been selected.
This option lets you choose the shadow instance number
Parameters Inputs: Number of process should depend upon the hardware/number of CPUs
Enter the number of ABAP,SQL and R3TRANS processes during UPTIME/DOWNTIME
background server:
>Hostname
Choose an execution strategy for transaction SGEN:
Quality Check
SPAM version check
Quality Check
On the Language Selection Screen, Ensure all Languages are selected for Update
Select the Add-ons you want to change the decision
Quality Check
Please select the Support Packages to Include during PREP_EXTENSION/BIND_PATCH as per the agreement
Prepare the Source & Target Specification document and get an approval from Customer
After Customer approves the Source & Target specification document, proceed further
Quality Check
Do you want to include a Single Change Request?
Select "NO".
Add-on Language package- Select option "Do Not Include"
Modification Adjustments Transport Requests(SPDD & SPAU)
ABAP SHADOW INSTANCE number and password for Shadow User
Check the pre-requisite for the Shadow instance number ,which customer has provided.
Provide the Unused Shadow instance Number and also provide the password for shadow schema user
Using the shadow system profiles of the previous upgraded system
Select "NO"
Evaluating the Results of the Configuration Roadmap Steps
Quality Check:
Repeat the Phase after resolving the errors reported
Evaluating the Results of the Configuration Roadmap
Checks Roadmap Step
Do you want to run the Phases JOB_RASUVAR1(2)? the RASUVAR<x> reports to save variants.

Check status of RASUVAR1 in client 000 user "DDIC"

Perform the ASU specific steps
Take confirmation from Customer for ASCS split
ASCS Split - Provide confirmation on ASCS split
solve the issues as mentioned in Checks log

Repeat the Checks phase again & Evaluate the Results and don't proceed with the next Roadmap step until unless "CHECKS" phase is completed successfully

Quality Check
Preprocessing Roadmap Step
Give Headups to Customer on the development lock and NO transports during the Import phase
Verify the log "UPGCOMPONENTCHECK.<SID>" for the errors
If required execute the report "rsupg_tadir_component_check" to correct LOCAL objects
Inform Customer on the objects reported and take approval
If approved to Ignore, Select "Ignore phase errors and proceed to next phase"
Customer Should not perform any transports during Import Phase
Take a confirmation from Customer before proceeding with Lock Development option
Inform Customer about Development Lock and the required steps to be performed
Release and confirm all the open repairs if required
Before you continue, you must release and confirm all the open repairs. If you ignore open repairs, you could lose modifications. After you have confirmed the ABAP
Workbench lock in REPACHK2, no more transports can be made into or out of the SAP system.
Inform Users\Developer about transport freeze (no import\export is possible)
Confirm "SAP" to proceed with Lock Development
ABAP Workbench Locking (Phase LOCKEU_PRE)
--> Select "Lock Now" and continue with next phase
Adjustment to the ABAP dictionary Objects?
Note:- Don't continue, Hold the SAP upgrade and perform the SPDD adjustments

Please proceed as follows:

- Logon to the shadow instance as user DDIC in client 000.
- Server: hostname Instance: <nr>
- Set the System Change option with transaction SE06.
- Create users for modification adjustment by copying user DDIC with transaction SU01.
- Logon to the shadow instance as ordinary user and make adjustments with transaction SPDD.

Perform SPDD Adjustments

DON'T Release the SPDD Request, release only the tasks under the Request
Mark SPDD Transport for export in TA SPDD
Repository adjustments processed?
Note:- After the confirmation mail from the IS team Select "Repository ok"
Check ACT_UPG errors. If there are some activation error exists, then unlock the shadow system and handover to SAPGD-IS
Perform ACT_UPG error rectification
If there is new task created for the activation errors, release the task and lock the shadow system
End of the “Preprocessing” step
Quality Check
Activities prior to Isolation
Decision for Starting Downtime "Yes/No"
RampDown activities
BASIS Activities(Parallel)
Make sure that all production work in the SAP system is stopped and no users are logged on to the SAP system and parallelly stop the R/3 application servers in
sequence
Lock all users (ewz5), except the technical upgrade users (DDIC, SAP* and SDC users)
Unlock key users
Restart SAP R/3 systems to kill all user sessions and start only R/3 application server
Process pending Batch Input log consistency in transactions SM35 and SM35P. See SAP note 175596 for details [2nd RUN]

Process all pending Queues and Clear the queues SMQ1 [2nd RUN]
Process all pending Queues and Clear the queues SMQ2 [2nd RUN]
Process all pending Locks and Updates and Clear SM13 failed Updates
Disable the RFC destinations and connections to other systems
Note:- To change RFC destinations pointing to other productive systems, use transaction SM59. For example, you can change the host name by adding a string like
“.syscopy” or a prefix like “#”. Then the host name points to a nonexistent server and communication is impossible using this destination.
Stop all the Jobs
1. Log on in client 000 as user DDIC
2. Execute report BTCTRNS1

OS Activities(Parallel)
Make sure that no CRON job is scheduled that affects the SAP system, such as starting and stopping the SAP system, saving the database or similar actions.
(comment out FS /interface housekeep cronjob)
Comment out the SAP auto start/stop command in HA start/stop scripts (COMMENT: vi edit HA start/stop script) & Stop the Monitoring agents and backup
scheduler
Take a backup of the SUM directory
Take a backup of the Instance, Profile directory
DBA Activities(Parallel)
Take Full DB backup
Ensure the Log mode is not Enabled
Final Ramp Down Steps
Restart SAP R/3 systems to kill all user sessions and start only R/3 CI server
Downtime Roadmap Step
Upgrade has reached the end of the “Preprocessing” step
Start of the Upgrade Downtime
Select " Action Completed" and chose "OK"
Check status of Downtime
Quality Check
Postprocessing & Finalization Roadmap Step
Select option "Continue with SPAU and Post phases"
Check the Results of Postprocessing
SUM BACKUP
Post steps
Perform Installation check SICK
System Integrity Check(SM21,SM50 and ST22)
Adapt old SAP profile parameters
Merge Start profile for other Application servers
During the update, the start profile is merged automatically with the instance profile for all instances that are started on the target system.
For those instances for which the profiles are not merged automatically during the update, perform manual steps to merge the profiles. The procedure is described
in SAP Note 1898687

Execute ./saproot.sh and change permission of icmbnd file

Deleting Old Tablespaces
Adapt and load system profiles in RZ10
Extract component information from table CVERS and check components version
Activate DB02
Refresh & Check DB02 for any missing table and indexes
Run Report SAP_UPDATE_DBDIFF
Check Tcodes ST22, sick, SM21, SM50
Adapt RFC server groups.
Call transaction RZ12 and change the instance name of the RFC server groups under Group assignment as per Source System
Open System: SCC4 & SE06 Client 000
Allow Changes as required for COM_PRODUCT_UPGRADE report
Change the RZ12 settings to utilize all work processes for SGEN
Manually execute report RASUVAR2 in client 000 in background
RASUVAR1 was executed manually during the PREPARE, so execute report RASUVAR2 in background mode
Client "000"
user:DDIC

Follow-up activities for language transport

Call TA smlt ; check sm37 for successful finished job RSTLAN_AFTER_UPGRADE
Adapt Glossary will be started automatically

Check the Kernel release

Check and release the delta SPDD transport request, if not released by Upgrade
Performing Follow-Up Activities for Application Link Enabling (ALE).The report must be run for each client in the system
If you are using Application Link Enabling Shared Master Data Management (SMD), you need to migrate the change pointers to the new table BDCP2. Until you have
migrated all change pointers, both the former and the new table are used. For performance reasons, migrate the change pointers as soon as possible after the
upgrade.

Procedure
1. To check which message types are affected and how many change pointers need to be migrated, run report RBDCPMIG_ALL_WITHOUT_MIG_FLAG in test mode.
2. Decide if you want to run the report for all message types at once or separately.
Running the report for each message type separately splits up the total runtime into smaller sections.
3. Run report RBDCPMIG_ALL_WITHOUT_MIG_FLAG in production mode.

Capture the output

Select mandt, count(*)from sapsr3.bdcp group by mandt;
Select mandt, count(*)from sapsr3.bdcps group by mandt;
Select mandt, count(*)from sapsr3.bdcp2 group by mandt;
Select mandt, count(*)from sapsr3.bdcpv group by mandt;
select count(*) from sapsr3.TBDA2 group by BDCP2_ACT;

Delete QCM entries

Check LONGPOST.log and inform the ABAP team
Language Supplementation (000 & productive client)
Execute Report COM_PRODUCT_UPGRADE
Make sure that operation mode is defined on the central instance as per the Original settings
Execute RTCCTOOL from SE38 & fix Addon Impl , Addon/Upgrade steps
DBA: ICF Service-Activation for WebDynpro DBA Cockpit
SAP Note1245200
Give heads-up to SAP ABAP team for their availability
Handover from SAP SDC to ECS
ECS Post Steps
ADS Setup
Addon installation
Handover from ECS to SAP SDC
ABAP Adjustments
Move SPDD/SPAU/HCA TR to Production
Perform Delta SPDD/SPAU adjustments
Functional Validation

RFC update for all connectors in use (Defined under SAP_R3_LG group), also which are assigned to default action and data source

S_RFCACL role movement with delta auth

Import TR ACTK904018 for error insert reason code while submitting access request
Correct SWU3
Smoke testing (RS1- Completed, AFS- Not delivered yet)
UAT
Handover from SAP to Customer
Functional Validation
Business User Validation
Unlock Business users for Validation (Key User)
Business User Validation
Ramp Up Activities
Connected systems- Customer to update the steps
Releasing the system for End Users
Provide system sign-off
 Start Date & Time End Date & Time Duration
Status Team Performed By
MM/DD/YY MM/DD/YY hh:mm:ss

Open SAP/Customer BASIS

Open Customer
Open Customer
Open Customer
Open Customer
Open Customer

Open Customer

Open Customer
Open Customer
Open Customer
Open Customer
Open Customer

Open Customer

Open Customer
Open Customer
Open Customer

Open Customer

Open Customer

Open Customer

Open Customer

Open Customer

Open Customer

Open Customer
Open Customer
Open Customer
Open Customer
Open Customer

Open Customer

Open Customer
Open Customer
Open Customer
Open Customer
Open Customer
Open Customer

Open Customer

Open Customer
Open Customer

Open Customer

Open Customer
Open SAP
Open SAP
Open
Open Customer
Open
Open Customer
Open Customer
Open Customer
Open Customer
Open Customer
Open Customer
Open Customer
Open Customer
Open Customer
Open Customer
Open Customer
Open Customer
Open Customer
Open Customer
Open Customer
Open
Open
Open Customer GRC
Open Customer GRC
Open Customer GRC
Open Customer GRC
Open Customer GRC
Open SAP GRC
Open
Open SAP GRC
Open Customer
Open SAP GRC

Open Customer

Open Customer

Open Customer

Open Customer

Open Customer

Open Customer
Open Customer
Open Customer
Open Customer
Open Customer
Open

Customer
Open

Open Customer

Open Customer

Open

Customer
Open

Open
Customer
Open
Open

Open

Open Customer
Open
Customer
Open

Open

Open Customer

Open
Open Customer
Open Customer
Open Customer
Open Customer
Open Customer

Open Customer

Open Customer

Open Customer
Open Customer
Open Customer
Open Customer

Open Customer

Open Customer
Open

Open Customer

Open SAP BASIS

Open SAP BASIS

Open SAP BASIS
Open SAP BASIS
Open SAP BASIS
Open

Open SAP BASIS

Open
Open
Open
Open SAP BASIS
Open SAP BASIS
Open SAP BASIS
Open SAP BASIS
Open SAP
Open SAP BASIS
Open SAP
Open SAP
Open SAP BASIS
Open SAP BASIS
Open SAP BASIS
Open SAP BASIS
Open SAP BASIS
Open SAP BASIS
Open SAP BASIS
Open SAP BASIS

Open SAP BASIS

Open SAP BASIS

Open SAP BASIS
N/A SAP BASIS

Open SAP BASIS

Open SAP BASIS

Open SAP BASIS

N/A SAP BASIS
Open SAP BASIS
Open SAP BASIS
Open SAP BASIS

Open SAP BASIS

Open SAP BASIS

Open SAP BASIS

Open SAP BASIS

Open SAP BASIS

Open SAP BASIS
Open SAP BASIS
Open SAP BASIS
Open SAP BASIS
Open SAP BASIS
Open SAP BASIS
Open SAP BASIS
Open SAP BASIS
Open SAP BASIS
Open SAP BASIS

N/A SAP BASIS

Open SAP BASIS

Open SAP BASIS

Open SAP BASIS

Open SAP BASIS
Open SAP BASIS
Open SAP BASIS
Open SAP BASIS
Open SAP BASIS
Open SAP BASIS

Open SAP BASIS

N/A SAP BASIS
Open SAP BASIS
N/A SAP BASIS
Open SAP BASIS

Open SAP BASIS

Open SAP BASIS

Open SAP BASIS
N/A SAP BASIS
Open SAP BASIS
Open SAP BASIS
Open SAP BASIS
Open SAP BASIS
N/A SAP BASIS
N/A SAP BASIS
N/A SAP BASIS

Open SAP BASIS

Open SAP BASIS

N/A SAP BASIS

Open SAP BASIS

Open SAP BASIS

Open SAP BASIS

Open SAP BASIS

Open SAP BASIS

Open SAP BASIS

Open SAP BASIS

Open SAP BASIS
Open SAP BASIS
Open SAP BASIS
Open SAP BASIS
Open SAP BASIS
Open SAP BASIS
Open SAP BASIS
Open SAP BASIS

Open SAP BASIS

Open SAP BASIS

Open SAP BASIS
Open SAP BASIS
Open SAP BASIS
Open SAP BASIS
Open SAP BASIS
Open SAP BASIS
Open SAP BASIS

Open SAP BASIS

Open SAP BASIS

Open SAP BASIS

Open SAP BASIS

Open SAP BASIS

Open SAP BASIS
Open SAP BASIS
Open SAP BASIS
Open SAP BASIS
Open SAP BASIS
Open SAP BASIS
Open SAP BASIS
Open SAP BASIS

Open SAP BASIS

Open SAP BASIS

Open SAP BASIS
Open SAP BASIS
Open SAP BASIS
Open SAP BASIS
Open SAP BASIS
Open SAP BASIS
Open SAP BASIS
Open SAP BASIS
Skip SAP BASIS

N/A SAP BASIS

Open SAP BASIS

N/A SAP BASIS
Open SAP BASIS
Open SAP BASIS
Open SAP BASIS

Open SAP BASIS

Open SAP BASIS

Open SAP BASIS

Open SAP BASIS

Open SAP BASIS

N/A SAP BASIS

Open SAP BASIS

Open SAP BASIS

Open SAP BASIS
N/A SAP BASIS

N/A SAP BASIS

N/A Customer BASIS
N/A SAP BASIS
Open SAP BASIS
Open SAP BASIS
N/A SAP BASIS

Open SAP BASIS

Open SAP BASIS

Open SAP BASIS
Open ECS ECS X
Open ECS ECS X
N/A ECS ECS X
Open ECS BASIS
Open SAP ABAP
Open SAP BASIS
Open SAP ABAP
Open SAP Functional

Open Wolverine BASIS\GRC

Open Wolverine BASIS\GRC

Open Wolverine BASIS\GRC
Open SAP GRC
Open SAP GRC
Open Wolverine GRC
Open SAP BASIS
Open Wolverine Func/Security
Open Wolverine BASIS
Open Wolverine BASIS
Open Wolverine BASIS
Open Wolverine BASIS
Open Wolverine BASIS
Open Wolverine BASIS
Open Wolverine BASIS
Comments
Can Wolverine team update these RFC in source itself during isolation activity, so that after migration these
RFC are automatically working?
 Activity list
Uptime/
Activity Status
Downtime

Ensure all the pre-requisite are completed & validated Open Wolverine
Source Access from WWW to SAP after Pre-requisite completion for
validaitons. Open Wolverine

Target access to be checked as per credentials sheet provided Open SAP

Create a non-DDIC administrator named user in 000 and

Production(working) clients Open SAP

check if CIFS utility has been mounted on Source as well as Target servers Open SAP

check if /migration_OTH is mounted on target servers Open SAP

Take system screenshots of all Relevant T-codes required Open SAP

Take the backup of kernel, global and profile of target PCE server Open SAP
Take the target skeleton system HANA DB Full backup Open SAP

Extract SWPM and set environment variables before starting SWPM Open SAP
Process all pending Batch Input jobs in transactions SM35 and SM35P. See
SAP note 175596 for details. Delete obsolete entries (unprocessed or in Open Wolverine
error)[1st run]
Process all pending Queues and Clear the queues SMQ1 [1st run] Open Wolverine
Process all pending Queues and Clear the queues SMQ2 [1st run] Open Wolverine
Decision for Starting Downtime "Yes/No" Open Wolverine
RampDown activities Open Wolverine
A BASIS Activities(Parallel) Open Wolverine
Put System to Maintenance Mode / SwitchOff Alerting/ Open Wolverine
Lock out users from SAP, and use SM04 to remove logged in users Open Wolverine
Send reminders to Logged in users SM02 Open Wolverine
Make sure that all production work in the SAP system is stopped and no
users are logged on to the SAP system and parallelly stop the R/3 Open Wolverine
Unlock required
application users
servers (Lock all users, except the technical upgrade
in sequence
users (DDIC, SAP*) and Users working on Migration and Isolation Steps
Open Wolverine
in productive client (SAPOSS, Carlos, Carol, Srikanth,
Abhishek, ,kumarpr) and WWW Technical Basis Users )
Restart SAP R/3 systems to kill all user sessions and start only R/3
Open Wolverine
application server
Process pending Batch Input log consistency in transactions SM35 and
Open Wolverine
SM35P. See SAP note 175596 for details [2nd RUN]

Stop scheduled periodic Backups, checkDB, Update Statistics (DB13 or

Open Wolverine
External Backup scheduler)

Clean all the extractor queues in the system. Open Wolverine

check SM37 and cancel Active Jobs Open Wolverine

Clear unwanted SCOT entries. Stop SCOT mails Open Wolverine

Disconnect Interfaces (Stop Data interfacing with external systems,

Open Wolverine
Portal, etc.)

Process all pending Queues and Clear the queues SMQ1 [2nd RUN] Open Wolverine

Process all pending Queues and Clear the queues SMQ2 [2nd
Open Wolverine
RUN]SM58, Process all IDOCS (BD64, etc.).
check if canceled or pending update requests exist in the system. If
canceled or pending updates exist, you must update these again or Open Wolverine
delete them from all clients (SM13) and SM12
Remove Process chains from schedule for outage period Open Wolverine

Process pending Batch Input log consistency in transactions SM35 and

Open Wolverine
SM35P. See SAP note 175596 for details

# Confidential
 WWW to add any other activity as part of isolation ( Please check with
Open Wolverine
WWW Functional as well)
Disable
Stop anythe RFC destinations
additional and
application connections
server, if any. to other systems Open Wolverine
Note:- To change RFC destinations pointing to other productive
systems, use transaction SM59. For example, you can change the host
Open Wolverine
name by adding a string like “.syscopy” or a prefix like “#”. Then the
check for unfinished
host name points to atable conversion
nonexistent then
server delete
and QCM tables (SE14:
communication is Open Wolverine
Extras -> Invalid
impossible using temp. table, mark all QCM tables and delete them
this destination.
Delete Entries from TATGPC and TATGPCA Open Wolverine
Stop all the Jobs
1. Log on in client 000 as user DDIC Open Wolverine
2. Execute report BTCTRNS1
WWW to check if anything relevant to be checked as per their landscape Open Wolverine

Functional Validation Open Wolverine

Run Reconciliation reports for Functional Validation Open Wolverine
Send results of reports for functional validation Open Wolverine
OS Activities(Parallel) Open Wolverine

Make sure that no CRON job is scheduled that affects the SAP system,
such as starting and stopping the SAP system, saving the database or Open Wolverine
similar actions. (comment out FS /interface housekeep cronjob)

Comment out the SAP auto start/stop command in HA start/stop scripts

(COMMENT: vi edit HA start/stop script) & Stop the Monitoring agents Open Wolverine
and backup scheduler
DBA Activities(Parallel) Open Wolverine
File System backup of (Application Server)

/usr/sap/GTD
Open Wolverine
/sapmnt/GTD

Also, backup any software installed by WWW

Take Full DB backup ( File mode and not via Backint ) and provide the path Open HEC
as well as DDIC(000) ,Schema & SYSTEM passwords of Tenant DB

Ensure the Log mode is not Enabled Open Wolverine

Handover from Customer to SAP Open Wolverine
Transfer Backup files to Target along with data file (secstore) and relevant
Open SAP
files required in PCE from source
Restore into Target system Open SAP
Set Log_mode to overwrite Open SAP
Start SWPM for the import & Parameter Input Open SAP
select homogeneous system copy method Open SAP

check if background jobs i.e BTC=0 ( interrupt before system starts option) Open SAP

Validate the logs once SWPM Restore is completed Open SAP

Post steps Open SAP
update hdbuserstore if applicable Open SAP
Perform Installation check SICK Open SAP
Adopt old profile parameters Open SAP
Start additional App server Open SAP
se14 ->delete tpfet and tpfht data from table Open SAP
import profiles of active servers Open SAP
Execute SGEN Open SAP

SICF_INST-> execute for WEB DYNPRO ABAP & WEB DYNPRO DBA COCKPIT Open SAP

SMLT Language supplementation if applicable Open SAP

Complete Excel spreadsheet for ECS Handover Open SAP
Validation of schema Open SAP
Slicense check Open SAP
KERNEL info and system info Open SAP
Target Component check Open SAP
System Integrity check(SM21,SM50 and ST22) Open SAP
Ensure that there are no open transport requests(SE01) Open SAP

# Confidential
 Remove old hostnames
Run RZ21 --> Topology --> Segment Overview and click Display Overview.
2. Click Local Segments Tab --> Edit and delete the entries from the list Open SAP
(which is old application server).
3. And save it.

Update spad with new server Open SAP

Update number range if required Open SAP
Migration check -> SHDB_Migration_check Open SAP
"Refresh & check DB02 for any missing table and indexes Open SAP
Run Report SAP_UPDATE_DBDIFF " DB02, SE14, ST06,SMLT
Update SE06 settings Open SAP

Migrate the ABAP secure store:

1. Call transaction SECSTORE to change the entries in the secure storage. Open SAP
2. In case of entries with errors with message text System-dependent data
for entry … changed, see SAP Note:816861

check the logon groups and the assignment of the application servers to
the logon groups as per Source System (transaction SMLG). check RZ12 and Open SAP
RZ04
Restart CI and all app server Open SAP
load system profiles in RZ10 Open SAP

STMS (To be taken care by ECS), By SAP only Create Virtual Transport route Open SAP

Set Log_mode to normal Open SAP

Take a complete restart of the system Open SAP
Handover from SAP SDC to ECS Open SAP
ECS Post Steps Open ECS
Handover from ECS to SAP SDC Open ECS
ABAP Adjustments if applicable Open SAP
Perform Transports as per list provided by SAP team Open SAP
Final Handover to Customer from SAP Open SAP

Functional Validation Open Wolverine

Unlock Functional and Key users as per the list Open Wolverine

Testing & Reconciliation reports(Execution of Validation Reports) Open Wolverine

Test Batch Input processing (SM35,SM35P) Open Wolverine

Business User Validation Open Wolverine
Unlock Business users for Validation (Key User) Open Wolverine
Business User Validation Open Wolverine
Ramp Up Activities Open Wolverine
Connected systems- Customer to update the steps Open Wolverine
Releasing the system for End Users Open Wolverine
SSL Certificatte import Open Wolverine
SSO Tasks Open SAP
Mount /usr/sap/trans Open Wolverine

# Confidential
 Duration
Duration hh.mm Duration hh.mm Duration hh.mm
Team Performed By hh.mm
DEV QAS GTT
SBX

BASIS Carol/Carlos

BASIS Carol/Carlos

BASIS Praveen

BASIS Praveen

BASIS Praveen

BASIS Praveen

BASIS Praveen
BASIS Praveen
BASIS Praveen

BASIS Praveen

BASIS Carol/Carlos

BASIS Carol/Carlos
BASIS Carol/Carlos
Carol/Carlos
BASIS Carol/Carlos
BASIS Carol/Carlos
BASIS Carol/Carlos
BASIS Carol/Carlos
BASIS Carol/Carlos

BASIS Carol/Carlos

BASIS Carol/Carlos

BASIS Carol/Carlos

BASIS Carol/Carlos

BASIS Carol/Carlos

BASIS Carol/Carlos

BASIS Carol/Carlos

BASIS Carol/Carlos

BASIS Carol/Carlos

BASIS Carol/Carlos

BASIS Carol/Carlos

BASIS Carol/Carlos

BASIS Carol/Carlos

BASIS Carol/Carlos

# Confidential
 BASIS Carol/Carlos

BASIS Carol/Carlos

BASIS Carol/Carlos

BASIS Carol/Carlos
BASIS Carol/Carlos

BASIS Carol/Carlos

BASIS Carol/Carlos

BASIS Carol/Carlos
BASIS Carol/Carlos
BASIS Carol/Carlos
BASIS Carol/Carlos

BASIS Carol/Carlos

BASIS Carol/Carlos

BASIS Carol/Carlos

BASIS Carol/Carlos

BASIS Erick/Surendra

BASIS Carol/Carlos
BASIS Carol/Carlos

BASIS Praveen

BASIS Praveen
BASIS Praveen
BASIS Praveen
BASIS Praveen

BASIS Praveen

BASIS Praveen
BASIS Praveen
BASIS Praveen
BASIS Praveen
BASIS Praveen
BASIS Praveen
BASIS Praveen
BASIS Praveen
BASIS Praveen

BASIS Praveen

BASIS Praveen
BASIS Praveen
BASIS Praveen
BASIS Praveen
BASIS Praveen
BASIS Praveen
BASIS Praveen
BASIS Praveen

# Confidential
 BASIS Praveen

BASIS Praveen
BASIS Praveen
BASIS Praveen

BASIS Praveen

BASIS Praveen

BASIS Praveen

BASIS Praveen

BASIS Praveen
BASIS Praveen

BASIS Praveen

BASIS Praveen
BASIS Praveen
BASIS Praveen
ECS X
BASIS Erick/Surendra
BASIS
BASIS Praveen
BASIS Praveen

BASIS Carol/Carlos

BASIS Carol/Carlos

BASIS Carol/Carlos
BASIS Carol/Carlos
BASIS Carol/Carlos N/A
BASIS Carol/Carlos N/A
BASIS Carol/Carlos
BASIS Carol/Carlos N/A
BASIS Carol/Carlos N/A
BASIS Carol/Carlos
BASIS Kanika
BASIS Carol/Carlos

# Confidential
 Comments

<== Total Runtime

<== Total Downtime

# Confidential
# Confidential
# Confidential
 Activity list

Uptime/
Activity Status
Downtime

1 Ensure all the pre-requisite are completed & validated . Pre-requiste file is located on WWW teams folder. Open Wolverine

All required passwords - SAP services user ID, PCEADMPO, Administrator, sidadm, schema, SLD users,
1.1 Communication Users should be provided with the Pre-requesite sheet. Open Wolverine

2 Check access and Validity of SAP HEC desktop access Open SAP
3 Source Access from WWW to SAP after Pre-requisite completion Open Wolverine

3,1 Ensure that you are able to logn to Jump hosts: ROCSAPMGT01, ROCSAPMGT02 and ROCSAPMGT03 Open SAP

Check and Connect to BLOB from Azure Explorer using SAS URl in Source System ( ECS team and request
3.2 new one from ECS if URL is expired.) Open SAP
4 Source Validations by SAP Services Open SAP
4.1 Ensure that all the internal links for PO are working in Source-Technical Open SAP
4.2 Ensure that all the internal links for PO are working in Source-Functional Open SAP
Data collection of the Source system and Take validation screenshots from Source System before starting
4.3 the migration activities- Technical Open SAP

Data collection of the Source system and Take validation screenshots from Source System before starting
4.4 Open SAP
the migration activities- Functional
5 Decision for Starting Downtime "Yes/No"- WWW to confirm. Open Wolverine
6 Ramp Down Activities to be performed by WWW Open Wolverine
6.1 Basis Activities(Parallel) Open Wolverine
6.1.1 Put System to Maintenance Mode / SwitchOff Alerting/ Open Wolverine
Make sure that all production work in the SAP system is stopped and no users are logged on to the SAP Open Wolverine
6.1.2 system.

Open Wolverine
Lock out users from SAP, and use nwa/session mgt to remove logged in users.
6.1.3 Unlock required users. Lock all users, except the Administrator and Communication users (eg PIAFSID,
PIRWBSID, PIDIRSID, PIREPSID, PIISSID, PIAPPLSID, PIBPMMSGSID,PIAPPLSID, PCEADMPO, Administrator,
Carol, Carlos, SLD_CL_SID, SLD_DS_SID, PISUPER and other Communication and key users)

6.1.4 Disable DR, SwitchOff Alerting/Archive Log, Archive log off Open Wolverine
6.1.5 Stop scheduled periodic Backups, CheckDB, Update DB Statistics (DB13 or External Backup scheduler) Open Wolverine
Disconnect Interfaces (Stop Data interfacing with external systems, Portal, etc.). Also Stop all Messages Open Wolverine
6.1.6
from SAP PO Partner Systems.
6.1.7 All communication channels should be stopped. Open Wolverine
Open Wolverine
6.1.8 WWW to add any other activity as part of isolation ( Please check with WWW Functional as well).

6.2 OS Activities(Parallel) Open Wolverine

Make sure that no CRON job or any task is scheduled in task scheduler that affects the SAP system, such as Open Wolverine
starting and stopping the SAP system, saving the database or similar actions. (comment out FS /interface
6.2.1 housekeeping cronjob)

Comment out the SAP auto start/stop command in HA start/stop scripts (COMMENT: vi edit HA start/stop Open Wolverine
6.2.2 script) & Stop the Monitoring agents and backup scheduler

6.3 DBA Activities(Parallel) Open Wolverine

6.3.1 Take Full DB backup Open Wolverine
6.3.2 Ensure the Log mode is not Enabled Open Wolverine
6.4 Final Ramp Down Step Open Wolverine
6.4.1 Restart SAP R/3 systems to kill all user sessions and start only R/3 CI server Open Wolverine
7 Handover from WWW to SAP SDC Open Wolverine
8 Source System Export from SWPM Open SAP
8.1 Check Source Database is up and running Open SAP
8.2 Create required directory Structure for export in PO Source OS. Open SAP
8.3 Execute export preparation using SWPM 1.0 SP33 Open SAP
8.4 Stop Source SAP Instances Open SAP
8.5 Start Export from Source System Open SAP

# Confidential
 8.6 Upload export dump to BLOB Open SAP
9 General Preparation Steps before Import Open SAP
9.1 Check if cifs and /migration_OTH are in place. Open SAP
9.2 Import export dump to PCE using azcopy utility Open SAP
9.3 Extract and place SWPM 1.0 SP33 and other required media for import Open SAP

Backup of the configuration files from /Sybase/SID/ASE-16_0

File are
9.4 1.SID.cfg Open SAP
2. hosts.allow
3. interfaces

Update following Sybase DB Parameters before import :

sp_dboption "SID", "enforce dump tran sequence", "false"
9.5 sp_dboption "SID", "select into/bulkcopy/pllsort", "true" Open SAP
sp_dboption "SID", "trunc log on chkpt", "true"

10 SWPM Import / Database Refresh Open SAP

10.1 Start SWPM Open SAP
10.2 Launch URL to access SWPM Open SAP
Run Database Refresh using SWPM->Open SWPM Path: Generic Options > SAP ASE > Refresh Database
10.3 content Open SAP

10.4 Pre Load(Part of SWPM tool) Open SAP

10.5 Table migration Import process(Part of SWPM tool) Open SAP
10.6 Post Load(Part of SWPM tool) Open SAP
10.7 Validate the import logs Open SAP
11 Post steps after SWPM Import Open SAP
11.1 Take a Backup of PO DB and move it to "/migration" file system Open SAP

Update following Sybase DB Parameters before import :

sp_dboption "SID", "enforce dump tran sequence", "true"
11.2 Open SAP
sp_dboption "SID", "select into/bulkcopy/pllsort", "false"
sp_dboption "SID", "trunc log on chkpt", "false"

11.3 Update j2ee/instance and Start Java application. Open SAP

11.4 Start SAP Application Open SAP
11.5 Check License Open SAP
11.6 Check System details and Compare Components with Source Open SAP
11.7 Check UME Destination Open SAP
11.8 Update CIM Model (Updated during SBX Cycle), if done. Open SAP
11.9 Import SSL Certificates Open SAP

11.10 Functional Unit configuration --> Disable the enabled ones and enable automatically by selecting only the Open SAP
Functional Units enabled on Source system.
11.11 Take System Restart Open SAP
11.12 Clear CPA Cache : 1) Delta 2) Full and validate CPA Refresh History ( It should be green) Open SAP
11.13 Check Connectivity with ESR, IB and SLD Open SAP
Check Cache Connectivity:
11.14 Open SAP
Goto SOA->Monitoring->Cache Connectivity test
11.15 Check and change the Resource Adapter 'inboundRA' and 'outboundRA' similar to Source Open SAP
11.16 Adjust HTTP and RFC destinations Open SAP
11.17 Update prxyinfo files for gateway connectivity Open SAP
11.18 Update Technical System data in PO SLD through RZ70 in Source Systems. Open SAP
Communication Channels adjustment according to the adapter meta-data in source system. (Comment: PO
11.19 Functional Activity in Parallel) Open SAP

Quick PO functional Validation-

11.20 - Verify adapter engine hostname in Integration Dir. Open SAP

12 Handover from SAP SDC to ECS Open SAP

ECS Post Steps Open ECS
ADS Setup N/A ECS
Addon installation N/A ECS
15 Handover from ECS to WWW Open ECS
15.1 Update Business Systems in PO SLD Open Wolverine
15.2 CTS+ Configuration Open Wolverine
16 Functional Validation Open Wolverine
16.1 Unlock Functional and Key users as per the list Open Wolverine
16.2 Enable the JCO destinations and connections to other systems & interfaces Open Wolverine
16.3 Enable/Start Interfaces Open Wolverine
17 Business User Validation Open Wolverine
17.1 Unlock Business users for Validation (Key User) Open Wolverine
17.2 Business User Validation Open Wolverine
18 Ramp Up Activities Open Wolverine

# Confidential
 19 Connected systems- Customer to update the steps Open Wolverine

20 Releasing the system for End Users Open Wolverine

21 Provide system sign-off Open Wolverine

# Confidential
 Duration hh.mm Duration hh.mm Duration hh.mm
Team Performed By
DEV SBX DR1

BASIS Carlos

BASIS Carlos

BASIS/Func Aman/Ravi
BASIS Carlos

BASIS/Func Aman/Ravi

BASIS Aman
BASIS/Func Aman/Ravi
BASIS Aman
Func Ravi

BASIS Aman

Func Ravi

BASIS/ Func
BASIS/Func
BASIS Carlos
BASIS Carlos

BASIS Carlos

BASIS Carlos
BASIS Carlos
BASIS/Func Carlos

BASIS/Func Carlos
BASIS Carlos

BASIS Carlos
BASIS Carlos

BASIS Carlos

BASIS Carlos
BASIS Carlos
BASIS Carlos
BASIS Carlos
BASIS Carlos
BASIS Carlos
BASIS Aman
BASIS Aman
BASIS Aman
BASIS Aman
BASIS Aman
BASIS Aman

# Confidential
 BASIS Aman
BASIS Aman
BASIS Aman
BASIS Aman
BASIS Aman

BASIS Aman

BASIS Aman

BASIS Aman
BASIS Aman
BASIS Aman

BASIS Aman

BASIS Aman
BASIS Aman
BASIS Aman
BASIS Aman
BASIS Aman
BASIS Aman

BASIS Aman

BASIS Aman
BASIS Aman
BASIS Aman
BASIS Aman
BASIS Aman
BASIS Aman
BASIS Aman

BASIS Aman

BASIS Aman
BASIS Aman
BASIS Aman
BASIS Aman
BASIS Aman
BASIS Aman
BASIS Aman
BASIS Aman

PO Func Ravi

PO Func Ravi

BASIS Aman
ECS X
ECS X
ECS X
BASIS Erick/Surendra
BASIS Carlos
BASIS Carlos
Func / Security Func
BASIS Carlos
BASIS Carlos
BASIS Carlos

BASIS Carlos

BASIS Carlos

# Confidential
 BASIS Carlos

BASIS Carlos

# Confidential
 Comments

# Confidential
# Confidential
# Confidential
 Activity list
Uptime/
Activity Status
Downtime

Ensure all the pre-requisite are completed & validated Open Wolverine
Source Access from WWW to SAP after Pre-requisite completion for validaitons. Open SAP
Technical members to inform functional team members to start validation. Open SAP
Ensure that you are able to logn to Jump hosts: ROCSAPMGT01, ROCSAPMGT02 and
ROCSAPMGT03 Open SAP

Check and Connect to BLOB from Azure Explorer using SAS URl in Source System ( ECS team and
request new one from ECS if URL is expired.) Open SAP

Check if cifs mount point are present in source and target. Open SAP/ECS/Wolverine
/migration_ERP mount point are in place . Open ECS
Azcopy installed on all the servers Open ECS
Functional data collection (configuration snapshot)(Parallel) Open SAP
Run Platform Task Automation Tool( Tr. Need to be imported RS1K900008 ) Open SAP
Identify big tables and Run table splitting preparation, if needed Open SAP
Generate migration key for OS/DB migration Open SAP
SBP/Windows DBBP Oracle Patches should be applied.(As per Snote : 1915316 - Database: Patches
for 12.1.0.2 ) Open Wolverine

Clear data in GVD_SGASTAT table (As this table belong to oracle) Open Wolverine
If target DB is HANA: Update latest version of cluster check using SAP Note: 1077403 as applicable
(Report SDBI_CLUSTER_CHECK) Open Wolverine

If target DB is HANA: Cluster Tables and Pool Tables check as per SAP Note 1784377 (Report
Open Wolverine
SDBI_POOL_CHECK and SDBI_CHECK_BCD_NUMBERS)
All required passwords - SAP services user ID, DDIC in 000, User in business client, sidadm, schema,
Open Wolverine
SAPJSF
SE38: Check Cluster Tables for corrupt or invalid cluster records or decimal numbers Open Wolverine
SM13: update or delete the corresponding update requests Open Wolverine
DB02 - Missing Table / Index check & fix if required Open Wolverine
Brtools: Update database statistics Open Wolverine
Brtools: Update database statistics Open Wolverine
Create required directory Structure for parallel export/import Open SAP
SWPM : Execute "Export Preparations" Open SAP
DB02: Extract Large tables > 3GB and verify with from POC/MOC Open SAP
Create Table Splitting plan Open SAP
Extend PSAPTEMP 20% of DBSIZE Open Wolverine
SWPM: Execute "Export Table Splitting" Open SAP
Backup Export Directory and make it empty Open SAP
SM02 : Message for system down for export Open Wolverine
Please change sapstart services to manual Open Wolverine

Brtools: Update database statistics (update/verify if ran in recent past) Open Wolverine

DB02 - Missing Table / Index check & fix if required Open Wolverine
SM13: update or delete the corresponding update requests Open Wolverine
SE14: Delete QCM tables Open Wolverine
SE38: Run report SMIGR_CREATE_DDL Open SAP
SM02 : Message for system down for export Open Wolverine
Please change sapstart services to manual Open SAP
Process all pending Batch Input jobs in transactions SM35 and SM35P. See SAP note 175596 for
Open Wolverine
details. Delete obsolete entries (unprocessed or in error)[1st run]
Process all pending Queues and Clear the queues SMQ1 [1st run] Open Wolverine
Process all pending Queues and Clear the queues SMQ2 [1st run] Open Wolverine
WWW to add any other activity as part of isolation ( Please check with WWW Functional as well). Open Wolverine
Decision for Starting Downtime "Yes/No" Wolverine
RampDown activities Open Wolverine
A BASIS Activities(Parallel) Open Wolverine
Make sure that all production work in the SAP system is stopped and no users are logged on to the Open Wolverine
SAP system and parallelly stop the R/3 application servers in sequence
Lock all users (ewz5), except the technical upgrade users (DDIC, SAP* and SDC users) Open Wolverine
Unlock key users Open Wolverine

# Confidential
 Restart SAP R/3 systems to kill all user sessions and start only R/3 application server Open Wolverine

Process pending Batch Input log consistency in transactions SM35 and SM35P. See SAP note
175596 for details [2nd RUN] Open Wolverine

Open Wolverine
Process all pending Queues and Clear the queues SMQ1 [2nd RUN]

Open Wolverine
Process all pending Queues and Clear the queues SMQ2 [2nd RUN]
Disable the RFC destinations and connections to other systems
Note:- Open Wolverine
ProcessTo
Before allchange
pending
performing
RFC
an
destinations
Locks and make
export,
pointing
Updates
sure and to other
Clear
that SM13 productive systems, use transaction SM59. For
failed conversion
no incremental Updates
example, you can change the host name by adding a string like “.syscopy”isorin aprogress
prefix like “#”. Then
To
the host name points to a nonexistent server and communication isICNV.
test if an incremental conversion is in progress, run transaction If thereusing
impossible are any
thistable
entries in table TICNV, an incremental conversion is in progress. In this case, you have the following Open Wolverine
destination.
Check for unfinished table conversion then delete QCM tables (SE14: Extras -> Invalid temp. table,
options:
mark
1. all QCM
Defer tables and delete
theRS_SCRP_D020S_CLEAN
migration until them
the incremental Open Wolverine
Run report to checkconversion
if there arehas finished.
invalid entries in tables D020S and
2. Try to finish the
DYNPSOURCE. incremental
If invalid entries conversion
are detected,by remove
performingthem the following
before steps:
running the export. See also SAP
● If the tables are in state For conversion or in state Done, delete the entries by choosing Control Open Wolverine
Note 870601
Delete Entry .
● If the tables are in any other state, you have to finish the incremental conversion. Choose Open Wolverine
Assistant and proceed according to the online documentation.
Delete Entries from TATGPC and TATGPCA Open Wolverine
BW : Run SAP_DROP_TEMPTABLES SAP Notes:1139396 N/A Wolverine
Put System to Maintenance Mode / SwitchOff Alerting/ Open Wolverine
Make sure that all production work in the SAP system is stopped and no users are logged on to the Open Wolverine
SAP system.
Disable DR, SwitchOff Alerting/Archive Log, Archive log off Open Wolverine
Stop all the Jobs
1. Log on in client 000 as user DDIC Open Wolverine
2. Execute report BTCTRNS1

Functional Validation Open Wolverine

Run Reconciliation reports for Functional Validation Open Wolverine
Send results of reports for functional validation Open Wolverine
OS Activities(Parallel) Open Wolverine
Make sure that no CRON job is scheduled that affects the SAP system, such as starting and stopping
the SAP system, saving the database or similar actions. (comment out FS /interface housekeep Open Wolverine
cronjob)

Comment out the SAP auto start/stop command in HA start/stop scripts (COMMENT: vi edit HA
Open Wolverine
start/stop script) & Stop the Monitoring agents and backup scheduler
DBA Activities(Parallel) Open Wolverine
Take Full DB backup Open Wolverine
Ensure the Log mode is not Enabled Open Wolverine
Final Ramp Down Steps Open Wolverine
Restart SAP R/3 systems to kill all user sessions and start only R/3 CI server Open Wolverine
Handover from Customer to SAP Open Wolverine
Export from Source System Open SAP
DownTime Activities Open SAP
Stop Source SAP Instances Open SAP
Ensure Source Database is up and running Open SAP
Create Export and Exchange directory Open SAP
Start SWPM for the parallel export Open SAP
Perform the Paraller export tasks Open SAP
Import into Target System Open SAP
Set Log_mode to overwrite Open SAP
Use the mass loader option of the installer, SAP note:1806935
To activate the option, set the environment variable HDB_MASSIMPORT=YES before starting the Open SAP
SWPM
Start SWPM for the import & Parameter Input Open SAP
Pre Load(Part of SWPM tool) Open SAP
Table migration Import process(Part of SWPM tool) Open SAP
Post Load(Part of SWPM tool) Open SAP
Validate the import logs Open SAP
Post steps Open SAP
Start additional App server Open SAP
Verify Schema name Open SAP
Perform Installation check SICK Open SAP
Execute SGEN Open SAP
SMLT Language supplementation Open SAP

# Confidential
 Complete Excel spreadsheet for HEC Handover Open SAP
Validation of schema Open SAP
Slicense check Open SAP
KERNEL info and system info Open SAP
Target Component check Open SAP
System Integrity Check(SM21,SM50 and ST22) Open SAP
Ensure that there are no open transport requests(SE01) Open SAP
Migration check -> SHDB_Migration_Check Open SAP
BW only: Start program RS_BW_POST_MIGRATION in the background Open SAP
"Refresh & Check DB02 for any missing table and indexes Open SAP
Run Report SAP_UPDATE_DBDIFF " DB02, SE14, ST06,SMLT
Update SE06 settings Open SAP

Migrate the ABAP secure store:

1. Call transaction SECSTORE to change the entries in the secure storage.
2. In case of entries with errors with message text System-dependent data for entry … changed, Open SAP
see SAP Note:816861

Check the logon groups and the assignment of the application servers to the logon groups as per Open SAP
Source System (transaction SMLG). Check RZ12
Adapt old SAP profile parameters Open SAP
Restart CI and all app server Open SAP
load system profiles in RZ10 Open SAP
STMS (To be taken care by HEC), By SAP only Create Virtual Transport route Open SAP
Set Log_mode to normal Open SAP
Handover from SAP SDC to ECS Open SAP
ECS Post Steps Open ECS
ADS Setup Open ECS
Addon installation Open ECS
Handover from ECS to SAP SDC Open ECS
Perform Transports as per list provided by SAP team Open SAP
Functional data comparison (configuration snapshot)(Parallel) Open SAP
Final Handover to Customer from SAP Open SAP
Functional Validation Open Wolverine
Unlock Functional and Key users as per the list N/A Wolverine
Testing & Reconciliation reports(Execution of Validation Reports) N/A Wolverine
Test Batch Input processing (SM35,SM35P) Open Wolverine
Business User Validation Open Wolverine
Unlock Business users for Validation (Key User) N/A Wolverine
Business User Validation N/A Wolverine
Ramp Up Activities Open Wolverine
Connected systems- Customer to update the steps Open Wolverine
Releasing the system for End Users Open Wolverine
SSL Certificatte import Open Wolverine

SSO Tasks Open SAP

Mount /usr/sap/trans work with ECS Open Wolverine/ECS

# Confidential
 Duration hh.mm Duration hh.mm Duration hh.mm
Team Performed By
DEV SBX QAS

BASIS Carol/Carlos
BASIS Vishal Soni
BASIS Vishal Soni

Func/Tech Vishal/Saumyadeep

Func/Tech Vishal/Saumyadeep

Carol/Carlos

Func Saumyadeep
BASIS Vishal Soni
BASIS Vishal Soni
BASIS Vishal Soni

BASIS Carol/Carlos
BASIS Carol/Carlos
BASIS Carol/Carlos

BASIS Carol/Carlos

BASIS Carol/Carlos
BASIS Carol/Carlos
BASIS Carol/Carlos
BASIS Carol/Carlos
BASIS Carol/Carlos
BASIS Carol/Carlos
BASIS Vishal Soni
BASIS Vishal Soni
BASIS Vishal Soni
BASIS Vishal Soni
BASIS Carol/Carlos
BASIS Vishal Soni
BASIS Vishal Soni
BASIS Carol/Carlos
BASIS Carol/Carlos

BASIS Carol/Carlos

BASIS Carol/Carlos
BASIS Carol/Carlos
BASIS Carol/Carlos
BASIS Vishal Soni
BASIS Carol/Carlos
BASIS Vishal Soni
BASIS Carol/Carlos

BASIS Carol/Carlos
BASIS Carol/Carlos
BASIS Carol/Carlos
BASIS Carol/Carlos
BASIS Carol/Carlos
BASIS Carol/Carlos
BASIS Carol/Carlos
BASIS Carol/Carlos
BASIS Carol/Carlos

# Confidential
 BASIS Carol/Carlos

BASIS Carol/Carlos

Carol/Carlos
BASIS

Carol/Carlos
BASIS

Carol/Carlos
BASIS

Carol/Carlos
BASIS
BASIS Carol/Carlos

Carol/Carlos
BASIS

Carol/Carlos
BASIS
BASIS Carol/Carlos
BASIS Carol/Carlos
BASIS Carol/Carlos
BASIS
Carol/Carlos
BASIS Carol/Carlos

BASIS Carol/Carlos

BASIS Carol/Carlos
BASIS Carol/Carlos
BASIS Carol/Carlos
BASIS Carol/Carlos

BASIS Carol/Carlos

BASIS Carol/Carlos

BASIS Carol/Carlos
Carol/Carlos
BASIS Carol/Carlos
BASIS Carol/Carlos
BASIS Carol/Carlos
BASIS Carol/Carlos
BASIS Vishal Soni
BASIS Vishal Soni
BASIS Vishal Soni
BASIS Vishal Soni
BASIS Vishal Soni
BASIS Vishal Soni
BASIS Vishal Soni
BASIS Vishal Soni
BASIS Vishal Soni
BASIS Vishal Soni
BASIS Vishal Soni
BASIS Vishal Soni
BASIS Vishal Soni
BASIS Vishal Soni
BASIS Vishal Soni
BASIS Vishal Soni
BASIS Vishal Soni
BASIS Vishal Soni
BASIS Vishal Soni
BASIS Vishal Soni
BASIS Vishal Soni

# Confidential
 BASIS Vishal Soni
BASIS Vishal Soni
BASIS Vishal Soni
BASIS Vishal Soni
BASIS Vishal Soni
BASIS Vishal Soni
BASIS Vishal Soni
BASIS Vishal Soni
BASIS Vishal Soni
BASIS Vishal Soni
BASIS Vishal Soni

BASIS Vishal Soni

BASIS Vishal Soni

BASIS Vishal Soni
BASIS Vishal Soni
BASIS Vishal Soni
BASIS Vishal Soni
BASIS Vishal Soni
BASIS Vishal Soni
ECS X
ECS X
ECS X
BASIS
BASIS
Func Saumyadeep
BASIS
Func / Security Carol/Carlos
BASIS Carol/Carlos
BASIS Carol/Carlos
BASIS Carol/Carlos
BASIS Carol/Carlos
BASIS Carol/Carlos N/A
BASIS Carol/Carlos N/A
BASIS Carol/Carlos
BASIS Carol/Carlos N/A
BASIS Carol/Carlos N/A
BASIS Carol/Carlos

BASIS/Security

BASIS Carol/Carlos

# Confidential
 Duration hh.mm
Comments
RS1

<== Total Runtime

<== Total Downtime

# Confidential
# Confidential
# Confidential
# Confidential
# Confidential
# Confidential
 Activity list

Uptime/
Activity Status
Downtime

Ensure all the pre-requisite are completed & validated Open Wolverine
General Preparation Steps Open Wolverine
Ensure that you are able to logn to Jump hosts: ROCSAPMGT01, ROCSAPMGT02 and ROCSAPMGT03 Open SAP

Check and Connect to BLOB from Azure Explorer using SAS URl in Source System ( ECS team and request
new one from ECS if URL is expired.) Open SAP

/migration_ERP mount point are in place . Open ECS

All required passwords - SAP services user ID, Administrator, sidadm, schema Open Wolverine

Create required directory Structure for export/import Open SAP

SWPM : Execute "Export Preparations" Open SAP
Please change sapstart services to manual Open SAP
Decision for Starting Downtime "Yes/No" Open Wolverine
Put System to Maintenance Mode / SwitchOff Alerting/ Open Wolverine
Make sure that all production work in the SAP system is stopped and no users are logged on to the SAP Open Wolverine
system.
Disable DR, SwitchOff Alerting/Archive Log, Archive log off Open Wolverine
Open Wolverine
WWW to add any other activity as part of isolation ( Please check with WWW Functional as well).

Functional Validation Open Wolverine

Run Reconciliation reports for Functional Validation Open Wolverine
Send results of reports for functional validation Open Wolverine
OS Activities(Parallel) Open Wolverine

Make sure that no CRON job is scheduled that affects the SAP system, such as starting and stopping the SAP
Open Wolverine
system, saving the database or similar actions. (comment out FS /interface housekeep cronjob)

Comment out the SAP auto start/stop command in HA start/stop scripts (COMMENT: vi edit HA start/stop Open Wolverine
script) & Stop the Monitoring agents and backup scheduler

DBA Activities(Parallel) Open Wolverine

Take Full DB backup Open Wolverine
Ensure the Log mode is not Enabled Open Wolverine
Handover from Customer to SAP Open Wolverine
Export from Source System Open SAP
DownTime Activities Open SAP
Stop Source SAP Instances Open SAP
Ensure Source Database is up and running Open SAP
Create Export directory Open SAP
Start SWPM for the export Open SAP
Import into Target System Open SAP
Set Log_mode to overwrite Open SAP
Use the mass loader option of the installer, SAP note:1806935 Open SAP
To activate the option, set the environment variable HDB_MASSIMPORT=YES before starting the SWPM
Start SWPM for the import & Parameter Input Open SAP
Pre Load(Part of SWPM tool) Open SAP
Table migration Import process(Part of SWPM tool) Open SAP
Post Load(Part of SWPM tool) Open SAP
Validate the import logs Open SAP
Post steps Open SAP
Update JAVA-ID and Start SAP System Open SAP
Verify Schema name Open SAP
Check Product Instance Open SAP

# Confidential
 Check Lincense Open SAP
Check JCO Destination Open SAP
Check system and Compoenet Info Open SAP
Check Message Server Open SAP
Check UME Destination Open SAP
Handover from SAP SDC to HEC Open SAP
ECS Post Steps Open ECS
Handover from HEC to SAP SDC Open ECS
Final Handover to Customer from SAP Open SAP

Functional Validation Open Wolverine

Unlock Functional and Key users as per the list Open Wolverine
Enable the JCO destinations and connections to other systems & interfaces Open Wolverine
Enable/Start Interfaces Open Wolverine
Business User Validation Open Wolverine
Unlock Business users for Validation (Key User) Open Wolverine
Business User Validation Open Wolverine
Ramp Up Activities Open Wolverine

Connected systems- Customer to update the steps Open Wolverine

Releasing the system for End Users Open Wolverine

Provide system sign-off Open Wolverine

# Confidential
 Duration
Team Performed By hh.mm
SBX

0.00

BASIS Carol/Carlos
BASIS Carol/Carlos
Func/Tech Vishal/Saumyadeep

Func/Tech Vishal/Saumyadeep

BASIS Carol/Carlos

BASIS Vishal Soni

BASIS Vishal Soni
BASIS Vishal Soni

BASIS Carol/Carlos
BASIS
Carol/Carlos
BASIS Carol/Carlos
BASIS
Carol/Carlos

BASIS Carol/Carlos
BASIS Carol/Carlos
BASIS Carol/Carlos
BASIS Carol/Carlos

BASIS Carol/Carlos

BASIS Carol/Carlos

BASIS Carol/Carlos
Carol/Carlos
BASIS Carol/Carlos
BASIS Vishal Soni
BASIS Vishal Soni
BASIS Vishal Soni
BASIS Vishal Soni
BASIS Vishal Soni
BASIS Vishal Soni
BASIS Vishal Soni
BASIS Vishal Soni
BASIS Vishal Soni

BASIS Vishal Soni

BASIS Vishal Soni

BASIS Vishal Soni
BASIS Vishal Soni
BASIS Vishal Soni
BASIS Vishal Soni
BASIS Vishal Soni
BASIS Vishal Soni
BASIS Vishal Soni
BASIS Vishal Soni

# Confidential
 BASIS Vishal Soni
BASIS Vishal Soni
BASIS Vishal Soni
BASIS Vishal Soni
BASIS Vishal Soni
BASIS Vishal Soni
ECS
BASIS
BASIS
Func /
Security
BASIS Carol/Carlos
BASIS Carol/Carlos
BASIS Carol/Carlos
BASIS Carol/Carlos
BASIS Carol/Carlos
BASIS Carol/Carlos
BASIS Carol/Carlos

BASIS Carol/Carlos

BASIS Carol/Carlos

# Confidential
 Comments

<== Total Runtime

<== Total Downtime

###
###
###
###

###

###

###
###
###
###
###
###
###
###
###
###
###
###

###

###
###
###
###
###
###

# Confidential
 ###

###
###

###
###
###
###
###
###
###
###

###

###

# Confidential
 Activity list
Uptime/
Activity Status
Downtime

Ensure all the pre-requisite are completed & validated Open Wolverine
Connection Set-up Validation Open Wolverine
Cloud connection setttings - Validate Open Wolverine
Sub-Account - Agents details validate Open Wolverine
Import connection validatoin Open Wolverine
Live connection validation Open Wolverine
File connection validation Open Wolverine
SAC Content validation Open Wolverine
Roles validation Open Wolverine
Other dependent objects high level validation Open Wolverine

Decision for Starting Downtime "Yes/No" Open Wolverine

RampDown activities Open Wolverine
A BASIS Activities(Parallel) Open Wolverine
Dual Maintenance Open Wolverine

Functional Validation Open Wolverine

Handover from Customer to SAP Open Wolverine

SAC ContentS Open Wolverine

Handover from SAP SDC to HEC Open SAP

Handover from HEC to SAP SDC Open HEC

Final Handover to Customer from SAP Open SAP

# Confidential
 Duration hh.mm Duration hh.mm
Team Performed By
QAS PROD

SAC Functional
BASIS
BASIS
BASIS
SAC Functional Giri/Shubham 1 Hour
SAC Functional Giri/Shubham 1 Hour
SAC Functional Giri/Shubham 2 Hour
SAC Functional Giri/Shubham 8 Hours
SAC Functional Giri/Shubham 1 Hour
SAC Functional Giri/Shubham 2 Hour

BASIS
BASIS

BASIS

SAC Functional Giri/Shubham

BASIS
SAC Functional Giri/Shubham

BASIS

BASIS

SAC Functional

# Confidential
 Comments

<== Total Runtime

<== Total Downtime

# Confidential
Phase Activity Transport Type Transport Request
Pre-Upgrade
During Upgrade ABAP - SPDD WorkBench CQ2K900024
Missing Notes for SAP EHP7 Upgrade WorkBench CQ2K900016

Post Upgrade ABAP - SPAU WorkBench

Fix WorkBench
Pre-Upgrade
During Upgrade
Post Upgrade ABAP - HCA WorkBench BS1K904019
Post Upgrade ABAP - HCA WorkBench BS1K904021
Fix
Pre-Migration Platform Task Automation Tool WorkBench Req ACTK900002
During Upgrade Missing SUM Notes ACTK9000010
During Upgrade SPDD Activity ACTK9000012
Post Upgrade SPAU Adjustment ACTK904016
Post Upgrade SPAU Adjustment ACTK904014
Fix
Pre-Migration Platform Task Automation Tool RS1K900008
Pre-Upgrade
During Upgrade
Post Upgrade HCA WorkBench Req RS1K904026
Post Upgrade HCA WorkBench Req RS1K904028
Fix
Pre-Upgrade
During Upgrade Migration SAC - Export Option
Post Upgrade Migration SAC - Export Option
Fix SAC_Fix SAC - Export Option
Post Upgrade Delta SPAU Adjustment WorkBench Req ACDK904578
Post Upgrade Delta HCA Adjustment WorkBench Req ACDK904581
Post Upgrade SPAU Adjustment WorkBench Req CQ2K904046
Post Upgrade Unicode Adjustment WorkBench Req CQ2K904056
Post Upgrade Unicode Adjustment WorkBench Req CQ2K904053
Description Team

SAP SDC: WB: CQ2-ABAP SPDD Activity 21st Feb 2022 ABAP
Implemented following missing notes caought by SUM
0001431044
0001523714
0001609895
0001614802
0001680583
0001719375
0001719977
0001861585
0002045835
0001714734
0002294460
0001994245
0002311092
0001741347
0002925002
0001279687
0002408559
0002122333

SAP SDC: WB: BS1- Hana Custom Code Adjustment 21st Feb 2022 (Local Workbench) ABAP
SAP SDC: WB: BS1- Hana Custom Code Adjustment 24st Feb 2022 ABAP

Platform Task Automation Tool

Missing SUM Notes
WWW: SPDD Adjustment GRC System (ACT) V1 ABAP
SAP SDC: WB: GRC-ABAP SPAU Activity 26st Mar 2022 ABAP
SAP SDC: WB: GRC-ABAP SPAU Activity 26st Mar 2022 ABAP

Platform Task Automation Tool

SAP SDC: WB: RS1- Hana Custom Code Adjustment 21st Feb 2022 ABAP
SAP SDC: WB: RS1- Hana Custom Code Adjustment ABAP

SAP SDC: ALL <SID>- SAC Migration Objects <Date>

SAP SDC: ALL <SID>- SAC Migration Objects <Date>
SAP SDC: ALL <SID>- SAC Migration BreakFix <Date>
SAP SDC: WB: GRC-ABAP Delta SPAU Activity 11th May 2022 ABAP
SAP SDC: WB: GRC-ABAP Delta HCA Activity 11th May 2022 ABAP
SAP SDC: WB: CQ2- SPAU Activity ABAP 20th Apr 2022 ABAP
SAP SDC: WB: CQ2- Unicode Adj Activity ABAP 29th Apr 2022 ABAP
SAP SDC: WB: CQ2- Unicode Adj Activity ABAP 29th Apr 2022 ABAP
Owner Date System
SBX CQ2 AFS
PCEADMAFS 21st Feb 2022 SBX CQ2 AFS
RAIKR 12th Feb 2022

SBX CQ2 AFS

SBX CQ2 AFS
SBX CQ2 AFS
SBX BS1 BW
SBX BS1 BW
PCEADMBW 21-Feb-22 SBX BS1 BW
PCEADMBW 24-Feb-22 SBX BS1 BW
SBX BS1 BW
TAMMINSR 31-Jan-22 SBX ACT GRC
TAMMINSR 10-Feb-22 SBX ACT GRC
SPDD_USR 11-Feb-22 SBX ACT GRC
Chaubeyn 26-Feb-22 SBX ACT GRC
Chaubeyn 26-Feb-22 SBX ACT GRC
SBX ACT GRC
SONIVI 10-Feb-22 SBX RS1 RET
SBX RS1 RET
SBX RS1 RET
PCEADMRET 21-Feb-22 SBX RS1 RET
PCEADMRET 21-Feb-22 SBX RS1 RET
SBX RS1 RET
SAC Migration
SAC Migration
SAC Migration
SAC Migration
Chaubeyn 11-May-22 DEV ACD GRC
Chaubeyn 11-May-22 DEV ACD GRC
PCEADMAFS 20-04-2022 SBX CQ2 AFS
PCEADMAFS 29-04-2022 SBX CQ2 AFS
PCEADMAFS 29-04-2022 SBX CQ2 AFS
Activity No. Component Activity

1 Network

2 Network
3 System

4 System
5
 WWW Infrastructure Tasks
Activity long description Sequence Dependency
Start Date End Date Duration Status Performed by

Open

Open

Open

Open

Open
Comments