Background: Special attention needs to be drawn to the implemented pilot notes. The implemented pilot notes will not be automatically included into the new release after the upgrade. The pilot notes may be introduced into the standard code and no more necessary of the new release, or they may need to be adjusted in the new release, etc.
Analysis: The implemented pilot notes can be evaluated in the following way:
- Logon to CS* (CSN, CSR, CSS)
- Execute transaction /nSA38
- Execute program: /SPN/PILOTNOTES
- Enter the (R/3) customer number
- Evaluation and resulting activities:
(a) If no notes are reported (no lines appear), there is nothing to do.
(b) If notes are reported, check the value in the column “A”:
1) If a 'u' or a blank (SPACE) appears in column 'A' for any note, you must create an issue with Business Impact: “Problems due to incorrect system behaviour can reappear after the upgrade.” and Recommendation: “The following SAP Notes have to be implemented after the upgrade: xxxxxx. Create a customer message on the component of the SAP Note for the following SAP Notes: yyyyyy.
2) If a 'c' appears in column 'A' and the target upgrade release is outside the range of 'Rel.Begin' and 'Rel.End', this means the note has been checked and can be deleted after the upgrade.
--------------
Then to check if they are really applied, go to the customer system SNOTE transaction. In the Note browser, list all the notes, it will provide the implementation status of the notes if ever downloaded.