SAP Business Application Studio

© 2020 SAP SE or an SAP affiliate company. All rights reserved.
PUBLIC
2020-09-13
SAP Business Application Studio
THE BEST RUN

Content
1 What is SAP Business Application Studio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
2 What's New in SAP Business Application Studio. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
3 Developer Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3.1 Managing Your Dev Spaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
3.2 Development Scenarios. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
3.3 Additional Extensions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.4 IDE Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Git Integration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Search. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
Terminal. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44
Command Palette. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Outline View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
Problems View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
3.5 Productivity Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
Application Wizard. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Cloud Foundry Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47
CAP Project Explorer. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
Consuming SAP Services. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
Creating Run Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49
MTA Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60
Deploy Tool. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
3.6 Managing Ports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
3.7 Accessing On Premise Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
3.8 Building and Deploying Multitarget Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
3.9 Working with a Trial Account. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
3.10 Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
Git Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Connectivity Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66
Dev Space Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .67
Contact SAP Support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .68
5 Administrator Guide for AWS and Azure Regions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

5.1 Getting Started. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72
Connecting to External Systems. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
5.2 Subscribe to SAP Business Application Studio. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74
5.3 Manage Authorizations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

2 PUBLIC Content
5.4 Export and Download Personal Data from Specific Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
5.5 Restart a Dev Space. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
5.6 Delete Personal Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
7 Administrator Guide for China (Shanghai) Region. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

7.1 Getting Started in China (Shanghai) Region. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80
7.2 Subscribe to SAP Business Application Studio. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
7.3 Manage Authorizations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
7.4 Export and Download Personal Data from Specific Users. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
7.5 Restart a Dev Space. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
7.6 Delete Personal Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85
9 Security Guide. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
9.1 Architectural Overview. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
9.2 Standards and Best Practices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
9.3 Data Protection and Privacy. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88

Content PUBLIC 3
1 What is SAP Business Application Studio
SAP Business Application Studio is a new SAP Cloud Platform service in SAP Cloud Foundry which offers a
modern development environment tailored for efficient development of business applications for the SAP
Intelligent Enterprise.
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 like 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.
Scenarios
SAP Business Application Studio provides a tailored-made development environment for various development
scenarios. With each of these scenarios you can create different types of applications.
See Development Scenarios [page 26].
Capabilities
In SAP Business Application Studio, you are provided with one or more dev spaces. A dev space is a
development environment with all of the tools, capabilities, and resources needed for developing your
application. Each type of application requires a different development environment. Based on the type of
application that you choose to build, you're provided with a different set of tools. You can add additional tools to
supplement the application with additional extensions for the scenario.
The dev space is an isolated development environment providing a local-like development experience. Among
other tools, it provides terminal access to the file system so you can run various commands, you can test-run
your application in the dev space itself without deploying to the target runtime (Cloud Foundry), almost as if
the you were working on your own desktop.
Unlike other desktop IDEs, SAP Business Application Studio is equipped with various tools specially built for
developing business applications in the SAP ecosystem.
These tools covers the end-to-end development cycle:
● Clone an existing project with a Git client or create new project using templates.
● Use editors for SAP-specific technologies.
● Easily test your application on your dev space while consuming services from remote sources.
● Build and deploy the application as a multitarget application (MTA).

4 PUBLIC What is SAP Business Application Studio
Availability
The following browsers are supported for working in SAP Business Application Studio. Additional browsers will
be added over time.
 Note
Unless specifically stated, only the latest browser version is supported.
● Mozilla Firefox
● Google Chrome
You can find the regions where SAP Business Application Studio is available in the SAP Cloud Platform Regions
and Service Portfolio page.

What is SAP Business Application Studio PUBLIC 5
2 What's New in SAP Business Application
Studio
Core Components, 2019
Techni
cal Envi Availa
Com Capa ron ble as
ponent bility ment Title Description Type of
SAP Exten Cloud Run You can now run an SAP Fiori application locally with an SAP API New 2020-0
Busines sion Foun ning Business Hub service. See Run Your Application with the SAP API 9-13
s Suite - dry SAP Business Hub.
Applica Devel Fiori
tion opment Appli
Studio Effi- cations
ciency
SAP Exten Cloud CAP You can now use the CDS Graphical Modeler when developing CAP New 2020-0
Busines sion Foun applications. See Design CDS Models Using SAP Business Appli 8-30
s Suite - dry cation Studio
Applica Devel
tion opment
Studio Effi-
ciency
SAP Exten Cloud Run You can now run your SAP Fiori project's automated tests using New 2020-0
Busines sion Foun ning Karma. See Run Automated Tests of Your Application. 8-30
s Suite - dry SAP
Applica Devel Fiori
tion opment Appli
ciency
SAP Exten Cloud SAP You can now add an SAP Fiori module to an existing MTA project. New 2020-0
Busines sion Foun Fiori See Add an Additional SAP Fiori Application to Your Project. 8-30
s Suite - dry Devel
Applica Devel op
tion opment ment
Studio Effi-
ciency

6 PUBLIC What's New in SAP Business Application Studio
Techni
cal Envi Availa
Com Capa ron ble as
SAP Exten Cloud SAP You can now use quick fix for missing IDs in XML view files. See Chang 2020-0
Busines sion Foun Fiori Validation of Stable IDs. ed 8-30
s Suite - dry Devel
Applica Devel op
tion opment ment
Studio Effi-
ciency
SAP Exten Cloud SAP You can now develop an SAP Fiori application consuming a CAP New 2020-0
Busines sion Foun Fiori service, run it locally, build, and deploy it to Cloud Foundry. See 8-16
s Suite - dry Devel Developing an SAP Fiori Application for a CAP Project.
Applica Devel op
tion opment ment
Studio Effi-
ciency
SAP Exten Cloud SAP You can now develop an SAP Fiori application consuming a service New 2020-0
Busines sion Foun Fiori from an ABAP Cloud System, run it locally, build, and deploy it to 8-16
s Suite - dry Devel Cloud Foundry, using the approuter managed by SAP Cloud Plat
Applica Devel op form or a standalone approuter. See Develop an Application for
tion opment ment Cloud Foundry.
Studio Effi-
ciency
SAP Exten Cloud SAP You can now develop an SAP Fiori application and deploy it to an New 2020-0
Busines sion Foun Fiori ABAP Cloud System. See Developing an SAP Fiori Application 8-16
s Suite - dry Devel Based on an ABAP Cloud System Service.
Applica Devel op
tion opment ment
Studio Effi-
ciency
SAP Exten Cloud SAP You can now perform "abap deploy" in your local environment, New 2020-0
Busines sion Foun Fiori outside of SAP Business Application Studio. See abap-deploy npm 8-16
s Suite - dry De documentation and Deploy to the SAPUI5 ABAP Repository.
Applica Devel ploy
tion opment ment
Studio Effi-
ciency

What's New in SAP Business Application Studio PUBLIC 7
Techni
cal Envi Availa
Com Capa ron ble as
SAP Exten Cloud CAP Development of CAP applications is now available in the China New 2020-0
Busines sion Foun (Shanghai) region. 8-16
s Suite - dry
Applica Devel
tion opment
Studio Effi-
ciency
SAP Exten Cloud SAP You can now deploy your SAP Fiori application to the SAPUI5 New 2020-0
Busines sion Foun Fiori ABAP Repository in SAP S/4HANA Cloud. See Deploy to the SA 8-02
s Suite - dry Devel PUI5 ABAP Repository.
Applica Devel op
tion opment ment
Studio Effi-
ciency
SAP Exten Cloud CAP You can now use Spring-boot tools when developing Spring-boot New 2020-0
Busines sion Foun applications. See spring-projects . 8-02
s Suite - dry
Applica Devel
tion opment
Studio Effi-
ciency
SAP Exten Cloud CAP SAP Business Application Studio has been updated to include Chang 2020-0
Busines sion Foun SapMachine 11. See SapMachine . ed 8-02
s Suite - dry
Applica Devel
tion opment
Studio Effi-
ciency
SAP Exten Cloud SAP The XML UI5 code validation is now enhanced with stable ID Chang 2020-0
Busines sion Foun Fiori checks. See Validation of Stable IDs. ed 8-02
s Suite - dry Devel
Applica Devel op
tion opment ment
Studio Effi-
ciency

Techni
cal Envi Availa
Com Capa ron ble as
SAP Exten Cloud SAP SAP Fiori is now selected by default when choosing the type of dev Chang 2020-0
Busines sion Foun Fiori space to create in SAP Business Application Studio. ed 8-02
s Suite - dry Devel
Applica Devel op
tion opment ment
Studio Effi-
ciency
SAP Exten Cloud Trial When you subscribe to SAP Business Application Studio in the New 2020-0
Busines sion Foun land Trial Landscape, the relevant roles are automatically assigned to 7-19
s Suite - dry scape the account.
Applica Devel
tion opment
Studio Effi-
ciency
SAP Exten Cloud CAP You can now run your CAP Node.js application from the Run Con New 2020-0
Busines sion Foun figurations view and bind it to an instance of SAP HANA Cloud or 7-19
s Suite - dry an instance of hanatrial. See Creating Run Configurations for CAP
Applica Devel Node Applications.
tion opment
Studio Effi-
ciency
SAP Exten Cloud Theia SAP Business Application Studio has been updated to include Chang 2020-0
Busines sion Foun fixes and improvements that are part of Eclipse Theia 1.3.0. ed 7-19
s Suite - dry
Applica Devel
tion opment
Studio Effi-
ciency
SAP Exten Cloud SAP You can develop SAP Fiori applications for Cloud Foundry using New 2020-0
Busines sion Foun Fiori the approuter on the subaccount level and run an HTML5 applica 6-28
s Suite - dry Devel tion managed by SAP Cloud Platform. See Create an SAP Fiori
Applica Devel op Project and Deploy Your Application.
tion opment ment
Studio Effi-
ciency

Techni
cal Envi Availa
Com Capa ron ble as
SAP Exten Cloud CAP You can now run your CAP Node application from the Run Config- New 2020-0
Busines sion Foun urations view and bind it to a destination. See Creating Run Con 6-28
s Suite - dry figurations for CAP Node Applications.
Applica Devel
tion opment
Studio Effi-
ciency
Busines sion Foun urations view using mock OData services. See Creating Run Con 6-28
s Suite - dry figurations for CAP Node Applications.
Applica Devel
tion opment
Studio Effi-
ciency
Busines sion Foun urations view and deploy it out-of-the-box to an SAP HANA data 6-28
s Suite - dry base. See Creating Run Configurations for CAP Node Applications.
Applica Devel
tion opment
Studio Effi-
ciency
SAP Exten Cloud Theia It is now possible to open concurrent embedded graphical editors New 2020-0
Busines sion Foun in SAP Business Application Studio and even display them side by 6-28
s Suite - dry side.
Applica Devel
tion opment
Studio Effi-
ciency
s Suite - dry
Applica Devel
tion opment
Studio Effi-
ciency

Techni
cal Envi Availa
Com Capa ron ble as
SAP Exten Cloud SAP The XML UI5 code validation is now enhanced with type aggrega Chang 2020-0
Busines sion Foun Fiori tion and deprecation checks. See Develop Your Application. ed 6-28
s Suite - dry Devel
Applica Devel op
tion opment ment
Studio Effi-
ciency
SAP Exten Cloud SAP The XML UI5 code assist provides settings for deprecated and ex Chang 2020-0
Busines sion Foun Fiori perimental element proposals. See Develop Your Application. ed 6-28
s Suite - dry Devel
Applica Devel op
tion opment ment
Studio Effi-
ciency
SAP Exten Cloud SAP SAPUI5 Adaptation Project is now available in SAP Business Appli New 2020-0
Busines sion Foun Fiori cation Studio. You can create an app variant for an existing SAP 6-21
s Suite - dry Devel Fiori application and make use of the extension capabilities for UI5
Applica Devel op controls. See Extending an SAP Fiori Application.
tion opment ment
Studio Effi-
ciency
s Suite - dry
Applica Devel
tion opment
Studio Effi-
ciency
SAP Exten Cloud Dev You can now open a dev space in a separate browser tab. New 2020-0
Busines sion Foun Space 6-21
s Suite - dry Man
Applica Devel ager
tion opment
Studio Effi-
ciency

Techni
cal Envi Availa
Com Capa ron ble as
SAP Exten Cloud SAP The XML UI5 code validation is now enhanced with duplicate ID New 2020-0
Busines sion Foun Fiori and aggregation cardinality checks. See Develop Your Application. 6-21
s Suite - dry Devel
Applica Devel op
tion opment ment
Studio Effi-
ciency
SAP Exten Cloud SAP You can now develop using Fiori elements. New 2020-0
Busines sion Foun Fiori 6-21
s Suite - dry Devel
Applica Devel op
tion opment ment
Studio Effi-
ciency
SAP Exten Cloud Appli The Application Wizard has been enhanced. Steps are now clicka Chang 2020-0
Busines sion Foun cation ble and you can press 'Enter' in the login control. ed 6-07
s Suite - dry Wizard
Applica Devel
tion opment
Studio Effi-
ciency
SAP Exten Cloud Run The Run Configuration tree shows 'shared' dependecies. New 2020-0
Busines sion Foun Config- 6-07
s Suite - dry ura
Applica Devel tions
tion opment
Studio Effi-
ciency
SAP Exten Cloud SAP You can now add a launchpad to an SAP Fiori project with a Cloud New 2020-0
Busines sion Foun Fiori Foundry target runtime. See Basic Development Flow in SAP Busi 6-07
s Suite - dry Devel ness Application Studio.
Applica Devel op
tion opment ment
Studio Effi-
ciency

Techni
cal Envi Availa
Com Capa ron ble as
SAP Exten Cloud SAP SAP Business Application Studio Trial is now available in the AWS New 2020-0
Busines sion Foun Cloud US East (VA) region. 5-24
s Suite - dry Plat
Applica Devel form
tion opment Re
Studio Effi- gions
ciency
SAP Exten Cloud SAP You can now deploy SAP Fiori applications to the HTML5 reposi New 2020-0
Busines sion Foun Fiori tory using the Generic Application Content Deployer (GACD). 5-24
s Suite - dry De
Applica Devel ploy
tion opment ment
Studio Effi-
ciency
s Suite - dry
Applica Devel
tion opment
Studio Effi-
ciency
SAP Exten Cloud Appli The New Application wizard now has a Back button. You can go to New 2020-0
cation
Busines sion Foun previous steps to change or view your entries. 5-10
Wizard
s Suite - dry
Applica Devel
tion opment
Studio Effi-
ciency
SAP Exten Cloud Appli You can now choose the location where the new projects should Chang 2020-0
cation ed
Busines sion Foun be generated. 5-10
Wizard
s Suite - dry
Applica Devel
tion opment
Studio Effi-
ciency

Techni
cal Envi Availa
Com Capa ron ble as
SAP Exten Cloud Con You can now insert a direct URL to consume a service and bind it Chang 2020-0
sume ed
Busines sion Foun to your project. 5-10
SAP
s Suite - dry
Serv
Applica Devel ices
tion opment
Studio Effi-
ciency
SAP Exten Cloud MTA With the new Cloud MTA Build Tool version 1.0.14, you can use the New 2020-0
Busines sion Foun module build features directly in SAP Business Application Studio. 5-10
s Suite - dry See Auxiliary Commands (https://sap.github.io/cloud-mta-build-
Applica Devel tool/usage/#auxiliary-commands).
tion opment
Studio Effi-
ciency
SAP Exten Cloud CAP You can now run your CAP Node application from the Run New 2020-0
Busines sion Foun Configuration view and bind to a local sqlite database. 5-10
s Suite - dry
Applica Devel
tion opment
Studio Effi-
ciency
SAP Exten Cloud SAP You can now specify a package and transport when deploying an New 2020-0
Fiori
Busines sion Foun SAP Fiori application to ABAP. 5-10
Devel
s Suite - dry
op
Applica Devel ment
tion opment
Studio Effi-
ciency
SAP Exten Cloud CAP The 'cds-dk' has been updated to version 1.6.4 and the 'generator- Chang 2020-0
Busines sion Foun cap-project' to version 1.0.6. ed 4-26
s Suite - dry
Applica Devel
tion opment
Studio Effi-
ciency

Techni
cal Envi Availa
Com Capa ron ble as
SAP Exten Cloud CAP You can now view data models from external services in the CAP New 2020-0
Busines sion Foun project explorer. 4-26
s Suite - dry
Applica Devel
tion opment
Studio Effi-
ciency
SAP Exten Cloud SAP When using freestyle templates, you can now consume services New 2020-0
Busines sion Foun Fiori and bind entities. 4-26
s Suite - dry project
Applica Devel crea
tion opment tion
Studio Effi-
ciency
SAP Exten Cloud Run You can now configure multiple data sources in SAP Fiori run con New 2020-0
Busines sion Foun Config- figurations for Cloud Foundry. Cloud Foundry login is not required. 4-26
s Suite - dry ura
Applica Devel tions
tion opment
Studio Effi-
ciency
SAP Exten Cloud SAP You can now get SAPUI5 code assist for XML views and fragments. New 2020-0
Busines sion Foun Fiori 4-26
s Suite - dry Devel
Applica Devel op
tion opment ment
Studio Effi-
ciency
SAP Exten Cloud SAP You can now get code validation for the application descriptor New 2020-0
Busines sion Foun Fiori (manifest.json file). 4-26
s Suite - dry Devel
Applica Devel op
tion opment ment
Studio Effi-
ciency

Techni
cal Envi Availa
Com Capa ron ble as
SAP Exten Cloud Cloud When you create a service instance, you can outline the service New 2020-0
Busines sion Foun Foun parameters. 4-26
s Suite - dry dry
Applica Devel Tools
tion opment
Studio Effi-
ciency
SAP Exten Cloud SAP You can now deploy HTML5 modules independently, using the New 2020-0
Busines sion Foun Fiori 'HTML5 Applications repository CLI' plugin. You can then inspect 4-26
s Suite - dry De these modules in runtime. See Deploy Your Application.
Applica Devel ploy
tion opment ment
Studio Effi-
ciency
SAP Exten Cloud SQL We have updated the SQL Tools to version 0.21.6. With this ver Chang 2020-0
Busines sion Foun Tools sion, you can now connect to SAP HANA as a Service (HaaS). ed 4-12
s Suite - dry
Applica Devel
tion opment
Studio Effi-
ciency
SAP Exten Cloud CAP You can now create a CAP application using the command palette New 2020-0
Busines sion Foun or the terminal. 4-12
s Suite - dry
Applica Devel
tion opment
Studio Effi-
ciency
SAP Exten Cloud Data When an account is closed or when an administrator unsubscribes Chang 2020-0
Busines sion Foun Privacy from SAP Business Application Studio, all the tenant's data is de ed 4-12
s Suite - dry leted automatically.
Applica Devel
tion opment
Studio Effi-
ciency

Techni
cal Envi Availa
Com Capa ron ble as
SAP Exten Cloud Project A default run configuration is now created as part of the project New 2020-0
Busines sion Foun Wizard wizard flow. You can create a project from template and run it. 4-12
s Suite - dry Tool
Applica Devel  Note
tion opment Not applicable for CAP applications.
Studio Effi-
ciency
SAP Exten Cloud Project When the project wizard ends, you can now choose between Open New 2020-0
Busines sion Foun Wizard New Workspace to open the generated project in the root, or Add 4-12
s Suite - dry Tool to Workspace to work in multi-root.
Applica Devel
tion opment
Studio Effi-
ciency
SAP Exten Cloud Run You can now run an SAP Fiori application with a Cloud Foundry tar New 2020-0
Busines sion Foun Config- get runtime consuming an ABAP on-premise service. 4-12
s Suite - dry ura
Applica Devel tions
tion opment
Studio Effi-
ciency
SAP Exten Cloud Con You can now perform service exploration in both the V2 and v4 for New 2020-0
Busines sion Foun suming mats. 3-29
s Suite - dry SAP
Applica Devel Serv
tion opment ices
Studio Effi-
ciency
SAP Exten Cloud Cloud The Cloud Foundry tools have been moved to the 'npm' package Chang 2020-0
Busines sion Foun Foun so that they can be used externally. ed 3-29
s Suite - dry dry
Applica Devel Tools
tion opment
Studio Effi-
ciency

Techni
cal Envi Availa
Com Capa ron ble as
SAP Exten Cloud Project New features have been added to the project wizard, such as dis Chang 2020-0
Busines sion Foun Crea playing prompts in advance, login control, and browse control. ed 3-29
s Suite - dry tion
Applica Devel
tion opment
Studio Effi-
ciency
SAP Exten Cloud Run When running an SAP Fiori app locally, you can now select the SA New 2020-0
Busines sion Foun Config- PUI5 version. See Creating Run Configurations for SAP Fiori Appli 3-29
s Suite - dry ura cations.
Applica Devel tions
tion opment
Studio Effi-
ciency
SAP Exten Cloud Exten SAP Cloud Platform Mobile Services New 2020-0
Busines sion Foun sions 3-15
Use the Mobile Development Kit (MDK) editor to edit various as
s Suite - dry
pects of your MDK application such as validating and bundling the
Applica Devel
MDK app, creating MDK metadata objects, and deploying the
tion opment
MDK app to Mobile Services. You can also use the MBT tool to cre
Studio Effi-
ate an OData CSDL file and generate an OData service in Java
ciency
from an OData CSDL file. See Setting Up the Editor in SAP Busi
ness Application Studio.
SAP Exten Cloud Run You can now use Local Run with test (mock) data when testing the New 2020-0
Busines sion Foun Config- "Consume SAP Services" tool in VS Code. 3-15
s Suite - dry ura
Applica Devel tions
tion opment
Studio Effi-
ciency
SAP Exten Cloud Con When running a CAP Node application using the Run Configuration New 2020-0
Busines sion Foun suming view, you can now easily bind it to depending Cloud Foundry serv 3-15
s Suite - dry SAP ices. See Creating Run Configurations for CAP Node Applications.
Applica Devel Serv
tion opment ices
Studio Effi-
ciency

Techni
cal Envi Availa
Com Capa ron ble as
SAP Exten Cloud Exten The following tools are now installed and exposed via the CLI as New 2020-0
Busines sion Foun sions part of the Basic Tools extension: make, bzip2, patch, perl, tar, 3-15
s Suite - dry sqlite3, vim, zip, and pv.
Applica Devel
tion opment
Studio Effi-
ciency
SAP Exten Cloud Run Freestyle SAPUI5 templates are available for project creation us New 2020-0
Busines sion Foun Config- ing the terminal. See Create an SAP Fiori Project. 3-15
s Suite - dry ura
Applica Devel tions
tion opment
Studio Effi-
ciency
SAP Exten Cloud Run The development dependencies to SAP Fiori projects are now in New 2020-0
Busines sion Foun Config- stalled upon project creation. 3-15
s Suite - dry ura
Applica Devel tions
tion opment
Studio Effi-
ciency
SAP Exten Cloud Run When running an SAP Fiori app locally, you can now select if you New 2020-0
Busines sion Foun Config- want to run it from the 'build' folder or from the 'source' folder. See 3-15
s Suite - dry ura Creating Run Configurations for SAP Fiori Applications.
Applica Devel tions
tion opment
Studio Effi-
ciency
SAP Exten Cloud Run You can now choose the relevant HTML file, such as a QUnit test or New 2020-0
Busines sion Foun Config- a mock server, when creating run configurations for a SAP Fiori 3-01
s Suite - dry ura application deployed to Cloud Foundry. See Creating Run Configu-
Applica Devel tions rations for SAP Fiori Applications.
tion opment
Studio Effi-
ciency

Techni
cal Envi Availa
Com Capa ron ble as
SAP Exten Cloud Work You can now use the Project Explorer feature for CAP applications. New 2020-0
Busines sion Foun ing See CAP Project Explorer. 3-01
s Suite - dry with
Applica Devel CAP
tion opment Appli
ciency
SAP Exten Cloud Run You can now select an HTML file from the Run Configurations view New 2020-0
Busines sion Foun ning to run your SAP Fiori project. 3-01
s Suite - dry SAP
Applica Devel Fiori
tion opment Appli
ciency
SAP Exten Cloud De You can now develop an SAP Fiori application consuming a service New 2020-0
Busines sion Foun velop from the ABAP Service Catalog. See Developing an SAP Fiori Ap 2-16
s Suite - dry Appli plication Based on an ABAP Service Catalog.
Applica Devel cation
tion opment Based
Studio Effi- on an
ciency ABAP
Service
Cata
log
SAP Exten Cloud Run You can now create and manage a run configuration for the Java New 2020-0
Busines sion Foun Config- service of an MTA application via the Run Configurations view. See 2-02
s Suite - dry ura Creating Run Configurations for Java Modules.
Applica Devel tions
tion opment  Note
Studio Effi- Available in AWS and Azure regions only.
ciency
SAP Exten Cloud Run You can now create run configurations for CAP applications and New 2020-0
Busines sion Foun Config- the Java service of MTAs within a multi-root workspace. See Multi- 2-02
s Suite - dry ura root Workspaces .
Applica Devel tions
tion opment  Note
Studio Effi-
Available in AWS and Azure regions only.
ciency

Techni
cal Envi Availa
Com Capa ron ble as
SAP Exten Cloud Exten You can now trigger an MTA build and deploy it from a context New 2020-0
Busines sion Foun sions menu and the command palette. See Build and Deploy Multitarget 2-02
s Suite - dry Applications.
Applica Devel
tion opment
Studio Effi-
ciency
SAP Exten Cloud Deploy You can now deploy an existing SAP Fiori project from SAP New 2020-0
Busines sion Foun to Business Application Studio to the SAPUI5 ABAP repository. See 2-02
s Suite - dry ABAP Deploy to the SAPUI5 ABAP Repository.
Applica Devel
tion opment
Studio Effi-
ciency
SAP Exten Cloud De You can now develop an SAP Fiori application consuming a service New 2020-0
Busines sion Foun velop from ABAP Cloud System Service catalog. See Developing an SAP 2-02
s Suite - dry Appli Fiori Application Based on an ABAP Cloud System Service.
Applica Devel cation
tion opment Based
Studio Effi- on
ciency ABAP
Cloud
System
SAP Exten Cloud Exten You can use the VS Code REST Client in your dev spaces. See VS New 2020-0
Busines sion Foun sions Code REST Client . 1-16
s Suite - dry
tion opment
Available in AWS and Azure regions only.
Studio Effi-
ciency
SAP Exten Cloud CDS We have updated the CDS extension to use @sap/cds-dk version New 2020-0
Busines sion Foun Exten 1.3.1. 1-16
s Suite - dry sions
tion opment Available in AWS and Azure regions only.
Studio Effi-
ciency

Techni
cal Envi Availa
Com Capa ron ble as
SAP Exten Cloud Con You can now select a data source for your project from the service New 2019-11
Busines sion Foun suming catalog of an ABAP system. The destination will appear with the -14
s Suite - dry SAP "Catalog" descriptor. See Consuming SAP Services.
Applica Devel Serv
tion opment ices
Studio Effi-
ciency

3 Developer Guide
With SAP Business Application Studio, you can develop business applications for the Intelligent Enterprise.
Managing Your Dev Spaces [page 23]

You can create, delete, stop, and start dev spaces. You can also configure dev space settings, download
dev space content, and import dev space content.
Development Scenarios [page 26]
Additional Extensions [page 31]

You can extend and enrich your development environment with tools and capabilities based on your
needs.
IDE Tools [page 33]

This sections describes the main IDE tools.
Productivity Tools [page 46]

Learn how to use the productivity tools in SAP Business Application Studio for an enhanced
development experience.
Managing Ports [page 62]

If you want to access an application that is running in your dev space from an external source (for
example a browser or REST client), you must first expose the port that is listening to the application.
Accessing On Premise Systems [page 62]

You can access on premise systems using a built-in Web Proxy.
Building and Deploying Multitarget Applications [page 64]

Build and deploy multitarget applications to SAP Cloud Foundry.
Working with a Trial Account [page 65]

Get a trial account to experience SAP Business Application Studio for free.
Troubleshooting [page 65]

Here are some common troubleshooting issues in SAP Business Application Studio.
3.1 Managing Your Dev Spaces
You can create, delete, stop, and start dev spaces. You can also configure dev space settings, download dev
space content, and import dev space content.
Develop Your Application with a Dev Space
A dev space is a development environment with all of the tools, capabilities, and resources needed for
developing your application. Each type of application requires a different development environment. Based on
the type of application that you choose to build, you're provided with a different set of tools.

Developer Guide PUBLIC 23
Use an SAP Business Application Studio Extension
An SAP Business Application Studio extension is a set of tools that help you perform a specific development
task. For example, the Java Tools extension provides you with the tools that you need to develop a Java
application. The Fiori Tools extension includes the template, CLI, and code completion required to create an
SAP Fiori application.
Select the Application Type
When you create a dev space, you're prompted to select the type of application that you want to create. The
application contains the SAP Predefined Extensions, a group of extensions that you need for performing a
specific end-to-end scenario. When choosing the application type, the list of tools that you need to develop,
build, and deploy your application is displayed.
You can add Additional SAP Extensions, other required tools to supplement the application with additional
components for the scenario, to your developer environment.
Create a Dev Space
You can generate a dev space to create and manage applications. You can select the application type that
includes the extensions that you need for performing a development task.
1. Open SAP Business Application Studio and log in with your credentials.
2. Click Create Dev Space.
3. Enter a name for the dev space.
4. Select the relevant application type.
5. (Optional) Select the relevant additional extensions to enhance your space.
6. Click Create Dev Space.
 Note
The button is only enabled if you entered a dev space name.
Stop, Start, or Delete Your Dev Space
If you don't need to work with your dev space for a while, you can stop your dev space. When your dev space is
running, it consumes memory, energy, and CPU. If you don't use your dev space and it sits idle for too long, the
dev space will be stopped.
When you restart your stopped dev space, all content in your dev space, including files and settings, remain and
will be available. If you want to apply updates to extensions and bug fixes, you must stop your dev space and
start it again.
You can also delete your dev space.

24 PUBLIC Developer Guide
 Note
By creating a dev space, you create a project and file system for yourself. If you delete your dev space, it
can't be recovered. We recommend syncing, backing up, and saving your project to the Git Repository.
Configure Dev Space Settings
After opening your dev space, you can configure your preferred settings for working in the dev space:
● Keyboard shortcuts
● Color theme
● File icon theme
● General preferences
To change your settings, go to File Settings .
 Note
Settings are relevant per dev space. You must set your settings for each dev space separately.
Download Dev Space Content
You can download the dev space content in the following situations:
● When your dev space is in the RUNNING state to save the dev space contents.
● When your dev space is in the ERROR state to recover your data and move the contents to another dev
space.
To download the content of your dev space, click and then Download.
After the download begins, the dev space state changes to STARTING. The dev space state then changes to
SAFE MODE and then the tar file downloads.
When the download is complete, the tar file appears, which contains the dev space content.
Import Dev Space Content
After downloading the dev space content, you can import the content to another dev space by performing the
following steps:
1. Create a new dev space and open it.

2. Open the project folder.
3. Select the project folder and click File Upload Files .
4. From the Downloads folder, choose the file with the dev space content.

5. Open the terminal.
6. Enter the following command to uncompress the uploaded file:
tar xvzf <yourFileName>.tar.gz
3.2 Development Scenarios
SAP Business Application Studio leverages dev spaces to provide tailored tools and pre-installed runtimes per
business scenario. 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.
Each scenario contains a set of predefined extensions that help improve your experience.
When creating a new dev space, select the scenario that best fits the application type you want to create. For
more information, see Managing Your Dev Spaces [page 23].
The list below shows a selection of our most used scenarios:
Scenario Desccription
Mobile Development Kit The Mobile Development Kit (MDK) lets you customize, de
ploy, and manage your customized iOS and Android apps in
the cloud.
This scenario contains the following predefined extension:
● Java Tools
Allows you to develop and run Java applications. In
cludes debugging capabilities and enhanced code edi
tors. The following tools will be installed as part of the
extension:
○ Java JDK V 8
○ Maven V 3.6.1
○ Tomcat V 9.0.33
See Language support for Java ™ for Visual Studio Code
and Debugger for Java .
See, Mobile Development Kit.

SAP Cloud Business Applications Build business services and business applications and ex
tend S/4HANA using SAP Cloud Application Programming
Model, Fiori and Java or Node.js.
This scenario contains the following predefined extensions:
● CDS Tools
Allows you to develop applications based on CDS using
the CDS command line and tools.
Includes enhanced code editors and database manage
ment capabilities. The following tool will be installed as
part of the extension:
○ CDS Command Line Tools v1.4.3
See SQLTools .
● Java Tools
Allows you to develop and run Java applications. In
cludes debugging capabilities and enhanced code edi
tors. The following tools will be installed as part of the
extension:
○ Java JDK V 8
○ Maven V 3.6.1
○ Tomcat V 9.0.33
See Language support for Java ™ for Visual Studio Code
and Debugger for Java .
● MTA Tools
Allows you to perform operations such as build, deploy
ment, and validation on multitarget applications. The
following tools will be installed as part of the extension:
○ Cloud Foundry environment CLI
○ Cloud Foundry environment deployment plugin
○ Cloud MTA Build Tool
○ MTA module runner (VSCode extension)
See MTA Tools.
See, Using SAP Business Application Studio
SAP Cloud Platform Workflow Automate business processes using workflow technology.
Design workflows based on Business Process Model and No
tation (BPMN) in a graphical editor. Model workflow user in
terfaces using forms.
See, SAP Cloud Platform Workflow in the Cloud Foundry En

vironment

SAP Fiori Develop SAP Fiori applications based on various environ

ments: Cloud Foundry, ABAP on-prem, and ABAP Cloud. See
Developing an SAP Fiori Application.
This scenario contains the following predefined extensions:
● Fiori Application
Allows you to create a fiori application, using the Yeo
man generator.
See Create an SAP Fiori Project.
● Fiori Freestyle Tools
Allows you to optimize your Fiori-based development.
This extension provides Fiori templates with the follow
ing tools:
○ UI5 CLI
○ Grunt CLI
○ abap-deploy CLI
● MTA Tools
Allows you to perform operations such as build, deploy
ment, and validation on multitarget applications. The
following tools will be installed as part of the extension:
See MTA Tools.
● SAP Fiori Tools
Allows you to simplify the development of SAP Fiori ele
ments applications by providing extensions that can
help you create applications, visualize navigation, auto
matically generate code and more. The following exten
sions will be installed:
○ Fiori elements Yeoman Generator
○ Application Modeler
○ Guided Development
○ Service Modeler
○ XML Annotation Language Server
See SAP Fiori Tools.
● SAPUI5 Layout Editor
Allows you to visually develop your XML view.
See Develop UI Using the Layout Editor.
● UI5 Freestyle Templates
Allows you to create an SAP Fiori worklist and master
details applications, using the Yeoman generator.

SAP Fiori
Develop SAP Fiori applications based on various environments: Cloud Foundry, ABAP on-prem, and ABAP
Cloud. See, Developing an SAP Fiori Application.
See the following topics for more information:
●
●
●
●
Expand to learn about the scenario's predefined extensions:

● Fiori Application
Allows you to create a fiori application, using the Yeoman generator.
See Create an SAP Fiori Project.
● Fiori Freestyle Tools
Allows you to optimize your Fiori-based development. This extension provides Fiori templates with the
following tools:
○ UI5 CLI
○ Grunt CLI
○ abap-deploy CLI
● MTA Tools
Allows you to perform operations such as build, deployment, and validation on multitarget applications.
The following tools will be installed as part of the extension:
See MTA Tools.
● SAP Fiori Tools
Allows you to simplify the development of SAP Fiori elements applications by providing extensions that can
help you create applications, visualize navigation, automatically generate code and more. The following
extensions will be installed:
○ Fiori elements Yeoman Generator
○ Application Modeler
○ Guided Development
○ Service Modeler
○ XML Annotation Language Server
See SAP Fiori Tools.
● SAPUI5 Layout Editor
Allows you to visually develop your XML view.
● UI5 Freestyle Templates
Allows you to create an SAP Fiori worklist and master details applications, using the Yeoman generator.

SAP Cloud Business Applications
Build business services and business applications and extend S/4HANA using SAP Cloud Application
Programming Model, Fiori and Java or Node.js. See SAP Business Application Studio in Capire .
● CDS Tools
Allows you to develop applications based on CDS using the CDS command line and tools.
Includes enhanced code editors and database management capabilities. The following tool will be installed
as part of the extension:
○ CDS Command Line Tools v1.4.3
● Java Tools
Allows you to develop and run Java applications. Includes debugging capabilities and enhanced code
editors. The following tools will be installed as part of the extension:
○ SapMachine11
○ Maven V 3.6.1
○ Tomcat V 9.0.33
See Language support for Java ™ for Visual Studio Code , Debugger for Java , and Spring Boot tools
.
● MTA Tools
Allows you to perform operations such as build, deployment, and validation on multitarget applications.
The following tools will be installed as part of the extension:
See MTA Tools.
Mobile Development Kit
The Mobile Development Kit (MDK) lets you customize, deploy, and manage your customized iOS and Android
apps in the cloud. See, Mobile Development Kit.
● Java Tools
Allows you to develop and run Java applications. Includes debugging capabilities and enhanced code
editors. The following tools will be installed as part of the extension:
○ Java JDK V 8
○ Maven V 3.6.1
○ Tomcat V 9.0.33
See Language support for Java ™ for Visual Studio Code and Debugger for Java .

SAP Cloud Platform Workflow
Automate business processes using workflow technology. Design workflows based on Business Process Model
and Notation (BPMN) in a graphical editor. Model workflow user interfaces using forms. See, SAP Cloud
Platform Workflow in the Cloud Foundry Environment.
Extension Factory Serverless Runtime Development Tools
Allows you to create and deploy extensions in a serverless environment. See, Create Extensions with Extension
Factory, serverless runtime Project Template.
3.3 Additional Extensions
You can extend and enrich your development environment with tools and capabilities based on your needs.
Each dev space contains a group of extensions that enhance its exiting functionality. Some extensions are
predeefined by each development scenario, and others can be manually enabled based on your specific
development needs.
The list below shows a selection of our most used additional extensions.
 Note
To learn about the predefined extensions, see Development Scenarios [page 26].
Extension Description
CDS Graphical Modeler Allows you to design SAP core data service models in SAP
cloud business application development projects.
The extension includes the CDS Editor, which provides capa

bilities for SAP business developers to visually design SAP
CDS models. Models include artifacts, such as entities,
types, unstructured types, enums, arrayed types, events, as
sociations and compositions, projects and services, which
accelerate SAP cloud business application development.
See Design CDS Models Using SAP Business Application

Studio.

Extension Description
Development Tools for SAP Work Zone The development tools allows you to build UI Integration
cards, which are user interface elements that present new
means to provide application information to the end user in a
unified way. The business information are represented com
pactly and allows interaction on it being executed. This edi
tor allows user to create new cards or build cards from avail
able samples, edit card properties and preview the changes.
Finally, users can bundle and deploy the cards into different
systems.
See SAP Work Zone Developer Guide.
Extension Factory Serverless Runtime Development Tools Allows you to create and deploy extensions in a serverless
environment.
See, Create Extensions with Extension Factory, serverless

runtime Project Template.
Launchpad Module Allows you to add a launchpad to your multitarget applica

tion.
See Basic Development Flow in SAP Business Application

Studio.
MTA Tools Allows you to perform operations such as build, deployment,

and validation on multitarget applications. The following
tools will be installed as part of the extension:
● Cloud Foundry environment CLI

● Cloud Foundry environment deployment plugin
● Cloud MTA Build Tool
● MTA module runner (VSCode extension)
See MTA Tools.
SAPUI5 Adaptation Project SAPUI5 Adaptation Project allows developers to extend SAP
Fiori application in SAP Business Application Studio.
See Extending an SAP Fiori Application.
SAPUI5 Layout Editor Allows you to visually develop your XML view.
Workflow Management Allows you to create workflow applications and process tem
plates with SAP Cloud Platform Workflow.
See SAP Cloud Platform Workflow Management.

3.4 IDE Tools
This sections describes the main IDE tools.
On the left side you find a quick bar to open most important views, most importantly the Explorer view to
browse the contents of your current workspace.
Other views, such as an outline, a problems view and a terminal can be opened with the respective menu entry
from the View menu. You can drag tabs around to adapt your window layout.
Git Integration [page 33]

SAP Business Application Studio enables you to connect and interact with the Git control system,
letting you connect and interact with remote Git repositories.
Search [page 42]

There are different Search capabilities in SAP Business Application Studio.
Terminal [page 44]

Opening the integrated terminal allows you to access the underlying system. The terminal is a
convenient tool because you don't need to switch windows or change the state of an existing terminal
to perform a quick command-line task.
Command Palette [page 45]

The command palette provides access to all the IDE functionality including shortcuts for the most
common operations.
Outline View [page 45]

The Outline view displays a symbol tree of the currently active editor. This view is useful for
understanding the structure of a file or for navigating to a specific element in a file.
Problems View [page 46]

The Problems view displays the coding errors and warnings of all open files in a list. When you click an
item from the list, the problematic piece of code is highlighted in the editor.
3.4.1 Git Integration
SAP Business Application Studio enables you to connect and interact with the Git control system, letting you
connect and interact with remote Git repositories.
Related Information
Connect to Your Corporate Git System [page 34]

Using the Git View [page 35]
Cloning Repositories [page 40]
Adding an Existing Project to Git Using the Terminal [page 41]
Using Personal Access Token authentication [page 41]
Git Troubleshooting [page 66]

3.4.1.1 Connect to Your Corporate Git System
You can work with on premise Git repositories once an appropriate destination has been created in your
subaccount.
Context
Make sure to use the exact same host and port as defined in the destination URL property.
 Note
The corporate Git connectivity supports only secure HTTPS connections. HTTP, SSH and other protocols
are not supported.
Procedure
1. Install and configure an SAP Cloud Platform connector. For more information, see Cloud Connector.
2. Configure the cloud connector to open a channel to your Git system. Follow the instructions as described in
Configure Access Control . Use the following settings:
Field Value
Back-end Type Non-SAP System
Protocol HTTPS
Internal Host / Port Enter the internal host and port for your Git system.
Host / Port Enter a virtual host and port for your Git system. You can use the same host
and port as for the virtual host and port.
Principal Type None
For the system you just added, specify the resources to enable, using the following settings:
Field Value
Enabled Checked
URL Path /
Access Policy Path and all sub-paths
3. Upload your organization's Git server certificate to the cloud connector (if your Git server is using
certificate-based authentication).

4. If you defined a custom identity provider, make sure that you have configured the assertion-based
attributes mapping for this identity provider. For more information, see Configure Trust to the SAML
Identity Provider.
5. Define your corporate Git destination. For more information, see .
a. In the SAP Cloud Platform cockpit, select Connectivity Destinations .

b. Select New Destination.
c. In the Destination Configuration section, set the Proxy Type to OnPremise.
d. In the Additional Properties section, configure the following:
Property Value
WebIDEEnabled true
HTML5.DynamicDestination true
HTML5.Timeout 60000
(Optional property)
3.4.1.2 Using the Git View

General overview of the Git view in SAP Business Application Studio.
SAP Business Application Studio provides a graphical user interface for executing Git commands and
managing your source control and versioning. You can also manually perform other Git commands from the
terminal.
Understanding the UI
The Git view consists of three major sections. The top section is for authoring the commit messages. It also
provides access to a couple of basic Git commands.

Below this, you find the commit section, which lists the changed files by their name and separates them in two
groups:
● STAGED CHANGES - A list of the files that have been staged. Click to open the selected file, or to
unstage it.
● CHANGED - Files listed under the CHANGED section contain unstaged changes. Each file name is followed
by a path to its parent directory and an indicator describing the status of the change.
Click to open the selected file, to stage the file, or to refresh it.
The files can be in any of the following statuses:
● A - A new file that has been staged.

● U - An unstaged file. An unstaged change can be reverted by clicking on the Discard Changes action next to
the file location.
● S - A staged file. Files can be staged (added to the index) by clicking on Stage.
● M - A modified file. Double-clicking on a modified file will open it in a diff editor. The read-only editor on the
left-hand side shows the state from the index. The right-hand side of the editor reflects the state of the
working tree, and it lets you to further modify the file.
● R - A renamed file.
● C - A copied file (if blue) or a conflicted file (if red).
● D - A deleted file.
At the bottom of the Git view you can see the last commit section, where a description of the most recent
commit is displayed.
After staging the desired files and specifying the commit message, the changes can be committed to the
repository. After a successful commit, the Last Commit section is automatically updated.
Using the Git View
1. From the left side-menu, click . The Git view opens.

2. In the Message field, enter a description for the commit.
3. Press <Ctrl> + <Enter> or click to commit the changes.
4. Click to refresh the Git pane.
5. Click to add your name to the commit.

6. Click Amend at the bottom of the pane to make changes to a commit.
7. From the menu bar, go to View Git History to see the commits that have been done on the project or
on a specific file.
8. Click (More) to open the list of Git commands available from the graphical user interface. See the
Available Git Commands section below.
Git Status Bar
At the bottom left corner of SAP Buisness Application Studio, you can find indicators describing the status of
your Git repository. They show the current branch, dirty indicators, and the number of ahead and behind
changes of the current branch.
The dirty indicators are as follows:
*: You have unstaged changes in your branch.
+: You have staged changes in your branch, but no unstaged.
!: You have conflicting changes in your branch.
By clicking on the branch name, you can perform a Git checkout. This operation is equivalent to the Git:
Checkout command from the command palette.
There is a Synchronize Changes action as well in the status bar, next to the branch indicator, if the currently
checked-out branch has an upstream branch configured. Synchronize Changes will pull remote changes to your
local repository and then push local commits to the upstream branch.

Branches and Tags
You can create and check out branches directly within the IDE through the Git: Checkout command in the
command palette.
To create a new branch:
1. Select Create new branch....

2. Entere a name for the new branch. A new branch is created and checked out.
Gutter Indicators
If you open a folder that is a Git repository and begin making changes, annotations are added to the gutter and
to the overview ruler.
● A red triangle indicates where lines have been deleted.

● A green bar indicates new added lines.
● A blue bar indicates modified lines.
Blame Annotations
You can show the blame annotation by either selecting the Show Blame Annotations from the editor’s context
menu or by selecting Git: Show Blame Annotations from the command palette. This will show the blame
annotations on the left hand-side of the editor.
Press Esc to hide the blame annotations.
Merge Conflicts
The IDE recognizes merge conflicts. The differences are highlighted and you can choose whether to accept the
local change or the new one. You can also accept both modifications at the same time.
Viewing Diffs
Selecting a modified file opens a diff viewer. Its left-hand side is a read-only editor showing the index state, and
the right-hand side is an editor for the working-tree state.

Git History
There are various ways to review the Git history. You can see the history of an individual file or you can see the
history of multiple files within a directory.
You can activate the Git History view by right-clicking on the file in the file explorer and selecting the Git History
context menu item. Alternatively, you can open the history view from the View Git History . The content
of the Git History view does not update when changing the active editor or when altering the selection in the file
explorer. To get the history of an individual resource you have to either use the Git History command from the
command palette or from the the file explorer’s context menu.
The top of the Git History view shows the path of the resource or resources. Right below the path, you can see
the list of commits with some details such as the committer, the subject of the commit message, and the
relative time of the commit. You can open up the commit in a read-only editor to review all the details about the
commit.
Available Git Commands
Command Description
Fetch Enables you to download objects and references from another repository
into your local repository. You can then merge or rebase the changes into
your project.
Merge Enables you to incorporate all the changes from one branch into another in a
single commit.
Pull Pulling is the same as fetching and merging. Pulling enables you to download
objects and references from another repository into your local repository,
and then merge the changes into your project.
Pull from Define the remote branch from which you want to pull your changes.

Command Description
Push The Push option incorporates all unsynced committed changes into the re
mote branch of the currently checked-out local branch. The number of un
synced committed changes is displayed next to the repository name. All
tags created within the open repository are pushed.
Push to Define the remote branch to which you want to push your changes.
Commit (Amend) Enables you to add the current changes to the last commit.
Commit (Signed Off) Enables you to save your changes to the local repository. Sign-off is a line at
the end of the commit message which certifies who is the author of the com
mit.
Discard All Changes Discarding removes all changes from an existing file in the local environ
ment. For example, discarding a new file deletes the file from the branch.
Stage All Changes Adds changed files to list of changes that will be included in the next com
mit.
Unstage All Changes Removes files from the next commit.
Apply Latest Stash If you have stashed changes, you can apply the latest stashed changes to
the files in your working directory
Apply Stash If you have stashed changes, you can apply the stashed changes to the files
in your working directory.
Drop Stash Removes stashed changes from the next commit.
Pop Latest Stash Removes the latest stash after it has been commited.
Pop Stash Removes the stased changes after they have been commited.
Stash If you made some changes that you are not yet ready to commit, you can
stash (store away) and revert them from your working directory, and resume
working on them later.
3.4.1.3 Cloning Repositories
Add an existing project to your local workpace by cloning its repository from Git.
1. Open a terminal.
2. Change the current working directory to the location where you want the cloned directory.
3. Type git clone, and then paste your URL.
For example:
 Sample Code
$ git clone https://github.com/YOUR-USERNAME/YOUR-REPOSITORY

3.4.1.4 Adding an Existing Project to Git Using the Terminal
You can use the terminal to add an existing project to Git so that you can continue working on it in SAP
Business Application Studio
1. Change the current working directory to your local project.

2. Initialize the local directory as a Git repository.
$ git init
3. Add the files in your new local repository. This stages them for the first commit.
$ git add .
4. Commit the files that you've staged in your local repository.
$ git commit -m "First commit"
5. In the Command prompt, add the URL for the remote repository where your local repository will be
pushed.
$ git remote add origin https://domain.com/user.name/RepoName.git
6. Push the changes in your local repository to GitHub.
$ git push origin master
3.4.1.5 Using Personal Access Token authentication
Personal access tokens (PATs) are an alternative to using passwords for authentication to GitHub when using
the GitHub API or the command line.
To create a token, follow the instructions described in the GitHub documentation .
Once you have your token, you can save it in your dev space so you will not be prompted for it on each Git
command.
To save your token in your dev space, create a .netrc file in the $HOME directory (/home/user) with the
following content:
machine <git_host>
login <user_id>
password <user_token>
For example:
machine github.com
login developer@sap.com
password 825270ffffe74d9f988a0f0066ad59f0

3.4.2 Search
There are different Search capabilities in SAP Business Application Studio.
You can perform a search from the Search view or from the Find widget in the editor.
● To open the Search view, select View Search .
● To open the Find widget, press Ctrl+F.
Find and Replace
You can find text and replace in the currently opened file. The search results will be highlighted in the editor,
overview ruler, and minimap.
If there is more than one matched result in the current opened file, you can press Enter and Shift+Enter to
navigate to next or previous result when the find input box is focused.
When the Find Widget is open, it will automatically populate the selected text in the editor into the find input
box. If the selection is empty, the word under the cursor will be inserted into the input box instead.
Find In Selection
By default, the find operations are run on the entire file in the editor. It can also be run on selected text. You can
turn this feature on by clicking the hamburger icon on the Find Widget.
Multiline support

You can search text in multiple lines by pasting it into the Find input box. Pressing Ctrl+Enter inserts a new
line in the input box.
Resize Find Widget
You can drag the left sash of the FInd Widget to enlarge it. You can also double-click the left sash to maximize it
or shrink it to its default size.
Search across files
You can search over all files in the currently opened folder. Press Ctrl+Shift+F and enter your search term.
Search results are grouped into files containing the search term, with an indication of the hits in each file and its
location. Expand a file to see a preview of all of the hits within that file. Then single-click on one of the hits to
view it in the editor.
Advanced search options
In the input box below the search box, you can enter patterns to include or exclude from the search.
If you enter a word, a search will be performed on every folder and file with the name of the word you entered in
the workspace.
If you enter ./ before the word, that will match the folder name at the top level of your workspace.
Use an exclamation mark ! to exclude those patterns from the search.
Use a comma , to separate multiple patterns.
Paths must use forward slashes.
You can also use glob syntax:
● * to match one or more characters in a path segment

● ? to match on one character in a path segment
● ** to match any number of path segments, including none
● {} to group conditions (for example {**/*.html,**/*.txt} matches all HTML and text files)
● [] to declare a range of characters to match
Some folders are excluded by default to reduce the number of search results that you are not interested in (for
example, node_modules). Open settings to change these rules.
Also note the Use Exclude Settings and Ignore Files toggle button in the files to exclude box. The toggle
determines whether to exclude files that are ignored by your .gitignore files and/or matched by your
files.exclude and search.exclude settings.
From the Explorer, you can right-click on a folder and select Find in Folder to search inside a folder only.
Search and replace
You can search and replace across files. Expand the Search input field to display the Replace one.

When you type text into the Replace input field, you will see a diff display of the pending changes. You can
replace across all files from the Replace input field, replace all in one file or replace a single change.
Advanced Search and Replace Options
In addition to search and replace with plain text, there are also advanced search options:
● Match Case
● Match Whole Word
● Regular Expression
● Include Ignored Files
3.4.3 Terminal
Opening the integrated terminal allows you to access the underlying system. The terminal is a convenient tool
because you don't need to switch windows or change the state of an existing terminal to perform a quick
command-line task.
You can create multiple terminals open to different locations and easily navigate between them.
With access to the terminal, you can use almost every tool, including running maven or using npm. You can
create new projects or modules, build applications, and deploy applications from the terminal.
To open the terminal in SAP Business Application Studio, select Terminal New Terminal from the menu
bar.

3.4.4 Command Palette
The command palette provides access to all the IDE functionality including shortcuts for the most common
operations.
To open the command palette in SAP Business Application Studio, select View Find Command from the
menu bar.
This will open a text field at the top of the IDE allowing you to type a command. Content assist then allows you
to find commands quickly.
Some commands will lead you into a minimal text-based wizard, allowing you to enter additional parameters.
Type ? into the input field to get a list of available commands you can execute from here:
3.4.5 Outline View

The Outline view displays a symbol tree of the currently active editor. This view is useful for understanding the
structure of a file or for navigating to a specific element in a file.
You can click on an element in the Outline view to open that element in the editor tab.
To open the Outline view in SAP Business Application Studio, select View Outline from the menu bar.
The Outline view opens on the right side of the IDE.

3.4.6 Problems View
The Problems view displays the coding errors and warnings of all open files in a list. When you click an item
from the list, the problematic piece of code is highlighted in the editor.
To open the Problems view in SAP Business Application Studio, select View Problems from the menu
bar.
3.5 Productivity Tools
Learn how to use the productivity tools in SAP Business Application Studio for an enhanced development
experience.
The productivity tools provide the following advantages:
● Increased development productivity from using a tailored set of tools.

● Seamless integration to SAP data sources.
● Guided development.
Application Wizard [page 47]

You can quickly create a new project based on templates using generators.

Cloud Foundry Tools [page 47]
CAP Project Explorer [page 47]

The project explorer displays logical objects in CAP projects.
Consuming SAP Services [page 48]

You can consume an SAP service from your application.
Creating Run Configurations [page 49]

Create run configurations that define how your project or unit test is executed.
MTA Tools [page 60]

The MTA Tools allow you to perform operations such as build, deploy, and validation on multitarget
applications.
Deploy Tool [page 61]

This tool simplifies the task of deploying SAP applications based on different technology stacks,
dependencies, and targets.
3.5.1 Application Wizard
You can quickly create a new project based on templates using generators.
To open the wizard:
1. From the Welcome page, click New Project from template or press F1 and, from the command palette,
select SAP Business Application Studio: Create Project from Template.
The Application wizard opens showing all the available templates from which you can create your project.
2. Select the template that is relevant for the type of application you want to build.
3. Follow the wizard steps.
The steps will vary depending on the template you choose.
3.5.2 Cloud Foundry Tools
3.5.3 CAP Project Explorer
The project explorer displays logical objects in CAP projects.
It displays services and data models found in the project from the semantic point of view and not that of the file
structure.
From the Project Explorer view, you can do the following:
● From each database namespace, hover over the namespace node and click to add a new entity.

● Hover over an entity and click to open the respecitve entity file.
● From the view title, hover and click to open the command pallete to search for workspace symbols.
3.5.4 Consuming SAP Services
You can consume an SAP service from your application.
Prerequisites
● Make sure that your administrator configured the required destination in your Cloud Foundry provider
account.
● Make sure that your workspace contains the project for which you want to consume the service.

Procedure
1. From the menu bar, click View Find Command Consume SAP Services .
2. From the dropdown list, select the project type to which you want to bind the service.
3. Select the project's module.
4. Select the location of your data source.
○ If your data source resides within one of your SAP systems:
1. From the list of sources (destinations) displayed, select the relevant source: System URL, Service
URL, or Catalog System URL.
2. If you selected System URL, enter the path to the specific service.
3. If you selected Catalog System URL, select the desired service from the list of exposed services
displayed.
○ If your data source resides in the SAP API Business Hub:
1. Select the relevant API package (API Business Hub destination).
2. Select the desired API from the list displayed.
 Note
You may require to enter credentials for the selected service.
Results
Once you select a data source, the metadata is retrieved and output is created depending on the project type
you chose.
● If you bound a service for a Business Application project, a folder called external is created. This folder
contains 2 subfolders:
○ edmx - Contains the retrieved data
○ csn - Contains a JSON file representing the CDS version of the metadata.xml file.
● If you bound a service for an SAP Fiori UI application, all the necessary configurations are automatically
added to the SAP Fiori app using the service in your UI.
3.5.5 Creating Run Configurations
Create run configurations that define how your project or unit test is executed.
SAP Business Application Studio provides default run configurations for your projects. You can create and
configure additional run configurations that define how your project or unit test is executed. You can also create
a new run cofiguration by duplicating an existing run configuration and then editing it.

Related Information
Creating Run Configurations for SAP Fiori Applications [page 50]

Creating Run Configurations for Java Modules [page 51]
Creating Run Configurations for CAP Java Applications [page 55]
Creating Run Configurations for CAP Node Applications [page 56]
3.5.5.1 Creating Run Configurations for SAP Fiori

Applications
You can create configuration settings for running your projects.
1. From the left-side menu, click Run Configurations.
2. Click + to create a new configuration.
3. From the command palette, select the runnable object for which you want to create the configuration.
4. Select the runnable file (HTML) and the SAPUI5 version to be used for this run configuration.
A configuration tree appears in the RUN CONFIGURATIONS view containing the run configurations that
were created for the runnable objects.
5. When running an SAP Fiori app locally, you can select if you want to run it from the build folder or from the
source folder.
6. Click the gray arrow to display an object's bindable services.
For information, see .
7. Click (Bind) to bind the desired dependency. To unbind a dependency from the object, click
(Unbind).
A list of all available dependencies is displayed:
○ Service dependencies are loaded from the logged on space in Cloud Foundry.
○ Data sources are loaded from destination configuration of the SAP Business Application Studio
account.
8. From the command palette, select the desired dependency to be assigned.
After the dependency is bound successfully, the icon for the bindable service type turns green ( ).
 Note
You can create multiple run configurations, each configuration pointing to a different data source.

9. Right-click the runnable object and click Configure Environment to open the environment (.env) file to
view the binding configuration.
10. Click (Run Module) to run the project.

The Debug Console opens.
11. A notification prompting you to expose and open the port (if it was not previously exposed), or to open the
service in a new tab is displayed. Click the relevant action to view the service in a new tab. See Managing
Ports [page 62].
12. Right-click a relevant run configuration to do the following (optional):
○ Configure Environment - Open the environment file to view the binding configuration.
○ Rename - Provide a new name for the selected run configuration.
○ Show in File - Open the JSON file containing the set of configuration properties, with the name
highlighted.
○ Delete - Delete the set of configuration properties from the JSON file.
 Note
Any manual change performed to the JSON files, is reflected on the configuration tree.
3.5.5.2 Creating Run Configurations for Java Modules
Create new run configurations to run a Java module for a multitarget application.
Run a Java module on the local Apache Tomcat server and allow binding the module's required resources to
specific Cloud Foundry services.
Prerequisites
● Your project must include an mta.yaml file that points to the Java module.
● The Java module's pom.xml file must include the following definition: packagingType= war.
Add a new configuration
1. Open the Run Configurations view.

2. Click + (Create Configuration).
3. Select the Java module as the runnable object.

A new configuration is added to your launch.json file.
 Note
Any manual change performed to the launch.json file is reflected in the configuration tree.

Bind dependencies
In the Run Configurations view, you can see the resources that are defined in the MTA descriptor. You can bind
or unbind these resources to a specific Cloud Foundry service instance.
 Note
The following Cloud Foundry service types are supported for binding:
● hana ( managed-hana is not supported)

○ PSA-based SAP HANA
○ HaaS (if configured as "Available for all IPs")
● xsuaa
● destination
● connectivity
● auditlog
● application-logs
To bind the resource:

2. Select the desired configuration.
3. Select the desired resource.
4. Click (bind).
If not already logged in, you are prompted to log in to Cloud Foundry.
A list of all available services that match your resource type are displayed in the command palette.
5. Select the desired service.
The resource is bound to the service.
This updates the resource's configuration files. See the Advanced Options section below to see the changes
mande to the configuration files.
If you are binding to an SAP HANA service, a new connection called '<my_service_instance name>' is
added to the SQLTools view where your tables and data are displayed.
Unbinding the resource removes all of the changes made to the configuration files.
To unbind the resource:

3. Select the desired resource.
4. Click (unbind).

Run a configuration
1. If you bound your service to a service that requires Chisel to run:

1. From the command palette, choose Task Run Task .
2. Select openChiselTunnelFor-<service name>.
 Note
If Chisel is already running in the same port and space, skip this step.
2. Select the desired run configuration.

3. Click (Run) to run the project.
Prelaunch and dependent tasks are run.
Ports [page 62].
5. If you need to stop a configuration that is already running, you can do so from the Debug view.
 Note
For more information about the tasks triggered by the run configuration, see the Advanced Options section
below.
Stopping a configuration from the Debug view does not stop any running tasks.
Edit a Run configuration
1. Right-click a run relevant configuration to do the following:

highlighted.
Delete a Run configuration
1. Right-click a run relevant configuration and choose Delete.
 Note
If you delete the launch configuration, it is removed from the launch.json file but the tasks remain.

Advanced options
In addition to the launch.json file that is created as part of the new configuration, the following files are
added or updated when creating a run configuration:
● Environment configuration file

A new environment file is created. After the resource is bound to a service, the file is populated with all the
environment variables required to connect to Cloud Foundry.
The environment configuration file is referenced from your Launch configuration.
● New tasks in the tasks.json file

The following tasks are added to the tasks.json file:
○ A technical generic task. This is the configuration's prelaunch task.
This task enables you to define additional tasks to run before starting the configuration (using the
dependsOn property).
○ A task that triggers the Apache Tomcat server running with the context of the application resources.
○ A build task that triggers the mvn clean install command.
● Tomcat runtime configuration directory
When you create a new configuration, a new Tomcat runtime configuration directory is created
containing the following configuration files:
○ ○ ROOT.xml (user/.tomcat/<configuration_name>/Catalina/localhost)
For example, /home/user/.tomcat/bookshop-srv-1/conf/Catalina/localhost
○ server.xml (user/.tomcat/<configuration_name>/conf)
For example, /home/user/.tomcat/bookshop-srv-1/conf
 Note
By default, Tomcat runs on port 8080. If you want to run multiple configurations at the same time,
you need to configure a different port for the additional Tomcat in the server.xml file. In addition,
you'll need to change the default ports 8009 and 8005 defined in this file to other ports to avoid
collision.

You also need to define a debug port (that is not the default 8000), both in the 'run-tomcat'
task in the tasks.json file, and in the matching launch configuration in the launch.json file,
which are all associated with the same run configuration.
You can modify the content of this directory to configure Tomcat as desired for this run configuration. For
example, you can add libraries to be used at runtime or change ports. For more information, see Apache
Tomcat .
Binding Process
Not all of the services that you want to bind to are publicly exposed. Therefore, we must use a secure tunnel to
access them from Cloud Foundry.
When binding to one of these services, we use chisel to open a secure channel to your Cloud Foundry space.
A new task is created within the binding step to run chisel. Run this task before running the configuration.
The environment configuration file is updated with the chisel and the selected service parameters.
The Tomcat configuration files are updated according to the chosen service.
3.5.5.3 Creating Run Configurations for CAP Java

Applications
Prerequisites
● Your project was created in an SAP Cloud Business Application dev space. See Managing Your Dev Spaces
[page 23].
● Your project is type CAP. See .
● Your project must include the pom.xml file in your root folder.
4. Click (Run) to run the project.
The Debug Console Opens.
5. Click Open in New Tab to view the UI in a new tab.
6. Right-click on a run relevant configuration to do the following:

highlighted.
 Note
Any manual change performed to the JSON files, is reflected on the configuration tree.
3.5.5.4 Creating Run Configurations for CAP Node

Applications
Prerequisites
● Your project was created in an SAP Cloud Business Application dev space. See Managing Your Dev Spaces
[page 23].
● Your project is type CAP. See .
● Your project must include the package.json file in your root folder.
● Your project does not include a pom.xml file in any folder.
Add a new configuration
A new configuration is added to your launch.json file.
 Note
In addition to the launch.json file that is created as part of the new configuration, an environment file is
added when creating a run configuration.
The environment configuration file is referenced from your Launch configuration.

Bind dependencies
In the Run Configurations view, you can see the available dependencies as defined in the package.json file.
You can bind or unbind these dependencies to a specific Cloud Foundry service instance or to your local
database.
 Note
The following Cloud Foundry service types are supported for binding:
● hana ( managed-hana is not supported)

○ PSA-based SAP HANA
○ HaaS (if configured as "Available for all IPs")
○ SAP HANA Cloud (if configured as "Available for all IPs")
● xsuaa
● auditlog
● application-logs
You can also bind directly to a destination.
To bind the dependency to a local database:

3. Select the desired dependency.
4. Click (bind). The database is now bound to a local database file.
 Note
○ If you are binding to an SQLite service, a new connection is added to the SQLTools view where your
tables and data are displayed.
○ Clicking Bind creates a Deploy task (or triggers it if it already exists). You can redeploy the database
at a later stage by running this task again.
To bind the dependency to an SAP HANA database:

4. Click (bind). The database is now bound to an SAP HANA database.
 Note
Clicking Bind creates a Deploy task. Depending on your SAP HANA version, you may be promted to
deploy. You can deploy manually by running the Deploy task.

 Note
If you are binding to an SAP HANA service, a new connection called '<my_service_instance name>' is
added to the SQLTools view where your tables and data are displayed.
To bind the dependency to a Cloud Foundry service:

4. Click (bind).
A list of all available services that match your dependency type are displayed in the command palette.
The dependency is bound to the service.
 Note
● After the dependency is bound to a service, the environment file is populated with all the environment
variables required to connect to Cloud Foundry.
To unbind the resource:

4. Click (unbind).
Bind and mock an external OData service
To bind the dependency to an external OData service using a destination:

3. Select a dependency of type OData.
4. Click (bind).
A list of all available destinations from your subaccount are displayed in the command palette.
5. Select the desired destination.
The dependency is bound to the destination.
To mock all OData services that are not bound to a destination:
1. Turn on the property to mock external OData services.

All dependencies of type OData that are not bound to a destination appear in the Run Configuration tree
marked as mocked.

Run a configuration
1. If you bound your service to a service that requires Chisel to run:

1. From the command palette, choose Task Run Task .
2. Select openChiselTunnelFor-<service name>.
 Note
If Chisel is already running in the same port and space, skip this step.
2. Select the desired run configuration.

3. Click (Run) to run the application.
Ports [page 62].
5. If you need to stop a configuration that is already running, you can do so from the Debug view.
 Note
Stopping a configuration from the Debug view does not stop any running tasks.
Edit a Run configuration
1. Right-click a run relevant configuration to do the following:

highlighted.
Delete a Run configuration
1. Right-click a run relevant configuration and choose Delete.
 Note
If you delete the launch configuration, it is removed from the launch.json file but the tasks remain.

3.5.6 MTA Tools
The MTA Tools allow you to perform operations such as build, deploy, and validation on multitarget
applications.
The MTA Tools are provided as an extension to SAP Business Application Studio and contains the following:
Cloud Foundry CLI
The Cloud Foundry Command Line Interface provides commands to deploy and manage CF services and
applications.
For more information, see Using the Cloud Foundry Command Line Interface .
Cloud MTA Build Tool
The Cloud MTA Build Tool is a standalone command-line tool that builds a deployment-ready multitarget
application (MTA) archive .mtar file from the artifacts of an MTA project according to the project’s MTA
development descriptor (mta.yaml file), or from the module build artifacts according to the MTA deployment
descriptor (mtad.yaml file).
For more information, see the Cloud MTA Build Tool user guide.
Cloud Foundry CLI MTA Plugin
A CLI plugin for Multitarget Application (MTA) operations in Cloud Foundry.
For more information, see the documentation .
Cloud Foundry Targets Plugin
This plugin facilitates the use of multiple API targets with the Cloud Foundry CLI.
Cloud Foundry CLI Copy Env Plugin
A Cloud Foundry CLI plugin to export application VCAP_SERVICES and VCAP_APPLICATION onto the local
machine.

generator-basic-multitarget-application
The generator-basic-multitarget-application is a Yeoman generator for creating a basic (empty)

multitarget application.
cf-cli-service-info-plugin
The cf-cli-service-info-plugin is a Cloud Foundry plugin which enables the following:
● Provides service key details.

● Provides service credentials.
● Calculates a VCAP_SERVICES json, compatible with how Cloud Foundry binds services to apps and
persists to file.
Chisel
Chisel is a fast TCP tunnel, transported over HTTP, secured via SSH.
3.5.7 Deploy Tool
This tool simplifies the task of deploying SAP applications based on different technology stacks, dependencies,
and targets.
The deploy tool allows you to do the following:
● Allows you to deploy any type of SAP business application with a single click.
● Allows you to create different deploy configurations for an application (different targets, different tasks).
● Allows you to define dependent tasks (such as build and running tests) to run pre\post deployment.
● Offers quick access for performing frequent deployment tasks.

3.6 Managing Ports
If you want to access an application that is running in your dev space from an external source (for example a
browser or REST client), you must first expose the port that is listening to the application.
Exposing Ports
When running an application that listens to a port, SAP Business Application Studio displays a notification
prompting you to expose and open the a port.
1. Click Expose and Open.

The port is exposed and you can preview the service in a new tab of the browser.
If you missed the notification you can do this manually from the command palette by entering the Ports:
Expose command.
2. Enter a name for the port.
Unexposing Ports
If you want to remove the external access, enter the Ports: Unexpose command in the command palette.
This will remove the internet access to applications running on the respective dev space.
Previewing Ports
1. Enter the Ports: Preview command in the command palette.

A list of all the exposed applications is displayed.
2. Click on the relevant application.
The exposed application opens in a new tab.
Renaming Ports
1. Enter the Ports: Rename command in the command palette.

2. Select the desired port.
3. Provide a new name for the port when prompted.
 Note
You can have a maximum of 5 ports exposed at a time.
3.7 Accessing On Premise Systems
You can access on premise systems using a built-in Web Proxy.
Your Dev Space includes a built-in Web Proxy (http://localhost:8887) that allows you access to on
premise systems. It is already configured with the HTTP_PROXY and the HTTPS_PROXY environment
variables.
The proxy requires destination configuration to your on-premise system from your Cloud Foundry Subaccount.

Defining On Premise Systems for the Web Proxy
1. Go to SAP Cloud Platform cockpit in the Cloud Foundry environment in the subaccount which is
subscribed to SAP Business Application Studio.
2. Create a destination of type HTTP that points to your system. For more information, see HTTP
Destinations.
HTTP requests including the host and port provided with this destination URL made from your dev space
using the proxy, will be transferred through this destination.
3. Add a new property with WebIDEEnabled as the name and true as the value.
4. To define an ABAP catalog data source for SAP Fiori application consumption, add the following properties:
○ HTML5.DynamicDestination as the name and true as the value.
○ WebIDEUsage set to odata_abap.
5. Make sure your system is correctly exposed in your cloud connector. For more information, see Cloud
Connector.
6. In SAP Business Application Studio, open a terminal and execute the following command:
curl http://localhost:8887/reload
This will trigger an immediate update of your on-premise destinations used by the dev space proxy.
Using Git On Premise Repositories
You can work with on premise Git repositories once an appropriate destination has been created in your
subaccount. Make sure to use the exact same host and port as defined in the destination URL property.
For more information, see Connecting to External Systems [page 73].
Using NPM Modules from On Premise Repositories
You can use NPM modules from an on premise NPM repository or an on premise Git repository.
Use standard NPM registry configurations to set the repository URL.
For example:
npm config set @<scope>:registry <URL>
Make sure an appropriate destination has been created in your subaccount and that you are using the exact
same host and port as defined in the destination URL property.

3.8 Building and Deploying Multitarget Applications
Build and deploy multitarget applications to SAP Cloud Foundry.
Building multitarget applications
Prerequisites
● Your dev space must contain a multitarget application.
There are several ways for building multitarget applications in SAP Business Application Studio:
● From the context menu.

1. Right-click on the mta.yaml file.
2. Choose Build MTA.
● From the command palette.
1. Enter MTA.
2. Choose Build MTA.
3. Select the desired mta.yaml file.
 Note
It there is only one mta.yaml available, the build will start automatically.
● From the CLI. See Cloud MTA Build Tool .
The terminal opens showing the output of the build. Once the build is complete, a folder named
mta_archives is added to the project which contains the relevant MTA archive (MTAR file).
Deploying multitarget applications
Prerequisites
● Your dev space must contain a multitarget application.

● You must have permissions to deploy to your Cloud Foundry space.
There are several ways for deploying multitarget applications to SAP Cloud Foundry:
● From the context menu.

1. Right-click on the relevant MTAR file.
2. Choose Deploy MTA Archive.
● From the command palette.
1. Enter MTA.
2. Choose Deploy MTA Archive.
3. Select the desired MTAR file.

 Note
It there is only one MTAR file available, the deployment will start automatically. If you are not
logged into Cloud Foundry, you will need to do this before deployment starts.
● From the CLI. See Deploy Commands .
The terminal opens showing the output of the deploy process.
3.9 Working with a Trial Account
Get a trial account to experience SAP Business Application Studio for free.
Trial accounts are intended for personal exploration, and not for production use or team development. They
allow restricted use of the services. To learn more about the difference between enterprise and trial accounts,
see Enterprise versus Trial Accounts.
 Note
SAP Business Application Studio is available on Trial in the Amazon Web Services (AWS) - Frankfurt and US
East (VA) regions.
If you do not have a subaccount in these regions, you need to create a new subaccount where Provider =
Amazon Web Services (AWS) and Region = Europe (Frankfurt) or Region = US East (VA).
Restrictions
When using a trial account for SAP Business Application Studio, you will have the following restrictions:
● A user can only have up to 2 dev spaces.

● A user can only have 1 dev space in the RUNNING state at a time.
What's New
Some features may be released to the trial account before they are released to the enterprise accounts.
See What's New in SAP Business Application Studio to learn about these features.
3.10 Troubleshooting
Here are some common troubleshooting issues in SAP Business Application Studio.

Git Troubleshooting [page 66]
Steps you can take if you have trouble using Git.
Connectivity Troubleshooting [page 66]

Locate the symptom and follow the recommended analysis and resolution steps for it.
Dev Space Troubleshooting [page 67]

Steps you can take if you have trouble with your dev space.
Contact SAP Support [page 68]

We suggest you report an incident or error through the SAP Support Portal.
3.10.1 Git Troubleshooting
Steps you can take if you have trouble using Git.
The following lists error messages you may receive when using Git, possible causes of the error, and possible
solutions.
Cannot Clone Git On Premise Repository
When trying to clone an on premise repository, the following message is displayed:

fatal: unable to access 'https://user-id@git.wdf.sap.corp/project-name/': Received
HTTP code 502 from proxy after CONNECT
This error indicates that there is no Cloud Connector configured in the account.
You must connect a Cloud Connector. See Git Integration [page 33].
3.10.2 Connectivity Troubleshooting
SAP Business Application Studio takes longer than expected to load
This might be due to a high latency or a network issue.
Solution
● Check that you are connected to the data center closer to your location. See SAP Cloud Platform Regions
and Service Portfolio.
● Make sure you have a stable internet connection.
● Make sure you are using a supported browser. See the Availability section in What is SAP Business
Application Studio [page 4].

When working in FireFox, the table records are not loaded in the SQLTools
view
This is related to an open bug in Firefox.
Solution
1. Open SAP Business Application Studio and go to your dev space.

2. Once the dev space has loaded, right-click on the SAP logo at the top-left corner and select This frame
Show only this frame . A new tab opens.
3. From the new tab's URL, copy the domain value starting from the second subdomain. For example:
URL: subdomain1.subdomain2.subdomain3.sap/path1/path2
Copy only: subdomain2.subdomain3.sap
4. Click the Firefox hamburger and select Options.
5. Search for Cookies and Site Data.
6. Make sure that the Delete cookies and site data when Firefox is closed checkbox is not selected.
7. Click Manage Permissions.
8. In the Address of website field, enter the domain value that was copied earlier.
9. Click Allow.
10. Click Save Changes.
3.10.3 Dev Space Troubleshooting
Steps you can take if you have trouble with your dev space.
You receive a popup error message describing failure of the backup of your
dev space files
This issue may occur when some or all of your dev space content isn’t being backed up.
If you don’t perform the steps in the error message, you will lose some or all of your recent changes.
Solution

Perform the following steps to save your changes:
1. Save your changes in all open SAP Business Application Studio files.
2. If you work with a Git repository, push all your latest changes.
3. Navigate to the Dev Space Manager.
4. Export the project. See Managing Your Dev Spaces [page 23] for instructions.
5. Restart the dev space.
6. Import the project.
○ If the issue is resolved, import the project to add lost changes.
○ If the issue still exist, create a new dev space, then import the project.
 Note
It is recommended to sync, back up, and save your project to a remote Git Repository. You should store all
changes in Git branches.
3.10.4 Contact SAP Support
We suggest you report an incident or error through the SAP Support Portal.
1. Log into the SAP Support Portal

1. Open SAP Support Portal .
2. Choose Report an Incident. The SAP ONE Support Launchpad opens.
3. Perform a search to check whether a similar incident was already reported.
4. Choose Contact SAP Support.
5. In the Customer Number field, enter the number related to your contract.
6. In the S-User ID field, enter your S-user (example: s1234567890). A form opens where you fill in
details about the incident.
2. Provide incident details
1. Select your language, set priority of the incident, and enter a subject. Note that if you set a high or very
high priority, you also have to describe the business impact of the incident.
2. To help the support team process your issue as fast as possible, please provide the following
information in the Description field:
○ Subaccount Organization
○ Subaccount ID
○ Landscape
○ System URL
○ Login user and password to reproduce the incident
○ Reproducible steps
○ The response of the system
○ The expected results
○ Whether the problem occurred after you performed a specific action (and what this action was)
○ Did the problem occur on a system different from the productive one (Development, QA)?
○ Affected users
○ Problem severity. Must the problem be solved urgently? If so, why?

○ All available log and trace files
○ Relevant screenshots
3. From the Installation dropdown list, select HANA CLOUD.
 Note
Select the correct installation type (HANA CLOUD), so that the correct support SLA is applied to
your case.
4. From the System dropdown list, select the affected system.

5. From the Component dropdown list, select the component name of the area that fits best to your issue.
Selecting the correct component directs your issue to the corresponding support team:
Component Description
CA-BAS SAP Business Application Studio issues.
CA-BAS SAP Business Application Studio issues.
CA-BAS-BLD- HTML5 module build - SAP Business Application Studio

HTML5
CA-BAS- BLD-MTA Build MTA applications - SAP Business Application Studio
CA-BAS-DPL- Deploy to ABAP - SAP Business Application Studio

ABAP
CA-BAS- DPL-MTA Deploy MTA applications - SAP Business Application Studio
CA-BAS-RUN- Run HTML5 Module - SAP Business Application Studio

HTML5
CA-BAS-RUN-CFG Run Configurations view - SAP Business Application Studio
CA-BAS-RUN-CAP Run CAP application - SAP Business Application Studio
CA-BAS-TPL-FIORI SAP Fiori project template- SAP Business Application Studio
CA-BAS- TPL-MTA MTA templates -SAP Business Application Studio
CA-BAS-WS-MNG Dev space Manager- SAP Business Application Studio
CA-BAS-WS-CTRL Dev Space Controller- SAP Business Application Studio
CA-BAS-EDT- Fiori development (code assist, validations, i18n) - SAP Business Application Studio
HTML5
CA-BAS-EDT-W5G Layout Editor (WYSIWYG) - SAP Business Application Studio
CA-BAS-EDT-JAVA JAVA tools - SAP Business Application Studio
CA-BAS-EDT-MTA MTA descriptor (mta.yaml) editor
CA-BAS-CNSM Consume SAP Services - SAP Business Application Studio
CA-BAS-BSC Basic Tools(npm,GIT) - SAP Business Application Studio
CA-BAS-CF Cloud Foundary Tools command palette - SAP Business Application Studio
CA-BAS-WIZ Yeoman-UI generator - SAP Business Application Studio

CA-BAS-FLO File system, logging, Operator Clusters - SAP Business Application Studio
CA-BAS-MON Monitoring - SAP Business Application Studio
CA-BAS-AUT Login, roles, authentication, authorizations- SAP Business Application Studio
CA-BAS-WEX Extension management- SAP Business Application Studio
CA-BAS-HAN-DPL HANA Explorer for SAP Business Application Studio
6. The reporter details are filled in automatically, but you can also define additional contacts.
7. When ready, choose Submit to create the incident.
 Note
If you have problems creating and sending an incident, or your ticket is not processed as fast as
you need, contact the 24/7 phone hotlines.

4 REFERABLE CONTENT
Variable Defini
tion (Copy / Template for
Paste Special Template for oXygen Author
Using oXygen Text Mode Mode (Copy / ID of Variable Automatically
Variable ID Editor) (Copy / Paste) Paste) Area Topic Replacable?
APP_STUDIO SAP Business <pname con SAP Business SAP Cloud Plat loioce0163 yes
Application key Application form ce7ae248d8
Studio ref="loioce0163 Studio b9128fbac3
ce7ae248d8b91 1d58c2
28fbac31d58c2
/
APP_STUDIO"/
>

REFERABLE CONTENT PUBLIC 71
5 Administrator Guide for AWS and Azure
Regions
Before you can work in SAP Business Application Studio, the account administrator must subscribe the
subaccount to the SAP Business Application Studio application.
 Note
The content in this section is only relevant for AWS and Azure regions.
5.1 Getting Started
Here's a checklist for setting up your system so you can develop applications using SAP Business Application
Studio.
Step Description Links/Information
Sign up for an SAP Cloud Plat You require an SAP Cloud Platform global account to Getting a Global Account
enable SAP Business Application Studio.
form global account.
Create subaccounts in the SAP When you create a subaccount in the SAP Cloud Create a Subaccount in the
Cloud Platform Cloud Foundry
Platform Cloud Foundry environment, a Cloud Foun Cloud Foundry Environment
environment.
dry organization is automatically created for that [Feature Set A]
Select a region according to the subaccount.
guidelines in the Neo and Cloud
Foundry Regions topic.
Create spaces You can create and delete spaces in a Cloud Foundry Create Spaces
organization using the SAP Cloud Platform cockpit or

the console client (Cloud Foundry command line in
terface).
We recommend at least one space for a development

team working on the same project (that is, one space
per project).
For staging/test and production organizations, one

space is sufficient.

72 PUBLIC Administrator Guide for AWS and Azure Regions
Assign members to your Cloud Enable your developers to work with your SAP Cloud Managing Members
Foundry organizations and Platform Cloud Foundry environments.

spaces
Your developers should be assigned to the space de
veloper role to be able to use the space from SAP
Business Application Studio.
Subscribe to SAP Business You need to subscribe to the SAP Business Subscribe to Multitenant Busi
Application Studio Application Studio. ness Applications in the Cloud
Foundry Environment Using the
Cockpit
Grant user permissions To enable working with SAP Business Application Manage Authorizations [page
Studio, developers need to be assigned the 75]
Business_Application_Studio_Develop
er role.
OPTIONAL: Enable identity pro If you define a custom identity provider for your sub Configure Trust to the SAML
vider (IdP)-based authentica
account in SAP Cloud Platform, be sure to configure Identity Provider
tion for SAP Business
the assertion-based attributes mapping for this IdP.
Application Studio applications
(optional)
5.1.1 Connecting to External Systems
For applications that do not need to run on Cloud Foundry, establish a connection to an external system by
creating one destination for multi-usage.
Context
You can access on premise systems using a built-in Web Proxy. Your dev space includes a built-in Web Proxy
(http://localhost:8887) that allows you access to on-premise systems. It is already configured with the
HTTP_PROXY and the HTTPS_PROXY environment variables. The proxy requires destination configuration to
your on-premise system from your Cloud Foundry Subaccount.
Procedure
1. Open SAP Cloud Platform cockpit in the Cloud Foundry environment and go to the subaccount which is
subscribed to SAP Business Application Studio.
2. Create a destination of type HTTP that points to your system. For more information, see HTTP
Destinations. HTTP requests including the host and port provided with this destination URL made from
your dev space using the proxy, will be transferred through this destination.

Administrator Guide for AWS and Azure Regions PUBLIC 73
3. Add these new properties:
Property Value
WebIDEEnabled true
HTML5.DynamicDestination true
4. Make sure your system is correctly exposed in your Cloud Connector. See Cloud Connector.
If you don't have any Cloud Connector to use, you can choose one of the following options:
○ Setup a Cloud Connector on your local machine/VM by following this tutorial .
○ Use the DLM Cloud Connector.
5. Choose Save.
5.2 Subscribe to SAP Business Application Studio
Prerequisites
● If your global account uses the subscription-based commercial model, then you must have purchased a
SaaS license for SAP Business Application Studio. See Pricing and Packaging . You can also contact us
on SAP Cloud Platform or via an SAP sales representative.
● You have created a subaccount in the Cloud Foundry. See Create a Subaccount in the Cloud Foundry
Environment [Feature Set A].
● You are an administrator of the subaccount.
Procedure
1. Open your global account in the cockpit.

2. Go to your subaccount.
3. In the navigation area, choose Subscriptions.
A list of the applications to which your global account is entitled in the Cloud Foundry environment is
displayed. The Subscribed / Not subscribed text, indicates whether the subscription is active in your
subaccount in the current region.
4. Search for Studio. The SAP Business Application Studio tile is displayed.
5. Click the application name to open its Overview page.
6. Choose Subscribe.
The Go to Application link becomes available once the subscription is activated. Choose the link to launch
the application and obtain its URL.

 Note
To remove a subscribed application, go back to the Overview page of the subscribed application and
then choose Unsubscribe. All data related to the application will be deleted in the respective
subaccount.
5.3 Manage Authorizations
To develop using SAP Business Application Studio or manage data stored by the tool, the relevant role needs to
be assigned.
Developers using SAP Business Application Studio must be assigned to developer roles created by the
Business_Application_Studio_Developer role template.
To allow administrator operations using SAP Application Studio, the relevant users must be assigned to
administrator roles created by the Business_Application_Studio_Administrator role template.
You can use any SAML 2.0 standard compliant identity provider. See Trust and Federation with SAML 2.0
Identity Providers.
Prerequisites
● Your subaccount is subscribed to SAP Business Application Studio. See Subscribe to SAP Business
Application Studio [page 74].
Manage Role Collections
 Note
The Developer and Administrator role collections together with their corresponding templates are created
automatically when you subscribe to SAP Business Application Studio.
You can skip this section and go to the Assigning Permissions section below.
Role collections are user-related authorizations that restrict access to resources and services based on defined
user permissions. They consist of individual roles. The roles are based on role templates. For SAP Business
Application Studio there are 2 role templates available: Developer role and Administrator role.
The Developer role, allows developers to load and develop applications using SAP Business Application Studio.
The Administrator role, allows administrators to manage (export and delete) user data.
Optionally, you can create a different set of roles as follows:
1. In the SAP Cloud Platform cockpit, navigate to your subaccount.

2. From the Navigation area, choose Security Role Collections .
3. Select an existing role collection or choose New Role Collection.
4. If you are creating a new role collection, provide a name for the new role.
5. Select your role collection and choose Add Role.
1. From the Application Identifier dropdown list, select <region<IAAS_#>>-app-studio!
t<generated-uaa-number>.
For example, jp20-app-studio!t333*
2. From the Role Template dropdown list, select Business_Application_Studio_Developer to
create a role collection for developers or Business_Application_Studio_Administrator to
create a role collection for administrators .
3. Save your changes.
Assigning Permissions
1. In the SAP Cloud Platform cockpit, navigate to your subaccount.

2. From the Navigation area, choose Security Trust Configuration .
3. Select the default IdP by clicking on the name attribute. The name might be SAP ID Service or Default
Identity provider.
4. From the Navigation area, choose Role Collection Assignment.
5. Enter the e-mail of the user to whom you want to give permissions.
6. Choose Show Assignments.
7. Choose Assign Role Collection.
8. From the Role Collection dropdown list, select the relevant role collection.
To assign permissions to groups, follow the instructions in the Map Role Collections to User Groups topic.
5.4 Export and Download Personal Data from Specific Users
You can export and download personal data from specific users from your workspace.
1. In your browser, get a list of all workspaces contained in a specific subaccount:
https://<sap-business-application-studio-url>/ws-manager/api/v1/workspace?
all=true
2. Enter your administrator credentials in the login page.

3. From the list provided, identify the dev space you want to export (for example by searching for the
username property).
4. Copy the url property under the runtime section and remove /theia/ from the URL. This URL is the
<runtime-url> parameter used in the request below.
5. Make sure the dev space you want to export is in status Running. If not, wake up the dev space before
exporting the data. See, Restart a Dev Space [page 77]

6. Use the following request to export data:
https://<sap-business-application-studio-url>/login?e=<runtime-url>/
wsmaintain/export
5.5 Restart a Dev Space
To change the state of a dev space to Running perform the following steps:
all=true

3. From the list provided, identify the dev space you want to wake up (for example by searching for the
username property).
4. Copy the id property under the config section . This ID is the <ws-id> parameter used in the request
below.
5. Copy the displayname property under the labels section . This display name is the <display-name>
parameter used in the request below.
6. Open a new tab in the browser and fetch your JWT token by sending the following request:
GET https://<sap-business-application-studio-url>/jwt
7. Copy the JWT value from the response.

8. In the REST API tool, send a PUT HTTP request to the following API:
PUT https://<sap-business-application-studio-url>/ws-manager/api/v1/workspace/
<ws-id>?all=true
Request Header:
X-Approuter-Authorization: Bearer <JWT_Token>
Request Body:
{"id":"<ws-id>", "Suspended":false, "WorkspaceDisplayName":"<display-name>"}
5.6 Delete Personal Data
You can delete personal data stored in your workspace.
 Sample Code
all=true

3. From the list provided, identify the dev space you want to delete (for example by searching for the
username property).
below.
exporting the data. See Restart a Dev Space [page 77].
 Sample Code

8. In the REST API tool, send a DELETE HTTP request to the following API:
 Sample Code
DELETE https://<sap-business-application-studio-url>/ws-manager/api/v1/
workspace/<ws-id>?all=true
Request Header:

6 REFERABLE CONTENT
Variable Defini
28fbac31d58c2
/
APP_STUDIO"/
>

REFERABLE CONTENT PUBLIC 79
7 Administrator Guide for China (Shanghai)
Region
 Note
The content in this section is only relevant for China (Shanghai) region.
Prerequisites
● Install a REST API tool such as Postman.
As an administrator, you can perform the following tasks:
● Subscribe to SAP Business Application Studio [page 81]

● Manage Authorizations [page 82]
● Restart a Dev Space [page 77]
● Delete Personal Data [page 77]
● Export and Download Personal Data from Specific Users [page 76]
7.1 Getting Started in China (Shanghai) Region
Here's a checklist for setting up your system so you can develop applications using SAP Business Application
Studio.
Sign up for an SAP Cloud Plat You require an SAP Cloud Platform global account to Getting a Global Account
enable SAP Business Application Studio.
form global account.
Create subaccounts in the SAP When you create a subaccount in the SAP Cloud Create a Subaccount in the
Cloud Platform Cloud Foundry Cloud Foundry Environment
Platform Cloud Foundry environment, a Cloud Foun
environment. [Feature Set B]
dry organization is automatically created for that
subaccount.

80 PUBLIC Administrator Guide for China (Shanghai) Region
Create spaces You can create and delete spaces in a Cloud Foundry Create Spaces
organization using the SAP Cloud Platform cockpit or

the console client (Cloud Foundry command line in
terface).
We recommend at least one space for a development

team working on the same project (that is, one space
per project).
For staging/test and production organizations, one

space is sufficient.
Assign members to your Cloud Enable your developers to work with your SAP Cloud Members and Roles in the Cloud
Foundry environment
Foundry organizations and Platform Cloud Foundry environments.
spaces
Your developers should be assigned to the space de
veloper role to be able to use the space from SAP
Business Application Studio.
Subscribe to SAP Business You need to subscribe to the SAP Business

Application Studio Application Studio.
Grant user permissions To enable working with SAP Business Application Manage Authorizations [page
82]
Studio, developers need to be assigned the
Business_Application_Studio_Develop
er role.
OPTIONAL: Enable identity pro If you define a custom identity provider for your sub Configure Trust to the SAML
vider (IdP)-based authentica
account in SAP Cloud Platform, be sure to configure Identity Provider
tion for SAP Business
the assertion-based attributes mapping for this IdP.
Application Studio applications
(optional)
7.2 Subscribe to SAP Business Application Studio
Prerequisites
● If your global account uses the subscription-based commercial model, then you must have purchased a
SaaS license for SAP Business Application Studio.
● You have created a subaccount in the Cloud Foundry. See Create a Subaccount in the Cloud Foundry
Environment [Feature Set B].

Administrator Guide for China (Shanghai) Region PUBLIC 81
● You are an administrator of the subaccount.
Procedure
1. Open your global account in the cockpit.

2. Go to your subaccount.
3. In the navigation area, choose Subscriptions.
A list of the applications to which your global account is entitled in the Cloud Foundry environment is
displayed. The Subscribed / Not subscribed text, indicates whether the subscription is active in your
subaccount in the current region.
4. Search for Studio. The SAP Business Application Studio tile is displayed.
5. Click the application name to open its Overview page.
6. Choose Subscribe.
The Go to Application link becomes available once the subscription is activated. Choose the link to launch
the application and obtain its URL.
 Note
To remove a subscribed application, go back to the Overview page of the subscribed application and
then choose Unsubscribe. All data related to the application will be deleted in the respective
subaccount.
7.3 Manage Authorizations
As a global account admin, use the terminal for SAP Cloud Platform to carry out the following tasks in your
global accounts and subaccounts.
Prerequisites
● Make sure you are subscribed to the SAP Business Application Studio application. See Subscribe to SAP
Business Application Studio [page 81].
● Make sure you have performed the following procedures described the Account Administration Using the
CLI topic.
○ Download the client
○ Get Started
○ Login to the subdomain of the subaccount

Manage Role Collections
Role collections are user-related authorizations that restrict access to resources and services based on defined
user permissions. They consist of individual roles. The roles are based on role templates. For SAP Business
Application Studio there are 2 role templates available: Developer role and Administrator role.
1. Create the Business_Application_Studio_Developer role to allow developers to load and develop

applications using SAP Business Application Studio.
1. Create a Developer role collection.
sapcp create security/role-collection "Dev Role Collection Name" --

description "Dev role collection" (optional)
2. List all subscribed applications and fetch the SAP Business Application Studio application ID. This will
provide the "appId" to be used in the request below.
sapcp list security/app
3. Add the Business_Application_Studio_Developer role to the role collection:
sapcp add security/role "Business_Application_Studio_Developer " --of-role-

template "Business_Application_Studio_Developer " --of-app "appId" --to-
role-collection "Dev Role Collection Name"
2. Create the Business_Application_Studio_Administrator role to manage (export and delete) user

data.
1. Create an Administrator role collection.
sapcp create security/role-collection "Admin Role Collection Name" --

description "Admin role collection" (optional)
2. List all subscribed applications and fetch the SAP Business Application Studio application ID. This will
provide the "appId" to be used in the request below.
sapcp list security/app
3. Add the Business_Application_Studio_Administrator role to the role collection:
sapcp add security/role "Business_Application_Studio_Administrator " --of-

role-template "Business_Application_Studio_Administrator " --of-app
"appId" --to-role-collection "Admin Role Collection Name"
Assign Role Collections to Users
You can assign and unassign role collections to and from users.
1. Display a list of all users.
sapcp list security/user
2. Assign a role collection to a user.
sapcp assign security/role-collection "<Dev or Admin> Role Collection Name" --

to-user "user_name" --of-idp "ldap" (default "ldap")

3. Verify the role collection is assigned to the user.
sapcp get security/user "user_name"
 Note
You can unassign a user from a role collection.
7.4 Export and Download Personal Data from Specific Users
You can export and download personal data from specific users from your workspace.
all=true

3. From the list provided, identify the dev space you want to export (for example by searching for the
username property).
4. Copy the url property under the runtime section and remove /theia/ from the URL. This URL is the
<runtime-url> parameter used in the request below.
exporting the data. See, Restart a Dev Space [page 77]
6. Use the following request to export data:
https://<sap-business-application-studio-url>/login?e=<runtime-url>/
wsmaintain/export
7.5 Restart a Dev Space
To change the state of a dev space to Running perform the following steps:
all=true

3. From the list provided, identify the dev space you want to wake up (for example by searching for the
username property).
below.

5. Copy the displayname property under the labels section . This display name is the <display-name>
parameter used in the request below.

8. In the REST API tool, send a PUT HTTP request to the following API:
PUT https://<sap-business-application-studio-url>/ws-manager/api/v1/workspace/
<ws-id>?all=true
Request Header:
Request Body:
{"id":"<ws-id>", "Suspended":false, "WorkspaceDisplayName":"<display-name>"}
7.6 Delete Personal Data
You can delete personal data stored in your workspace.
 Sample Code
all=true

3. From the list provided, identify the dev space you want to delete (for example by searching for the
username property).
below.
exporting the data. See Restart a Dev Space [page 77].
 Sample Code

8. In the REST API tool, send a DELETE HTTP request to the following API:
 Sample Code
DELETE https://<sap-business-application-studio-url>/ws-manager/api/v1/
workspace/<ws-id>?all=true
Request Header:

8 REFERABLE CONTENT
Variable Defini
28fbac31d58c2
/
APP_STUDIO"/
>

86 PUBLIC REFERABLE CONTENT
9 Security Guide
This guide contains the security elements for SAP Business Application Studio.
It includes infomration on the following:
● Architectural Overview [page 87]

● Standards and Best Practices [page 88]
9.1 Architectural Overview
SAP Business Application Studio is part of SAP Cloud Platform and the SAP Multi-cloud offering (AWS, Azure,
Alibaba…).
Developers (end users) use a web browser to access their own dev space, personal, restricted, and tailored.
The dev space is a Developer Virtual Appliance which includes everything a developer requires: development
environment, technology stacks, security and connectivity instruments, developed source code, and
applications.
SAP Business Application Studio is based on the SAP Cloud Foundry Business Application Pattern to provide
Multi-tenant Software-as-a-Service (SaaS).
The Identity and Access Management (IAM) is based on SAP Cloud Foundry Authorization and Trust
Management. Once the developers pass the authorization process, they are granted access with appropriate
scopes to the dev space.

Security Guide PUBLIC 87
The developers can access different services (outside of SAP Cloud Platform), from the dev space based on the
SAP Cloud Foundry destination they created. The SAP Cloud Connector is used, in addition, to provide a
secured access to the on-premise landscape.
Related Information
SAP Cloud Foundry Business Application Pattern

Authorization and Trust Management
SAP Cloud Foundry destinations
SAP Cloud Connector
Manage Authorizations from CLI
Manage Authorizations from Cloud Platform cockpit
Connecting to External Systems [page 73]
9.2 Standards and Best Practices
SAP Business Application Studio implements security standards and best practices to guarantee secured
solution.
For example:
● Enforce authentication and authorization

● Encrypt communication
● Prevent untrusted input
● Audit
9.3 Data Protection and Privacy

88 PUBLIC Security Guide
Important Disclaimers and Legal Information
Hyperlinks
Some links are classified by an icon and/or a mouseover text. These links provide additional information.
About the icons:
● Links with the icon : You are entering a Web site that is not hosted by SAP. By using such links, you agree (unless expressly stated otherwise in your
agreements with SAP) to this:
● The content of the linked-to site is not SAP documentation. You may not infer any product claims against SAP based on this information.
● SAP does not agree or disagree with the content on the linked-to site, nor does SAP warrant the availability and correctness. SAP shall not be liable for any
damages caused by the use of such content unless damages have been caused by SAP's gross negligence or willful misconduct.
● Links with the icon : You are leaving the documentation for that particular SAP product or service and are entering a SAP-hosted Web site. By using such
links, you agree that (unless expressly stated otherwise in your agreements with SAP) you may not infer any product claims against SAP based on this
information.
Videos Hosted on External Platforms

Some videos may point to third-party video hosting platforms. SAP cannot guarantee the future availability of videos stored on these platforms. Furthermore, any
advertisements or other content hosted on these platforms (for example, suggested videos or by navigating to other videos hosted on the same site), are not within
the control or responsibility of SAP.
Beta and Other Experimental Features

Experimental features are not part of the officially delivered scope that SAP guarantees for future releases. This means that experimental features may be changed by
SAP at any time for any reason without notice. Experimental features are not for productive use. You may not demonstrate, test, examine, evaluate or otherwise use
the experimental features in a live operating environment or with data that has not been sufficiently backed up.
The purpose of experimental features is to get feedback early on, allowing customers and partners to influence the future product accordingly. By providing your
feedback (e.g. in the SAP Community), you accept that intellectual property rights of the contributions or derivative works shall remain the exclusive property of SAP.
Example Code
Any software coding and/or code snippets are examples. They are not for productive use. The example code is only intended to better explain and visualize the syntax
and phrasing rules. SAP does not warrant the correctness and completeness of the example code. SAP shall not be liable for errors or damages caused by the use of
example code unless damages have been caused by SAP's gross negligence or willful misconduct.
Gender-Related Language
We try not to use gender-specific word forms and formulations. As appropriate for context and readability, SAP may use masculine word forms to refer to all genders.

Important Disclaimers and Legal Information PUBLIC 89
www.sap.com/contactsap
© 2020 SAP SE or an SAP affiliate company. All rights reserved.
No part of this publication may be reproduced or transmitted in any form

or for any purpose without the express permission of SAP SE or an SAP
affiliate company. The information contained herein may be changed
without prior notice.
Some software products marketed by SAP SE and its distributors

contain proprietary software components of other software vendors.
National product specifications may vary.
These materials are provided by SAP SE or an SAP affiliate company for

informational purposes only, without representation or warranty of any
kind, and SAP or its affiliated companies shall not be liable for errors or
omissions with respect to the materials. The only warranties for SAP or
SAP affiliate company products and services are those that are set forth
in the express warranty statements accompanying such products and
services, if any. Nothing herein should be construed as constituting an
additional warranty.
SAP and other SAP products and services mentioned herein as well as
their respective logos are trademarks or registered trademarks of SAP
SE (or an SAP affiliate company) in Germany and other countries. All
other product and service names mentioned are the trademarks of their
respective companies.
Please see https://www.sap.com/about/legal/trademark.html for

additional trademark information and notices.
THE BEST RUN

SAP Business Application Studio

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

SAP Business Application Studio

Uploaded by

Copyright:

Available Formats

© 2020 SAP SE or an SAP affiliate company. All rights reserved.