Trailsap

The processing status does not get set automatically but is something you set manually yourself as you process the note. This helps you keep track of each note implementation so you can easily see what state each one is at from the initial overview page.   New Once you have started the implementation process  In Processing Once you […]

Can be implemented This indicates that the note is valid for your SAP system release/support package level and contains instructions that can be implemented.   Cannot be implemented  Note isn’t valid for your system and does not contain any instructions that can be implemented.   Completely Implemented  The note has already been implemented in your SAP system. 

OSS note implementation has been made much easier since transaction SNOTE was made available and in most cases is as easy as clickig a few buttons. SNOTE performs many of the tasks automatically, and even shows you if the note is valid for your system without you having to check manually. Step 1 – Download

If you are not familiar with SAP notes please see here for more information about SAP OSS Notes and how they are downloaded and implemented using transaction code SNOTE.  Basically, an OSS note is a support fix supplied by SAP that can be downloaded to your SAP system and often automatically implemented using transaction code SNOTE. <brOnce a

SNOTE was a lifesaver when it came to note application and it doesn’t seem that long ago all SAP notes needed implementing manually including any code changes, table/fields creations etc.  The Note itself was pretty much the same as it is now, especially when viewed as a SAPScipt document. The note would still describe the

If you want to download an OSS note onto your SAP system it is a very simple process using transaction SNOTE. First, check if the note exists on your system i.e. see the following example using Note 379269 for how to do this.  Then to download the note you simply execute tcode SNOTE and click on the