Now accepting guest editorial from SAP, Oracle, Workday and ServiceNow practitioners.Pitch a guide
The Sign-Off Table

Lesson 1 of 5

SAP Notes

10 min

Listen to this lesson

0:00 / 7:38

An SAP Note is SAP's unit of advice and correction. Many notes only explain something (a known limitation, a recommended setting, a workaround). Others carry correction instructions: precise changes to SAP repository objects that fix a defect. The Note Assistant, transaction SNOTE, downloads notes into your system and implements correction instructions automatically, tracking what was done so that later support packages and upgrades know about it.

Note textSymptom, cause, affected releases and support package levels, solution, manual steps
Correction instructionsSource code changes SNOTE can apply automatically, valid for specific release and SP ranges
Manual activitiesSteps SNOTE cannot do, such as dictionary or customizing changes, before or after implementation
Prerequisite notesOther notes that must be implemented first; SNOTE downloads and chains them
What a correction note contains.
The Sign-Off Table · thesignofftable.com/academy/sap-bas-203

Implementing a note: the safe sequence

  1. ReadCheck that the note matches your symptom, release and SP level; read manual steps and prerequisites
  2. DownloadIn CMD, download the note into SNOTE (notes are digitally signed; your system must be set up for signed downloads)
  3. ImplementSNOTE implements prerequisites and corrections; changes are recorded in a transport request
  4. Manual stepsPerform documented manual activities, recording them in the same or a linked transport
  5. TestDeveloper and functional tests in CMD; set the note's processing status to completed
  6. TransportRelease the request and import into CMQ and then CMP; never run SNOTE in CMQ or CMP
Implementing an SAP Note in development and moving it through the landscape.
The Sign-Off Table · thesignofftable.com/academy/sap-bas-203

SAP training is explicit on the last step: implement the note with SNOTE in the development system and transport it to quality assurance and production. Running SNOTE again in each system creates differences that no transport explains. For SNOTE to change SAP objects in development, the affected software components must be modifiable or restricted in SE06; changes made through SNOTE do not need a separate modification key.

A note's processing status in SNOTE in CMD: it is set to completed only after implementation, manual steps and tests, and the transport carries the result onward.
The Sign-Off Table · thesignofftable.com/academy/sap-bas-203

When a note is more than code

Classic correction instructions handle source code. For corrections that need dictionary objects, table content or other object types, SAP uses transport-based correction instructions (TCI): a note that delivers one transport request plus installation attributes, uploaded and implemented through SNOTE. TCIs can be de-implemented like other notes. If someone implemented a note by hand in the past, report SCWN_REGISTER_NOTES registers it, so that SNOTE knows it is there and later adjustments recognize it.

Note typeWhat happensWatch out for
Consulting or information noteNothing to implement; you act on the adviceSettings it recommends still need a change and a transport
Correction note (automatic)SNOTE applies correction instructionsPrerequisite chains and the SP range the note is valid for
Correction note with manual activitiesSNOTE plus documented manual stepsManual steps must also reach CMQ and CMP, usually by transport
TCI noteSNOTE imports a transport-based correctionLarger scope; test like a small support package
Note types and what each means for the landscape.
The Sign-Off Table · thesignofftable.com/academy/sap-bas-203

Setting up and finding notes

SNOTE needs a working download path. Current releases download notes over HTTP using RFC destinations created for the purpose, or through the ABAP Download Service; SAP training states that the old RFC destination SAPOSS is no longer supported, and that notes are digitally signed, which requires a one-time setup described in SAP Notes. To find the right note, search SAP for Me or the SAP Support Portal with the message number, runtime error or program name. For errors in application transactions, the Automated Note Search Tool (transaction ANST, also reachable from SNOTE) searches for corrections that match the objects used in a transaction you record.

ANST finds notes from what a transaction actually used: record the failing step, then let the tool match corrections to those objects.
The Sign-Off Table · thesignofftable.com/academy/sap-bas-203

What would you do?

A finance key user finds an SAP Note that fixes a wrong tax amount in CMQ. Under time pressure, someone proposes implementing it with SNOTE directly in CMQ and later in CMD. What should Sam insist on?

Key points
  • SNOTE downloads and implements SAP Notes, chains prerequisites and records changes in transports.
  • Read the note first: symptom, release and SP validity, manual steps.
  • Implement only in development; transport to QA and production.
  • TCI notes deliver transport-based corrections; register manual implementations with SCWN_REGISTER_NOTES.

Check your understanding · not graded

Lesson check

  1. 1. Which transaction is the Note Assistant?

  2. 2. Where should an SAP Note be implemented with SNOTE?

  3. 3. What does a transport-based correction instruction (TCI) deliver?

  4. 4. What does report SCWN_REGISTER_NOTES do?