Search SAP Notes
sap_note_searchSearch SAP Knowledge Base for troubleshooting articles, bug fixes, patches, and known issues to resolve SAP software errors and problems.
Instructions
Search SAP Knowledge Base (SAP Notes) for troubleshooting articles, bug fixes, patches, corrections, and known issues. Returns a ranked list of matching notes with metadata.
SAP Notes are official support articles that document: • Known bugs and their fixes • Patches and corrections for SAP software • Troubleshooting guides for specific errors • Performance optimization tips • Security vulnerabilities and patches • Missing or incorrect functionality
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ USE WHEN: ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ • User mentions "error", "issue", "bug", "problem", "not working" • User asks about "fixes", "patches", "corrections" • User reports unexpected behavior or incorrect functionality • User mentions specific error codes (e.g., "error 415", "dump ABAP_EXCEPTION") • User asks "why isn't this working?" or "how to fix?" • User references a specific Note ID (e.g., "Note 2744792")
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ DO NOT USE WHEN: ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ • User asks "how to configure" or "how to set up" → use sap_help_search instead • User wants implementation guides or best practices → use sap_help_search instead • User asks about product features or capabilities → use sap_help_search instead • User wants training materials or tutorials → use sap_community_search instead • User asks general "what is" questions → use sap_help_search instead
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ QUERY CONSTRUCTION: ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ Effective queries should:
Include specific error codes, messages, or transaction codes
Use SAP terminology (not generic terms)
Be concise (2-6 words typically)
Include product/module context if known
Query Formula: [Error Code/Transaction] + [Module/Component] + [Issue Type]
Examples: ✓ GOOD: • "error 415 CAP action" (specific error + context) • "MM02 material master dump" (transaction + module + issue) • "ABAP CX_SY_ZERODIVIDE" (specific exception class) • "S/4HANA migration performance" (product + issue) • "Note 2744792" (direct note ID lookup)
✗ BAD: • "how to configure SAP" (too vague, use sap_help_search) • "mm22" (transaction only, no issue context) • "I have a problem" (no specifics) • "SAP not working" (too generic)
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ WORKFLOW PATTERN: ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
Call sap_note_search(q="your query") to find relevant notes
Review results array for relevant note IDs
Call sap_note_get(id="note_id") for detailed content of top 2-3 notes
Synthesize answer from fetched note content
Example Chain: sap_note_search(q="OData gateway error") → Returns: [{id: "2744792", title: "OData Gateway 415 Error"}, ...] → Then call: sap_note_get(id="2744792") → Returns: Full note content with solution
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ IMPORTANT NOTES: ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ • SAP Notes require S-user credentials to access full content • Note IDs are typically alphanumeric (e.g., "2744792", "438342", "123ABC") • Results are ranked by relevance (best matches first) • Empty results suggest trying sap_help_search instead • Language parameter defaults to English (EN)
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| q | Yes | Search query: Specific error codes, transaction codes, component names, or issue descriptions. Use concise SAP terminology (2-6 words). Examples of effective queries: • "OData gateway error" - Specific error with context • "MM02 material master dump" - Transaction + module + issue • "ABAP CX_SY_ZERODIVIDE" - Specific exception class • "S/4HANA migration performance" - Product + issue • "Note 2744792" - Direct note ID lookup • "error 415 CAP" - Error code + technology • "Fiori launchpad not loading" - Specific symptom Query construction tips: • Include error codes, transaction codes, or component names • Use SAP terminology (not generic terms) • Be specific but concise (2-6 words typically) • Format: [Error Code/Transaction] + [Module/Component] + [Issue Type] Avoid vague queries like: "SAP problem", "not working", "help" | |
| lang | No | Language code for search results and note content. • EN (English) - Default and recommended, most comprehensive coverage • DE (German) - Available for German-language notes Use EN unless user specifically requests German content. | EN |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | The exact search query that was executed (for reference and debugging) | |
| results | Yes | Array of matching SAP Notes, ranked by relevance (best matches first). Typical workflow after getting results: 1. Review the first 2-5 results 2. Identify the most relevant note IDs based on title and summary 3. Use sap_note_get(id) to fetch full content for top 2-3 notes 4. Synthesize the solution from the detailed note content Do NOT fetch all notes - only retrieve details for the most relevant ones. | |
| totalResults | Yes | Total number of SAP Notes found matching the search query. • 0 results: Try different search terms or use sap_help_search instead • 1-5 results: High relevance, likely good matches • 6+ results: Multiple relevant notes found Results are ranked by relevance (best matches first). |