OData CRUD Operations (Create and Update)
The concept name is not defined in the provided sources, which cover SAP Git repository management API operations — such as creating branches, clones, pulls, tags, and execution logs — all exposed via the MANAGE_GIT_REPOSITORY OData service. Developers use these endpoints to programmatically manage Git-based source code repositories on SAP Business Technology Platform. Without a defined concept name, no further specific definition can be provided based solely on the available sources.
Tutorials that teach this
- Tutorial SAP HANA XS Advanced, Creating an OData Service with Create Operation and XSJS Exit
- Tutorial Create an App Using the SAP BTP SDK Assistant for iOS
- Tutorial Perform S/4HANA CRUD Operations in SAP Build Apps
- Tutorial Create and Deep Insert with the Virtual Data Model for OData
- Tutorial 10 - Create Action Project to Post Data to CAP Service
- Tutorial Add a Custom Event Handler
- Tutorial Generate the UI for a Custom Business Object and grant Access
- Tutorial 5 - Create Skill to Create / Update Shipment
- Tutorial 3 - Configure the Shopping Cart Page
- Tutorial Create Action Projects
- Tutorial Consume a CAP Service in SAP Build Apps
- Tutorial Consume an OData Service with Create Option
Docs explaining this concept
Prerequisites
- Concept No-code app development with SAP Build Apps The concept provided is `undefined` and the supplied sources contain only tutorial titles with no substantive content to ground a definition. A valid concept name and at least one source snippet with descriptive content are required to produce an accurate, source-grounded definition.
- Concept UI5 MVC View/Controller Pattern The concept name is not defined in the provided sources, so a grounded definition cannot be written. Based on the available source snippets, the closest identifiable topic is **`sap.f.routing.Router`** — a routing utility in SAPUI5 that developers use to manage navigation between pages and layouts within an application. It is utilized, for example, to handle transitions such as navigating from a start page to other pages or adding detail and detail-detail pages, as described in the [SAPUI5 routing tutorials](https://ui5.sap.com/#/topic/7f651316d396400d88835adb0d021532).
- Concept OData Query Parameters The concept name was not provided, but based on the available source, **Read Branches** is an OData-based operation in SAP's Git repository management API that allows a developer to retrieve one or multiple branches from a managed Git repository. A developer uses it by sending a request to the URI `/sap/opu/odata/sap/MANAGE_GIT_REPOSITORY/Branch` as part of working with [SAP Business Technology Platform](https://help.sap.com/docs/btp/sap-business-technology-platform/e8e40c2d3fd1431a86c7bf324d70ba7d?locale=en-US&state=PRODUCTION&version=Cloud) Git repository management services.
- Concept OData Service Exposure via CAP The concept name provided is "undefined," which does not correspond to a recognizable SAP developer concept that can be grounded in the supplied source snippets. No definition can be responsibly written without a valid concept name and supporting source material.
- Concept ABAP RESTful Application Programming Model (RAP) The concept name was not provided (marked as "undefined"), and the supplied source snippets cover several broad SAP BTP and ABAP topics — such as the ABAP Environment, RAP development, authorization basics, and system workload analysis — without converging on a single, specific concept to define. There is insufficient information to produce an accurate, source-grounded definition.
- Concept Consuming OData APIs from SAP S/4HANA The concept provided is **undefined** — no specific SAP developer concept was supplied for definition. Please provide a valid concept name (for example, "ABAP SQL", "SAP Build Actions", or "Business Partner API") so that a precise, source-grounded definition can be written.
- Concept SAPUI5 Smart Controls (SmartFilterBar, SmartList) Smart Controls are UI5 controls that use OData metadata to dynamically configure themselves, reducing the amount of manual UI coding a developer must write. A developer uses them to automatically generate UI elements — such as table columns or form fields — based on the metadata exposed by an OData service, as demonstrated in the [Smart Controls Tutorial](https://ui5.sap.com/#/topic/64bde9a8879d4f418e2849f7285dd757). They also support create operations against OData services, enabling developers to build data-entry scenarios with minimal boilerplate configuration.
- Concept CAP Node.js Development The provided sources do not contain enough grounded detail to write a precise, factually supported definition for an unnamed or undefined concept. Based on the available source snippets, these materials collectively relate to the [SAP Cloud Application Programming Model (CAP)](https://help.sap.com/docs/btp/sap-business-technology-platform/bc8d5c0598774f87a54cb63cb6abecc6?locale=en-US&state=PRODUCTION&version=Cloud) and development on SAP Business Technology Platform, covering topics such as building business applications with Node.js, consuming web services, and integrating with SAP HANA Cloud. Developers use these resources to build, extend, and expose services within the SAP BTP ecosystem.
- Concept OData Virtual Data Model Custom Field Extensibility The concept name is not defined in the provided sources, and no factual claims about a specific concept can be grounded in the available snippets. The sources reference the [SAP Cloud SDK's Virtual Data Model for OData](https://developers.sap.com/tutorials/cloudsdk-js-vdm-getall.html) and its use within the [SAP Cloud Application Programming Model](https://developers.sap.com/tutorials/cloudsdk-cap-js.html), but without a named concept to define, no accurate definition can be produced. Please provide a valid concept name so a precise, source-grounded definition can be written.
- Concept UI5 App Descriptor (manifest.json) The concept name was not provided (marked as "undefined"), and the supplied source snippets cover several distinct SAPUI5 topics — CORS, `resources.json`, the Component Controller, manifest model preload, and others — without a single shared concept that can be reliably identified and defined. A meaningful, source-grounded definition cannot be written without knowing which concept to define.
- Concept SAP HANA Extended Application Services (XS) The [Neo environment](https://help.sap.com/docs/btp/sap-business-technology-platform/0f79436cf43a4785bb5b7ee9dac0c76a?locale=en-US&state=PRODUCTION&version=Cloud) is a platform environment on SAP Business Technology Platform that lets developers build and run HTML5, Java, and SAP HANA extended application services. Developers use it to create and deploy cloud applications within the SAP BTP ecosystem.
- Concept OData Service Development in ABAP The concept name was not provided, so a precise definition cannot be generated. Based on the available sources — which cover publishing OData services for remote consumption, exposing custom business objects as external web services, and enriching Shell Plug-ins with OData services — the subject appears to relate to **OData service exposure** in SAP development. An OData service allows developers to make business data and logic available as a standardized web API that can be consumed remotely by external applications or UI components.
- Concept CAP service development The concept provided is **undefined** and no valid concept name was supplied. Without a specific SAP developer concept to define, and with the available sources covering topics such as CAP services, SAP Build Actions, SAP Business Application Studio, and SAP SuccessFactors extensions, it is not possible to generate an accurate, source-grounded definition. Please provide a valid concept name so a precise definition can be written.
- Concept SAP Integration Suite Adapter Configuration
- Concept UI5 Model Data Binding The concept name provided is "undefined," which does not correspond to a defined SAP developer concept. Based on the available sources, no coherent or supported definition can be constructed for a concept literally named "undefined." Please provide a valid concept name so that an accurate, source-grounded definition can be written.
- Concept Java application development
- Concept OData service consumption The provided sources do not contain sufficient information to write a grounded definition for an undefined concept. Please provide a valid concept name and relevant source snippets to generate an accurate definition.
- Concept SAPUI5 Application Development The concept name was not provided, so a precise definition cannot be produced from the available sources. The sources cover general SAPUI5 development topics — such as [developing SAPUI5 apps](https://ui5.sap.com/#/topic/3da5f4be63264db99f2e5b04c5e853db), tutorials, and UI development on SAP BTP — but do not supply enough detail to define an unnamed concept accurately. Please supply the concept name so a grounded definition can be written.
- Concept manifest.json Data Sources Configuration The concept name was not provided (marked as "undefined"), and the available source snippets do not collectively describe a single, clearly identifiable SAP developer concept. The sources reference topics such as the [Smart Filter Bar](https://ui5.sap.com/#/topic/b96dbb603b004b399a5b787794d2fe60) and [Additional Annotation Files](https://ui5.sap.com/#/topic/fd715d97ebf842739697c9a0f276f0c0) in SAPUI5, as well as several OData and UI5 integration tutorials, but without a defined concept to document, a grounded and accurate definition cannot be written.
- Concept SAP Mobile Services Account Setup and Configuration No concept was provided, and the supplied sources do not converge on a single, identifiable SAP developer concept that can be defined. A meaningful definition cannot be written without a specified concept to define.
- Concept MVC Controller Assignment The concept name provided is "undefined," which does not correspond to a defined SAP developer concept supported by the available source snippets. Based on the sources provided, a definition cannot be accurately or responsibly constructed for an unnamed or undefined concept.
- Concept SAP BTP SDK for iOS App Development
- Concept SAP Destination Service Configuration The concept name is not defined in the provided sources, so a grounded definition cannot be written. The sources cover related topics such as [inbound communication via principal propagation](https://help.sap.com/docs/btp/sap-business-technology-platform/387b3deb12474762b593d4b1f2b392ad?locale=en-US&state=PRODUCTION&version=Cloud), OAuth 2.0 SAML Bearer Assertion Grant, client certificate authentication, and [routing via destination](https://help.sap.com/docs/btp/sap-business-technology-platform/97d7a02cd6fd4f579fd96f41ee0d0c1d?locale=en-US&state=PRODUCTION&version=Cloud) in the ABAP environment on SAP BTP, but without a defined concept name, no accurate definition can be produced from these snippets alone.
- Concept CAP OData V4 Service Development The concept provided is **undefined**, and the supplied sources do not describe a specific, identifiable SAP developer concept that can be accurately defined. No definition can be responsibly written without a clearly stated concept name and supporting source content.
- Concept MVC Controller onInit Hook The provided sources do not contain sufficient information to write a grounded definition for an undefined concept. The snippets reference UI5 tile components, routing tutorials, and chatbot integration, but no specific concept has been identified to define.
- Concept SAP HANA XS Classic Application Development The concept to be defined is not specified — "undefined" was provided in place of a concept name. Based on the available sources, a definition cannot be accurately scoped or written without knowing the target concept. Please provide a valid concept name so a precise, source-grounded definition can be produced.
- Concept XML View The concept name is missing or undefined, so a precise definition cannot be provided. Based on the available sources, the closest identifiable concept is the **XML View** in SAPUI5 — a [view type](https://ui5.sap.com/#/topic/91f292806f4d1014b6dd926db0e91070) defined in an XML file with a name ending in `.view.xml`, used by developers to declaratively define and render the UI within the Model-View-Controller (MVC) pattern. Developers use XML Views to declare SAPUI5 controls using namespaces that map to control libraries, handle control aggregations, and bind data to UI elements.
- Concept SAP BTP SDK Flows Component Integration and Configuration The provided sources do not contain sufficient information to write a grounded definition for an undefined concept. No relevant source snippets describe a clearly identifiable SAP developer concept that can be accurately and specifically defined based solely on the provided materials.
- Concept SAPUI5 MVC Architecture The concept name provided is "undefined," which does not correspond to a defined SAP developer concept. Based on the available sources, a **Model** in SAPUI5 is a core component of the Model View Controller (MVC) pattern that holds data and provides methods to retrieve and modify it, while a [Controller](https://ui5.sap.com/#/topic/121b8e6337d147af9819129e428f1f75) contains methods that define how [models](https://ui5.sap.com/#/topic/e1b625940c104b558e52f47afe5ddb4f) and views interact. If you intended to define one of these concepts, please clarify the concept name so an accurate definition can be provided.
- Concept OData V2 Service Integration The concept name is missing or undefined, so a precise definition cannot be produced from the provided sources. Based on the available source snippets — which cover topics such as consuming OData services, SAP Cloud Integration, SAPUI5 user interfaces, and SAP Business Accelerator Hub APIs — the concept appears to relate to **OData service consumption** in SAP development contexts. Developers use OData services to read and write structured business data (such as sales orders or product listings) from SAP and third-party backends, as demonstrated in tutorials like [consuming an OData service with create option](https://developers.sap.com) and [using OData metadata to dynamically create UI columns](https://developers.sap.com). Please provide the specific concept name for a more accurate definition.
- Concept CSRF Token Authentication The concept name was not provided, but based on the sources, the subject is the **MANAGE\_GIT\_REPOSITORY** OData API for SAP BTP ABAP Environment. It is an OData service exposed at `/sap/opu/odata/sap/MANAGE_GIT_REPOSITORY` that developers use to manage Git repository operations — such as [cloning repositories](https://help.sap.com/docs/btp/sap-business-technology-platform/0552763b6c184281893e808391ea5380?locale=en-US&state=PRODUCTION&version=Cloud), creating and checking out branches, pulling changes, and creating tags — programmatically within an SAP BTP ABAP Environment system. Developers can also use it to read transport logs and deploy ATC configurations, enabling automated Git-based development workflows.
Concepts that build on this
- Concept CAP OData V4 Service Development
- Concept XSJS Exit for OData Service Operations
- Concept BTP Destination Configuration for API Testing
- Concept XSODATA Service File Definition
- Concept Barcode and QR Code Scanner Integration in iOS
- Concept Virtual Data Model and CDS Views
- Concept OData V4 Draft Mode Handling
- Concept CAP Declarative Constraints
- Concept SAP Fiori Collection View for Android
- Concept MDK Data Binding and Object Browser
- Concept CAP Event Handlers
- Concept MDK CRUD Operations
- Concept CSRF Token Handling in OData Requests
- Concept OData Deep Insert