Implementation considerations for SAP

Business One Cloud

SAP Business One Cloud Landscape Workshop
Section Objectives

This section of the course will enable you to:

Consider options and limitations when implementing in the cloud

Work with the SAP Business One Cloud trial and reseller
processes

Explore the customer engagement lifecycle

© 2013 SAP AG. All rights reserved. 2

Introduction

Although implementation of SAP Business One customers in the cloud can

be largely carried out in the same way as an on-premise implementation, the
question we should pose ourselves is, do we want to?

We should consider two things:

• What tools/software/add-ons do we normally use in an implementation and are
there any restrictions on their use in a cloud environment?
• Do we want to approach cloud customers in the same way as on-premise ones,
or is this an opportunity to streamline an implementation to make it more “on-
demand” from a customer’s perspective?

© 2013 SAP AG. All rights reserved. 3

Workshop Discussion

Discuss

1. Which tools/add-ons/additional software packages are currently used in

your SAP Business One implementations?

© 2013 SAP AG. All rights reserved. 4

Demonstration

Demonstrate how to make SAP Business One applications such as DTW

available in the SAP Business One Cloud landscape

© 2013 SAP AG. All rights reserved. 5

Implementation Limitations (SAP Business One)

Note: 1856036 - Unsupported SAP Business One 8.82 Components in SAP

Business One Cloud 1.0
The following SAP Business One 8.82 components are not supported in SAP
Business One Cloud 1.0:
• SAP Business One DI Server
• Microsoft Outlook Integration add-on

Note: 1855972 - Unsupported SAP Business One 9.0 Components in SAP

Business One Cloud 1.0
The following SAP Business One 9.0 components are not supported in SAP
Business One Cloud 1.0:
• SAP Business One DI Server
• Microsoft Outlook Integration add-on
• Workflow Service
• SAP Business One Client (64 bit) and 64-bit add-ons

© 2013 SAP AG. All rights reserved. 6

Implementation Limitations (SAP Business One)

Note: 1856016 - SAP Business One Cloud 1.0 Office Integration

SAP Business One enables users to export reports and documents to Microsoft Excel and Microsoft Word.
You can work with Microsoft Office in on-demand environments using either of the following methods:

Install Microsoft Office on presentation servers in the cloud.

Integrate a local installation of Microsoft Office into the remote access solution.

For more information about integration Microsoft Office into remote access solutions, see SAP Business
One OnDemand Administrator's Guide.

If Microsoft Office is installed on presentation servers in the cloud, then using it together with SAP Business
One is the same as a typical on-premise installation.

When using Microsoft Office on a local machine, you can store documents in dedicated user storage in the
cloud, edit them on the local machine, and then save them back in the cloud. In SAP Business One, when
you export a document, it is opened in the local version of Microsoft Office.

When using Microsoft Office templates to generate target documents in the SAP Business One client
application or add-ons in on-demand environments, the file generation process may be handled by a locally
installed version of Microsoft Office. For more information, see SAP Business One OnDemand
Administrator's Guide.

© 2013 SAP AG. All rights reserved. 7

Using Solution Packager

In a SAP Business One Cloud environment Solution Packager provides the

ability to:
• Develop tailored solutions for customer categories, industries etc.
• Rapidly deploy pre-configured SAP Business One Cloud tenants to customers
• Increase repeatability and accelerate volume business
• Decrease implementation time
• Sell more, implement less!

SAP Business One Solution Packager can package:

• Administration settings
• Document and report layouts
• UDT, UDF, Queries, Alerts
• Users and Authorizations

Further information on Solution Packager is available on the Channel Partner

Portal
© 2013 SAP AG. All rights reserved. 8
Configure the SAP Business One Mobile Application

To configure the SAP Business One Mobile Application first:

• Ensure that the SAP Business One Integration Framework has been installed and
deployed correctly (see note 1618978 for troubleshooting)
• Each user that will use the mobile solution has been assigned a B1i license.

In SAP Business One:

• Enable a user to access the mobile solution has their user record updated with the
correct information
• Important – Make sure you specify a password for the user.
• Users can be emailed the required connection information directly from SAP
Business One
On the iOS device:
• Install the SAP Business One mobile application
• Configure the settings for the application

Troubleshooting information available in note 1840117

© 2013 SAP AG. All rights reserved. 9

User Local Devices and Resources in the Cloud

To complete and enhance the user experience we need to give the users the
ability to access their local devices and resources, e.g.:
• Print at their chosen printer
• Transfer files to and from the cloud

To enable/disable the redirection of local devices and resources:

• On the Session host server open Remote Desktop Configuration
• Select Properties under Connections
• In Properties open the Client Settings tab
• Under Redirection, select to enable/disable the redirection of the device or
resource

This can also be done by Group Policy Settings, which is desirable given the
number of Session Hosts potentially available in the landscape

Remember to provide education for users on how to use these settings

© 2013 SAP AG. All rights reserved. 10

Demonstration

Demonstration of where to set the local devices and resources redirection

© 2013 SAP AG. All rights reserved. 11

The Trial Process

SAP Business One Cloud offers the possibility of giving prospects access to
an SAP Business One Cloud trial tenant at no SAP license cost
• Access is controlled through the SAP Business One Cloud Control Center
• Trial access defaults to 30 days but can be configured at any duration up to 90
days

The SAP Business One Cloud User Access Portal template contains built in
functionality for a prospect to request a trial. A cloud controller can then:
• Reject the request
• Approve the request and complete the wizard to create a trial tenant.

© 2013 SAP AG. All rights reserved. 12

Exercise

Request a trial and provision a trial tenant before accessing the tenant as the
trial user.

© 2013 SAP AG. All rights reserved. 13

Reseller Operators

An operator assigned to a reseller can:

• Create, edit and delete customers
• Add users to and remove users from customers and tenants
• Create, edit, duplicate and delete tenants
• Assign extensions to tenants
• Import license files
• View information about service units assigned to them

When you create a reseller you can specify the following:

• The service units they are assigned to
• Basic authorizations:
• Create tenant, Upgrade tenant, Create customer
• If a reseller is not authorized to perform an operation a request is sent to the Cloud
Control Center operators

© 2013 SAP AG. All rights reserved. 14

Exercise

Create a Reseller and a Reseller Operator and test the various settings
available for them

© 2013 SAP AG. All rights reserved. 15

The Customer Engagement Lifecycle

Demand
Generation

Lifecycle
Trial
Management

Operation & Customer

Support Acquisition

Go-live Implementation

© 2013 SAP AG. All rights reserved. 16

Group Exercise: The Customer Engagement Lifecycle

Discuss the tasks in the Customer Engagement Lifecycle:

1. Place them in the correct categories

2. Discuss how a cloud implementation could affect the task

3. Add any additional ones that come up in discussion

© 2013 SAP AG. All rights reserved. 17

Summary

In this section we have:

Considered the options and limitations when implementing in the

cloud

Worked with the SAP Business One Cloud trial and reseller
processes

Discussed the customer engagement lifecycle

© 2013 SAP AG. All rights reserved. 18

© 2013 SAP AG. 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 AG. The information contained herein may be
changed without prior notice.
Some software products marketed by SAP AG and its distributors contain proprietary
software components of other software vendors.
Microsoft, Windows, Excel, Outlook, PowerPoint, Silverlight, and Visual Studio are
registered trademarks of Microsoft Corporation.
IBM, DB2, DB2 Universal Database, System i, System i5, System p, System p5, System x,
System z, System z10, z10, z/VM, z/OS, OS/390, zEnterprise, PowerVM, Power
Architecture, Power Systems, POWER7, POWER6+, POWER6, POWER, PowerHA,
pureScale, PowerPC, BladeCenter, System Storage, Storwize, XIV, GPFS, HACMP,
RETAIN, DB2 Connect, RACF, Redbooks, OS/2, AIX, Intelligent Miner, WebSphere, Tivoli,
Informix, and Smarter Planet are trademarks or registered trademarks of IBM Corporation.
Linux is the registered trademark of Linus Torvalds in the United States and other countries.
Adobe, the Adobe logo, Acrobat, PostScript, and Reader are trademarks or registered
trademarks of Adobe Systems Incorporated in the United States and other countries.
Oracle and Java are registered trademarks of Oracle and its affiliates.
UNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.
Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin
are trademarks or registered trademarks of Citrix Systems Inc.
HTML, XML, XHTML, and W3C are trademarks or registered trademarks of W3C®,
World Wide Web Consortium, Massachusetts Institute of Technology.
Apple, App Store, iBooks, iPad, iPhone, iPhoto, iPod, iTunes, Multi-Touch, Objective-C,
Retina, Safari, Siri, and Xcode are trademarks or registered trademarks of Apple Inc.
IOS is a registered trademark of Cisco Systems Inc.
RIM, BlackBerry, BBM, BlackBerry Curve, BlackBerry Bold, BlackBerry Pearl, BlackBerry
Torch, BlackBerry Storm, BlackBerry Storm2, BlackBerry PlayBook, and BlackBerry App
World are trademarks or registered trademarks of Research in Motion Limited.
© 2013 SAP AG. All rights reserved.
Google App Engine, Google Apps, Google Checkout, Google Data API, Google Maps,
Google Mobile Ads, Google Mobile Updater, Google Mobile, Google Store, Google Sync,
Google Updater, Google Voice, Google Mail, Gmail, YouTube, Dalvik and Android are
trademarks or registered trademarks of Google Inc.
INTERMEC is a registered trademark of Intermec Technologies Corporation.
Wi-Fi is a registered trademark of Wi-Fi Alliance.
Bluetooth is a registered trademark of Bluetooth SIG Inc.
Motorola is a registered trademark of Motorola Trademark Holdings LLC.
Computop is a registered trademark of Computop Wirtschaftsinformatik GmbH.
SAP, R/3, SAP NetWeaver, Duet, PartnerEdge, ByDesign, SAP BusinessObjects Explorer,
StreamWork, SAP HANA, and other SAP products and services mentioned herein as well
as their respective logos are trademarks or registered trademarks of SAP AG in Germany
and other countries.
Business Objects and the Business Objects logo, BusinessObjects, Crystal Reports, Crystal
Decisions, Web Intelligence, Xcelsius, and other Business Objects products and services
mentioned herein as well as their respective logos are trademarks or registered trademarks
of Business Objects Software Ltd. Business Objects is an SAP company.
Sybase and Adaptive Server, iAnywhere, Sybase 365, SQL Anywhere, and other Sybase
products and services mentioned herein as well as their respective logos are trademarks or
registered trademarks of Sybase Inc. Sybase is an SAP company.
Crossgate, m@gic EDDY, B2B 360°, and B2B 360° Services are registered trademarks
of Crossgate AG in Germany and other countries. Crossgate is an SAP company.
All other product and service names mentioned are the trademarks of their respective
companies. Data contained in this document serves informational purposes only. National
product specifications may vary.
The information in this document is proprietary to SAP. No part of this document may be
reproduced, copied, or transmitted in any form or for any purpose without the express prior
written permission of SAP AG.
19