技术问询：如何通过Web服务调用发现SAP中可用的Web服务？

Hey there, I totally get the headache here—dealing with multiple siloed SAP instances after a string of M&As is tough enough, and SAP’s infamous "do anything 10 different ways" approach doesn’t make consolidating security checklists any easier. Let’s walk through some universal methods you can use to discover available SAP web services via web service calls, no matter which instance you’re working with:

• Tap into SAP’s Standard WSDL Discovery Endpoints
  Most SAP systems expose built-in endpoints that let you pull up available services directly. A go-to one is sap/bc/soap/wsdl11. You can send a GET request like this:

  GET /sap/bc/soap/wsdl11?services=*&sap-client=<YOUR_CLIENT> HTTP/1.1
  Host: <SAP_SERVER_ADDRESS>
  

  Swap in your client number and server address, and use the wildcard * to list every service in that client. The response will be WSDL documents that spell out each service’s methods, parameters, and structure—perfect for your security inventory.

• Use the SOAP Runtime Metadata Web Service
  SAP has a dedicated web service for digging up RFC-based service details: sap/bc/soap/rfc. You can call the RFC_GET_FUNCTION_INTERFACE function module via SOAP here. Just pass in filters like function group or service name, and the response will give you full details on each service’s interface, activation status, and input/output fields. This is great for tracking down RFC-exposed web services.

• Query the SAP Service Registry (If You Have It)
  If your landscape uses an SAP Service Registry (part of NetWeaver), it has a web service interface you can hit to get a centralized list of registered services. The endpoint is usually sr/repository/query—send a SOAP request with filters (like service type or system) to fetch all services across connected instances. This is a huge time-saver if your registry is linked to all your M&A-acquired systems.

• Discover OData Services with the Catalog Service
  For OData-based web services, start with the catalog service endpoint: sap/opu/odata/IWFND/CATALOGSERVICE;v=2/ServiceCollection. A simple GET request here will return a list of every active OData service in the instance, including their URLs and descriptions. And if you need the full schema for a specific service, just append $metadata to its OData URL.

Quick Tips for Your Multi-Instance Setup #

• Since your instances are fully independent, you’ll need to run these checks on each system separately—unless you’ve got a central registry aggregating all services.
• Double-check that you have the right permissions: roles like SAP_BC_WEBSERVICE_ADMIN or similar are usually required to access these metadata endpoints. Keep this in mind for your security checklist!
• Older SAP versions might have slightly different endpoints (e.g., pre-NetWeaver 7.0 uses sap/bc/soap/wsdl instead of wsdl11), so test each method against your specific releases.

内容的提问来源于stack exchange，提问作者user610217