Skip to end of metadata
Go to start of metadata
  • 1.Is it possible to download old version of SAP Notes?

  • 2. Is the implementation of SAP Notes using SNOTE a kind of modification?

  • 3. How to adjust "Note Corrections" part in SPAU list?

  • 4. What is the difference between processing status and implementation status for one SAP Note?

  • 5. I downloaded one SAP Note using SNOTE, but I cannot find it in my worklist in SNOTE initial screen, why?

  • 6. How to judge whether one SAP Note has prerequisite SAP Notes or not, and how to implement these prerequisite notes?

  • 7. When I was implementing one SAP Note, some prerequisite notes were asked to be downloaded. But after downloading, I found some of them were obsolete, no need to implement them. Why they are required to be downloaded even not necessary to implement them at all?

  • 8. Why there is no implementation logs for sap notes in the system?

  • 9. Why I cannot implement the SAP note again after downloading the latest version?

  • 10. Can I de-implement already-implemented SAP notes?

  • 11. The corrections included in the already-implemented SAP note were not completely implemented, I tried to implement this SAP note again, but was told that "SAP Note already completely implemented". Can I de-implement this SAP note and implement it again?

  • 12. During implementation a SAP Note, yellow traffic light occurred for some objects with message "Corrections incompletely copied". Does the yellow traffic light just mean a warning which can be ignored?

  • 13. Inactive Objects are found in phase CHECK_INACT_OBJECTS during SPs implementation using SPAM/SAINT. Where did these inactive object come from? How to handle them?

  • 14. Is it possible to implement SAP Notes using SNOTE during upgrade? 

 

1.Is it possible to download old version of SAP Notes?

No, it is impossible. When note creator/owner found there was inconsistencies or errors in the SAP Note, he/she would do correction accordingly and release a new version for this note. whenever you download SAP notes, you will always get the latest version ONLY. Even SAP Support cannot help you download the old version of one SAP Note. 

Back to top

 

2. Is the implementation of SAP Notes using SNOTE a kind of modification?

  Yes, implementation of SAP Notes using SNOTE is also a kind of modification, although the same code change delivered by the correction instructions included in the SAP Notes will be implemented again during system update (SPS implementation, EHP installation or system upgrade). It can also explain why "note corrections" part is displayed in SPAU list. As to how to adjust note correction in SPAU list, please refer to 3.  

Back to top


3. How to adjust "Note Corrections" part in SPAU list?

  During or after system update (upgrade or SPs implementation etc.), you should perform modification adjustment for SAP Notes that were implemented using SPAU. In SPAU list, already-implemented SAP Notes were determined with different adjustment modes which are identified with different traffic lights as below:    

  "Green traffic light" means "SAP Note implemented, although parts included in Support Package". By clicking the green traffic light, it will change to "green check mark" automatically.    
"Yellow traffic light" means " SAP Note implemented, but not included in Support Package" or "Correction implemented by an SAP Note and included in a Support Package, however SAP Note version is different ". By clicking the yellow traffic light, SAP Note can be implemented again. Before that, it is better to download the latest version for it using SNOTE, and "determine adjustment mode" in SPAU.    
"Traffic light without colors" (called "grey traffic light" as well) means "Correction implemented by an SAP Note and included in a Support Package". By clicking the grey traffic light, you can reset the SAP Note.
"Green question mark" means "Adjustment mode for SAP Note implementation undetermined". You should do two things: First step, download the latest version of the SAP Note using SNOTE; Second step, calculate the adjustment modes again by "Goto" -> "Determine Adjustment Mode " in SPAU. After that, refresh SPAU list, generally the question mark will change to yellow/green/grey traffic light, then you can go ahead with the adjustment accordingly.
"Green check mark" means "adjustment already done, no action any more". After you adjusted one SAP Note, yellow/green/grey traffic light will change to green check mark, or disappear from SPAU list. For more detailed information, you can refer to online help:
http://help.sap.com/saphelp_snc_uiaddon_10/helpdata/en/48/b41a60fc096ff4e10000000a42189b/content.htm  

 

4. What is the difference between processing status and implementation status for one SAP Note?
Implementation status indicates whether the SAP note was implemented completely or not. "Can be implemented" means that the SAP note is valid but is not implemented yet ( or implemented before but de-implemented now). "Completely implemented" means that all the valid correction instructions within the SAP note was completely implemented (or you have confirmed that the SAP note was implemented completely even though it was not.) "Incompletely implemented" means that not all valid correction instructions were implemented, it is still necessary for you to continue the implementation. "obsolete version implemented" means that the version implemented before is an old one, now you just have downloaded the latest version, it is necessary to implement it again. By clicking "Implement SAP note" button, the old version will be de-implemented and then the latest version will be implemented. "Cannot be implemented" means that the SAP note is not valid for your system, it is not necessary to implement this SAP note. So implementation status indicates whether the note was implemented completely or not. If implementation status is "completely implemented", even though processing status is still "in processing", we can say that the SAP note was implemented.
Generally the processing status is not important, can be ignored. Well, if the SAP note was completely implemented by you, you can set the processing status to be "completed", then this SAP note will disappear from your worklist in SNOTE's initial screen. Generally it is not necessary for you to do it. But when your worklist is too long, too large, it might lead to long time for you to open SNOTE, then to set the processing status for those already-implemented sap notes to be "completed" would be helpful.

 

5. I downloaded one SAP Note using SNOTE, but I cannot find it in my worklist in SNOTE initial screen, why?
The reason might be that thi SAP note was downloaded and processed by other users before, so it is not in your worklist. You can display this SAP note by Goto->SAP Note Browser->input the SAP note number->Execute, you will see this SAP note under who's name. Then you can display implementation log to check whether it was downloaded with the latest version.

 

6. How to judge whether one SAP Note has prerequisite SAP Notes or not, and how to implement these prerequisite notes?
We can judge whether the SAP Note to be implemented has prerequisite notes or not from correction instructions. For example:

As you can see that correction instruction 0120061532 0000878907 within SAP Note 1035309 for BBPCRM 400 needs prerequisite notes like 639960, 681002, 691379......932314. But it is not necessary to implement these prerequisite notes manually one by one. When you implement SAP Note 1035309 using SNOTE, SNOTE will check whether these prerequisite notes are existing in the system or not. If not yet, the prerequisite notes will be downloaded automatically. Then SNOTE will implement all necessary prerequisite notes together with note 1035309 automatically. 

 

7. When I was implementing one SAP Note, some prerequisite notes were asked to be downloaded. But after downloading, I found some of them were obsolete, no need to implement them. Why they are required to be downloaded even not necessary to implement them at all?

It is mentioned in SAP note 421211 that SNOTE can determine whether the SAP note is valid or not ONLY after it has been downloaded. So even though many prerequisite SAP notes were downloaded automatically during implementing the target SAP note, not all of them are necessary to be implemented. Finally you migth find that only few of them can be implemented together with the target SAP note. BTW, you do not need to wonder about which note to be implemented firstly, which one is the second, the third. . . SNOTE will calculate and implement all the necessary notes in the right sequence automatically. But before you start to implement them using SNOTE, please check the text of these notes carefully, whether there is manual steps to be implemented or not. If there are pre-implementation manual steps mentioned in these notes, please implement all the pre-implementation  manual steps firstly. Most of the pre-implementation manual steps are to update DDIC objects(table, structure, view etc.) in SE11, as such manual changes cannot be performed by SNOTE. If you do not perform the pre-implementation manual steps,  syntax errors might occur during implementation using SNOTE.


8. Why there is no implementation logs for sap notes in the system?
As you know, it is recommended to implement SAP notes in development system, after that transport the generated request into next systems. The request includes the note information, all the objects changed by the implementation. However implementation log is not included in the request. So Generally implementation log can only be found in development system. Well, if you downloaded and adjusted SAP notes manually during SPAU adjustment in QAS and PRD systems, you can also find the relevant information in implementation log. 

 

9. Why I cannot implement the SAP note again after downloading the latest version?
  Generally after downloading the latest version of the SAP note, the impelmentation status will change to "obsolete version implemented" automatically. But it happen ONLY when there is change in correction instruction. If there is no change on correction instruction, for example, the note creator/owner just edited the note description, the implementation status will not change, keeps as "completely implemented". In such situation, there is nothing necessary for you to do.


10. Can I de-implement already-implemented SAP notes?
It is not recommended to de-implement any already-implemented SAP note. Even you de-implemented the SAP note, the corrections included in this SAP note will be implemented again sooner or later with the corresponding support package in the future.

  SAP Support can help customers to implement SAP Notes which were not implemented completely, but we cannot help customers de-implement any already-completely-implemented SAP Note. Only if sap developer(s) suggested customers to de-implement one individual SAP note, can SAP support help de-implement this individual SAP note for customers.
 

If the corrections included in the SAP note were not completely implemented, or errors occured after note implementation, you have to implement this SAP note again. If the implementation status of this SAP note has been changed to "completely implemented" after implementation, you can "de-implement" it in a special way, then implement it again. About how to "de-implemnt" the SAP note in the specail way, please refer to 11.


11. The corrections included in the already-implemented SAP note were not completely implemented, I tried to implement this SAP note again, but was told that "SAP Note already completely implemented". Can I de-implement this SAP note and implement it again?
Yes, it is possible for you to "de-implement" this SAP note and implement it again.
If corrections included in the SAP note were not completely implemented, you must have ignored some errors during implementation and confirmed that the SAP note was completely implemented in the final screen during implementation as below:

The above screen generally indicates that not all corrections were implemented completely, if you clicked "Yes", the implementation status will change to "completely implemented". If you want to implement this SAP note again later, you will be refused with a message "SAP note already completely implemented". 
In order to implement this SAP note again, you should firstly "de-implement" this SAP note and implement it again later. 
You can click the "Reset SAP Note Implementation" button to start "de-implementation", and you will get "confirm changes" screen, for example:

Here please de-flag the check box for "copy changes":

 (Here there is only one object, but generally there would be several objects in this screen. You should de-flag the check box for all of them.)
Later on you will receive the same screen, asking you to confirm that the SAP note has been correctly de-implemented, you can just click "Yes" to continue.
After that, the implementation status for this SAP note will change to "can be implemented", then you can implement it again.
As to how to re-implement Already-implemented SAP Notes, you can refer to http://wiki.scn.sap.com/wiki/x/AIVsGQ for an example.

 

12. During implementation a SAP Note, yellow traffic light occurred for some objects with message "Corrections incompletely copied". Does the yellow traffic light just mean a warning which can be ignored?
You may find yellow traffic light displayed for some objects as below:
Perhaps you think that yellow means Warning, so you just go ahead. It is WRONG. The yellow traffic light here means error/problem, should NOT be ignored. If you click the yellow traffic ligth, you will be leaded into the Split-Screen Editor, in which you will find error like "context block (not found)" or "delete block (not found)" as below:

As you can see that SNOTE cannot find delete block. As the result, SNOTE will do nothing change. 
And if you continue without any adjustment, you will receive a message like

If you click "Yes" and go ahead, the implementation status will change to "completely implemented". But some corrections were not implemented actually, and you will find message "Correction instructions xxxxxxxx xxxxxxx incompletely implemented" in the implementation log. That will lead to syntax errors/problems after implementation.

 

13. Inactive Objects are found in phase CHECK_INACT_OBJECTS during SPs implementation using SPAM/SAINT. Where did these inactive object come from? How to handle them?
These inactive objects are generally caused by modification. You must have modified these objects before, but failed to activate them in the end. As the result, these objects were left in the system with the modified (inactive) version. Goto Utility -> Versions -> Version Management in workbench tools (such as SE38, SE37, SE24 etc), you will find the Modif. version existing with the active version together. 
As the first step. we should find out where these inactive objects come from. I would suggest you to use Modification Browser (transaction: SE95). Modification Browser contains all modifications that have been performed before. In the modification Browser, you should expand subtree, and then search the inactive object, to see the modification history. Here, I would emphasize: in most cases as we found that, these inactive objects were caused by incomplete note implementation. That is, these objects haven been changed by implementing some individual SAP Notes before, but those SAP Notes were not implemented or de-implemented completely, so that these inactive objects were left in the system. So please expand the subtrees in Note Corrections part, search the inactive object, to see which SAP Note(s) were involved. Then you can check the SAP Note(s) in SNOTE. Sometime it is difficult to confirm whether the SAP Note(s) were implemented completely or not as to implementation log or implementation status, in this case you have to implement the SAP Note(s) again as per 11. But because SNOTE is locked by SPAM/SAINT, you may have to reset the import queue in SPAM/SAINT firstly, then you can using SNOTE to implement the SAP Note(s).


14. Is it possible to implement SAP Notes using SNOTE during upgrade?

During SUM execution the implementation of SAP Notes with transaction SNOTE is disabled so as not to corrupt the system state.

To make the implementation of changes to SAP objects easier, SNOTE has been enabled during the following update phases:

  • XPRAS_AIMMRG

  • XPRAS_UPG

  • XPRAS_AIMMRG_CUST

  • XPRAS_UPG_CUST 

Further details can be found in the SAP KBA  1993236 - Implementing SAP note corrections during Upgrade Downtime.

As from SUM SP15, it is possible to implement SAP Notes using SNOTE in shadow instance for a short time frame if you run either SUM with the Zero Downtime Option or run SUM with release SAP_BASIS >=7.50. Futher details can be found in SAP Note 2207944 - How to implement a SAP Note during System update using SUM (ABAP only).

Back to top

  • No labels

7 Comments

  1. Like! Very helpful.

  2. Hello Mike,

    I am glad you find the information helpful.  To continue improve and create valuable content for our customers, we would like to hear your feedback. Please take a few moments to complete a short survey.

    Your feedback is very valuable to us.  

    Thank you in advance for your time.

    Kind regards,

    James Wong

    SAP 

    1. Hello James,

      I have finished the survey.

      Mike Han

  3. Hi Julia/James Wong,

    I have a question..

    Lets say, we have manual pre-steps, and also post steps for a NOTE implementation...

    Can we save all the changes into same Transport, or separated them into 3 different transport no:-

    1. One for manual pre-steps
    2. One for SAP Note implementation
    3. One for post-steps

    We use to save all the changes into the same transport, but just wondering the correct way to move the changes to other systems, to avoid issues later.

     

    Thanks

    Regards

    Shahul

    1. Hello Shahul,

      It is necessary to save all the changes (including pre/post manual steps and implemented correction instruction using SNOTE) in one transport request.

      Image that, you saved the changes separately into several requests A(changes of pre-manual steps) B(changes of correction instructions) and C(changes of post-manual steps). After releasing these requests in DEV system, you should import them to next systems in the correct order: first A, then B, at last C. Otherwise, you might get errors during import.

      BTW, from note assistant management point of views, all changes in one SAP Notes must be saved in ONLY ONE request.

      Well, it is OK for you to save changes of several SAP Notes in one request. But for the changes within one SAP Note, they should be saved in one request only. Changes of one SAP Note in separated requests is not permitted, and will lead to inconsistent implementation status for the SAP Note in SNOTE.

      Best Regards,

      Julia

  4. Very useful document, thanks for publishing and helping us.

  5. Hi Julia/James,


    I have a scenario where I have implemented multiple notes and recorded them in same TR, and later I would like to know the list of prerequisite notes were applied for a specific note as it caused some inconsistency due to manual steps missing.  Please help me, where can I get those list of prerequisite notes applied along with some xyz note.

    In SE01, we can get all the list of notes of the TR, but here we have difficulty with finding the prerequisite notes for specific primary note.

     

    Thanks,

    Suresh