glossary-6e251fa.md

Glossary

Add-on Assembly Kit as a Service (AAKaaS)	The Add-on Assembly Kit as a Service registers and publishes the software product. It is accessible via APIs with a technical communication user.
ABAP environment pipeline	The ABAP environment pipeline enables continuous integration for the ABAP environment. The pipeline contains several stages and supports different scenarios. See ABAP Environment Pipeline.
ABAP System	The ABAP environment service (abap/standard) is used to create development and test systems. See Creating an ABAP System.
ABAP System (SaaS, OEM)	The ABAP environment (abap/saas_oem) service is used to create the add-on installation test system and production systems, where a specific add-on product needs to be installed in the system.
Add-on build pipeline	A pipeline configured for the add-on build scenario of the ABAP environment pipeline. See Build and Publish Add-on Products on SAP BTP ABAP Environment.
Add-on descriptor	The build process is controlled by an add-on descriptor file called addon.yml. This file must be created manually and stored in the Git repository of the pipeline. It must contain information about the software product version to be delivered and the containing software component versions. See Add-On Descriptor File.
Add-on installation test system	To verify that the delivery packages included in the add-on product version being built are installable, a target vector is published in "test" scope. In the integration tests stage, an ABAP system of service plan saas_oem is created. This ABAP OEM service allows you to install a specific add-on product version into an ABAP system that is provisioned.
Add-on product version (software product version)	To install and maintain ABAP software, software product versions are used. A software product version is a bundle of software component versions made available at the same time for implementing a well-defined scope of functionality. See Software Product Version.
ABAP Solution (Provider)	The ABAP Solution service maintains ABAP systems and tenants to provide an add-on product as a SaaS solution.
Assembly System	The ABAP system responsible for the add-on build. It is created during the pipeline and eventually deleted. All actions related to the ABAP source code are executed on this system, e.g. running checks with the ABAP Test Cockpit or the build of the software components.
ABAP Test Cockpit	ABAP Test Cockpit checks can be executed using abapEnvironmentRunATCCheck. The step can receive software components or packages configured in a YML file. The results are returned in checkstyle format. With the use of a pipeline extension, you can configure quality gates. See ATC and ABAP Test Cockpit Configurator.
Branch	Git repository branches can be used to control the flow of changes through the test and production landscape. They separate changes from each other, which shall or might not be delivered together (i.e. development vs. correction, feature A vs. feature B). A branch is created on the current state of another branch, the parent branch, and reflected by a new copy of all included objects. Depending on which branch is supposed to be changed, the corresponding copy is worked on.
Business role	A business role provides users with authorizations to access apps.
CI/CD server	The pipeline for building ABAP add-ons has been created specifically for Jenkins. Therefore, a Jenkins server is required. The project "Piper" provides a Jenkins image, which already includes the necessary configurations. Note that you can also configure an existing server.
Cloud Foundry environment	The Cloud Foundry environment enables you to develop new business applications and business services, supporting multiple runtimes, programming languages, libraries, and services. See Cloud Foundry Environment.
Communication arrangement	A communication arrangement describes a communication scenario with a remote system during configuration time. It provides the necessary metadata for service configuration. See Communication Arrangement.
Communication scenario	A communication scenario in the ABAP environment is a design time description of how two communication partners communicate with each other. It provides technical information, such as the used inbound and outbound services and their service type, for example OData or SOAP, and the number of allowed communication arrangement instances. See Communication Scenario.
Consumer	The service consumer is an end-customer of the service provider and has access to the SaaS application in a specific tenant
Correction codeline	Corrections need to run in parallel to development and on a released state. This is performed in the correction codeline and on a maintenance branch.
Cx server	Cx server is a life-cycle management tool to bootstrap a preconfigured Jenkins instance within minutes on your own (virtual) server, that uses Docker images. To avoid manual startup of the Docker image with all the required parameters and sidecar images, this command line tool automates the bootstrapping. See Cx Server.
Destination service	The Destination service lets you find the destination information that is required to access a remote service or system from your Cloud Foundry application. See Consuming the Destination Service.
Development codeline	Infinity development (infinity codeline) is done based on the latest software component state in the main branch.
Development namespace	Naming conflicts can be avoided through agreements on naming conventions or by carrying out development in separate namespaces. See SAP note 84282 and Maintain Namespaces.
Global account	A global account is the realization of a contract you made with SAP. A global account is used to manage subaccounts, members, entitlements, and quotas. You receive entitlements and quotas to use platform resources per global account and then distribute the entitlements and quotas to the subaccount for actual consumption. See Getting a Global Account.
Identity Provider	SAP Business Technology Platform supports identity federation, a concept of linking and reusing digital identities of a user base across loosely coupled systems. Identity federation frees applications on SAP Business Technology Platform from the need to obtain and store the credentials of users to authenticate them. Instead, the application user base is reused from identity providers, which support the administration of digital user identities, authentication, and authorizations in a centralized and decoupled manner. See Trust and Federation with Identity Providers.
Landscape Portal	The Landscape Portal app acts as a central tool to allow service providers to perform lifecycle management operations such as add-on updates, provisioning new consumers as new tenants, and more. SeeLandscape Portal .
Multitenancy	A multitenant service/application serves requests from different customers - the tenants - and processes their data strictly isolated from one another.
Patch level	Patch deliveries shall only contain small corrections. They are shipped with delivery packages of type Correction Package. For both the add-on product version and the software component version, the patch level is denoted in the third digit.
Project "Piper"	SAP implements tooling for continuous delivery in project "Piper". The goal of project "Piper" is to substantially ease setting up continuous delivery in your project using SAP technologies. See Project Piper.
Provider	The provider is responsible for the development and maintenance of the SaaS application. This is typically an independent software vendor or development partner.
Release	Release deliveries contain the whole software component and deliver new features and enhancements of existing functionalities. For both the add-on product version and the software component version, the release is denoted in the first digit.
SAP Business Application Studio	Available as a cloud service, SAP Business Application Studio provides a desktop-like experience similar to leading IDEs, with command line and optimized editors. At the heart of SAP Business Application Studio are the dev spaces, which are similar to isolated virtual machines in the cloud containing tailored tools and pre-installed runtimes per business scenario, such as SAP Fiori, SAP S/4HANA extensions, Workflow, Mobile and more. This simplifies and saves time in setting up your development environment and allows you to efficiently develop, test, build, and run your solution locally or in the cloud. See What is SAP Business Application Studio.
SAP Cloud Identity Services - Identity Authentication	The Identity Authentication service provides you with controlled cloud-based access to business processes, applications, and data. It simplifies your user experience through authentication mechanisms, single sign-on, on-premise integration, and convenient self-service options. See What Is Identity Authentication?.
SAP Cloud Identity Services - Identity Provisioning	The Identity Provisioning service automates identity lifecycle processes. It helps you provision identities and their authorizations to various cloud and on-premise business applications. See What is Identity Provisioning.
SAP ID service	The default platform identity provider and application identity provider of SAP Business Technology Platform is SAP ID service. See Default Identity Provider.
SAP ONE Support launchpad	SAP ONE Support Launchpad provides you access to task-driven support resources in an intuitive interface. By using customizable role profiles, it displays only the relevant applications and insights to you. See SAP ONE Support Launchpad.
SAP PartnerEdge	Get information, training, tools, and resources regarding partner licensing at SAP Partner Portal.
SAP Store	SAP Store is the enterprise marketplace where we bring together customers and partners on a single, easy-to-use, global online platform. Here, customers can discover, try, and buy SAP-validated partner applications that are built on or extend their existing SAP technology and solutions. For partners, it's the only place they can market and deliver their apps, add-ons, and integration kits to SAP's global customers — solutions that help customers grow their business. See SAP Store.
Software component	In ABAP environment systems, you develop within software components (also called repositories). The add-ons being built in this scenario are made up by one or multiple software components combined to an add-on product. See Software Components.
Software component version	A software component version is a technically distinguishable unit of software and is installed and patched as a whole. See Software Component Version.
Subaccount	Subaccounts allow you to structure a global account according to your organization’s and project’s requirements with regard to members, authorizations, and entitlements. See Subaccounts.
Support Package (Stack) Level	Support package deliveries contain a larger collection of corrections and may contain smaller functional enhancements. For both the add-on product version and the software component version, the support package level is denoted in the second digit.
Web Access for ABAP	Subscribe to the Web access for ABAP to get direct browser access to your instances in the ABAP environment, including access to the administration launchpad for ABAP. See Subscribing to the Web Access for ABAP.