OSS
OSS
OSS stands for Online Service System and as the name implies, the service is
accessible thru internet. SAP notes are part of SAP service portal. In simple
terms, it is SAP’s Knowledge Base that specifically addresses known issues in SAP
system. It is continually updated as SAP customers report issues in SAP system and
SAP releases note with detailed instructions on how to fix / address the issue.
Most issues get fixed when SAP releases next version of the same component and
hence it is very necessary to see applicability of a note with respect to the
version where an issue is being addressed. Each note applies to a version and
mostly all its predecessor version.
Once all custom code errors and data errors are ruled out, consultant can take a
first level quick search in SAP OSS notes database by keying in the symptoms.
Many SAP Notes will be retrieved based on the symptoms sorted by relevance.
Consultant has to review notes to see if any of the notes are available for the
issue faced. Once found, check for the release versions that the note applies to
and ensure that the system where issues are observed are same or predecessors.
Later versions will have the issue fixed.
If no SAP note is obtained, customer can always log an issue with SAP which will be
addressed by SAP support but these are subject to SAP support contract etc. and
hence always advised to be done after consulting BASIS support team and ensuring
issues are logged with customer’s S-User for which support is available.
This is the SAP Note number that uniquely identifies the note in SAP OSS notes
database.
Processing Status
This applies when viewing note from SNOTE. For a note that can be implemented, this
gives info whether it is completely implemented or not.
Implementation Status
This is a critical info for any note. This tells if the note contains any code
corrections that needs to be implemented in SAP system or just contains info and /
or instructions to circumvent the issue when observed. The note that has status
‘Can Be Implemented’ is the one that has code corrections in it and applying that
will resolve the issue. How to apply the corrections is discussed in sections
below.
The note that has status ‘Cannot be Implemented’ implies that there are no code
level corrections that can fix the issue. Either SAP advises to avoid / take
certain practice / steps to ensure the identified error doesn’t occur or just
explains the system design and why the error occurs. Either ways, there are no code
level changes and hence no action required per the note. Notes of this category are
not discussed further in this document.
Short Text
Summary of the issue that is being addressed in the note is mentioned here.
Component
This specified SAP component that this note applies to. This is useful to rule out
note usage for certain issues – for example if the note is for specific area and
the observed issue is not in that area, this info helps to rule out any help from
the note. So a note to fix IS-Oil component will not be of use if the system is not
IS-Oil.
Long Text
This section details out the symptoms, often accompanied by an example scenario,
followed by the details of the error.
This tells why the error occurs and what the conditions that cause the error are.
When given an issue and analyze if the note works for it or not, this helps to see
if the conditions that cause the error are part of the issue making it a valid
scenario for note.