Service Consumption Models (SRVC)
A Service Consumption Model is an ABAP development object used to consume external services — such as OData, SOAP, or RFC-based services — from within the SAP BTP, ABAP Environment. Developers use it to generate the necessary proxy classes and artifacts that allow ABAP code to call remote services in a structured, type-safe way. It supports scenarios such as consuming SOAP-based web services or generating RFC proxy classes for remote function call integration.
Tutorials that teach this
Docs explaining this concept
Prerequisites
- Concept SAP BTP ABAP Environment (Steampunk) The concept name provided is "undefined," and the supplied sources do not contain a definition or description of a concept by that name. Based on the available source snippets — which cover topics such as the [XCO Library](https://help.sap.com/docs/btp/sap-business-technology-platform/c154dffe892b4d9ea4566722f0bcd5f1?locale=en-US&state=PRODUCTION&version=Cloud), ATC configurations, abapGit, and the Cloud Connector — no grounded definition can be written for an "undefined" concept. Please provide a valid SAP developer concept name so an accurate, source-grounded definition can be produced.
- Concept ABAP Development Tools (ADT) in Eclipse The concept name is not defined in the provided sources, and no specific concept is identified for definition. Based on the available source snippets, a general definition cannot be accurately constructed without risking unsupported claims. Please provide a valid concept name and relevant source material to generate an accurate definition.
- Concept ABAP Package and Transport Request Management The concept name was not provided, and the available source snippets do not converge on a single, clearly identifiable concept — they cover a range of topics including [transferring ABAP source code via abapGit](https://help.sap.com/docs/btp/sap-business-technology-platform/3d734bec294441f498880e93ed3222dd?locale=en-US&state=PRODUCTION&version=Cloud), the Application Log Design Time API, Table Functions and AMDP, and others. Without a defined concept to document, a grounded and accurate definition cannot be written. Please provide the concept name so a precise, source-supported definition can be produced.
- Concept RFC Remote Connection Protocol The concept name provided is "undefined," and the available sources do not contain sufficient detail to ground a precise, factual definition of a specific SAP developer concept. A meaningful definition cannot be written without a valid concept name and supporting source content.
- Concept ABAP CDS Object Types ABAP CDS (Core Data Services) object types are a set of released ABAP repository object types that developers use to define and work with data models, views, and related artifacts in the ABAP environment. They form part of the broader catalog of [supported ABAP object types](https://help.sap.com/docs/btp/sap-business-technology-platform/aa9742dfb60e49deb033c2b8966e7461?locale=en-US&state=PRODUCTION&version=Cloud) available on SAP Business Technology Platform. Developers use these object types to create structured data definitions — such as CDS views and CDS view entities — that can be consumed in ABAP SQL queries and application services.
- Concept ABAP Connectivity Basics The concept name is not defined in the provided sources, and the source snippets do not contain sufficient shared context to identify a single, clearly named concept. The sources cover a range of loosely related SAP BTP ABAP environment integration topics — such as outbound communication monitoring, the SAP Destination Service, ABAP Test Cockpit integration, and client certificate authentication — but do not converge on one definable concept. A meaningful, source-grounded definition cannot be written for an undefined concept.
- Concept RFC-based ABAP Function Module Invocation The concept name is missing or undefined, so a targeted definition cannot be written. Based on the available source, the closest identifiable concept is **SAP Java Connector (SAP JCo)** — a component available through SAP Java Buildpack that developers use to enable Java applications to connect and communicate with SAP systems. You can learn more from the [SAP Java Connector documentation](https://help.sap.com/docs/btp/sap-business-technology-platform/3cee866c27ec4492b789b10c5d52d94b?locale=en-US&state=PRODUCTION&version=Cloud).