NOTE

IMPLEMENTATION
NOTE IMPLEMENTATION
• SAP notes are small corrections delivered by sap before releasing the
support package.
• It is used to fix the single bug and enhance the functionality.
• While implementing note, it generates the workbench request , once
request is released , we can’t revert the changes.
• The generated TR will be moved to the quality and production system
respectively.
Types of Notes
• We have three types of notes

• Manual note : it provides the manual steps which needs to be taken

care.
• Information note: It provides the information about the errors or
solutions.
• Correction note(snote): Using snote t-code we can implement the
corrections.
How to deploy SAP Note :
1.Go to SAP transaction SNOTE > MENU >GOTO > "Download SAP note" and enter the
note number you want to deploy.
2.Now press the check button to see if the note implementation status. If you see note
status "Can be Implemented" then press Execute button to proceed.
3.This will download the SAP note in in your system , now drill down under the
"New" section to check your note.
4.Select the note and go to Menu > SAP Note >"Implement SAP Note".
5.This will trigger following confirmation screens, just confirm.
6.Now system will prompt you for the transport request to capture all the changes.Click
on "Create" button and give some short description in the next window and Save.

7.Now the system will prompt you to confirm the changes that will implement with this SAP note.
8. Once you confirm the changes, your note will be deployed and you will found your note in "In
processing" section (please note that at this stage your note is already deployed).
9.Once the changes are verified you can change the status of SAP note to "Completed". To do that
select the SAP note and go to Menu >SAP Note > "Set Processing Status".

10. Your SAP note is deployed and now you can move the transport to other system to implement
this note.
SYSTEM REFRESH
AND
SYSTEM COPY
SYSTEM COPY: Building a system with source data with new SID.

SYSTEM REFRESH : Building a system with source data without

changing the SID.
SYSTEM COPY

• A system copy is a duplicate of an SAP system. You re-install all instances

of the SAP system but create the target database as a copy of the source
database (database copy). Some settings in the target system may be
different from those in the source system.
 SOURCE SYSTEM:
• PRE STEPS: • POST STEPS:
• No failed updates. • Unlock users.
• No failed TRFC’s. • Release the suspended jobs.
• No invalid temporary tables. • Release the server to business.
• No old lock entries.
• Suspend background jobs.
• Lock users.
• Make sure enough space at operating system level
to create export dictionary.
TARGET SYSTEM :
• Once export is completed , copy the exported source system data to target system.
• We have to log on to target system before uninstalling and should make sure information backups are done.
• Take screenshot of 1) client settings 2) Logical system settings 3) logon groups 4) update groups 5)RFC
server groups 6)SCOT settings 7) op modes.
• Once all backup is completed uninstall target system.
• Using source system exported data we build target system.
• To build target system we have to install Database of our choice and SAP central instance installation .
• We need to enter SAP migration key if we are performing SAP heterogeneous system copy.
POST STEPS IN TARGET SYSTEM:
• Delete the old license and install new license .
• Delete old profiles and install new profiles.
• Reconfigure the STMS and import secure information data which we have taken backup.
• Import RFC connections , logical system name and printer devices.
• Delete the finished and cancelled jobs.
• Delete old spool requests.
SYSTEM REFRESH:

• A System Refresh, which is similar to a System Copy, is simply copying one SAP
System to another when the target SAP System already exists.
• System refresh activity comprises of following 3 phases
• Pre refresh activity
• Refresh activity (Database restoration)
• Post refresh activity
PRE STEPS:
1 . Export of user master data and authorizations from all SAP clients on the target system(SCC8)
2 . Please take snapshots of :
Client settings (SCC4) ; Logon groups (SMLG); Processing groups (RZ12) ;AL11, SE03 and SM61
Printer details (SPAD) ;Operation modes (RZ03, RZ04 and SM63)
RFCs (SM59); Partner profiles (WE20) and ports (WE21); Logical systems (BD54);Services that are
active (SICF)
These screenshots are to be captured because after system refresh, we need to check and maintain
the same settings in target system
3. Using SE01 transaction , create transport request for backing up of AL11,SE03,SMLG( logon
groups) RZ12(processing groups) , SM69,SPAD, SM61,RZ03.
Refresh activity :

• 1) Please stop the target sap system and handover to database team

• 2) Database team will restore the data from source system to target system and validate

• 3) Once everything is fine, database team will handover system to SAP Basis team
 POST STEPS:
• Start database and SAP
• Perform preliminary checks
• Cancel unwanted background jobs and disable / reconfigure SMTP and FAX in SM37 , SCOT.
• Change client details in SCC4
• Maintain RFC connections in SM59
• Update profiles in RZ10
• Reconfigure operation modes in RZ04
• Install SAP license
• Recreate SAP* user using SU01 and restart SAP system
• Configure TMS – SE06 and STMS
• Import user master records back – import transports in STMS and do post processing in SCC7.
• Run logical system remapping job