In SAP API Management, the "Resources" tab of an API proxy lists endpoints (e.g., /get, /post). Let’s diagnose why it’s empty:
Step 1: Resources Tab- Displays operations/paths from the API spec or backend discovery.
Step 2: Evaluate Options-
A. Plain REST API: A REST API (e.g., via URL or OpenAPI) typically provides paths (e.g., /users), populating the tab.
B. OData API: OData services (e.g., /sap/opu/odata/sap/SERVICE) use entity sets (e.g., ProductSet), not REST-style resources. SAP API Management doesn’t auto-parse these as individual resources unless an OpenAPI spec is provided.
C. API Provider: A provider (e.g., SAP Gateway) can expose discoverable services; resources depend on the spec, not the provider alone.
D. SAP Graph API: SAP Graph provides RESTful endpoints, which should appear as resources.
Step 3: OData Behavior- When creating a proxy from an OData source (e.g., via provider or URL), without an OpenAPI overlay, the tab shows a single base path (e.g., /SERVICE), not entity-specific resources.
Step 4: Official Verification- The SAP Help Portal’s "Creating API Proxies" notes that OData sources often require manual resource definition or an imported spec, unlike REST APIs, which auto-populate.
Conclusion: Option B is 100% verified per SAP documentation.References:
SAP Help Portal: "Creating API Proxies" (SAP API Management)
SAP Help Portal: "OData API Proxy Configuration"
