A Service Consumption Model (SRVC) generates proxy artifacts to consume OData, RFC, or SOAP services.
To consume OData, SOAP, or RFC services, you must first create a Service Consumption Model (SRVC). See Creating Service Consumption Model for more information. An SRVC creates proxy artifacts and a code snippet that you can copy and paste to your code to perform the service call. For RFC, the SRVC is optional.
A remote client proxy request needs a corresponding SRVC.
The benefits of using an SRVC (instead of manually creating a corresponding model) are:
-
Simple creation using XML or EDMX file uploading. You don't need to manually define the model.
-
The code generator creates code snippets to use as blueprint on how to write client proxy-related coding.
Create a Service Consumption Model for remote consumption of your OData service. You have the metadata of the corresponding OData service that you want to consume in an XML or EDMX file.
See the following information for how to create your SRVC:
- Generating Proxies for Remote OData Service
- Generating Proxies for Remote Function Call (RFC)
- Generating Proxies for Remote Web Service
Not all OData service model features are supported for Service Consumption Models. For example, you might not be able to create a Service Consumption Model for your underlying OData service. This is the case if your Service Model contains Complex Collections, Actions, or Functions.