BTP

• 9 usecases:

  • reduce complexity: post-merger integration (merger = Zusammenschluss), rationalisation of application (app. = hoe endusers get their tasks done), integration architectures

  • ensure compliance: technology risk management, data compliance, governance standarts

  • enabling growth: from monoliths (kommt aus einem Guss) to microservices, cloud transformation, IoT architecture

• 2 types of architects:

  • enterprise: focus = strategic, not technical; aligning IT infrastructure with buiness subjects, make project plans: analyze company and business environment characteristics and define all IT requirements (focus: strategic: 10, technik: 2)

  • solution architect: develops and implements solutions that fulfill business requirements, ensure that the solutions are technically feasible and economically viable (focus: strategic: 5, technik: 5)

• frameworks: Zachmann, TOGAF, FEAF, Gartners

1. Extension Architecture Guide: finds the right extension technologie (clean core!) and Methodological support (systematische Vorgehensweise) -> WHERE TO DEVELOP STH, extensions should be in a Modul

   • right technologie: f.e. SAP BTP, in-App extension or classic ABAP

   • recommendation (Empfehlung) for architecture

   • recom. for best building blocks for presentation tier and back ends (einsetzen im Front- oder Backend)

   • On-Stack (extension in S/4HANA) or Side-by-Side (BTP)

2. Integration Architecture Guide: find right technologie, how to connect Cloud and on-prem in a clean way, modernize integrationstrategy without lossing overview

   1. overview all SAP integration technologys

   2. 3 integration areas: process integration (E2E), data I., analytics I

   3. Further development of existing architectures (Weiterentwicklung)

3. SAP BTP Developer’s Guide: develop and implement business applications

   1. Blueprints (vorgefertigte Architekturvorlagen) with core SAP BTP services

   2. automated SAP BTP Infrastructure setup

   3. Standard technologies for smooth integrations

1. SAP Integration Solution Advisory Methodology: more than technical integration: holistic (=ganzheitlich) integration

   1. integration strategies

   2. Capability Models and cases to guide decisions (“Fähigkeitsmodelle, Praxisbeispiele, Bewertungsmethoden -> fundierte AuswahlIntegrationslösungen)

   3. cloud and on-premise integration

2. SAP Application Extension Methodology: independently appoach (=Ansatz) for extension strategy

   1. Guidelines for extending SAP applications

   2. Support of scalability and aligns with business needs

   3. Efficient use of SAP tools (how to use?)

3. SAP Data and Analytics Advisory Methodology: design and validation of solution architectures, comes with:

   1. data domain reference model

   2. data and anatytics capability model (Daten- und Analysefunktionen)

   3. use case patterns (Muster für anwedungsfälle)

   4. reference architectures

   5. 
      

SAP Discovery Center:

= Service Catalogs (tools, other services, APIs, applications for helping integrate and extend solution)

= mission catalog with ready-to-run projects

= learning materials, step-by-step guidance

= with coaches

Benefits: self-service, accelerates (=beschleunigen) innovation, on-demand support

Business Accelerator Hub (Accelerate = Beschleunigen): platform that provides preconfigured business processes, integrations and extensions, f.e. APIs, integration scenarios with third-party systems, SAP Build = process automation (test and business processes

SAP BTP Reference Architectures: template solutions for architecture in a particular technology domain, such as integration, extensions, hyperscaler integration, or data and analytics

1. account model =

   • global accounts —> defintion: which regions are allowed?

   • directories (can be used like structure foldings, 5 levels possible, organizes subaccounts), can be labeled (=free text)

   • subaccounts —> independent to each other, run in a region (= where hosted?), require a uique subdomain (used in URL access) (and a global account or directory)

   • environments —> they are purhased (and billed), they are distributed as assignment to subaccounts with a quota for actual consumption (Kontingent für den tatsächlichen Verbrauch)

2. SAP BTP cockpit: operations, including administration and development

3. Services, before usage

   1. select the right ervice plan for your scenario and (depending on service:)

   2. subscribe to it OR create a instance for service

      • Subscription = standalone, runs without need of sth else, comes mostly with an app

      • Instance = set of capabilities (Funktionen), get consumed via API’s and/or bindings, sometimes a additional environment (f.e. Cloud Foundry or Kyma) is required (if a graphical app is used -> ad environm. is required because service instances don’t have their own runtime build in)

1. responsibility customer (develops and manages applications and data:

   1. Account Management

   2. Application Evolution and Change Mangement

   3. Application Creation

   4. SAP HANA Service Management (this is also SAPs responsibility)

      —> their data, acces management, apps and their security

2. responsibility SAP

   manages platform,

   -> infratructure (incl. physical security of data centers, not technical), network controls, operational security incl. monitoring

A. Set up account model

1. creation of global accounts, directories and subaccounts

2. assignment of entitlements

3. assignment of authorizations

4. configuration of environments and services

B1. types of users :

• platform users (administrators, operators = DevOps)

• business users (application users or extensions)

B2. subaccount or environment

B3. from low to high level: Subaccount administrator, directory admin, global admin (Cloud Foundry: Space member, Org member (CF member does not exist)

B4. autorization via role collection assignment to user (stand alone role assignment not possible); static in BTP or federed (förderiert) = via Identity Provider (f.e. Azure AD) assigned: role collections are assigned to groups (coming from ID-Provider, groups have mebers f.e. group Purchasing) = federation, ID-Provider hosts users

B5. role collections are managed on every leel seperately

B6. yes, f.e. global account administrator and global account viewer

1. SAP Cloud Identity Services consist a set of services within BTP for seamless identity and access management across multiple systems

1. for connection/integration of side-by-side extensions/custom development pojects to capabilities or data from internet or on-prem system landscape

2. services for connectivity

   1. destination service: provides access to resources (access and opr. save technical information) from the internet or to resources in on-prem landscape -> applications call a destination instead of a direct URL

   2. connectivity service: provides a connectivity proxy (=Vermittler, “reist kein Loch in Firewall von on-prem) -> connection from subaccounts to SAP on-prem via encypted tunnel = bidirectional

3. 
   

1. main options -> all public cloud excluded classic extensibility:

   1. on-stack (in S/4HANA):

      • Key-User Extensibility (“In-App_Erweiterung): directly in SAP Fiori UI, Key user can extens fields, forms and simple logics, no developer knowlege required, uses ABAP Cloud Environment

      • Developer Extensibility (RAP): complex extensions within SAP/4HANA by professional developer, safe for upgrades, uses ABAP Cloud with full developer access in Cloud

      • Classic Extensibility (only private cloud/on prem): classic ABAP development, not safe for upgrades

   2. side-by-side (in SAP BTP on platforms, not in S/4HANA)

      • SAP BTP, ABAP environment: extensions on BTP in own ABAP system, communication with S/4 via API, safe for upgrades because disconnected from SAP-core (=PC pro code)

      • SAP BTP Cloud Foundy and Kyma runtime: there run developments in java, Node.js or other languages, uses SAP Cloud SDK (Software Development Kit) for connection to SAP systems = for new applications like machine learing, WebApps etc. (PC)

      • (low-code/no-code appoach (LCNC)

   
   

• extensions ust be seperated from standart software and only use released APIs

• core = processes, extensions, data, integrations, operations

• best practices, methodogies and tools exists -> clean = if they are used

• rules:

  1. fit to standart -> use sandart processes

  2. use (=utilize) new enhancement options

  3. eliminate extensions that are redundant

1. tools

   1. SAP Fiori (used from UI5) -> Standart

      • SAP UI5 = for creation off Cloud Application = technical base(framework

      • SAP Fiori = used as user interface = designsystem/frontendlogic (how does Application looks and how to use them)/design concept

      • Fiori Elements = templates for layout, list report (Listing several items in a tabular format with a section at the top for defining and applying filters), worklist, object page, overview page, analytical list page

   2. CAP

      • building blocks =

        • integrated development environment (where code is written)

        • core data services (CDS) for modelling -> data models are described, f.e. which info is saved in which application -> CDS enable the simplification and harmonization of a company's business data models

        • Service SDKs for Node.js and Java -> help providing services, f.e. APIs, authentifications (= software development kip that is delivered with CAP)

      • what is it?

        • delivers ready-made solutions and best practices

        • convention over configuration -> much is preconfigured

        • supports synchon and asynchrone interfaces (direct and delayed communication between systems)

      • tools:

        • SAP Business Application Studio (should be used)

        • Sap Build Code (=LCNC?)

        • optional open source tools like Visual Studio Code

      • CAP Applications run at BTP: Cloud Foundy environment or Kyma runtime

   3. RAP = for developing Apps and interfaces (APIs)Communication App with SAP

      • artfacts and their dependencies:

        1. business objects (BO): defeinition, which data are used (customer, order,…) and how thexy are used (reading, changing,…)

        2. BO projections: a “projection” (=Ausschnitt) of a BO, adapted for a specific purpose or user group

        3. service definition: defines the scope of a business service

        4. service binding: defines communicaton protocol (f.e. OData V2 or V4) and type of service that is offered to enduser (f.e. UI-Services or webservice)

        5. Fiori UI

        6. Web API = offers public interface for accessing the OData service by any OData client independent of a particular UI

2. OData = protocoll based on REST = can read, write, change or delete data, enables standardized access to data via APIs

1. no code/low code

   • SAP Build Apps: Create Apps

   • SAP Build process automation: automate processes and tasks with drag-and-drop and AI capabilities (=Fähigkeiten) (xxx)

   • SAP Build work zone: design engaging business sites (=Webseiten?, site = Platz) nto get work done quickly across enterprise applications

2. pro code

   • SAP BTP ABAP Enviornment

   • SAP Build code

   • SAP CAB

1. CAB: Java or JavaScript

   RAP: ABAP

2. CAB: SAP BTP (Business Technology Platform, Cloud Foundry)

   RAP: SAP S/4HANA (Cloud/On-Prem), BTP ABAP Environment

3. CAB: extension of existing ABAP-Systems

   RAP: developemnt of new Cloud Apps (side-by-side)

4. CAB: SAP Fiori (or other frameworks)

   RAP: SAP Fiori (mit SAPUI5 und Fiori Elements)

5. CAB: SAP BTP Cloud Foundry or Kyma

   RAP: on a ABAP stack (f.e. S/4HANA, BTP)

1. Android, iOS or Web

2. central platform on BTP to manage, configure and develop Apps

3. MDK = Mobile Development Kit = construction kit (Baukasten) to easy build Apps with configuration

4. mobile cards = “mini Apps” / digital business cards (Visitenkarte) where infos are shown (f.e. tickets, infos, tasks)

5. development kits for native Apps for Apple/Android device (Gerät) with functions like Fingerprint or location

6. functions: app management (control apps throughout their entire lifecycle – from development to use), push notifications, offline functions, security, user reports (how often is app used), updates

7. How to develop an App:

   1. Low-code with MDK

   2. SAP Mobile Cards: for to dos or notifications

   3. native development with iOS/Android SDK = for developers -> building Apps with device technologies like GPS, cam,…)

SAP Build Apps:

1. Web and Mobile Application: create with drag-and-drop, after creation the app can be doployed (=bereitstellen/transportieren) to cloud foundy

2. Application Backend: create data-based back ends on SAP BTP -> allows you to persist (=beibehalten) data and execute application logic. Programming can then be carried out against this back end.

1. build new apps and deploy them (in appropriate(=passendes) system or extend existing apps with SAPUI5 customization project

2. This allows CAP applications to be created almost automatically through Generative AI (Joule). These are then deployed on Cloud Foundry