OpenSAP Gcts1 Week 1 All Slides

Week 1: gCTS Basics and Preparation
Unit 1: Why gCTS?

Why gCTS?
The story
gCTS Basics Leverage Git Tailor gCTS gCTS in

Use gCTS
and Capabilities to Your CI/CD
Basics
Preparation in ABAP Needs Processes
© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

Why gCTS?
The story
gCTS Basics and Preparation

▪ Why gCTS?
▪ gCTS in action
▪ Introduction to the exercises
▪ Introduction to the exercise landscape
▪ Configuration to enable gCTS
▪ Create a repository on GitHub Use gCTS
Leverage Git Tailor gCTS gCTS in
Capabilities to Your CI/CD
Basics
in ABAP Needs Processes

Why gCTS?
CTS – where ABAP comes from
Change and Transport System (CTS) has been an DC

integral part of ABAP development processes since BWD
the beginning TR BWQ BWP
With CTS, you: SAP BW/4HANA landscape

▪ Model system landscapes (e.g. DEV → TEST → PROD)
▪ Transport changes through the landscape
▪ Monitor your transports DC
▪ Can integrate into Change Request Management and S4D
quality gate management (QGM) TR S4Q S4P
→ Safe and controlled
SAP S/4HANA landscape

Why gCTS?
DevOps – where ABAP should go
The developers’ world has changed:

▪ DevOps processes are widely used
▪ Git is used to manage development artifacts
▪ Automation servers (e.g. Jenkins) are used to automate Code Release
DevOps processes
Operate
→ One ‘world of tools’ for many development
Build
languages / environments
Test Feedback
But: How about ABAP?
DevOps Principles (CALMS)

Why gCTS?
DevOps – get ABAP in
It should be possible to add ABAP to the

DevOps world
▪ To share source code on Git
▪ To enable automation of development Code Release
processes via pipelines
Operate
▪ To manage ABAP development similar to what
Build
you do in other languages and environments
→ This is what Git-enabled CTS (gCTS) aims at
Test Feedback

Why gCTS?
DevOps – get ABAP in
It should be possible to add ABAP to the

DevOps world
▪ To share source code on Git
▪ To enable automation of development Code Release
processes via pipelines
Operate
▪ To manage ABAP development similar to what
Build
you do in other languages and environments
→ This is what Git-enabled CTS (gCTS) aims at
Test Feedback

Why gCTS?
The idea
PRD
DEV TST
Development Target
CTS* gCTS
* Change and Transport System
Why gCTS?
Planned use case: feature development and maintenance in parallel
New Feature
Feature
NFD NFQ
Maintenance
Master
MTD MTQ MTP
Maintenance
Production
One branch for feature development
One branch for maintenance
No doubled system landscape needed
Deploy the latest commit of one or the other branch to develop new features or to do maintenance
Why gCTS?
Planned use case: distributed development
Two development teams can Commit changes Merge into master Deploy to production
work on the same object to repository branch, deploy to QA after test
DEVELOPMENT
TEAM A
TEST/INTEGRATION
QUALITY PRODUCTION
LIVE SYSTEM
DEVELOPMENT
TEAM B

Why gCTS?
The story

▪ Why gCTS?
▪ gCTS in action
Basics
What to remember: ▪ gCTS is the option to harmonize non-ABAP processes and tools with ABAP
▪ gCTS is planned as an alternative to CTS (which is still maintained!)
▪ gCTS and CTS can be used in parallel (to start with pilot projects)
Why gCTS?
Further reading
▪ Blog post gCTS is here

▪ gCTS on SAP Help Portal

Thank you.
Contact information:
open@sap.com
Follow all of SAP
www.sap.com/contactsap
© 2021 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.
In particular, SAP SE or its affiliated companies have no obligation to pursue any course of business outlined in this document or
any related presentation, or to develop or release any functionality mentioned therein. This document, or any related presentation,
and SAP SE’s or its affiliated companies’ strategy and possible future developments, products, and/or platforms, directions, and
functionality are all subject to change and may be changed by SAP SE or its affiliated companies at any time for any reason
without notice. The information in this document is not a commitment, promise, or legal obligation to deliver any material, code, or
functionality. All forward-looking statements are subject to various risks and uncertainties that could cause actual results to differ
materially from expectations. Readers are cautioned not to place undue reliance on these forward-looking statements, and they
should not be relied upon in making purchasing decisions.
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.
See www.sap.com/trademark for additional trademark information and notices.
Unit 2: gCTS in Action
gCTS in action
The story

▪ Why gCTS?
▪ gCTS in action
Basics

gCTS in action
Demo
DemoRepo
Main
VSID DEVELOPMENT
DEV TST
TEST
CREATE NEW UPDATE TO LATEST
OBJECTS AND COMMIT COMMIT
gCTS in action
Demo

gCTS in action
gCTS supports Workbench objects
Workbench objects
▪ Use transport layer resulting from vSID
Technical background
▪ All objects that can be part of a Workbench
transport request can make use of gCTS
▪ Objects are added to a commit when a transport
request is released

gCTS in action
gCTS supports Customizing objects
Customizing
▪ Requires SAP S/4HANA 2020
▪ Choose the vSID that you created as
target for the transport request
Technical background
▪ TDAT and VDAT are enabled with SAP S/4HANA
2020
▪ CDAT requires SAP S/4HANA 2020 FPS1 plus
SAP Notes (3016865)

gCTS in action
The story

▪ Why gCTS?
▪ gCTS in action
Basics
What to remember: ▪ Workbench and Customizing objects can be handled via gCTS
▪ The development tools ADT or SE80 and SPRO are the same for gCTS
▪ The gCTS app supports the development processes
Thank you.
open@sap.com
Follow all of SAP

warranty.
Unit 3: Introduction to the Exercises
Introduction to the exercises
The story

▪ Why gCTS?
▪ gCTS in action
▪ Introduction to exercise landscape
▪ Create repository on GitHub Use gCTS
Basics

Exercise overview
DEVELOPMENT
DEVELOPMENT
DEV DEV
Week 1 Week 2 Week 3 Week 4 Week 5

▪ Create ▪ Create credentials ▪ Set repo parameters ▪ Commit a task ▪ Use a CI platform
repositories on ▪ Create local repositories ▪ Merge branches ▪ Register objects with gCTS
GitHub ▪ Add Customizing ▪ Solve conflicts ▪ Use registry when ▪ Set up a pipeline
▪ Add Workbench objects developing
▪ Pull into target system
▪ Explore gCTS app
DEVELOPMENT
DEVELOPMENT
DEVELOPMENT
DEV TST DEV TST
TEST
TEST
Exercise scope – week 1
3
Create
repositories on
YourRepo on GitHub GitHub
Main
1 2
DEVELOPMENT
DEV Run gCTS TST
TEST
enablement
wizard

2 YourRepo on GitHub
Create local Main
repositories
VSID
1
DEVELOPMENT
DEV Create TST
TEST
credentials
6
Explore
3 4 gCTS app 5
Add Add Workbench Pull into target
Customizing objects system

YourRepo on GitHub
Main
1
Set repository
VSID DEVELOPMENT parameters
DEV TST
2
Merge
TEST
branches
3
Solve conflicts

YourRepo on GitHub
Main
1
VSID DEVELOPMENT
Commit a task
DEV TST
2
Register
TEST
objects
3
Use registry
when developing

YourRepo on GitHub
Main
1
Use a CI
VSID platform with
gCTS
2
DEVELOPMENT
DEV TST
Set up a
TEST
pipeline

General remarks
All exercises are demonstrated in the

corresponding units
Additional material available for each week

▪ Provides URLs and access information
▪ Contains detailed exercise description with screenshots

The story

▪ Why gCTS?
▪ gCTS in action
Basics
What to remember: ▪ Exercises will cover the full range from basic to advanced activities
▪ Some steps can only be performed once and are not available as exercises
▪ Look into additional material for exercise descriptions
Thank you.
open@sap.com
Follow all of SAP

warranty.
Unit 4: Introduction to the Exercise Landscape
Introduction to the exercise landscape
The story

▪ Why gCTS?
▪ gCTS in action
Basics

System landscape
YourRepo on GitHub
Main
VSID
DEVELOPMENT
DEV TST
TEST
Tools
ABAP Development Tools (ADT)

or SE80 for Workbench objects ABAP Development Tools
SPRO for Customizing
gCTS app to manage repositories,

work with commits and branches, …
GitHub for remote repositories
Jenkins for pipelines

SAP S/4HANA systems
DEV and TST are SAP S/4HANA 2021 systems
Data needed to connect to them will be shared in

the additional material and in the confirmation mail
when registering for the exercises
The systems are shared between all participants

▪ The objects created in the exercises follow naming
conventions to avoid conflicts
▪ Number of parallel users is limited; if you don’t get
access, please retry later
▪ When you have completed your work, please log out
▪ Please don’t break the systems, activities will be tracked
Systems are backed up daily (just in case…)

Demo

The story

▪ Why gCTS?
▪ gCTS in action
Basics
What to remember: ▪ DEV is development system, TST is test system

▪ gCTS app is the main tool for working with gCTS
▪ Landscape is shared between all participants
Further reading
▪ System information data in additional material

▪ If you registered for the exercises, you should have
received an e-mail containing your access information

Thank you.
open@sap.com
Follow all of SAP

warranty.
Unit 5: Configuration to Enable gCTS
Configuration to enable gCTS
The story

▪ Why gCTS?
▪ gCTS in action
Basics

Which systems do I need?
Git platform
▪ to host your repositories
Git platform
(e.g. GitHub)
ABAP systems
DEV TST PRD
▪ e.g. development, test and
production system
ABAP systems
MUST
optional
CI server
▪ to host your pipelines
CI server
(e.g. Jenkins)

What do I need to install on these systems?
Git platform
▪ (nothing special)
Git platform
(e.g. GitHub)
ABAP systems
▪ SAP S/4HANA 1909 (2020 for
Customizing support) DEV TST PRD
▪ SapMachine Version 11 or
comparable JRE
▪ Some SAP Notes (depending on SP)
ABAP systems
MUST
optional
CI server
▪ (nothing special – you can use
pipeline steps provided in project CI server
“Piper”) (e.g. Jenkins)

What do I have to configure on these systems?
Git platform
▪ Create repository (with initial commit)
Git platform
(e.g. GitHub)
ABAP systems
▪ gCTS Fiori UI
▪ Authorizations DEV TST PRD
▪ Set parameters, initialize systems
▪ Clone repository
▪ Create branches ABAP systems
MUST
optional
CI server
▪ Set up project
▪ Provide credentials CI server
▪ Set up libraries (e.g. Jenkins)
▪ Set hooks in repository

Wizard to support initial setup
▪ Guides through main configuration steps to

enable a system for gCTS
▪ Executes health check at the end
▪ Available starting with SAP S/4HANA 2020
and 1909 SPS03, requires implementation of
SAP Notes in previous SPs for SAP S/4HANA
1909 – check SAP Note 2821718

Health check
▪ Shows information about gCTS configuration,

permissions, …
▪ Can be filtered by level
▪ Available starting with SAP S/4HANA 2020 and
1909 SPS03, requires implementation of SAP Notes
in previous SPs for SAP S/4HANA 1909 – check
SAP Note 2821718

Demo scenario
Assumption:
▪ Java is installed
▪ SAP Fiori enablement is done
▪ Certificates are imported DEV
set Initialize
Demo will show
▪ gCTS enablement wizard
PRODUCTION
▪ Results in health check paths

Demo

The story

▪ Why gCTS?
▪ gCTS in action
Basics
What to remember: ▪ gCTS requires configuration

▪ Java is required on each ABAP system that uses gCTS
▪ Certificates to access Git are required
Further reading
▪ Configuring Git-Enabled Change and Transport System

on SAP Help Portal

Thank you.
open@sap.com
Follow all of SAP

warranty.
Unit 6: Create a Repository on GitHub
Create repository on GitHub
The story

▪ Why gCTS?
▪ gCTS in action
Basics

Create a repository on GitHub
What is Git?
Git is a version control system

▪ Main entity is repositories containing files
▪ Changes to files are stored in commits
▪ Commits allow moving back and forth between versions
▪ Repositories can be worked on locally
▪ Repositories can be private or public
Repositories can consist of several branches

▪ This allows working distributed and locally
▪ Branches can be merged to combine work from several locations
▪ Branches can be used temporarily

Why GitHub?
Why GitHub?
▪ We need a place for the remote repositories
▪ GitHub is currently best supported by gCTS
What we will use

▪ Separate repositories for Customizing and
Workbench
▪ Authentication via token

System landscape
2
1 Add observer job
Create user as
repositories collaborator
YourRepo on GitHub
Main
VSID
DEVELOPMENT
DEV TST
TEST
Week 1
Create Week 2 Week 3 Week 4 Week 5
repositories on
GitHub

Demo

The story

▪ Why gCTS?
▪ gCTS in action
Basics
What to remember: ▪ Git provider is needed for repositories

▪ Token or Basic Authentication can be used

Thank you.
open@sap.com
Follow all of SAP

warranty.

OpenSAP Gcts1 Week 1 All Slides

Uploaded by

Document Information

Original Description:

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

OpenSAP Gcts1 Week 1 All Slides

Uploaded by

Copyright:

Available Formats

Week 1: gCTS Basics and Preparation

Unit 1: Why gCTS?

gCTS Basics Leverage Git Tailor gCTS gCTS in

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

gCTS Basics and Preparation

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 3

Change and Transport System (CTS) has been an DC

With CTS, you: SAP BW/4HANA landscape

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4

The developers’ world has changed:

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5

It should be possible to add ABAP to the

DevOps Principles (CALMS)

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6

It should be possible to add ABAP to the

DevOps Principles (CALMS)

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 7

One branch for feature development

One branch for maintenance

No doubled system landscape needed

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 10

gCTS Basics and Preparation

▪ Blog post gCTS is here

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 12

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

gCTS Basics and Preparation

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6

gCTS Basics and Preparation

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

gCTS Basics and Preparation

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

Week 1 Week 2 Week 3 Week 4 Week 5

DEV Run gCTS TST

Week 1 Week 2 Week 3 Week 4 Week 5

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4

DEV Create TST

Week 1 Week 2 Week 3 Week 4 Week 5

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 5

Week 1 Week 2 Week 3 Week 4 Week 5

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 6

Week 1 Week 2 Week 3 Week 4 Week 5

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 7

Week 1 Week 2 Week 3 Week 4 Week 5

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 8

All exercises are demonstrated in the

Additional material available for each week

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 9

gCTS Basics and Preparation

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

gCTS Basics and Preparation

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 2

ABAP Development Tools (ADT)

SPRO for Customizing

gCTS app to manage repositories,

GitHub for remote repositories

Jenkins for pipelines

© 2021 SAP SE or an SAP affiliate company. All rights reserved. ǀ PUBLIC 4

DEV and TST are SAP S/4HANA 2021 systems

Data needed to connect to them will be shared in

The systems are shared between all participants