Skip to main content
Glama
ClementRingot

SAP Released Objects Server

Search SAP Objects

sap_search_objects
Read-onlyIdempotent

Search SAP Cloudification Repository for released objects and APIs. Filter by Clean Core Level, object type, component, and state to find upgrade-safe alternatives for ABAP Cloud.

Instructions

Search for SAP objects (classes, interfaces, CDS views, tables, data elements, function groups, RAP artifacts, etc.) in the SAP Cloudification Repository. Filter by Clean Core Level (A/B/C/D), object type, application component, and state. Use this tool to find released APIs for ABAP Cloud development, check if a specific object is available for your target system, or discover alternatives when an object is not released.

SEARCH TIPS:

  • Use separate words for business concepts: 'purchase order' not 'PURCHASEORDER'

  • SAP abbreviations are automatically resolved: 'billing document' also finds BILLGDOC*, BILDOC* objects

  • Compound abbreviations work too: 'purchase order' finds PO* objects, 'bill of material' finds BOM*

  • Separate words trigger fuzzy matching on SAP abbreviations (e.g., 'physical inventory' finds both PHYSICALINVENTORY* and PHYSINVTRY* objects)

  • Use exact SAP names only when you know the precise object name (e.g., 'I_PRODUCT', 'MARA')

  • Combine with app_component filter for targeted results (e.g., query='inventory', app_component='MM-IM')

  • Prefer singular forms: 'handling unit' not 'handling units' (plural 's' can reduce match accuracy)

  • Keep queries to 2-3 words maximum; use filters instead of adding more words

System types:

  • public_cloud (S/4HANA Cloud Public Edition): Only Level A Released APIs

  • btp (BTP ABAP Environment / Steampunk): Only Level A Released APIs (separate, smaller dataset)

  • private_cloud / on_premise: Levels A-D available, version-specific

Clean Core Levels (cumulative filter):

  • A: Released APIs only (ABAP Cloud, upgrade-safe)

  • B: + Classic APIs (upgrade-stable)

  • C: + Internal/unclassified objects

  • D: + noAPI objects (not Clean Core)

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
limitNoMaximum number of results to return (1-100). Default: 25.
queryYesSearch string to match against object names (case-insensitive). Supports two search styles: 1) SAP technical names for exact/prefix matching: 'I_PRODUCT', 'CL_ABAP', 'MARA', 'BAPI_MATERIAL', '/SCWM/PACKING' 2) Natural language with SEPARATE WORDS for fuzzy matching across SAP abbreviations: 'purchase order', 'handling unit', 'physical inventory', 'delivery document' IMPORTANT: Prefer natural language with separate words when searching by business concept. SAP often abbreviates compound names (PHYSICALINVENTORY → PHYSINVTRY, PURCHASEORDER → PURCHORD). Separate words like 'physical inventory' will find BOTH I_PHYSICALINVENTORY* AND I_PHYSINVTRY* objects, while the concatenated form 'PHYSICALINVENTORY' only finds the first group. Keep queries to 2-3 words maximum and use app_component filter to narrow by functional area.
stateNoFilter by specific object state. 'released' = Level A, publicly released APIs. 'deprecated' = Was released, now deprecated (usually has a successor). 'classicAPI' = Level B, classic but upgrade-stable. 'notToBeReleased' = Level C, internal object. 'noAPI' = Level D, not recommended. 'stable' = Level C, stable but without release contract. Leave empty to include all states within the selected Clean Core Level.
offsetNoNumber of results to skip for pagination. Default: 0.
versionNoS/4HANA version for Private Cloud or On-Premise systems. Use 'latest' for the most recent version. Format: YEAR for base release, or YEAR_FPS where FPS is the Feature Pack Stack / SP number. IMPORTANT: '2022_1' = FPS01/SP01, '2023_3' = FPS03/SP03, etc. Always use the YEAR_N format when a specific SP/FPS is requested. Use sap_list_versions to see all currently available versions. Ignored for public_cloud and btp systems. Default: latest.latest
object_typeNoFilter by TADIR object type (e.g., 'CLAS', 'DDLS', 'TABL'). Use the sap_list_object_types tool to discover all available types and their counts. Leave empty to search all types.
system_typeNoSAP system type. 'public_cloud' = S/4HANA Cloud Public Edition (Level A Released APIs only). 'btp' = BTP ABAP Environment / Steampunk (Level A Released APIs only, separate dataset from public_cloud). 'private_cloud' = S/4HANA Cloud Private Edition (Levels A-D, version-specific files available). 'on_premise' = S/4HANA on-premise (Levels A-D, version-specific files available). Default: public_cloud.public_cloud
app_componentNoFilter by SAP application component prefix (case-insensitive, partial match). Examples: 'MM-PUR' (Purchasing), 'FI-GL' (General Ledger), 'SD-SLS' (Sales), 'BC-SRV' (Basis Services), 'EWM' (Extended Warehouse Management). Leave empty to search all components.
clean_core_levelNoMaximum Clean Core Level to include in results (cumulative). Replaces the 3-tier extensibility model since August 2025. Level A: Released APIs only (ABAP Cloud, fully upgrade-safe). Level B: + Classic APIs (upgrade-stable, governance recommended). Level C: + Internal/unclassified objects (manageable risk, consult changelog). Level D: + noAPI objects (not Clean Core, should be remediated). For public_cloud and btp systems, only Level A is available. Default: A.A
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description confirms the read-only, idempotent nature (consistent with annotations), explains result pagination via limit/offset, and clarifies search behavior for different system types and clean core levels without contradicting any annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness3/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with sections and front-loaded purpose, but it is lengthy due to extensive tips and explanations; some redundancy could be trimmed without losing value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

With no output schema, the description covers all necessary aspects: search behavior, pagination, filtering by multiple criteria, system type differences, and clean core levels; it is fully adequate for an agent to use correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

All 9 parameters have schema descriptions (100% coverage). The description adds significant extra context with search tips, system type meanings, and clean core level definitions, enhancing understanding beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description explicitly states it searches for SAP objects in the SAP Cloudification Repository, lists object types, and clearly distinguishes this search tool from sibling tools like sap_get_object_details which focus on details of specific objects.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides extensive search tips and behavior (natural language vs exact names, query length, singular forms) and explains system types and clean core levels. However, it does not explicitly state when to use alternatives like sap_get_object_details for post-search details.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ClementRingot/ROSA'

If you have feedback or need assistance with the MCP directory API, please join our Discord server