week 3: business flexibility unit 1: introduction: why

Week 3: Business Flexibility

Unit 1: Introduction: Why Flexibility?

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

Introduction: Why flexibility?

Need

Kopal

SAP Business ByDesign Expert

I would want to try quick

and small. If everything’s

good, I would invest in

more business

processes

I need that extra

business functionality

to scale my business

faster

My requirement is

similar but not the

same, I need a few

changes

We have these

various formats

where we

collect inputs, is

this possible?

I need to constantly

review certain market

stocks reports to run

it right



Answer

Business Flexibility

Kopal

SAP Business ByDesign Expert

I would want to try quick

and small. If everything’s

good, I would invest in

more business

processes

I need that extra

business functionality

to scale my business

faster

My requirement is

similar but not the

same, I need a few

changes

We have these

various formats

where we

collect inputs, is

this possible?

I need to constantly

review certain market

stocks reports to run

it right


Offering

ExtensibilityBusiness

Configuration

Business

FlexibilityForms

Mashups

Cloud

Applications

Studio

Business Flexibility enables administrators and users to adapt and

extend the SAP Business ByDesign solution as

well as integrating it with external services.


Business flexibility

Thank you.

Contact information:

[email protected]

© 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.

www.sap.com/contactsap

Follow all of SAP

http://www.sap.com/trademark

https://www.sap.com/registration/contact.html

https://plus.google.com/+SAP

https://www.linkedin.com/company/sap

https://www.youtube.com/user/SAP

https://twitter.com/sap

https://www.facebook.com/SAP


Unit 2: Business Configuration


Offering

▪ There is pre-configuration from SAP for the delivered software product (e.g. SAP Business ByDesign) for

the end user to scope-in as per their requirements for a particular application.

▪ Organized as a hierarchy of business areas, packages, topics, and options based on industry best practices

▪ Business Configuration (BC) enables a customer to fine-tune the SAP Business ByDesign (ByD) system

▪ Business Configuration is a universal approach embedded in ByD that empowers prospects, customers,

and partners to rapidly build and continuously adapt and enhance the solution to meet their individual

business requirements throughout the entire lifecycle.

Business Configuration

Introduction

https://sapedia.int.sap/wiki/ByD


Offering

• Speaks business language, enabling you to create your own solution by

making a series of logical decisions, without having to rely on external

consultants or delve into complex system settings.

• Adopts a user-centered approach, giving you the highest possible level of

control to autonomously shape the future of your business – both during

the initial implementation and as changes are made to your solution

throughout the life cycle.

• Records all the decisions you make and stores them in your own unique

solution profile, which is seamlessly carried forward through the life of

your solution.



Offering

▪ A Business Configuration set (BC Set) is a management tool that allows users to record, save and share

customized settings.

▪ In general, BC sets are snapshot of customization settings. They capture the changes done to the

customization settings which we can use as template or customization backup.

▪ BC set is associated to a BAC tree.


Business Configuration sets

▪ There are 3 different BC set types:

− Content Set: Mainly contains Row content which will be used as pre-delivered

content during loading of CW.

− Context Set: Mainly contains Column content, especially with the condition

content, to works as a View of Fine tuning of CW.

− Metadata Set: Mainly contains Node level content ,and also with the condition

content, but unlike Context set, here condition is used as “Prefix

(i.e namespace)” roles. Although they takes different roles, but technically they

share same data model and logical object.

▪ Benefits of BC sets

− Store customization settings backup

− Efficient Change Management

https://wiki.wdf.sap.corp/wiki/display/BC/BCE+-+Context+Set

https://wiki.wdf.sap.corp/wiki/display/BC/BC+Set


Prospects decide on their implementation in a scoping process using a business adaptation catalog

Scoping

▪ Define functional areas or processes to be used

Questions

▪ Define detail options within scoped areas by answering Yes/No question

Activities

▪ Execute mandatory configuration steps

▪ Fine tuning settings

▪ Comprehensive configuration

Define available features

“Adaptation”

Configure details

“Configuration”


Configuration phases


Offering

Solution capabilities are outlined

in the business adaptation

catalog for all applications.

Built-in scoping rules are pre-

delivered to ensure consistent

and logical selections from a

business and technical point of

view.

First implementation project is

used for scoping the desired

solution by selecting the desired

solution capabilities.

De

sig

n tim

e e

nviro

nm

en

t

Ru

n tim

e e

nviro

nm

en

t

Define solution scope

Configuration Workspace with consistent configuration

Fine Tuning

CRM@SAP SAP Service Backbone

Operation

Evaluate/Design

Build

Load Configuration Content

Continuous Change

Change List

Productive ByD

Productiontenant

Go-Live

Deploy

Testtenant

Go-Live Checklist

Data Migration

Sign-of-Life

Testing

Work Item List

Pre

defin

ed c

onte

nt

Scope Selection

Configur ation UI

Representation of ByD

Solution Capabilities

Storage of customer decisions/changes

Customer profile


Process overview


Offering

Once the Activity List scoping has

been done in the Prepare phase, you

then review the project plan, prepare

for data migration, maintain key users,

and prepare the organizational

structure.

Scoping changes are then deployed to

the target system.

Fine-tuning of the solution is done to

ensure all mandatory configuration

activities have been completed before

going live.

Go-Live deploys all the fine-tuning

changes to the target system.


Process overview

De

sig

n tim

e e

nviro

nm

en

t

Ru

n tim

e e

nviro

nm

en

t

Define Solution Scope

Configuration Workspace with consistent configuration

Fine Tuning

CRM@SAP SAP Service Backbone

Operation

Evaluate/Design

Build

Load Configuration Content

Continuous Change

Change List

Productive ByD

Productiontenant

Go-Live

Deploy

Testtenant

Go-Live Checklist

Data Migration

Sign-of-Life

Testing

Work Item ListPre

defin

ed c

onte

nt

Scope Selection

Configuration UI

Representation of ByD

Solution Capabilities

Storage of customer decisions/changes

Customer profile


OfferingBusiness ConfigurationAdditional Information

SAP Business By Design Library

SAP Quick Guide

https://help.sap.com/viewer/2754875d2d2a403f95e58a41a9c7d6de/2008/en-

US/2be6d189722d101492b2a6215aa2c011.html

https://help.sap.com/viewer/2754875d2d2a403f95e58a41a9c7d6de/2008/en-US/2be6d189722d101492b2a6215aa2c011.html

https://help.sap.com/viewer/2754875d2d2a403f95e58a41a9c7d6de/2008/en-US/2be6d189722d101492b2a6215aa2c011.html

Thank you.


[email protected]










warranty.














Follow all of SAP









Unit 3: Extensibility


Offering

▪ Field extensibility enables key users to enable

additional fields delivered by SAP on the UI

▪ Key users can also define custom fields on

the UI and choose to enable them in various

artifacts using the underlying business object

▪ Seamless integration of extension fields into

all related artifacts using it, such as forms,

services, other UIs, queries, and reports

▪ Flexibility to define screen layouts, for

example, show or hide fields and screen

sections, rename fields and sections, change

the order of fields and sections, adapt the

table display, change branding, background,

and company settings

Extensibility

Field extensibility

Company-wide UI model

SAP defined model

Key-user

Flexibility End-users

Test Mode

Runtime Mode

Company incl.

Personalization

Personalization

Gen

erat

ion

Company Staging LayerUnpublished Key-user changes

Company LayerPublished Key-user changes

Partner LayerPartner Add-ons


Offering

▪ A business object node must technically be explicitly prepared to carry client-dependent extension fields.

▪ Therefore, a business object node must be explicitly marked as “Field Extensible” in the MDRS (simple case):

Extensibility

How?


Offering

▪ Technically an instance of the “Custom Field” Object is created in the MDRS:

▪ Custom Field (MDRS: MO MDRS_CUSTOM_FIELD)

▪ The custom field is the technical representation of the extension field created by the customer

▪ It consists of:

− The definition of the field, e.g. field type, label, calculation (if it is a calculated extension field),

code list (if it is a field of type “List”)

− To which BO node(s) it is attached

• Optional information how to calculate

the value of the field

• Information about the appearance of

the field (e.g. on Controller objects)

Extensibility

What?


Offering

Extension Fields to a

Form, a Service Interface, or Enterprise

Search

Extension Fields to a UI

Business Object Node

Extension Fields to Report

Extension Scenarios

Extensibility

Types


Offering

The key user must enter adaptation mode and

open the “Extension Fields” area in the side car:

Some areas of the UI (e.g. “General Information”)

are prepared for field extensibility (see next unit

how this is achieved), which means they have

information on which extensible BO node they are

related to. Thus the side car on the right can show

all extension fields located on the related

extensible BO node.

Pressing “Add Field” above this list allows to add

an extension field.

On “Save”, the corresponding extension field is

created in the ABAP backend and attached to the

BO node.

Extensibility

Process overview


OfferingExtensibilityAdditional Information


Thank you.


[email protected]










warranty.














Follow all of SAP









Unit 4: Forms


▪ Form templates are used to define the content and layout of documents that can be output (generated)

from the system.

▪ SAP provides a form template for all business documents that are system-generated.

▪ For country-specific templates, a country-specific variant in the country’s language and a fallback

language – English – are provided.

▪ For non-country-specific templates, a language variant for all languages is provided.

Print Forms

Read-only portable document format (PDF) documents that are generated from data stored in the system. Print forms can be printed, sent as an e-mail attachment,

or faxed to business partners.

Interactive Forms

Interactive PDF files that can be generated from the system and sent as e-

mail attachments to business partners. The business partners enter data directly into the form and send it back. Data can

then be uploaded into the system.

Forms

Introduction


Offering

▪ In the Form Template Maintenance view, administrators

can create and adapt form templates, as well as

manage form template versions.

▪ You can access this view from the Administrator and/or

Application and User Management work center under

Business Flexibility.

▪ This view displays all form template language and

country variants available in your system. By default,

the variants are grouped by form template.

▪ For each form template variant, only the most recent

published or not-published version is shown.

▪ If a not-published version exists for a template, then

you can view the current published version by selecting

the form template variant and clicking Versions.

▪ When you adapt a form template variant, this leads to

the creation of different versions of the form template

variant.

Forms

Maintenance


Forms

Versions

Not Published

▪ Form template that has been adapted or created either as a copy or by uploading an XDP file. This version can be viewed

and edited by administrators but is not available for use by other users.

Published

▪ Form template available for general use when users are outputting documents from the system. The initial templates that

are delivered by SAP or partners typically have the status Published and are ready for productive use. Administrators can

publish new or adapted form templates.

Archived

▪ This status is applied to versions that have become outdated due to more recent upgrades or customizing.

Deleted

▪ A form template that has been deleted. You can reinstate a deleted form template by reverting to the last archived version.

New

▪ When a template that was initially provided by SAP is upgraded as part of a system upgrade, if any customized version of

the template exists that is already published, then the upgrade template variant version is given the status New. This

ensures that the custom version is not overwritten by SAP or partner upgrades.


▪ View a Form Template

▪ Copy a Form Template

▪ Edit a Form Template

▪ Download a Form Template Variant

▪ Upload a Form Template Variant

▪ Publish a Form Template Variant

▪ Create an E-mail Template

▪ Delete an E-mail Template

▪ Maintain E-mail Subject

▪ Maintain Document Name

▪ Maintain Attachment Prefix

▪ Change the Master Template Usage of a Template

▪ Edit the Name and Description of a Form Template

▪ Delete a Form Template Variant

▪ Revert to a Previous Version of a Template

▪ Delete a Not-Published Version of a Template

▪ Reinstate a Deleted Version of a Template

▪ Adapt a Form Template for Sending as an E-mail Attachment

Forms

Scenarios

Thank you.


[email protected]










warranty.














Follow all of SAP









Unit 5: Mashups


▪ Mashups are used to integrate

data from your cloud solution

from SAP with data provided by

an online Web service or

application.

▪ They are light-weighted ways of

composing external RESTful

Web services and integrating

HTML content into the

application UIs.

▪ They consume the business

data mainly via UI out-ports and

write data back to UI in-ports.

Mashups

Introduction

Integration: Type of Mashup Components

External Browser Window

UX-Component

Field

Link List

Menu

Pane

Pane Embedded

Component Pane

Service List

Dark Mashup

Component

WS

External Mashup

Component

Internal

Mashup

Component

In-Ports

Out-Ports


Creating Mashups for Your Organization

The administrator can create new URL, HTML, or data mashups based on a mashup category provided by

SAP. Depending on your solution, preconfigured mashup Web services are provided, which the administrator

can use to create data and HTML mashups. To display them, go to Application and User Management >>

Business Flexibility >> Mashup Web Services.

How to Access Mashups

Once a mashup has been activated and made visible on screens, you can access it in the following ways:

▪ A mashup can be displayed as an embedded screen.

▪ You can click a link on the screen.

▪ You can click Web Services and choose the mashup.

▪ You can use Enterprise Search and access external search providers that are integrated there

Mashups

Access/Creation


▪ A few preconfigured mashups are provided in SAP Business ByDesign.

▪ Your organization can procure mashups from SAP Store. These mashup partner solutions are provided by

SAP partners.

▪ The administrator can create mashups for your organization.

Some preconfigured mashups for Web services are provided in SAP Business ByDesign:

Mashup Name Mashup Type Mashup Category Port Binding

SAP (sap.com) URL Mashup News & Reference Search Provider

SAP Business ByDesign Community

(sap.com)

URL Mashup News & Reference Search Provider

Embedded Map (bing.com) Custom Mashup Location & Travel Web Map

Embedded Route (bing.com) Custom Mashup Location & Travel Route Planner

Sales Intelligence for Accounts

(insideview.com)

HTML Mashup Business & Finance InsideView Account

Information

Mashups

Access


Combines and displays data from

both internal and external sources.

.

A mashup that has been created as

an add-on solution by SAP.

A mashup that embeds an HTML or

JavaScript-based Web page directly

on a screen.

Sends data from SAP ByD to the URL of

an online service provider.

URL Mashup

HTML Mashup

Data Mashup

Custom Mashup

Mashups

Types


OfferingMashUpsAdditional Information


Blog:

https://blogs.sap.com/2016/03/11/byd-account-overview-with-google-maps-mashup/

https://blogs.sap.com/2016/03/11/byd-account-overview-with-google-maps-mashup/

Thank you.


[email protected]










warranty.














Follow all of SAP









Unit 6: SAP Cloud Applications Studio


▪ SAP Cloud Applications Studio allows SAP

partners, resellers, and customers to work

with the same entities that SAP uses in the

core development of its cloud solutions and

to develop solution capabilities that have the

same look and feel as the SAP standard

cloud solutions

▪ The development tools provided are

presented in an integrated development

environment (IDE) based on Microsoft Visual

Studio

SAP Cloud Applications Studio

Introduction

▪ Using SAP Cloud Applications Studio, you can develop, deploy, and test specific add-on functionality.

Furthermore, you can create and integrate new business content, services, and user interfaces to provide

complete micro-vertical business solutions.


Integrated Development Environment

Model-Based Development

Lightweight Scripting Language

Integration with Services

Designer for Desktop and Mobile

UI

Translation Support

E2E Software Lifecycle

Management

Cloud Readiness


Features


Use our powerful cloud platform providing a rich set of standard business objects and

benefit from the speed of reuse with SAP Cloud Applications Studio.

Benefit from the use of a modern

Software Development Kit

Leverage a solid infrastructure in the cloud with mobile

applications support

Adapt and expand the solution

capabilities of SAP Business ByDesign


Advantages

Thank you.


[email protected]










warranty.














Follow all of SAP








week 3: business flexibility unit 1: introduction: why

Documents