sap_note_get
Retrieve complete SAP Note details including full HTML content, step-by-step solutions, and metadata by providing a specific Note ID to access detailed problem descriptions and implementation guides.
Instructions
Fetch complete content and metadata for a specific SAP Note by ID. Returns full HTML content, solution details, and all metadata.
SAP Notes contain: • Detailed problem description • Step-by-step solution instructions • Root cause analysis • Affected releases/versions • Related notes and references • Corrections and patches • Implementation guides
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ USE WHEN: ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ • You have a Note ID from sap_note_search results • User asks for details about a specific note (e.g., "get details for note 2744792") • You need full solution steps, not just the summary • User wants to see the complete note content • You're following the search → get workflow pattern
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ DO NOT USE WHEN: ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ • You don't have a specific Note ID (use sap_note_search first) • User hasn't asked for detailed note content (summaries may suffice) • Note ID is invalid (contains spaces or special characters) • You're just browsing/searching (use sap_note_search instead)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ PARAMETER REQUIREMENTS: ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Note ID Format: • Typically alphanumeric characters only • No spaces, no prefixes • Valid examples: "2744792", "438342", "3089413", "123ABC" • Invalid examples: "Note 2744792", "SAP Note 2744792", ""
If user input includes text, extract the ID only: "Note 2744792" → "2744792" "SAP Note 438342" → "438342"
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ WORKFLOW PATTERN: ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Typical usage flow:
Search for relevant notes: sap_note_search(q="OData 415 error")
Review search results, identify relevant note IDs: Results: [{id: "2744792", ...}, {id: "438342", ...}]
Fetch full content for top 2-3 relevant notes: sap_note_get(id="2744792") sap_note_get(id="438342")
Synthesize solution from full note content
Do NOT fetch all notes - only get details for the most relevant 2-3.
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ERROR HANDLING: ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Common errors and solutions:
• "Note ID must contain only alphanumeric characters" → Validate ID format before calling → Extract alphanumeric ID only from user input
• "Note not found" → Note ID doesn't exist or is invalid → Try searching again with different terms
• "Access denied" → Some notes require special S-user permissions → Inform user to access directly on SAP Support Portal
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BEST PRACTICES: ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Always validate Note ID format (alphanumeric) before calling
Only fetch notes that are clearly relevant from search results
Limit to 2-3 note fetches per user query
Parse and summarize the HTML content field for users
Include the note URL in your response
Extract key sections: Symptom, Solution, Affected Releases
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | SAP Note ID: Typically 6-8 digits, but may include letters or vary in length. Valid examples: • "2744792" (7 digits) • "438342" (6 digits) • "12345678" (8 digits) • "123ABC" (mixed alphanumeric) Invalid examples: • "Note 2744792" (contains text prefix - extract ID only) • "" (empty) If user input includes text (e.g., "Note 2744792" or "SAP Note 2744792"), extract only the ID portion before calling this tool. | |
| lang | No | Language code for note content. • EN (English) - Default, recommended for most cases • DE (German) - Use if note exists in German and user requests it Note: Not all notes are available in both languages. | EN |