Not all SAP Notes can be applied via the SNOTE transaction. Some are information only, providing no code corrections. Others entail corrections that can only be done manually. This latter type of SAP Note should be applied to your SAP system in conjunction with a trained ABAP programmer. Also, SAP recommends that SNOTE change requests NOT be transported into other systems. Use the SNOTE transaction in each SAP system that needs the correction, and delete the generated change requests since they should never be transported and could lock resources during application of other SAP Notes and support package application.
If you do not have a working OSS connection, you can download an OSS note from the SAP Marketplace using the SAP Download Manager and use the upload feature in SNOTE to load it into the SAP instance instead.
1. Log on to client 000 in the appropriate SAP system.
2. Go to transaction SNOTE.
3. On the Note Assistant - Version XXX/XXXX: Worklist screen, on the top-most menu bar click Goto → SAP Note download.
4. On the Note Assistant: Download Notepopup, type the number of the SAP note in the Note number box and click the clock picture-icon. A SAP Note XXXXXX is being downloaded message will appear in the bottom status bar. If you get a communications error message, verify that saprouter is up and try again.
5. Once the SAP Note has been downloaded, it will appear on the Assistant - Version XXX/XXXX: Worklist screen under the SAP Notes → New navigation tree. The SAP Note can only be applied if there is a blue box with a black arrow to the left of the note number. If there is a gray diamond instead, the downloaded note cannot be applied or is not application for this SAP system.
6. To apply the SAP Note, on the Note Assistant - Version XXX/XXXX: Worklist screen double click on the downloaded SAP Note number.
7. On the Note Assistant – Display Note XXXXXXscreen, read the note text to see if there are any necessary manual tasks to be performed after the note is applied. When you are ready to apply the note, click on the clock picture-icon.
8. If there are any prerequisite SAP Notes which need to be applied to the SAP system before the downloaded SAP Note can be applied, a list will appear in a Load the following notes into your SAP system popup will appear. Click the clock picture-icon to download these prerequisite SAP Notes as well. If any of the prerequisite SAP Notes must be applied in parallel with the original downloaded SAP Note, a list will appear in a SAP Note queue to be Importedpopup. Click the clock picture-icon to apply all the listed SAP Notes.
9. Before applying any SAP Notes to your SAP system, a Confirmation: SAP Note read popup will appear. Once you have read the information contained in this popup, click the Yes button.
10. A standard Make repairs in foreign namespaces... popup will appear. Click the green √ to continue.
11. On the Prompt for transportable Workbench request popup, click the blank page picture-icon to create a new change request. On the Create Request popup, fill in the Short description and click the Save picture-icon. You will be returned to the Prompt for transportable Workbench requestpopup which contains the generated change request number for this system change. Click the green √ to continue.
12. On the Confirm changes popup, click the green √ to continue.
13. After the SAP Note has been applied to the SAP system, you will be returned to the Note Assistant - Version XXX/XXXX: Worklistscreen. There is no completion message. Click the green √ and pencil picture-icon.
14. On the Set Processing Status for Note XXXXXXpopup, click on the Completed line to turn “on” the radio button. Click the green √. You can now leave the SNOTEtransaction. Modified programs, functions, etc. may require recompilation.
15. If the OSS note you applied changed a ABAP program, you must go to the SE38 transaction and manually recompile the program. If it changed a function, go to transaction SE37 and click the Single Test button – this is enough to force the function to rebuild and you can back out of the SE37transaction.
No comments:
Post a Comment